An eDOCS DM audit is made to provide a technical overview on the current installation. We do that to ensure the system can manage the upgrade. Outcome with needed details for the migration + a complete plan for migration.
2. BUILD TEST ENVIRONMENT
We will test everything before the final upgrade takes place. To make sure the upgrade can be done with as little hassles as possible for the company. Outcome with result of test protocol, adjusted plan and migration schedule.
3. MIGRATE TEST ENVIRONMENT
During this phase, thorough testing and control are performed and new eDOCS features are installed and configured. Outcome with result of test protocol, adjusted plan and migration schedule.
We deliver MSI package for the distribution system and run test protocols. Outcome with result of test protocol, adjusted plan and migration schedule.
5. MIGRATE PRODUCTION
Newest version of eDOCS DM are being installed and tested. After the customer's approval, status and in-depth documentation are stated. Outcome with Post migration “eDOCS DM test protocol”, status and documentation.
6. PROJECT EVALUATION
Last step is a thorough evaluation to make sure that all areas of the upgrade project were successfully covered.
We have an holistic approach to the upgrade project. It's not only about technical issues. User satisfaction and how accessible they find the system and it's features is also very important. 'Cause if you buy a solution but don't use it, what's the point then? We want our customers to get the most out of what we deliver.
Any change deemed necessary to do in accordance to the original agreement of the eDOCS project, is always cleared between the parties involved before it is effected. It may be information about encountered challenges in the system, servers etc.
In every upgrade project we work after PRINCE2 principles. It's a structured project management method that helps keeping track of all stages and costs.