An automated warehouse scene links inbound, outbound and transfer orders, stacker and conveyor tasks, locations and stock, equipment status, exceptions, task detail and messages, so order tracking and equipment location share one view.
Both sides show inbound trend, tasks waiting and in progress, and stacker and conveyor status, so progress and equipment can be compared in one view.
The central 3D rack places shelves, equipment and status labels in the warehouse, so site and office staff can talk about the same location. Capacity is a daily reference.
Task status, equipment error trends and exception messages are shown together as leads to check. When a task is late, the related equipment and location can be checked against the business record.
This page is a desensitized view of a real project. Orders, tasks, materials, locations, stock, equipment IDs, people, times, completion rates and exception counts explain the interface. They are sample or desensitized information, not the customer’s current data, and not a conclusion about go-live, warehouse efficiency or acceptance.
Agree location and equipment codes, stock and batch fields, inbound, outbound and transfer flows, task states and alarm rules, then set what WMS, WCS, PLC and the visualization platform may read or write. The table below lists page content that can be agreed and where it usually comes from.
| Object | Usual source | Page content that can be agreed |
|---|---|---|
| Orders and stock | WMS, ERP, MES, and stock and material master data. | Inbound, outbound, transfer and count orders; quantity, status, completion, priority, handling time, batch and location changes. |
| Execution tasks | WCS, the dispatch service, the task queue and the state machine. | How a business order, a WCS task and an equipment subtask correspond; current step, position, material, carrier, command, feedback, previous and next state, timeline, result and failure reason. |
| Automated equipment | PLC, stacker, conveyor, lift, shuttle and scanner. | Mode, position, load and cycle time; running, idle, offline, fault and communication state shown separately. |
| 3D objects | Warehouse model, BIM or 3D model, object map and coordinates. | Zone, aisle, rack, location, goods, carrier and equipment position; selection, status highlight and task location. |
| Exceptions and messages | Equipment alarms, task timeouts, stock differences, manual interventions and the notification center. | Blocked tasks, location conflicts, scan failures, communication loss and recovery; business notices separated from exceptions, filtered by level, equipment, task and handling state. |
| Operations and reports | Operation logs, task history and the statistics service. | Today’s work, inbound and outbound volume, task completion, capacity use, equipment load and error trend; performance analysis and audit trace as agreed. |
Acceptance checks orders, tasks, equipment, stock and 3D objects one by one. A representative flow checks state sync, task order and exception prompts, then interface logs, site status and test records.
Usually no. The platform can summarize orders, tasks, stock, equipment, alarms and 3D position while WMS, WCS, PLC and the equipment controls remain. Replacing an existing system is a separate decision about interfaces and business boundaries.
Zone, aisle, row, column, level, location and carrier need one coding scheme, synchronized and checked against WMS or WCS results, equipment feedback and counts, with a list of differences.
The 3D page can offer a controlled entry, but the command should go through the WCS or PLC interlock, permission and feedback. The page should not bypass the site control layer for a high-risk action.
Choose representative flows such as inbound, outbound, transfer, exception recovery and manual intervention, and replay them against the order, task, equipment state, location change, alarm, log and 3D object.