Flow assumptions · interface ownership · acceptance evidence
Simulation LabDefine a Site Assessment
Simulation · emulation · orchestration

Alstef Group Digital Twin Lab turns flow assumptions into traceable tests

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.

Digital twin laboratory for warehouse automation
Input data contract

The model begins with named files and quality findings

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.

Demand

Orders and replenishment

Timestamped lines, quantities, priorities, release rules and cancellations.

Inventory

SKU and load state

Velocity class, location eligibility, unit geometry and handling constraints.

Resources

Capacity and calendars

Travel, transfer and service times with shift and planned-downtime calendars.

Controls

States and ownership

Commands, acknowledgements, timeouts, retry behavior and recovery authority.

Simulation scenarios

Test the peak window and the way flow returns

A result includes the environment, method, inputs and observed output—not only a utilization chart.

Baseline

Normal operating day

Warm-up, typical order mix, replenishment and expected resource availability establish the reference.

Peak

Sustained design window

Order lines/hour or units/hour is observed with buffer occupancy, queueing and station balance over the agreed duration.

Disturbance

Selected resource or interface loss

A blocked destination, delayed confirmation or unavailable asset tests containment and graceful degradation.

Recovery

Backlog clearance

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.

SignalWCS.Mission.ReleaseCommand issued
PLCReady → BusyCycle time recorded
FaultDestination blockedRetry limit reached
OwnerOperator decisionEscalation trace retained
Controls emulation

Exercise state transitions before field devices are available

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.

Acceptance traceability

One requirement, four evidence contexts

Evidence strength increases as the system moves from model to installed operation, while every earlier assumption stays linked.

ContextEvidence availableWhat remains unprovenExit record
SimulationMaterial flow, queues, utilization and scenario KPIs.Actual controls timing and field behavior.Versioned run package.
EmulationInterface states, cycle timing, alarms and restart sequences.Mechanical tolerance and installed network behavior.Signal and event trace.
FATIntegrated software/equipment behavior under controlled conditions.Site geometry, production load and live dependencies.Signed test protocol.
SATInstalled end-to-end flow with agreed loads and disturbances.Performance outside stated conditions or observation period.Acceptance and open-item register.
Technical boundaries: throughput is scenario-specific; system availability changes with the downtime definition; model accuracy depends on source-data completeness; software interfaces remain version-dependent; functional-safety claims require the applicable design and validation evidence. Price comparisons are not offered because scope, controls ownership, site work and acceptance duration vary by project.
Prepare a reproducible first run

Send the data dictionary and the exception list

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.

  • Source-file owner, date, unit and scope
  • Normal, peak and disturbed scenario definitions
  • WMS/WCS/WES/PLC signal and ownership matrix
  • FAT/SAT requirements and evidence format

Request a Digital Twin Lab review

Please enter your name.
Please enter a valid work email.
Please describe the project boundary.