Prepare the authority change
Commissioning connects installation, tests, procedures and startup. Name cutover authorization, subsystem owners and stop authority. Old and new software must not command the same resource concurrently.
Record versions, configurations, open tasks and known load positions. Drain or reconcile pending work. Copying records without interpreting state can replay already executed tasks.
Ramp up against evidence
Start with controlled scope and volume. Each stage needs limits for discrepancies, unresolved exceptions and performance. Progress should not follow the clock alone: an unknown load position can justify stopping expansion despite good throughput.
Provide correlated diagnostics and access to WMS, network, PLC and operations owners. Classify incidents by boundary and avoid simultaneous uncoordinated changes.
Rollback after movement
Returning to old software may require translating states and reconciling loads moved after cutover. Restoring a database does not reverse physical actions. Define the last simple return point and the procedure beyond it.
Maintain evidence and version control during urgent fixes. Otherwise the delivered configuration can differ from the tested one.
Worked zone ramp-up
Start zone A with limited destinations. Expand only after identification, confirmations and exceptions stabilize. Tracking discrepancies trigger admission restriction and reconciliation before more routes are enabled.
Handover includes restart, recovery, manual intervention and escalation procedures. Train using project scenarios. Completion should include operational autonomy and accepted outstanding issues, not merely running software.
Project verification criteria
- Assign command authority throughout cutover.
- Define advance, stop and rollback criteria.
- Train reconciliation and recovery before ending startup support.
Examples describe engineering decisions and test scenarios. Implemented interfaces, limits and features are defined by each project’s scope.