Configuration and Development: Regardless of the type of project, when we move to the implementation phase we manage the projects the same way. Our Project Team configures the solution to meet your business requirements. While most projects are handled through configuration alone, we love a challenge. If you need something brand new, our developers jump in to work alongside the project team. Throughout this process we keep you informed on progress with regular calls and feedback sessions.
While the core system is being configured, our MIS specialists are busy behind the scenes setting up your dashboards, reports, and any third-party integrations required.
Before you ever see the system, our in-house Quality Assurance (QA) team puts it through its paces with rigorous manual and automated testing. At the end of this process we carry out a detailed workshop with your Project Team to asses if any more configuration work is required before we move onto training and UAT.
Implementation: Before training begins, we deploy the system onto your own dedicated EDP Cloud Environment. We then train key members of your Project Team over a series of sessions, between which they can explore the system in their own time. At this point we only activate the base system subscription (which covers a project team of up to 10 users), remaining user subscriptions only need to be activated as the wider team is trained by your project team.
Our Project Team are on hand to assist throughout the User Acceptance Testing (UAT) process. This process is also iterative, as your team come across things that are not quite right, we make tweaks and these are tested until your team are satisfied everything works as intended. We will be supporting you throughout this process, helping as needed.
As you near the end of UAT, we will meet with your team to plan the deployment of the solution.
Deployment: We know that switching systems can feel daunting, but there’s no need to worry. We’ve done this many times, and we’ll be right there with a clear plan for:
- Data Conversion: Deciding what data is going to be migrated, refactored and how this is going to be done, for static, historical and open transactional data.
- Data Cleansing: Making sure your new system starts with "clean" information.
- The Big Day: Recommending the best practices for a smooth "cut-over" and helping you manage your legacy data.