Orders and replenishment
Timestamped lines, quantities, priorities, release rules and cancellations.
The lab connects demand data, physical resources and control behavior so reviewers can see what a result depends on, reproduce a run and carry accepted cases into FAT and SAT.

Every input receives an owner, extraction time, scope, unit and version. Missing or inconsistent fields remain visible in a quality log; they are not silently filled with favorable assumptions.
Demand data typically includes SKU velocity, order lines, release waves, replenishment and cutoff behavior. Physical data includes load dimensions, rated load in kg, resource geometry, aisle clear width in mm and buffer locations. Control data identifies WMS, WCS, WES, PLC and fleet-management interfaces.
Timestamped lines, quantities, priorities, release rules and cancellations.
Velocity class, location eligibility, unit geometry and handling constraints.
Travel, transfer and service times with shift and planned-downtime calendars.
Commands, acknowledgements, timeouts, retry behavior and recovery authority.
A result includes the environment, method, inputs and observed output—not only a utilization chart.
Warm-up, typical order mix, replenishment and expected resource availability establish the reference.
Order lines/hour or units/hour is observed with buffer occupancy, queueing and station balance over the agreed duration.
A blocked destination, delayed confirmation or unavailable asset tests containment and graceful degradation.
Time to stable flow, residual queue and manual intervention are measured after service returns.
Reproducible path: retain source files and model version → record random seeds or deterministic schedules → execute the run identifier → export event and KPI traces → compare observed behavior with the signed scenario definition.
Virtual equipment responses connect to PLC or software under test through the defined OPC UA, fieldbus or API boundary. Nominal sequences are paired with late confirmations, duplicates, lost messages, blocked transfers and controlled restart.
Emulation has limits: it cannot duplicate every sensor failure, network condition, mechanical tolerance or operator action. Those limitations are documented, and installed SAT cases target the remaining risk.
Evidence strength increases as the system moves from model to installed operation, while every earlier assumption stays linked.
| Context | Evidence available | What remains unproven | Exit record |
|---|---|---|---|
| Simulation | Material flow, queues, utilization and scenario KPIs. | Actual controls timing and field behavior. | Versioned run package. |
| Emulation | Interface states, cycle timing, alarms and restart sequences. | Mechanical tolerance and installed network behavior. | Signal and event trace. |
| FAT | Integrated software/equipment behavior under controlled conditions. | Site geometry, production load and live dependencies. | Signed test protocol. |
| SAT | Installed end-to-end flow with agreed loads and disturbances. | Performance outside stated conditions or observation period. | Acceptance and open-item register. |
Include sample orders, load units, resource calendars, interface states and the recovery behavior that matters to operations. Unknowns can remain flagged for controlled sensitivity tests.