Map the installed system
A Dematic installation may include equipment, PLCs, local controllers and coordination software. Determine which components remain, which functions change and which documented interfaces are accessible. Equipment branding alone does not define the boundary.
ABNET WCS can operate with Dematic equipment. Verify access rights, documentation, dependencies and maintenance responsibilities for each project. Replacing coordination software does not automatically replace embedded logic or safety functions.
Capacity and execution contracts
For each subsystem, specify movement requests, availability and results. Availability may depend on manual mode, faults, occupancy and blocks. If a local controller owns internal routes, WCS should not compete with it.
Keep task and load identifiers traceable at both boundaries. A subsystem may accept one task and execute several stages. Completion must represent the agreed delivery point, not merely an empty internal queue.
Controlled retrofit domains
Where isolation permits, migrate by zone or equipment. Define how to stop new admissions, drain or reconcile open tasks and decide whether return to the previous system is possible.
Rollback after physical movement requires reconciliation. Restoring an old database does not reverse material movement. Preserve logs, configurations and named responsibilities during cutover.
Worked zone migration
Stop new loads entering Z2, finish eligible tasks and record remaining loads at known positions. The new coordinator takes authority only after validating state. Any return must account for movements performed during the trial.
Measure rejection, tracking discrepancies and recovery time as well as throughput. Scope must identify which components are reused or changed; acceptance depends on coherent load-level evidence.
Project verification criteria
- Inventory retained components, interfaces and responsibilities.
- Validate partial tasks and subsystem delivery confirmation.
- Rehearse cutover and rollback with known load positions.
Examples describe engineering decisions and test scenarios. Implemented interfaces, limits and features are defined by each project’s scope.