Orpington's ERP Go Live Readiness Checklist
O R P I N G T O N T E C H N O L O G I E S
☐
Every interface to and from the ERP has been tested end-to-end, not only tested in
isolation.
☐
Integrations have been tested at realistic production data volumes, not sample-sized test
data.
☐
Error-handling and retry behavior for failed integration calls has been tested, not just the
success path.
☐
Middleware, API gateways or EDI connections have documented, tested failover
procedures.
☐
Timing and sequencing dependencies between integrations are documented and tested,
not assumed.
☐
Third-party vendors or partners connected via integration have been included in test
cycles.
☐
Monitoring and alerting for integration failures is live before go-live, not added afterward.
☐
A named technical owner exists for each integration, reachable during cutover weekend.
6. CUTOVER AND ROLLBACK PLANNING
8 points
☐
A detailed, hour-by-hour cutover runbook exists and has been walked through by the full
team.
☐
Specific go/no-go checkpoints are defined during cutover, not just at the start.
☐
A documented rollback plan exists, including the criteria that trigger it and who is
authorized to call it.
☐
A defined post-go-live stabilization period exists before legacy systems are
decommissioned.
☐
Communication to end users and external partners about the cutover schedule has gone
out with adequate notice.
☐
Hypercare support staffing (extended hours, on-site presence) is arranged for the first
weeks after go-live.
☐
Backup and disaster-recovery procedures for the new production environment have been
tested, not just documented.
☐
A lessons-learned review is scheduled for after stabilization, with a mechanism to act on
the findings.
The ERP Go-Live Readiness Checklist | Page
4
of
5