Compare CARGOES TOS+ (Zodiac) vs Tideworks Mainsail for terminal operations across vessel, yard, gate, equipment, automation/integration, deployment, evidence coverage and known research gaps.
TechSelectAI compares CARGOES TOS+ (Zodiac) and Tideworks Mainsail 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. Tideworks Mainsail currently has 10 supported, 35 conditional, 43 unknown/not-yet-verified, and 0 not-supported capabilities. Known-fact confidence is 97% for CARGOES TOS+ (Zodiac) and 97% for Tideworks Mainsail. Latest recorded review or verification activity across the comparison: Sep 20, 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.
Marine terminal operating system for cargo, inventory, vessel activity and gate operations, supported by Tideworks planning, equipment-control, customer-visibility and EDI companion products where selected.
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) | Tideworks Mainsail |
|---|---|---|
| Billing, Analytics & Operational Control | 5 / 9 known4 conditional · 4 research pending · 0 explicitly unsupported | 6 / 9 known2 conditional · 3 research pending · 0 explicitly unsupported |
| Equipment Dispatch & Automation | 8 / 10 known7 conditional · 2 research pending · 0 explicitly unsupported | 6 / 10 known6 conditional · 4 research pending · 0 explicitly unsupported |
| Gate, Truck & Landside Operations | 4 / 11 known4 conditional · 7 research pending · 0 explicitly unsupported | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported |
| Integration, Data & Ecosystem | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported | 6 / 11 known4 conditional · 5 research pending · 0 explicitly unsupported |
| Platform Architecture, Resilience & Security | 2 / 8 known0 conditional · 6 research pending · 0 explicitly unsupported | 3 / 8 known3 conditional · 5 research pending · 0 explicitly unsupported |
| Rail & Intermodal Operations | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported | 5 / 7 known5 conditional · 2 research pending · 0 explicitly unsupported |
| Reefer, DG & Special Cargo | 0 / 7 known0 conditional · 7 research pending · 0 explicitly unsupported | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported |
| Vessel & Berth Planning | 4 / 11 known4 conditional · 7 research pending · 0 explicitly unsupported | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported |
| Yard Strategy & Inventory | 3 / 11 known3 conditional · 8 research pending · 0 explicitly unsupported | 8 / 11 known7 conditional · 3 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) | Tideworks Mainsail |
|---|---|---|
| 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. | Supported99% confidenceMainsail 10 records revenue-generating events, applies contract rates and generates customer billing while integrating with ERP and CRM systems. |
| Customer self-service portalBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported99% confidenceForecast provides terminal customers with container information, clearance/demurrage status, notifications and online payments, but Forecast is a separate companion customer-service portal rather than base Mainsail functionality. |
| Operational audit historyBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| 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. | Supported97% confidenceTideworks documents real-time operational visibility and data-driven planning across the Mainsail terminal platform. |
| 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. | Supported98% confidenceMainsail 10 supports historical reporting, real-time visibility, trending analysis, custom ad-hoc reports and dynamic recap for terminal operational data. |
| Shift / control-room dashboardBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported95% confidenceMainsail 10 provides real-time visibility and highly configurable reporting, but a dedicated shift/control-room dashboard workflow is not separately established. |
| 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. | Not Yet Verified0% confidence |
| 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. | Supported99% confidenceMainsail 10 billing explicitly applies rates and service agreements, creates charges from revenue-generating events, supports configurable invoicing, and Tideworks documents centralized management of billing contracts, rates and tariffs. |
| Volume / workload forecastingBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| 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. | Not Yet Verified0% confidence |
| 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. | Partially Supported95% confidenceTerminal equipment dispatch and control are documented through Tideworks Traffic Control, a companion product integrated with Mainsail. |
| 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. | Partially Supported97% confidenceTraffic Control supports optional DGPS and standardized position-detection integrations, but equipment-position tracking belongs to the companion execution stack and may require external positioning technology. |
| 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 Supported99% confidenceTraffic Control explicitly prioritizes moves and pools equipment against yard, rail, vessel and gate operations; it remains a separate equipment-control companion product. |
| 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 Supported97% confidenceTraffic Control provides electronic equipment dispatch, move prioritization and crane optimization; equipment-dispatch functions are attributed to the companion Traffic Control system, not base Mainsail. |
| 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. | Not Yet Verified0% confidence |
| 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 Supported97% confidenceTraffic Control dispatches work instructions to handling equipment and pools equipment by operational zones; exact truck/straddle configuration depends on the companion execution system deployment. |
| 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% confidenceTraffic Control provides web-deployable mobile clients and touch-screen handling-equipment interfaces for electronic work instructions; this is a Traffic Control companion capability, not native Mainsail mobile execution. |
| 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 Supported99% confidenceGateVision integrates gate video, voice communication and the TOS and centralizes lane processing, but GateVision is a separate companion gate-operations system rather than base Mainsail functionality. |
| 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% confidenceTideworks documents gate operations in Mainsail; advanced gate imaging/processing may use the companion Gate Vision product. |
| 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. | Not Yet Verified0% confidence |
| 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 | Not Yet Verified0% confidence |
| Truck turn-time & queue monitoringGate, Truck & Landside Operations | Not Yet Verified0% confidence | Partially Supported96% confidenceGateVision is designed to process trucks faster and distributes lane calls efficiently, but detailed turn-time measurement and queue analytics are not established as universal Mainsail-native functions. |
| Weighbridge & VGM workflowsGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| 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. | Partially Supported96% confidenceMainsail 10 documents standardized API integration, while managed EDI is delivered through the companion EDI Porter service in current deployments. |
| ERP / finance integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Partially Supported96% confidenceTideworks documents Mainsail integration with third-party ERP systems, but universal finance/ERP connector coverage is not established. |
| Event / webhook / streaming integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Partially Supported99% confidenceMainsail 10 explicitly uses Real-Time Messaging for integration, establishing event/messaging integration; webhook semantics are not separately documented in the reviewed public material. |
| 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. | Supported99% confidenceMainsail 10 explicitly supports OCR and LPR third-party integrations; exact OCR/LPR vendors and project topology remain implementation-specific. |
| 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. | Partially Supported98% confidenceMainsail 10 explicitly supports Port Community System integrations, but customs integration is not separately established by the reviewed current public material. |
| 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% confidenceMainsail 10 explicitly uses RESTful API calls and real-time messaging for third-party integrations, and current cloud deployments document standardized APIs for data exchange. |
| 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 | Supported98% confidence · mobile_webResponsive browser access is verified for Mainsail 10 across a variety of devices; exact small-screen feature parity is not separately documented. Native Android and iOS applications are not inferred. |
| 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. | Not Yet Verified0% confidence |
| Disaster recovery & RPO/RTO controlsPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| High availability architecturePlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Multi-terminal / multi-site operationPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Partially Supported99% confidenceTideworks states Mainsail can scale across multiple terminals, and TOTE operates Mainsail 10 across its Alaska and U.S. mainland terminal network with a unified operational view; the public evidence does not establish a single shared instance or every cross-site administration boundary. |
| RBAC / SSO / enterprise identityPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Partially Supported98% confidenceMainsail 10 explicitly supports granular role-based permissions, but SSO and specific enterprise identity-provider standards are not established in the reviewed Mainsail evidence. |
| 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. | Partially Supported97% confidenceTideworks positions Mainsail as scalable as terminal requirements and throughput grow and as suitable across terminal sizes, but the reviewed public material does not publish a universal Mainsail TEU ceiling. |
| Rail / intermodal operationsRail & Intermodal Operations | Not Yet Verified0% confidence | Partially Supported94% confidenceTideworks documents rail planning through the companion Spinnaker component deployed with Mainsail; do not treat it as a universal core-Mainsail entitlement. |
| 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. | Partially Supported98% confidenceSpinnaker rail planning supports incoming/outgoing train planning, railcar movement and automated railcar stowage; this remains a companion-product boundary. |
| Rail-yard inventory visibilityRail & Intermodal Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceSpinnaker provides real-time terminal inventory visibility together with rail-yard/track planning and railcar movement tools, but a distinct rail-inventory reconciliation workflow is not separately established. |
| Train schedule & service managementRail & Intermodal Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceSpinnaker includes graphical rail planning and schedule visibility, but rail planning belongs to the companion Spinnaker product rather than universal base Mainsail entitlement. |
| Wagon / consist planningRail & Intermodal Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceSpinnaker rail planning can split trains, plan incoming and outgoing trains, move railcars between tracks and automate railcar stowage; this establishes consist/railcar planning at the companion-product level without making it native base Mainsail. |
| Container weight / VGM controlReefer, DG & Special Cargo | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| 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 | Partially Supported98% confidenceMainsail explicitly manages over-dimensional cargo inventory, but dedicated OOG equipment selection, lift planning and special-handling execution are not separately established. |
| 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 | Not Yet Verified0% confidence |
| 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 Supported98% confidenceGraphical berth planning is explicitly delivered through Spinnaker, a companion planning system integrated with Mainsail; it is not assumed as universal core-Mainsail entitlement. |
| Carrier vessel-plan collaborationVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| 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. | Partially Supported99% confidenceSpinnaker automatically sequences discharge containers and calculates efficient load-back sequences; this capability is attributed to the companion planning system, not base Mainsail. |
| 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. | Not Yet Verified0% confidence |
| 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. | Partially Supported96% confidenceSpinnaker can create bay-by-bay worklists and electronic work orders for real-time dispatch, but work-order execution depends on the integrated planning/dispatch stack rather than base Mainsail alone. |
| 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% confidenceSpinnaker provides graphical vessel planning and stowage tools, including automated stowage functions; these are companion-product capabilities rather than universal core Mainsail functionality. |
| Twin / tandem lift planningVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Vessel & berth planning / executionVessel & Berth Planning | Not Yet Verified0% confidence | Partially Supported95% confidenceMainsail manages vessel activity, while full graphical vessel and berth planning is documented through the companion Spinnaker Planning Management System. |
| 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. | Supported98% confidenceMainsail explicitly manages vessel activity as part of its core marine terminal operating system; detailed graphical vessel and berth planning remains a Spinnaker companion-product boundary. |
| Automated decking / grounding decisionsYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported98% confidenceSpinnaker automates container location assignments for grounded or wheeled operations; this is not promoted as native base-Mainsail decking functionality. |
| Block / stack allocation planningYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported98% confidenceSpinnaker automates container location assignments for grounded or wheeled operations and optimizes container positions, but this is a companion planning capability rather than universal core Mainsail entitlement. |
| Configurable yard strategy rulesYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported98% confidenceSpinnaker provides yard planning tools and supports terminal-specific decking strategies; advanced graphical yard-strategy planning is a companion-product capability. |
| 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. | Partially Supported96% confidenceMainsail provides complete container inventory management and explicitly discusses steamship-line empty allotments and excess empty inventory, but release/order and full empty-depot workflow depth are not separately documented. |
| 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 | Not Yet Verified0% confidence |
| Rehandle minimizationYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported98% confidenceSpinnaker explicitly helps avoid costly rehandles and set-asides through optimized yard positioning; it remains a companion-product capability. |
| Yard density & capacity visibilityYard Strategy & Inventory | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Yard holds & exception managementYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported98% confidenceSpinnaker explicitly lets operators control container-placement exceptions and uses automatic set-aside logic, but formal regulatory/customs hold-release workflows remain unverified and the function is a companion planning capability. |
| Yard inventory reconciliationYard Strategy & Inventory | Not Yet Verified0% confidence | Supported98% confidenceMainsail manages cargo and inventory with real-time operational visibility; Tideworks describes active inventory control as tightly coupled with Mainsail, while advanced graphical yard planning remains in Spinnaker. |
| 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. | Partially Supported95% confidenceMainsail manages cargo and inventory, while advanced graphical yard planning is documented with the companion Spinnaker planning system. |
| Deployment model | CARGOES TOS+ (Zodiac) | Tideworks Mainsail |
|---|---|---|
| On-premise | Supported99% confidence | Not recorded |
| Public SaaS | Not recorded | 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