Hangcha Digital Twin Lab with forklift fleet emulation
Simulation · emulation · orchestration

Hangcha Digital Twin Lab

Expose throughput assumptions, traffic timing and recovery paths before the live warehouse becomes the test environment. Models remain useful only when their inputs, simplifications and acceptance links are visible.

Inspect the input contract
Input data contract

A model is bounded by what it represents

The input contract names source, period, owner, unit and treatment for each dataset. Order history is separated from forecast scenarios. Physical travel distance is separated from nominal truck speed. Failure and recovery assumptions sit beside the responsible control layer.

Missing information is not silently replaced by a favorable default. It is marked as an assumption with a sensitivity test, an owner and a date for confirmation so later design changes stay traceable.

Demand

Orders, lines and waves

Timestamped demand, SKU velocity, order size, cutoff logic, cancellations and replenishment.

Physical

Loads and geometry

Rated load, load center, aisle clear width, rack geometry, floor condition and station envelope.

Behavior

Mission and queue rules

Priorities, batching, charging, blocked destinations, retry limits and manual interventions.

Interfaces

States and timing

WMS, WCS, WES, PLC and fleet messages, cycle time, confirmations, timeouts and ownership.

Simulation scenarios

Compare truck decisions across a controlled scenario deck

Every reported output carries the scenario identifier, input revision and observation period. A result is interpreted inside that boundary rather than promoted as a universal system rate.

Baseline

Representative operating day

Tests normal SKU and order distributions, replenishment, breaks and routine aisle variability before peak or failure cases are introduced.

Observe
Pallets/hour, availability, travel, queue time and equipment occupancy
Peak

Sustained demand window

Raises release demand for the defined duration while retaining realistic downstream capacity, separating a burst from stable shipping-window output.

Observe
Buffer occupancy, unserved missions, charger utilization, backlog
Disturbance

Blocked aisle and reduced capacity

Removes a route, transfer point or truck and applies the agreed response so failure isolation and recovery time stay measurable.

Observe
Graceful degradation, reroute delay, recovery time, manual work
Reproduction path: retain the input snapshot, model build, scenario script, random seed where used, run duration and output definition. Re-run after any routing or traffic-rule change that affects acceptance.
WMS / ERPWork demand and inventory intent
WCS / WESRelease, routing and global coordination
Fleet / truck controlMission allocation, traffic and charging
PLC / equipmentPhysical state, interlocks and transfer
Controls emulation

Exercise the handshake before the machinery is available

Emulated devices respond to commands, delay confirmations and inject defined faults so interface behavior can be reviewed ahead of site commissioning. The method is useful for message structure and state transitions; it cannot prove wireless coverage, physical sensor performance or real load stability.

A documented responsibility matrix identifies which layer detects each condition, which layer decides the next state and who authorizes a restart.

  • Environment: versioned software build, interface definition and seed where stochastic routing is used
  • Method: scripted state sequence with expected and observed results for WMS, WCS, WES, PLC and fleet layers
  • Evidence: timestamped message log, issue record and signed disposition linked to FAT/SAT gate IDs
  • Limits: emulation cannot prove wireless coverage, physical sensor performance, floor grade or real load stability under residual capacity stress
Acceptance traceability

Link twin outputs to FAT and SAT evidence

Simulation does not replace physical acceptance. It narrows which residual capacity, traffic and recovery cases must appear in factory and site gates.

Design assumption register

Every twin input that lacks a measured source is tagged with owner, due date and sensitivity. Closed assumptions become part of the RFQ baseline.

FAT mapping

Scenario outputs that depend on truck configuration map to factory checks for residual capacity (kg @ mm), stability, scanner fields and interface handshake cycle time in seconds.

SAT mapping

Site geometry (aisle clear width mm), floor condition, charging parks and live traffic rules are confirmed under the same scenario identifiers. Example envelope (project-approved, not a Hangcha claim): 120-minute nominal duty, then blocked-aisle, charger-loss and host-timeout cases with measured recovery minutes and availability %.

Change control

After any aisle, battery or control-rule change, the twin revision and affected acceptance gates are reopened together.

Twin lab RFQ

Request a Hangcha Digital Twin Lab session

Share load unit, SKU and order profile, peak rate, interfaces and site constraints so the lab can build a bounded scenario deck instead of a decorative animation.

Book a twin review

Lab data checklist

  • Layout and aisle clear widths (mm)
  • Load unit kg @ load-center mm and residual capacity basis
  • Peak window minutes with SKU/order structure and buffer occupancy
  • Traffic and charging rules with expansion boundary
  • WMS / WCS / PLC / fleet ownership matrix
  • Disturbance cases and exception recovery clock