| Operational audit history | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal's container intelligent management explicitly uses container history and configurable reports/search, providing operational-history evidence without establishing a complete immutable audit trail for all terminal changes. |
| Operational visibility, analytics & KPIs | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal includes operation analysis and simulation; richer digital-twin visualization/analytics may use the separate OPUS DigiPort product and is not treated as universally included. |
| Productivity & equipment KPIs | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal includes operation analysis, configurable reports and productivity-oriented decision support, while richer real-time KPI dashboards and digital-twin analytics are documented under the separate OPUS DigiPort product. |
| Shift / control-room dashboard | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | CyberLogitec states that OPUS Terminal provides planning, operation, monitoring and dashboards, but richer real-time visualization and digital-twin analytics are separately associated with OPUS DigiPort and are not attributed to base OPUS Terminal. |
| Simulation / what-if analysis | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal explicitly provides operation simulation for task workload and yard location using automated planning information, including workload estimation by time, block and equipment. |
| Volume / workload forecasting | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal simulation estimates future workload by time, block and equipment, but broader container-volume, labor or resource-demand forecasting is not established; AI prediction functions are documented separately in OPUS DigiPort. |
| AGV / ASC automated-equipment integration | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | CyberLogitec documents OPUS Terminal interfacing automated equipment control systems in projects using AGVs and automated rail-mounted gantry cranes, supporting operational planning and field execution. |
| Equipment dispatch & control | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | OPUS Terminal documents optimized equipment workload execution and unified equipment operations across terminal layouts. |
| Equipment position tracking | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | Real-time container and vehicle location tracking is documented in the DGT implementation, but that deployment also uses TLC and the separate OPUS DigiPort IoT/data platform; native OPUS Terminal-only scope is not assumed. |
| Job pooling & dispatch optimization | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | CyberLogitec states the TLC module optimizes overall terminal workload and equipment/yard work orders; TLC module entitlement is not assumed as universal base OPUS Terminal entitlement. |
| Quay crane job execution | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | Automated-terminal implementations prepare work plans, assign equipment and manage real-time allocation including double-trolley quay cranes; exact QC work-queue entitlement depends on the implemented OPUS/TLC stack. |
| RTG / RMG dispatch & work queues | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the terminal operating model? | CyberLogitec documents ARMGC operations with OPUS Terminal, TLC and the automation stack; RTG/RMG dispatch is therefore evidenced at implementation/module level rather than assumed as identical universal base-product scope. |