gocompliance Migration Strategy
1. System Provisioning: We assist clients in coordinating with cloud ops to provide the appropriate cloud environments for non-production and production environments.
2. Pre-implementation training: Prior to having migration workshops, we have found that gocompliance training for business process owners who would be making decisions about migration to the cloud results in much better input and decisions from business process owners.
Our Subject Matter Expert (SME) facilitates workshops that are attended by relevant process area owners. The objective of the workshops is to collaboratively determine how the client’s current processes can be optimized and mapped to gocompliance. After the workshops, our team documents the migration plan of the system and gets it approved by the client.
Our proven methodology for gathering requirements from different business stakeholders includes:
A series of workshops are held with the appropriate business users.
Each workshop covers a specific topic so that the relevant people may be included
The topics are refined with examples and the users are led through the topics with detailed discussions about requirements and nice-to-haves.
Also, if the customer is already using a compliance system, we include the current configuration and business processes in the discussions to identify what is working and what needs to be changed.
4. Multiple conference room pilots: Once we have configured the system, we request key process owners who participated in the migration workshops to test if the configurations have been done properly. In order to keep this step focused, we provide CRP scripts that 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.
5. 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.
6. End User Training: We provide end-user training material to enable you to deliver the training.
7. Go-Live: Usually this activity starts on a Friday afternoon when changes to the legacy system are disabled and complete data extraction, transformation and gocompliance & PLM communication takes place. Once the system is ready, it is made available to key process area teams to validate the system over the weekend to make it available on Monday to end-users. We also complete the delta load of the source system after going live.
8. Post Go-Live support: Although most end-user requests after go-live can be handled by the client’s internal teams by the time the system goes live, our 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 us.
Data Migration Strategy
Steps in Data Migration
1. gocompliance and compliance data are extracted from the customer’s systems. The entities include all information pertaining to items, MPNs, BOM, and AMLs.
2. The extracted compliance data is cleansed, merged, formatted, transformed, as required, and validated by us and the customer according to what is finalized.
3. Conversion reviews are carried out before the data is loaded into gocompliance — reconciliation and validation checks are performed to minimize any discrepancies and possible rejections pointed out in the preceding reviews.
4. Once the compliance data has been verified and merged, it is imported into gocompliance by us using customer-filled templates and the environment is ready to be used by the customer.
5.The ongoing process of pushing data related to compliance statuses of items and MPNs to the customer’s source system is performed by us.