Compare Tideworks Mainsail vs Total Soft Bank CATOS for terminal operations across vessel, yard, gate, equipment, automation/integration, deployment, evidence coverage and known research gaps.
TechSelectAI compares Tideworks Mainsail and Total Soft Bank CATOS using recorded product evidence rather than user-specific recommendation scoring. Tideworks Mainsail currently has 10 supported, 35 conditional, 43 unknown/not-yet-verified, and 0 not-supported capabilities. Total Soft Bank CATOS currently has 24 supported, 21 conditional, 43 unknown/not-yet-verified, and 0 not-supported capabilities. Known-fact confidence is 97% for Tideworks Mainsail and 97% for Total Soft Bank CATOS. 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.
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.
Container terminal operating system for berth, ship, rail, gate and yard planning with equipment supervision, optimization, EDI connectivity and operational analytics.
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 | Tideworks Mainsail | Total Soft Bank CATOS |
|---|---|---|
| Billing, Analytics & Operational Control | 6 / 9 known2 conditional · 3 research pending · 0 explicitly unsupported | 5 / 9 known3 conditional · 4 research pending · 0 explicitly unsupported |
| Equipment Dispatch & Automation | 6 / 10 known6 conditional · 4 research pending · 0 explicitly unsupported | 8 / 10 known2 conditional · 2 research pending · 0 explicitly unsupported |
| Gate, Truck & Landside Operations | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported |
| Integration, Data & Ecosystem | 6 / 11 known4 conditional · 5 research pending · 0 explicitly unsupported | 4 / 11 known0 conditional · 7 research pending · 0 explicitly unsupported |
| Platform Architecture, Resilience & Security | 3 / 8 known3 conditional · 5 research pending · 0 explicitly unsupported | 3 / 8 known2 conditional · 5 research pending · 0 explicitly unsupported |
| Rail & Intermodal Operations | 5 / 7 known5 conditional · 2 research pending · 0 explicitly unsupported | 4 / 7 known3 conditional · 3 research pending · 0 explicitly unsupported |
| Reefer, DG & Special Cargo | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported |
| Vessel & Berth Planning | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported | 7 / 11 known4 conditional · 4 research pending · 0 explicitly unsupported |
| Yard Strategy & Inventory | 8 / 11 known7 conditional · 3 research pending · 0 explicitly unsupported | 10 / 11 known4 conditional · 1 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 | Tideworks Mainsail | Total Soft Bank CATOS |
|---|---|---|
| Billing / tariff / financial integrationBilling, Analytics & Operational Control | Supported99% confidenceMainsail 10 records revenue-generating events, applies contract rates and generates customer billing while integrating with ERP and CRM systems. | Not Yet Verified0% confidence |
| Customer self-service portalBilling, Analytics & Operational Control | 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. | Partially Supported93% confidenceCATOS supports ordering through CATOS Web-IP and integrated platforms, but the reviewed public material does not establish the full breadth of customer self-service status, document, invoice or service-request functions. |
| Operational audit historyBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Operational visibility, analytics & KPIsBilling, Analytics & Operational Control | Supported97% confidenceTideworks documents real-time operational visibility and data-driven planning across the Mainsail terminal platform. | Supported98% confidenceCATOS documents digital-twin visualization and an automated real-time analytics dashboard for terminal performance evaluation. |
| Productivity & equipment KPIsBilling, Analytics & Operational Control | Supported98% confidenceMainsail 10 supports historical reporting, real-time visibility, trending analysis, custom ad-hoc reports and dynamic recap for terminal operational data. | Supported99% confidenceCATOS explicitly provides an automated real-time analytic dashboard for performance evaluation and key performance metrics. |
| Shift / control-room dashboardBilling, Analytics & Operational Control | Partially Supported95% confidenceMainsail 10 provides real-time visibility and highly configurable reporting, but a dedicated shift/control-room dashboard workflow is not separately established. | Partially Supported97% confidenceCATOS provides an automated real-time analytic dashboard for facility performance, but a dedicated shift/control-room workflow is not separately established in the reviewed material. |
| Simulation / what-if analysisBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Partially Supported96% confidenceRTGSS uses scheduling simulation, while richer terminal-wide 3D simulation and digital-twin capabilities are separately presented as CATOS Digital Twin; those CATOS DT functions are not assumed as universal base CATOS entitlement. |
| Storage, tariff & service billingBilling, Analytics & Operational Control | 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. | Not Yet Verified0% confidence |
| Volume / workload forecastingBilling, Analytics & Operational Control | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| AGV / ASC automated-equipment integrationEquipment Dispatch & Automation | Not Yet Verified0% confidence | Supported99% confidenceATCSS supervises unmanned transfer cranes and CATOS documents integration with ASC/ARMG, autonomous trucks, STS and ATC infrastructure; exact project equipment mix remains implementation-specific. |
| Equipment dispatch & controlEquipment Dispatch & Automation | Partially Supported95% confidenceTerminal equipment dispatch and control are documented through Tideworks Traffic Control, a companion product integrated with Mainsail. | Supported99% confidenceCATOS documents quay, RTG/RMG, rail and container-handling-equipment supervisor systems for optimized scheduling and work instructions. |
| Equipment position trackingEquipment Dispatch & Automation | 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. | Partially Supported97% confidenceCATOS documents GPS and autonomous-infrastructure integrations and equipment supervisor functions, but exact positioning technology and entitlement depend on the implementation. |
| Equipment status & downtime awarenessEquipment Dispatch & Automation | Not Yet Verified0% confidence | Partially Supported96% confidenceATCSS, RTGSS and CHESS explicitly monitor and supervise unmanned cranes, RTG/RMG and yard trucks/straddle carriers, establishing live equipment-status awareness; maintenance-state and downtime-management depth are not separately documented. |
| Job pooling & dispatch optimizationEquipment Dispatch & Automation | 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. | Supported99% confidenceATCSS, RTGSS and CHESS explicitly perform optimal job scheduling, routing or work-instruction optimization across cranes and horizontal transport. |
| Quay crane job executionEquipment Dispatch & Automation | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| RTG / RMG dispatch & work queuesEquipment Dispatch & Automation | 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. | Supported99% confidenceRTGSS explicitly monitors and supervises manned RTG/RMG transfer cranes for optimal job scheduling and work instructions using scheduling simulation. |
| Terminal automation / ECS integrationEquipment Dispatch & Automation | Not Yet Verified0% confidence | Supported98% confidenceCATOS documents automated transfer-crane supervision and equipment optimization; exact third-party ECS integration scope should be validated per terminal implementation. |
| Terminal tractor / straddle dispatchEquipment Dispatch & Automation | 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. | Supported99% confidenceCHESS explicitly monitors and supervises yard trucks and straddle carriers, calculating routing and shortest paths for optimal job scheduling and work instructions. |
| VMT mobile work instructionsEquipment Dispatch & Automation | 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. | Not Yet Verified0% confidence |
| Automated gate lane orchestrationGate, Truck & Landside Operations | 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. | Partially Supported96% confidenceCATOS includes Gate Planning and has integration experience with GOS and autonomous infrastructure, but kiosk/barrier/scale lane orchestration is not enumerated as universal native functionality. |
| Driver identification & authorizationGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Gate & truck operationsGate, Truck & Landside Operations | Supported98% confidenceTideworks documents gate operations in Mainsail; advanced gate imaging/processing may use the companion Gate Vision product. | Supported99% confidenceCATOS explicitly documents gate planning and container entry/exit ordering within its integrated operating platform. |
| Gate customs / line / terminal holdsGate, Truck & Landside Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Gate OCR / ANPR integrationGate, Truck & Landside Operations | Not Yet Verified0% confidence | Partially Supported97% confidenceCATOS documents integration references with GOS, QC OCR and rail OCR, but ANPR is not separately stated and recognition may be provided by external subsystems. |
| 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 | 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. | Not Yet Verified0% confidence |
| 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 Supported96% confidenceMainsail 10 documents standardized API integration, while managed EDI is delivered through the companion EDI Porter service in current deployments. | Supported97% confidenceCATOS documents EDI, web ordering and integrated-platform connectivity; exact API/interface catalogue should be validated for the selected release. |
| ERP / finance integrationIntegration, Data & Ecosystem | Partially Supported96% confidenceTideworks documents Mainsail integration with third-party ERP systems, but universal finance/ERP connector coverage is not established. | Not Yet Verified0% confidence |
| Event / webhook / streaming integrationIntegration, Data & Ecosystem | 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. | Not Yet Verified0% confidence |
| Gate / OCR subsystem integrationIntegration, Data & Ecosystem | Supported99% confidenceMainsail 10 explicitly supports OCR and LPR third-party integrations; exact OCR/LPR vendors and project topology remain implementation-specific. | Supported99% confidenceCATOS explicitly documents integration references with GOS, QC OCR and rail OCR systems, establishing operational subsystem integration without assuming CATOS is the recognition engine. |
| MOVINS / BAPLIE vessel messagingIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| PCS / customs / authority integrationIntegration, Data & Ecosystem | Partially Supported98% confidenceMainsail 10 explicitly supports Port Community System integrations, but customs integration is not separately established by the reviewed current public material. | Supported99% confidenceCATOS explicitly documents integration references with customs and Port Community Systems across multiple countries. |
| Reefer monitoring system integrationIntegration, Data & Ecosystem | Not Yet Verified0% confidence | Supported99% confidenceCATOS explicitly lists reefer monitoring systems among its established IoT and infrastructure integration references. |
| REST / web-service API integrationIntegration, Data & Ecosystem | 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. | Not Yet Verified0% confidence |
| Android mobile applicationMobile Access | Not Yet Verified0% confidence · native_android_appMobile availability has not yet been verified from first-party evidence. | 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 · native_ios_appMobile availability has not yet been verified from first-party evidence. | Not Yet Verified0% confidence · native_ios_appMobile availability has not yet been verified from first-party evidence. |
| Mobile web accessMobile Access | 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. | 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 | Not Yet Verified0% confidence | 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 | 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. | Partially Supported94% confidenceCATOS container-position optimization includes inter-terminal movement control, but the reviewed public material does not establish centralized multi-terminal administration or shared-instance operating scope. |
| RBAC / SSO / enterprise identityPlatform Architecture, Resilience & Security | 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. | Partially Supported99% confidenceCATOS explicitly supports single sign-on across multiple applications, but the reviewed public material does not separately establish the full RBAC model or identity-provider standards. |
| Security & administrative audit loggingPlatform Architecture, Resilience & Security | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Throughput & scale for large terminalsPlatform Architecture, Resilience & Security | 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. | Supported99% confidenceTSB states CATOS serves terminals from below 100,000 TEU to over 5,000,000 TEU and is used by more than 100 terminals across more than 20 countries. |
| Rail / intermodal operationsRail & Intermodal Operations | Partially Supported94% confidenceTideworks documents rail planning through the companion Spinnaker component deployed with Mainsail; do not treat it as a universal core-Mainsail entitlement. | Supported99% confidenceCATOS explicitly documents rail planning and rail-supervisor workflows. |
| Rail crane work queuesRail & Intermodal Operations | Not Yet Verified0% confidence | Partially Supported95% confidenceCATOS documents Rail Supervisor SRT estimation and rail planning, but explicit rail-crane work-queue generation and execution are not separately described. |
| Rail interchange eventsRail & Intermodal Operations | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Rail load / discharge planningRail & Intermodal Operations | Partially Supported98% confidenceSpinnaker rail planning supports incoming/outgoing train planning, railcar movement and automated railcar stowage; this remains a companion-product boundary. | Partially Supported97% confidenceCATOS Rail Planning and Rail Supervisor functions support rail operation planning, but detailed wagon-level load/discharge sequencing is not separately established. |
| Rail-yard inventory visibilityRail & Intermodal Operations | 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. | Not Yet Verified0% confidence |
| Train schedule & service managementRail & Intermodal Operations | 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. | Partially Supported96% confidenceCATOS explicitly includes Rail Planning, but train-service schedules, cutoffs and consist-management depth are not separately documented. |
| Wagon / consist planningRail & Intermodal Operations | 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. | Not Yet Verified0% confidence |
| 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 | Partially Supported98% confidenceMainsail explicitly manages over-dimensional cargo inventory, but dedicated OOG equipment selection, lift planning and special-handling execution are not separately established. | 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 | Partially Supported96% confidenceCATOS documents successful reefer-monitoring-system integrations, but the reviewed material does not establish that CATOS itself provides native temperature sensing or every alarm workflow. |
| 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 | 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. | Partially Supported96% confidenceCATOS explicitly includes Berth Planning, but the reviewed public material does not separately establish berth-window conflict handling, arrival/departure window rules or dedicated slot-management depth. |
| Carrier vessel-plan collaborationVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Discharge / load sequencingVessel & Berth Planning | 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. | Supported99% confidenceCATOS Auto Ship Planning explicitly generates ship loading, discharging and re-stow planning and is designed to reduce unnecessary crane movement. |
| Quay crane split planningVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Quay crane work queuesVessel & Berth Planning | 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. | Partially Supported95% confidenceCATOS provides Quay Supervisor SRT estimation and terminal-wide work supervision, but explicit quay-crane work-queue semantics and prioritization are not separately documented. |
| Restow & vessel rehandle planningVessel & Berth Planning | Not Yet Verified0% confidence | Supported99% confidenceCATOS Auto Ship Planning explicitly includes re-stow planning and aims to minimize restow and unnecessary crane movement. |
| Stowage & bay planningVessel & Berth Planning | 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. | Partially Supported98% confidenceCATOS Auto Ship Planning generates loading, discharging and re-stow plans using configurable planning patterns and constraints, but the public material does not separately enumerate all bay/deck/hatch stowage controls. |
| Twin / tandem lift planningVessel & Berth Planning | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Vessel & berth planning / executionVessel & Berth Planning | Partially Supported95% confidenceMainsail manages vessel activity, while full graphical vessel and berth planning is documented through the companion Spinnaker Planning Management System. | Supported99% confidenceCATOS explicitly documents berth, ship and planning workflows including automated ship planning. |
| Vessel call lifecycle managementVessel & Berth Planning | 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. | Partially Supported96% confidenceCATOS explicitly provides Berth Planning and Ship Planning and supports vessel-related container moves, establishing vessel-operation scope without proving the full vessel-call lifecycle from pre-arrival through completion and departure. |
| Automated decking / grounding decisionsYard Strategy & Inventory | Partially Supported98% confidenceSpinnaker automates container location assignments for grounded or wheeled operations; this is not promoted as native base-Mainsail decking functionality. | Partially Supported97% confidenceCATOS provides Auto Positioning and automated shifting/remarshalling, but the reviewed material does not use explicit decking/grounding terminology for all workflows. |
| Block / stack allocation planningYard Strategy & Inventory | 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. | Supported98% confidenceCATOS container-position optimization controls grouping, boundaries, pile quality and container placement, directly supporting yard allocation decisions. |
| Configurable yard strategy rulesYard Strategy & Inventory | Partially Supported98% confidenceSpinnaker provides yard planning tools and supports terminal-specific decking strategies; advanced graphical yard-strategy planning is a companion-product capability. | Supported99% confidenceCATOS container-position optimization supports grouping, boundary, pile-quality, scattering and inter-terminal movement controls, providing configurable yard strategy logic. |
| Empty container inventory managementYard Strategy & Inventory | 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. | Partially Supported94% confidenceCATOS auto-swapping covers unexpected empty-container pickup changes, but the reviewed public material does not establish full empty-container inventory, release and stock-control depth. |
| Housekeeping & remarshalling planningYard Strategy & Inventory | Not Yet Verified0% confidence | Supported99% confidenceCATOS explicitly includes Remarshalling Planning plus Auto Shifting and Auto Remarshalling for yard preparation and reorganization. |
| Import / export / prestack segregationYard Strategy & Inventory | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Rehandle minimizationYard Strategy & Inventory | Partially Supported98% confidenceSpinnaker explicitly helps avoid costly rehandles and set-asides through optimized yard positioning; it remains a companion-product capability. | Supported99% confidenceCATOS optimization explicitly targets container positioning, shifting/rehandling efficiency, and Auto Ship Planning minimizes re-stow and unnecessary crane movement. |
| Yard density & capacity visibilityYard Strategy & Inventory | Not Yet Verified0% confidence | Partially Supported96% confidenceCATOS positions its optimization around maximizing yard utilization and container-position efficiency, but explicit occupancy thresholds and congestion-control functions are not separately documented. |
| Yard holds & exception managementYard Strategy & Inventory | 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. | Partially Supported95% confidenceCATOS explicitly supports exceptional-case handling through auto-swapping for unexpected changes in stacking position, loading sequence, empty pickup and yard-truck assignments, but formal hold/release and regulatory restriction workflows are not separately established. |
| Yard inventory reconciliationYard Strategy & Inventory | 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. | Supported99% confidenceCATOS explicitly provides an automated reconciliation system for data accuracy, consistency, integrity, reliability and process-wide validation. |
| Yard planning & container inventoryYard Strategy & Inventory | Partially Supported95% confidenceMainsail manages cargo and inventory, while advanced graphical yard planning is documented with the companion Spinnaker planning system. | Supported99% confidenceCATOS documents yard planning, remarshalling and container-position optimization. |
| Deployment model | Tideworks Mainsail | Total Soft Bank CATOS |
|---|---|---|
| Public SaaS | Supported99% confidence | Not recorded |
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