TechSelectAITOS research hub · Compare products
Original specialist framework · Terminal operations

Terminal Operating System Capability Taxonomy

TechSelectAI uses a domain-specific TOS requirements model to structure terminal software discovery, evidence research, comparison and buyer requirement capture. The current framework contains 85 specialist operational criteria across nine TOS modules, with 3 mobile-access criteria tracked separately.

Taxonomy depth is not evidence depth. A criterion appearing here means it is relevant to TOS evaluation; it does not mean every product supports it. Product support is established separately from evidence and may remain not yet verified.
Cross-category selection criteria

Mobile Access

3 buyer-selectable criteria.

Android mobile application

A vendor-supported Android application is available for the software.

terminal-operating-systems-mobile-android-app

iOS mobile application

A vendor-supported iOS application is available for the software.

terminal-operating-systems-mobile-ios-app

Mobile web access

The software provides vendor-supported mobile web or responsive browser access.

terminal-operating-systems-mobile-web-access
TOS operational module

Vessel & Berth Planning

11 buyer-selectable criteria.

Twin / tandem lift planning

Plan or validate twin, tandem or multi-lift quay operations where equipment and stowage rules allow.

tos-twin-tandem-lift-planning

Quay crane work queues

Generate, prioritize and execute quay-crane work queues and move instructions.

tos-quay-work-queues

Quay crane split planning

Assign vessel work across quay cranes, crane ranges, bays or work areas and manage crane split plans.

tos-quay-crane-split-planning

Discharge / load sequencing

Sequence discharge and load work to coordinate quay operations, yard readiness and vessel constraints.

tos-discharge-load-sequencing

Stowage & bay planning

Plan container positions, bays, decks, holds and stowage constraints for vessel load and discharge operations.

tos-stowage-bay-planning

BAPLIE import / export

Import, validate, update or export BAPLIE bay-plan messages used for vessel planning and exchange.

tos-baplie-import-export
TOS operational module

Yard Strategy & Inventory

11 buyer-selectable criteria.

Yard inventory reconciliation

Reconcile system inventory with physical yard locations, corrections, scans or operational confirmations.

tos-yard-inventory-reconciliation

Rehandle minimization

Optimize stack choices and move sequences to reduce unproductive container rehandles.

tos-rehandle-minimization

Configurable yard strategy rules

Configure yard rules for allocation, segregation, dwell, service priority, equipment type or operational strategy.

tos-yard-strategy-rules
TOS operational module

Gate, Truck & Landside Operations

11 buyer-selectable criteria.

Gate & truck operations

Manage terminal gate transactions, truck processing, interchange and related landside workflows.

tos-gate-truck-operations

Weighbridge & VGM workflows

Integrate weighing, gross-mass capture or VGM-related checks into applicable terminal transactions.

tos-weighbridge-vgm

Interchange / EIR processing

Create and manage equipment interchange, EIR or equivalent receipt/delivery transaction records.

tos-eir-interchange

Gate OCR / ANPR integration

Use or integrate OCR, container recognition and ANPR data for automated or assisted gate processing.

tos-ocr-anpr-gate

Truck appointment integration

Integrate or coordinate truck appointment and time-slot information with terminal gate execution.

tos-truck-appointment-integration
TOS operational module

Rail & Intermodal Operations

7 buyer-selectable criteria.

Rail / intermodal operations

Plan or execute rail and intermodal container movements within supported terminal operations.

tos-rail-operations

Rail interchange events

Capture rail interchange, handoff, arrival, departure and related intermodal operational events.

tos-rail-interchange-events

Rail crane work queues

Generate and execute work queues for rail-mounted or rail-service handling equipment.

tos-rail-crane-work-queues

Rail load / discharge planning

Plan rail discharge, loading and transfer sequences using train, yard and equipment constraints.

tos-rail-load-discharge-planning

Wagon / consist planning

Plan wagon consists, slots, railcars and container assignments for rail loading and discharge.

tos-wagon-consist-planning
TOS operational module

Equipment Dispatch & Automation

10 buyer-selectable criteria.

Equipment dispatch & control

Assign, dispatch, monitor or optimize work for terminal tractors, straddle carriers, quay cranes, RTGs, RMGs or other handling equipment.

