Skip to content

Customer Implementation Project Guide

Realtime Despatch Software Ltd

Document Version: 4.0.6

Document Built: 2020-10-12

This document and its content is copyright of Realtime Despatch Software Limited. All rights reserved.
You may not, except with our express written permission, distribute, publish or commercially exploit the content.
Any reproduction of part or all of the contents in any form is prohibited.

After Go Live

After Go-live

By the time the OrderFlow Support Engineer leaves your premises at the end of the Go-Live phase, you will be confidently processing orders, handling stock, and dealing with any on the ground situations that arise. There will need to be a little bit of 'tidying up' before the launch is complete. This takes place during the After Go-live phase.

Project After Go Live

The main main deliverable here is formal completion of the launch phase, which itself will require all remaining launch issues to be resolved.

Deliverables
Resolution of all remaining launch issues
Sign-off on completion of launch phase

Helping

Resolution of Launch Issues

Here we undertake work to resolve any launch issues that were not closed off during Launch Issue Resolution. This will be done via ticket interactions on the Support Portal.

Formal completion of the launch should not take place until all of the Launch Issues have been resolved. In practical terms, this means that all of the issues in the 'Launch' project on the Support Portal will have been closed off.

Data Retention and Removal

During the Project Scoping phase, we would have covered your requirements regarding Data Retention and Removal. This is both to ensure that we are compliant with any Data Protection regulation and best practice, but also to ensure that data does not accumulate on the system in a way that will harm performance or result in excessively long upgrades.

During the immediate post-launch period, we will put these policies into effect.

For more information, please see the Data Retention and Removal Policy.

Addressing Non-launch Issues

As mentioned in the previous section, further non-launch issues may have been identified as Unanticipated Further Requirements. High priority issues in this category, that is, issues are having a significant operational impact, will also be addressed at this point.

Lower priority issues, or issues involving more substantial effort, will not be addressed until after the launch is formally completed.

Customer Sign-off Notes

We like to end the project launch phase with a formal sign-off that launch is complete. This involves an acknowledgement from you the customer that the system meets all of the requirements that are within the scope of the project's launch.

There may be plenty still to do to get the system exactly working the way that you want, but this activity can begin as part of the post-launch effort.

Any significant post-launch activity, including custom feature development or new projects, can be initiated once the completion of the launch has been signed off.