Help ensure a successful implementation by tapping into the expertise and experience that eCheck has acquired the understanding of standardizing processes.
Launch methodology PUBLIC
eCheck Launch is the methodology that ensures a successful eCheck ByDesign implementation by prescribing the implementation activities and the resulting deliverables.
eCheck Launch methodology ensures that the solution will be delivered on time and will meet all the agreed requirements. This process specifically supports eCheck cloud-based solutions and our partners are prepared to guide customers step-by-step from the first kick-off meeting through the implementationof eCheck ByDesign.
Each phase includes work streams, deliverables, workshops, and quality gate. Let’s take a close look at each of them.
Implementation starts with the Prepare phase which covers work streams and deliverables for:
Project Management, Solution Design and Integration Preparation.
This phase ensures that the project is planned accurately and the implementation scope is determined.
Project Management – starts with handover to the services delivery team where the goals, objectives and success metrics are decided; project planning, kick-off and execution follow.
Solution Design – review best practices and define the configuration to confirm project scope.
Integration Preparation – validate the integration, making sure the security and infrastructure prerequisites have been met.
The Realise phase helps to ensure that the agreed scope s manageable within the system and if needed, the adjustments are made.
Project Management – the project execution deliverable continues to control project status and risk management.
Project Team Enablement – with the project initiation, the project team is preparing for the project and working with the solution.
Solution Configuration – system configuration and testing with the sample customer data.
Solution Walkthrough – demonstration to the customer how the end-to-end processes will look within the system.
The Verify phase ensures the system and people are ready to switch from the previous systems and run their processes in eCheck ByDesign.
Project Management – continues with control of the project statutes and risk management.
Data migration – deliverables go through all phases starting with the data preparation to its further cleansing and testing within the system.
Integration setup – initial testing within the test tenant and then uploading to the production tenant.
Solution Testing – once the testing documentation is prepared, customer fully tests the system with the migrated data.
Cutover planning – identification and scheduling of all the tasks and resources. The Project Verification Quality Gate is complete when all stakeholders agree on the scope to be delivered during the implementation.
The Launch Phase is the final step that ensures successful solution adoption and usage of the solution.
Project Management – customer handover to eCheck Support and the project closure.
Solution Adoption – adoption preparation and execution. Customer uses the change management plan to roll out the new solution within the organization.
Cutover execution – Go-Live with a productive system.
Review integration scenarios for eCheck ByDesign for information on integrating the software with third-party on-premise and cloud solutions.
Consult the custom data integration guide for eCheck ByDesign for an overview of the architecture options needed to merge data from your legacy systems.
Access the technical connectivity guide for on-demand, on-premise, and hybrid applications to learn how to connect eCheck ByDesign to your existing apps.
See how Web service APIs simplify integration with eCheck ByDesign with secure remote access to data and processes based on standards such as SOAP and WSDL.
See how Web service APIs simplify integration with eCheck ByDesign with secure remote access to data and processes based on standards such as SOAP and WSDL.
Continuous release cycles may contain new business functionality as well as error corrections. In-between releases contain corrections for issues are continuously provided through fixes and patches. Critical issues are resolved through hot fixes. Other important issues are addressed through a bi-weekly collection of hot fixes.