tos-equipment-dispatch-control

Equipment position tracking

Use equipment-position or location data to support dispatch, execution, confirmation or optimization.

tos-equipment-position-tracking

VMT mobile work instructions

Deliver work instructions, confirmations and exceptions to vehicle-mounted or operator mobile terminals.

tos-vmt-mobile-work-instructions

Quay crane job execution

Dispatch and execute quay-crane jobs and related move instructions from vessel plans.

tos-qc-work-queues
TOS operational module

Reefer, DG & Special Cargo

7 buyer-selectable criteria.

Container weight / VGM control

Store, validate or use container gross weight and VGM data in operational planning and shipment handling.

tos-vgm-weight-control

Damage & inspection workflow

Record inspections, damage condition, exceptions, photos or related operational cargo/equipment findings.

tos-damage-inspection

OOG & special-equipment handling

Manage out-of-gauge, special-equipment or exceptional-dimension cargo requirements in terminal workflows.

tos-oog-special-equipment

Reefer plug / unplug workflow

Track reefer plug, unplug, connection location, service status or related terminal reefer actions.

tos-reefer-plug-monitoring
TOS operational module

Integration, Data & Ecosystem

11 buyer-selectable criteria.

EDI, APIs & external-system integration

Exchange operational data with carriers, port authorities, customs, gate systems, financial systems or other applications through EDI, APIs or other interfaces.

tos-edi-api-integrations

ERP / finance integration

Exchange customers, services, billable events, invoices or accounting data with ERP and finance systems.

tos-erp-finance-integration

Gate / OCR subsystem integration

Integrate external gate automation, OCR, ANPR, kiosk or access-control subsystems with TOS transactions.

tos-ocr-gate-system-integration

COPARN / COPRAR EDI messaging

Exchange COPARN booking/order and COPRAR load/discharge instruction messages or equivalent carrier EDI.

tos-coparn-coprar
TOS operational module

Billing, Analytics & Operational Control

9 buyer-selectable criteria.

Operational audit history

Preserve traceable history of operational transactions, changes, user actions and execution events.

tos-audit-operational-history

Volume / workload forecasting

Forecast container volume, workload, resource demand, congestion or operational pressure from available planning data.

tos-forecasting-demand

Productivity & equipment KPIs

Measure vessel, crane, yard, gate, rail, equipment and labor productivity using terminal-operational data.

tos-productivity-kpis

Customer self-service portal

Provide customers with approved self-service access to status, bookings, orders, documents, invoices or service requests.

tos-customer-self-service
TOS operational module

Platform Architecture, Resilience & Security

8 buyer-selectable criteria.

RBAC / SSO / enterprise identity

Provide role-based access controls and enterprise authentication or SSO integration for operational and administrative users.

tos-rbac-sso

Cloud / on-prem deployment flexibility

Offer documented deployment choices appropriate to enterprise terminal environments, such as cloud, on-premises or hybrid patterns.

tos-cloud-onprem-flexibility

High availability architecture

Support redundant or clustered application/database architecture designed to reduce service interruption.

tos-high-availability

Terminal Operating System implementation roadmap

A TOS implementation is an operating-model transformation touching vessel, yard, gate, equipment, billing, external interfaces and terminal-control processes. The implementation plan should therefore be built around terminal flows and exception recovery, not only application installation.

Why this matters: software selection is incomplete until the buyer can explain how the chosen solution will be configured, integrated, tested, cut over and supported. This framework is vendor-neutral; exact installation commands and sizing must come from the selected vendor and implementation partner.

1. Operational discovery

Freeze the target operating model before configuration.

  • Map vessel, yard, gate, rail, equipment, reefer, dangerous-goods, billing and exception flows.
  • Baseline truck turn time, yard rehandles, equipment productivity, berth/vessel KPIs and manual interventions.
  • Define future-state responsibilities between operations, planning, IT, finance and external stakeholders.

2. Terminal model configuration

Translate the physical and operational terminal into controlled master data and rules.

  • Model terminal layout, blocks, rows, stacks, lanes, berths, equipment, service definitions and calendars.
  • Define yard strategies, work queues, allocation rules, operational statuses and exception codes.
  • Document which behaviors are standard configuration, custom logic, companion module or external subsystem responsibility.

