Continuous Implementation is Comprised of What Two Phases
Approach
Our robust implementation approach is designed to focus on People, Process, and Technology and to provide a fully integrated solution for Jefferson.
With this approach, Project ASCENT will optimize supply chain and finance processes, implement PeopleSoft tools that enable the business processes, and involve and guide Jefferson's employees through the transition to help them be successful in using the new processes and PeopleSoft.
Project ASCENT is following a phased approach that categorizes People, Process, and Technology implementation activities into five phases by logical sequence and schedule. The project is currently into the Build Phase. The activities within each project phase are described below:
| Phase | What needs to be Accomplished |
| The purpose of this phase is getting the project started, identifying the project team members, and developing a detailed project plan. Initial training is performed, giving the project team a foundation in both the software package and the implementation methodology. The key processes required to monitor and guide the progress of the project are designed and put into place, including status reporting, issue tracking and resolution, scope management and quality assurance. The base technology infrastructure and a "sandbox" environment are also created during this phase. | |
| | |
| The purpose of this phase is to create the detailed design containing the results gathered during requirements collection, confirmation workshops and prototyping efforts. A key component of this phase is the process design and an understanding of the potential changes to Jefferson's workflow requirements. It is during this phase that a common 'detailed' understanding of how we will run our business, using the selected software package, will be developed. To support the process design, design involving technical components such as hardware, infrastructure, database etc. are also developed. | |
| | |
| The purpose of this phase is to configure and test the business and technical requirements that have been established in the Design Phase. The objectives are to complete configuration of the system, conduct an overall integration test and acceptance test, and release the system for production operation. Additionally, all interfaces, reports, and conversions will be developed and tested, security profiles will be created, and the testing, training and production environments will be established during this phase. | |
| | |
| The purpose of this phase is to prepare for 'go-live' with the implementation and will include final system testing, user training, cutover activities, and formation/enhancement of an internal help desk for support after we 'go-live'. During this phase, all remaining open issues will be addressed. Upon successful completion of this phase, Jefferson will be ready to run on the upgraded system and move on to the next phase of implementation. | |
| | |
| The purpose of this phase is to transition from a pre-production environment to business operations. During this phase, the implementation team transfers responsibilities to the support organization, optimizes overall system performance, and institutes continuous improvement. A successful support organization is critical to the long-term success of the implementation. | |
| | |
Another significant milestone has been achieved by the Project ASCENT team with the completion of the second of five phases – the Design Phase. The design work is vital and will direct the team's efforts during the current Build Phase. Over the next several months, the team will be focused on the critical task of configuring and testing the business and technical requirements that have been established during the Design Phase. The objectives are to complete configuration of the system, conduct an overall integration and acceptance test, and release the system for production. The remaining phases – Deliver and Operate, will prepare end users for process changes and system go-live; and, ultimately transitioning to steady state business operations.
As we chart this new course to transform the way we manage our supply chain, there will be inevitable changes to the way we approach our tasks on a daily basis. An essential element of success for Project ASCENT is the change management strategy we have put in place to involve all stakeholders in a meaningful way and help us all get it right the first time.
Leadership at every level of Jefferson is committed to supporting stakeholders through each stage of this transformation. We plan to fulfill this commitment by providing two way communication, training, and technical support to everyone who will be impacted by these changes.
Our communications will not be solely dependent on high tech channels like email or this website, but will include high touch interactions such as information sessions, road shows, and departmental meetings. We will be communicating with you and not to you.
Building a culture of positive change will not be without challenges; however, we ask that you embrace this. We all play an important role in the implementation of Project ASCENT and the challenges in this process are simply opportunities for all of us to excel.
Source: https://www.jefferson.edu/university/supply_chain/project_ascent/phases.html
0 Response to "Continuous Implementation is Comprised of What Two Phases"
Post a Comment