Compare CARGOES TOS+ (Zodiac) vs Navis N4 TOS for terminal operations across vessel, yard, gate, equipment, automation/integration, deployment, evidence coverage and known research gaps.
TechSelectAI compares CARGOES TOS+ (Zodiac) and Navis N4 TOS using recorded product evidence rather than user-specific recommendation scoring. CARGOES TOS+ (Zodiac) currently has 5 supported, 25 conditional, 58 unknown/not-yet-verified, and 0 not-supported capabilities. Navis N4 TOS currently has 17 supported, 29 conditional, 42 unknown/not-yet-verified, and 0 not-supported capabilities. Known-fact confidence is 97% for CARGOES TOS+ (Zodiac) and 98% for Navis N4 TOS. Latest recorded review or verification activity across the comparison: Sep 19, 2026.
This summary reflects recorded TechSelectAI evidence only. It is separate from buyer-specific Fit Score, Evidence Confidence, TechSelectAI Verified Reviews and Public Review Intelligence. Unknown means not yet verified, not unsupported.
DP World-developed terminal operations suite, historically known as Zodiac, with OPS and optional suite modules spanning billing, auto gate, yard and equipment optimization, automation, RTLS and operational analytics.
Navis N4 terminal operating system from Kaleris for complex container terminals, covering planning, execution, automation integration, optimization, operational visibility and enterprise terminal workflows.
Different coverage percentages can reflect how much TechSelectAI has researched and verified, not which product is better. “Research pending” means the current evidence set is incomplete; it is not evidence that the product lacks the capability.
This summarizes the current evidence record by operational module. Known counts include supported and conditional facts. Pending counts are research gaps, not negative capability findings.
| TOS operational module | CARGOES TOS+ (Zodiac) | Navis N4 TOS |
|---|---|---|
| Billing, Analytics & Operational Control | 5 / 9 known4 conditional · 4 research pending · 0 explicitly unsupported | 9 / 9 known5 conditional · 0 research pending · 0 explicitly unsupported |
| Equipment Dispatch & Automation | 8 / 10 known7 conditional · 2 research pending · 0 explicitly unsupported | 8 / 10 known4 conditional · 2 research pending · 0 explicitly unsupported |
| Gate, Truck & Landside Operations | 4 / 11 known4 conditional · 7 research pending · 0 explicitly unsupported | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported |
| Integration, Data & Ecosystem | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported | 5 / 11 known2 conditional · 6 research pending · 0 explicitly unsupported |
| Platform Architecture, Resilience & Security | 2 / 8 known0 conditional · 6 research pending · 0 explicitly unsupported | 5 / 8 known2 conditional · 3 research pending · 0 explicitly unsupported |
| Rail & Intermodal Operations | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported | 0 / 7 known0 conditional · 7 research pending · 0 explicitly unsupported |
| Reefer, DG & Special Cargo | 0 / 7 known0 conditional · 7 research pending · 0 explicitly unsupported | 2 / 7 known2 conditional · 5 research pending · 0 explicitly unsupported |
| Vessel & Berth Planning | 4 / 11 known4 conditional · 7 research pending · 0 explicitly unsupported | 5 / 11 known4 conditional · 6 research pending · 0 explicitly unsupported |
| Yard Strategy & Inventory | 3 / 11 known3 conditional · 8 research pending · 0 explicitly unsupported | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported |
The links below are the most recently checked verified sources in this comparison dataset. Source recency and confidence describe the research record; they do not establish a universal product ranking.
Status and confidence reflect recorded evidence. Unknown means not yet verified, not unsupported. In the summary above, TechSelectAI labels this state “research pending”.
| Capability | CARGOES TOS+ (Zodiac) | Navis N4 TOS |
|---|---|---|
| Billing / tariff / financial integrationBilling, Analytics & Operational Control | Partially Supported96% confidenceThe CARGOES TOS+ PLUS portfolio lists Billing with user-defined quick invoicing; detailed tariff and finance integration scope is not inferred. | Supported97% confidenceKaleris documents capture of billable terminal events and N4 billing/invoicing; detailed tariff scope depends on implementation. |
| Customer self-service portalBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported96% confidenceA multi-terminal N4 implementation gives customers real-time access to cargo information and online work orders; packaging and portal scope are implementation-dependent. |
| Operational audit historyBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported95% confidenceA live N4 dry-port implementation explicitly cites event monitoring and reporting, but the reviewed public material does not establish a complete immutable audit history for all operational changes. |
| Operational visibility, analytics & KPIsBilling, Analytics & Operational Control | Partially Supported97% confidenceRTLS and FMS modules are documented with BI data analytics and OEE model support; module entitlement is not assumed in every TOS+ deployment. | Supported98% confidenceKaleris documents real-time operational data, productivity KPIs, control-room visibility and decision-support optimization. |
| Productivity & equipment KPIsBilling, Analytics & Operational Control | Partially Supported96% confidenceCARGOES TOS+ RTLS/FMS modules document BI data analytics and OEE model support; broader KPI coverage is not generalized. | Supported97% confidenceKaleris documents N4 real-time operational visibility and performance/productivity insights used to improve terminal execution. |
| Shift / control-room dashboardBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Supported98% confidenceN4 Control Room centralizes operational views and functions used to monitor and maintain terminal operations. |
| Simulation / what-if analysisBilling, Analytics & Operational Control | Supported99% confidenceDP World Southampton documents a simulation-modeling capability where terminal operations and planning results can be viewed in advance and fine-tuned before changes are made in production. | Partially Supported96% confidenceYard Intelligence evaluates alternative scenarios and recommends pre-emptive moves, but it is an advanced optimization suite rather than universal base-N4 functionality. |
| Storage, tariff & service billingBilling, Analytics & Operational Control | Partially Supported95% confidenceBilling and quick invoicing are explicit, but public evidence does not establish full storage, tariff and event-rating depth. | Partially Supported97% confidenceN4 captures billable events and invoices and supports granular billable tasks, but the reviewed evidence does not establish universal storage/tariff configuration depth for every deployment. |
| Volume / workload forecastingBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported96% confidenceYard Intelligence anticipates congestion and yard imbalances hours in advance; broader volume/resource-demand forecasting is not inferred beyond the documented yard scope. |
| AGV / ASC automated-equipment integrationEquipment Dispatch & Automation | Partially Supported97% confidenceYard Crane Automation explicitly integrates ARMG and ASC automation systems; AGV support is not inferred where it is not stated. | Supported98% confidenceKaleris states N4 automation supports automated stacking cranes, AGVs and auto-trucks and coordinates automated yard, transport, quay and gate execution through ECS integration. |
| Equipment dispatch & controlEquipment Dispatch & Automation | Partially Supported98% confidenceSmart Dispatcher and Smart Yard Crane Scheduler provide dispatch and equipment-planning functions as named CARGOES TOS+ suite components rather than universal core-OPS entitlement. | Supported99% confidenceKaleris documents PrimeRoute, RTG/RMG optimization and VMT workflows for terminal handling equipment dispatch and execution. |
| Equipment position trackingEquipment Dispatch & Automation | Partially Supported97% confidenceRTLS is a named TOS+ component integrated with the TOS; exact positioning technologies and entitlement depend on implementation. | Supported98% confidenceN4 Control Room visualizes where containers, cranes and trucks are in the yard, providing equipment/location visibility for operational control. |
| Equipment status & downtime awarenessEquipment Dispatch & Automation | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Job pooling & dispatch optimizationEquipment Dispatch & Automation | Partially Supported99% confidenceSmart Dispatcher explicitly supports tractor pooling and travelling-distance setup, but it is a named suite component rather than universal base OPS entitlement. | Partially Supported98% confidenceKaleris Advanced Optimization continuously evaluates crane, truck and yard tasks to determine the next best move; these optimization products complement N4 and are not assumed base entitlement. |
| Quay crane job executionEquipment Dispatch & Automation | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| RTG / RMG dispatch & work queuesEquipment Dispatch & Automation | Partially Supported96% confidenceSmart Yard Crane Scheduler provides auto yard planning and dynamic CHE zoning, but the public material does not establish identical RTG/RMG dispatch depth for every implementation. | Partially Supported99% confidenceKaleris RTG Optimization and N4 resource-planning workflows optimize yard-crane work, but RTG Optimization is an advanced add-on rather than assumed in every N4 deployment. |
| Terminal automation / ECS integrationEquipment Dispatch & Automation | Supported99% confidenceDP World explicitly documents integration with real-time systems and terminal automation, including RTLS, ARMG/ASC automation and STS automation integrations. | Supported99% confidenceKaleris documents N4 coordination of automated yard, transport, quay and gate operations through ECS integration for semi- and fully automated terminals. |
| Terminal tractor / straddle dispatchEquipment Dispatch & Automation | Partially Supported96% confidenceSmart Dispatcher explicitly includes tractor pooling and travel-distance setup; straddle-carrier support is not inferred from tractor evidence. | Partially Supported98% confidenceTerminal Truck Optimization and PrimeRoute optimize terminal-truck dispatch using N4 data; straddle-carrier-specific dispatch depth is not generalized from truck evidence. |
| VMT mobile work instructionsEquipment Dispatch & Automation | Partially Supported98% confidenceDP World Limassol documents equipment operators switching to devices to receive operational instructions; VMT-specific device/platform behavior and universal base entitlement are not separately established. | Partially Supported98% confidenceKaleris documents an N4 Vehicle Mounted Terminal interface for RTG/RMG drivers, but VMT availability is a specific N4 application/module rather than assumed universal entitlement. |
| Automated gate lane orchestrationGate, Truck & Landside Operations | Partially Supported97% confidenceAGS is explicitly described as an Auto Gate System in the CARGOES TOS+ suite; selected hardware and lane orchestration scope are implementation-dependent. | Partially Supported97% confidenceN4 is documented orchestrating automated gate traffic in a live implementation, but the exact lane-device stack is project-specific and should not be treated as universal native hardware control. |
| Driver identification & authorizationGate, Truck & Landside Operations | Partially Supported98% confidenceThe Batangas CARGOES AVA+ AGS deployment explicitly provides automatic driver identification, but this remains a companion gate-system capability integrated with TOS+. | Not Yet Verified0% confidence |
| Gate & truck operationsGate, Truck & Landside Operations | Partially Supported97% confidenceDP World lists AGS Auto Gate System within the CARGOES TOS+ suite; exact gate functions and lane-device scope depend on the selected suite configuration. | Supported98% confidenceKaleris documents terminal execution across the gate and truck workflows; exact optional optimization modules should be validated for the selected N4 package. |
| Gate customs / line / terminal holdsGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Gate OCR / ANPR integrationGate, Truck & Landside Operations | Partially Supported99% confidenceCARGOES AVA+ AGS at Batangas uses intelligent cameras to capture container numbers and truck license plates, but OCR/LPR capability is provided through the companion Auto Gate solution rather than assumed inside base TOS+ OPS. | Partially Supported96% confidenceA documented N4 terminal implementation integrates automated gate OCR and license-plate recognition. This is evidence of integration, not proof that N4 itself is the native OCR/ANPR engine. |
| Interchange / EIR processingGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Pre-gate & out-gate validationGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Truck appointment integrationGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Truck pre-advice & booking validationGate, Truck & Landside Operations | Not Yet Verified0% confidence | Partially Supported99% confidenceBaltic Container Terminal used N4 to completely incorporate its pre-booking system, establishing proven pre-booking integration without proving that a universal native booking module is included in every N4 deployment. |
| Truck turn-time & queue monitoringGate, Truck & Landside Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceKaleris documents materially reduced gate/truck turn times after N4 implementation at BCT and Caacupe-mi, but the public evidence does not separately establish a universal native queue-management or turn-time analytics module. |
| Weighbridge & VGM workflowsGate, Truck & Landside Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceA live N4 implementation links container weighing systems to N4 for SOLAS VGM compliance. Universal weighbridge hardware/protocol coverage is not inferred. |
| Carrier booking & release integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| CODECO / COARRI EDI messagingIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| COPARN / COPRAR EDI messagingIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| EDI, APIs & external-system integrationIntegration, Data & Ecosystem | Partially Supported94% confidenceDP World documents a robust integration environment for equipment automation and RTLS, but the reviewed public evidence does not enumerate a universal EDI/API catalogue. | Supported99% confidenceKaleris documents robust EDI and API integration for container terminal cargo and external systems/data streams. |
| ERP / finance integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Partially Supported99% confidenceAt Riyadh Dry Port, the SAP Billing module explicitly retrieves data from N4. This proves a live ERP/finance integration while not establishing a universal SAP or ERP connector catalogue. |
| Event / webhook / streaming integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Partially Supported98% confidenceKaleris documents Kafka-based messaging enhancements in N4 4.0, establishing event-streaming capability; webhook support is not separately established by the reviewed public evidence. |
| Gate / OCR subsystem integrationIntegration, Data & Ecosystem | Supported99% confidenceDP World states that CARGOES AVA+ AGS automatically transmits captured gate data to CARGOES TOS+ in real time for seamless processing. | Supported98% confidenceKaleris documents N4 integration with automated gate OCR/license-plate recognition and traffic-flow systems in production terminal operations. |
| MOVINS / BAPLIE vessel messagingIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| PCS / customs / authority integrationIntegration, Data & Ecosystem | Partially Supported96% confidenceDP World documents an ATI Batangas implementation connecting TOS, automated gate systems, customs functions and other CARGOES solutions; this proves a customs-connected implementation but not a universal PCS/customs connector catalogue. | Not Yet Verified0% confidence |
| Reefer monitoring system integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| REST / web-service API integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Supported99% confidenceKaleris explicitly documents robust API integration for N4 with external systems and data streams. |
| Android mobile applicationMobile Access | Not Yet Verified0% confidence | Not Yet Verified0% confidence · native_android_appMobile availability has not yet been verified from first-party evidence. |
| iOS mobile applicationMobile Access | Not Yet Verified0% confidence | Not Yet Verified0% confidence · native_ios_appMobile availability has not yet been verified from first-party evidence. |
| Mobile web accessMobile Access | Not Yet Verified0% confidence | Not Yet Verified0% confidence · mobile_webMobile availability has not yet been verified from first-party evidence. |
| BCP / degraded or offline operationsPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Cloud / on-prem deployment flexibilityPlatform Architecture, Resilience & Security | Supported99% confidenceDP World explicitly states Cargoes P&T can be hosted on-site premises or in the cloud. This does not by itself classify the cloud option as public SaaS. | Supported98% confidenceKaleris explicitly discusses N4 4.0 for existing on-premises customers and cloud adoption, supporting more than one enterprise deployment pattern. |
| Disaster recovery & RPO/RTO controlsPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Partially Supported99% confidenceRiyadh Dry Port documented a backup site, replicated N4 data and successful continuity with no data loss during a major outage, establishing demonstrated DR capability while keeping the implementation architecture project-specific. |
| High availability architecturePlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Partially Supported99% confidenceRiyadh Dry Port operated N4 across primary and secondary data centers with synchronized and replicated data and maintained N4 service through a major power outage; the HA architecture was customer-designed and is not assumed as universal product topology. |
| Multi-terminal / multi-site operationPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Supported98% confidenceTransnet documents operating multiple terminals on a single N4 system while standardizing processes across the terminal network. |
| RBAC / SSO / enterprise identityPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Security & administrative audit loggingPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Throughput & scale for large terminalsPlatform Architecture, Resilience & Security | Supported99% confidenceDP World states the OPS planning and operations module is proven at marine terminals exceeding 10 million TEU per year. | Supported99% confidenceKaleris states N4 4.0 scales to very large container-terminal volumes, including published capacity up to 16 million TEU. |
| Rail / intermodal operationsRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Rail crane work queuesRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Rail interchange eventsRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Rail load / discharge planningRail & Intermodal Operations | Partially Supported95% confidenceThe Southampton implementation documents deadline handling for rail-yard moves, but full train/wagon load-discharge planning is not separately established. | Not Yet Verified0% confidence |
| Rail-yard inventory visibilityRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Train schedule & service managementRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Wagon / consist planningRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Container weight / VGM controlReefer, DG & Special Cargo | Not Yet Verified0% confidence | Partially Supported97% confidenceN4 has documented SOLAS VGM compliance through integration with container weighing systems in a live terminal; exact VGM workflow depth can vary by implementation. |
| Damage & inspection workflowReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Dangerous-goods segregation controlsReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| OOG & special-equipment handlingReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Reefer plug / unplug workflowReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Reefer temperature & alarm integrationReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Reefer, dangerous goods & special cargo controlsReefer, DG & Special Cargo | Not Yet Verified0% confidence | Partially Supported94% confidenceExpert Decking explicitly applies yard-planning logic to reefer containers, but the reviewed N4 evidence does not yet establish full dangerous-goods, OOG and reefer-service control as one universal capability. |
| BAPLIE import / exportVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Berth window & berth allocation schedulingVessel & Berth Planning | Not Yet Verified0% confidence | Partially Supported99% confidenceKaleris documents Berth Window Manager deployed within the N4 optimization stack. Treat it as an optional/advanced planning module rather than universal base-N4 entitlement. |
| Carrier vessel-plan collaborationVessel & Berth Planning | Not Yet Verified0% confidence | Partially Supported95% confidenceA Kaleris N4 implementation documents stronger collaboration with shipping-line stowage coordinators around vessel and crane workplans; universal collaboration tooling is not inferred. |
| Discharge / load sequencingVessel & Berth Planning | Partially Supported97% confidenceThe Southampton implementation documents improved planning of discharge operations, but the public evidence does not establish a complete load/discharge sequencing engine across all deployments. | Not Yet Verified0% confidence |
| Quay crane split planningVessel & Berth Planning | Partially Supported98% confidenceDP World Southampton documents dynamic zoning of quay cranes to improve discharge planning, but exact crane-split algorithms and universal entitlement are not established. | Partially Supported95% confidenceKSSP deployed Quay Commander with N4 and reports optimized vessel and crane workplans; exact crane-split depth and entitlement should be confirmed for the selected package. |
| Quay crane work queuesVessel & Berth Planning | Partially Supported99% confidenceSmart Stow explicitly provides automatic work-queue activation, but Smart Stow is a named CARGOES TOS+ suite component rather than assumed universal base OPS entitlement. | Not Yet Verified0% confidence |
| Restow & vessel rehandle planningVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Stowage & bay planningVessel & Berth Planning | Not Yet Verified0% confidence | Partially Supported99% confidenceN4 Vessel Autostow generates vessel stowage plans, but Autostow is an advanced optimization module and is not assumed in every N4 license. |
| Twin / tandem lift planningVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Vessel & berth planning / executionVessel & Berth Planning | Not Yet Verified0% confidence | Supported99% confidenceKaleris documents vessel planning support including N4 Vessel Autostow and terminal planning across berth, yard and quay workflows. |
| Vessel call lifecycle managementVessel & Berth Planning | Partially Supported96% confidenceDP World describes CARGOES TOS+ as providing real-time information on vessel, gate and yard movements, which establishes vessel-operational visibility but not the full vessel-call workflow, berth-window or stowage scope. | Not Yet Verified0% confidence |
| Automated decking / grounding decisionsYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported99% confidenceExpert Decking automatically distributes containers according to terminal-specific business rules, but Expert Decking is an optional N4 optimization module. |
| Block / stack allocation planningYard Strategy & Inventory | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Configurable yard strategy rulesYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported99% confidenceExpert Decking uses terminal business rules and Yard Intelligence adds strategy-oriented optimization; these capabilities are advanced/optional modules rather than assumed base-N4 entitlement. |
| Empty container inventory managementYard Strategy & Inventory | Partially Supported98% confidenceSmart Stow explicitly supports generic empty loading and Southampton documents empty-container selection, but broader empty-depot and inventory-control depth is not established for every deployment. | Not Yet Verified0% confidence |
| Housekeeping & remarshalling planningYard Strategy & Inventory | Partially Supported97% confidenceSmart Housekeeping is a named CARGOES TOS+ component for efficient yard-container management; it is not assumed as universal base OPS functionality. | Not Yet Verified0% confidence |
| Import / export / prestack segregationYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported97% confidenceExpert Decking explicitly automates decking decisions for import, export, reefer and empty containers; a distinct universal prestack workflow is not inferred. |
| Rehandle minimizationYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported99% confidenceExpert Decking and Yard Intelligence explicitly target rehandle reduction, but the optimization capability depends on optional advanced modules. |
| Yard density & capacity visibilityYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported97% confidenceYard Intelligence forecasts emerging congestion and yard imbalance and supports capacity-oriented decisions, but it is a separate advanced optimization suite for N4 users. |
| Yard holds & exception managementYard Strategy & Inventory | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Yard inventory reconciliationYard Strategy & Inventory | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Yard planning & container inventoryYard Strategy & Inventory | Partially Supported98% confidenceDP World documents Smart Housekeeping and Smart Yard Crane Scheduler within the broader CARGOES TOS+ suite; these named components are not assumed in every OPS configuration. | Supported99% confidenceKaleris documents N4 yard planning, Expert Decking, yard utilization and real-time container/equipment visibility. |
| Deployment model | CARGOES TOS+ (Zodiac) | Navis N4 TOS |
|---|---|---|
| On-premise | Supported99% confidence | Supported99% confidence |
Comparison facts, TechSelectAI analysis, community-derived insights and estimates are kept as separate evidence types. Missing evidence is not treated as proof of non-support.
Adjust the context below. Context Fit is calculated from the same published TechSelectAI evaluation signals and scoring methodology; it does not replace verified product facts or the saved project Decision Matrix.
What could change this recommendation? Confirmed requirements, must-have failures, exact integrations, regional availability, pricing, security requirements, and implementation capacity can materially change fit. For a saved, reproducible decision with custom weights, use a Selection Project.
A feature comparison is not the same as a recommendation. TechSelectAI can evaluate both products against your must-have capabilities, integrations, deployment constraints, security requirements, region and budget.
Evaluate for my company