3. Integration & automation

Prove every operational interface and its recovery path.

  • Catalogue EDI, API, PCS/customs, OCR/ANPR, gate, VBS, reefer, equipment-control, ERP/billing and reporting interfaces.
  • Define idempotency, retries, sequencing, monitoring, reconciliation and manual fallback for each critical interface.
  • Validate automation boundaries and safe degraded modes for equipment or gate subsystems.

4. Data migration & rehearsal

Enter cut-over with reconciled operational data.

  • Classify master, reference, historical and open operational transactions.
  • Run repeatable migration rehearsals with record counts, financial totals and operational reconciliations.
  • Rehearse open vessel calls, yard inventory, appointments, holds, reefer and dangerous-goods states.

5. Operational acceptance

Test the terminal, not just screens.

  • Run representative vessel, gate, yard, equipment and exception scenarios end-to-end.
  • Load-test critical interfaces and peak operational windows.
  • Test TOS/network/subsystem interruption, BCP operation and post-restore reconciliation.

6. Cut-over & stabilization

Make go-live controlled and reversible.

  • Use a minute-by-minute cut-over plan with freeze windows and rollback criteria.
  • Establish command center, vendor escalation, hypercare shifts and KPI monitoring.
  • Compare post-go-live productivity and exception rates against the pre-implementation baseline.

Configuration and architecture questions

Use these questions during discovery, solution design, vendor workshops and implementation governance. They are intended to expose hidden dependencies before they become change requests.

Terminal topology

  • How are blocks, lanes, berths, equipment and operational zones represented?
  • Which changes require downtime, migration or re-planning?
  • How are temporary or overflow areas governed?

Operational rules

  • Which yard strategy, dispatch, planning and exception rules are configurable?
  • How are rules versioned, approved and moved between environments?
  • What operational behavior depends on custom code?

Interfaces

  • Who owns carrier EDI mappings and external certificates?
  • How are duplicates, late messages and replay handled?
  • What is the manual fallback if a gate/OCR/PCS/equipment interface fails?

Resilience

  • What functions remain available during WAN, database or subsystem outages?
  • What RPO/RTO is contractually supported?
  • How is open transactional state reconciled after recovery?

Implementation acceptance tests

A demo can establish product potential; acceptance testing must prove the configured solution in the buyer's operating model. These scenarios should be adapted into formal UAT and operational-readiness evidence.

ScenarioWhat to proveEvidence to retain
Vessel-to-yard flowDischarge/load planning, execution updates, exceptions and inventory accuracy across a representative vessel call.Scenario script, timestamps, inventory reconciliation, interface logs and business sign-off.
Truck gate journeyAppointment/pre-advice, OCR/ANPR, driver/truck/container validation, lane exception and completion.Turn-time record, gate transaction logs, exception evidence and fallback result.
Yard exceptionUnplanned location, blocked equipment, rehandle, hold, reefer or dangerous-goods exception without corrupting inventory.Before/after inventory, work instructions, audit trail and supervisor approval.
Interface outageCritical carrier/PCS/gate/equipment interface unavailable and later restored.Queued/retried messages, reconciliation totals, manual workaround and recovery timing.
BCP recoveryTOS or core infrastructure interruption followed by controlled restoration.RTO/RPO result, BCP transactions, reconciliation evidence and unresolved exceptions.

Implementation evidence pack

Before final acceptance, retain an auditable package covering the following artifacts.

Architecture & scope

  • Approved solution architecture
  • Environment and responsibility matrix
  • Licensed modules / edition scope
  • Security and identity design

Configuration & data

  • Configuration workbook and change history
  • Master-data ownership and migration mapping
  • Interface inventory and reconciliation rules
  • Known limitations and accepted design decisions

Testing & cut-over

  • UAT scenarios, defects and retest evidence
  • Performance/resilience/recovery results
  • Cut-over schedule and rollback criteria
  • Business continuity and manual fallback procedures

Operations

  • Monitoring and alert ownership
  • Backup/recovery and DR runbook
  • Support/escalation matrix and hypercare plan
  • Upgrade/patch governance and periodic access review