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.

Preparing for Launch

Preparing for Launch

With the system functionally complete and the warehouse fully ready, we're now ready to plan for and verify the mechanics of the launch itself.

Up until now we may have had a target launch date in mind. For the first time, we will be able to propose an actual launch date that we can commit to.

Project Prep for Launch

The key deliverable for this phase involves us preparing a tailored Go-Live Launch Plan, which we can use to plan the precise timings around launch, and use during the Go-Live phase to ensure that everything we need to do is completed. However, we also want to dry run the data migration, and ensure that the launch plan is fully signed off before the Go-Live day arrives.

Deliverables
A Go-Live Launch Plan, covering the timing and mechanics of migrating of from your existing system
A Dry Run of the data migration from your existing system
Sign off on the Launch Plan, with an agreed actual Go-live Date and onsite presence

Dry Run of Data Migration

There are two objectives we are looking to satisfy when doing the dry run:

  • we are able to easily and accurately transfer the stock position from the old position into OrderFlow, without having to do a full stock check.
  • we are able to ensure that status of pending orders can be accurately captured to ensure that no order goes through both the old system and OrderFlow, and that no order is 'lost' during the migration.

In both cases, we will be relying on relevant reports and/or control mechanisms being present in the e-Commerce system. The dry run will be to ensure that these can effectively be applied on the day itself.

Go-Live Plan

The detail of this plan will depend on whether you wish the instance of OrderFlow you have been testing to become your live instance, or we need to create a completely new one.

The Go-Live Plan launch plan will cover:

  • All the implementation steps - extracted from our Redmine implementation tickets - required to configure your live instance of OrderFlow.
  • Confirmation of the steps that need to be taken to migrate data from your current Warehouse Management System (WMS) onto OrderFlow, already verified during the Dry Run.
  • The timing of out on site presence to support the launch.
  • The timing of individual steps in the launch sequence.

Once prepared, the Go-Live Plan will be internally reviewed, before being signed off by the customer. We will only present the Go-Live Plan for sign-off from the customer once the dry run of the data migration has been verified.

Sign-off Notes

During the Go-live it is critical that the customer sticks to all elements of the agreed launch sequence. For this reason, we will request formal sign-off on the Go-live Plan.

Note that our scope for making changes will be limited after this point. If unanticipated changes do need to be made during the Go-Live, please be aware that are likely to be cost implications and a potential delay to the actual launch date.