Our team implementation methodology, which is based on our team’s experience of hundreds of successful PLM implementations, is minimally invasive and ensures successful organizational acceptance of the solution. The following are the key steps that GoSaaS proposes for this project:
- Pre-Implementation Training: Prior to having workshops to understand requirements, we have found that product training for business process owners who would be providing the requirements results in much better input and decisions from business process owners.
- Business Process Workshops & Functional Design: GoSaaS’s Subject Matter Expert (SME) facilitate workshops which are attended by relevant process area owners. The objective of the workshops is to collaboratively determine how the client’s process can be optimized and mapped to the system. After the workshops, GoSaaS’s team documents the functional design of the system and gets it approved by the client.
- Configuration: Based on the approved functional design, GoSaaS configures the system.
- Data Migration: Data extraction from legacy systems is discussed during the workshops and are part of the functional design document. GoSaaS provides a format to the client in which the data extracted and cleaned needs to be provided to GoSaaS so it can be loaded into Oracle Cloud PLM. GoSaaS recommends that we test the process with partial data before doing a complete data load to help in identifying any issues which may need to be fixed. This process may need to be repeated. Please see the scope section to determine the number of data loads which are in scope.
- Conference Room Pilot(s) (CRP): Once GoSaaS has configured the system, we request key process owners who participated in the business process workshops to test if the configurations have been done properly. In order to keep this step focused, GoSaaS provides CRP scripts which focus only on the processes being implemented in the system. At each step, the scripts also provide a mechanism to capture feedback. Depending on the feedback from a CRP, this process may be repeated a second time “CRP-2” after making configuration adjustments. The second CRP usually also involves more real data to be available for testing. Please see the scope section to determine if multiple CRPs are included in scope.
- User Acceptance Test (UAT): Once the process owners have validated the system through CRPs, a broader set of users are involved to test the system and provide any feedback that may have been missed.
- End User Training: GoSaaS employs a train-the-trainer approach. At this stage of the project, most process areas become very comfortable with the system and usually these process areas owners conduct the training of the broader team based on material provided by GoSaaS for the system modules being implemented.
- Go-Live: Usually this activity starts on a Friday afternoon when changes to the legacy system are disabled and a complete data extraction, transformation and loading takes place. Once the system is ready, it is made available to key process area teams to validate the system over the weekend make it available on Monday to end users.
- Post Go-Live support: Although most end user requests after go-live can be handled by client’s internal teams by the time the system goes live, GoSaaS’s implementation team remains available for a limited number of days to assist with any requests which may hinder adoption. This type of support can be extended for longer durations or even permanently through a separate maintenance and support contract with GoSaaS.
- Project kick-off meeting: This is a meeting to introduce the project, timelines and expectations with the broader client team.
- Project Status Updates: GoSaaS updates all team members with a project status update each week and holds weekly or bi-weekly meetings with the project steering committee.