Compare Navis N4 TOS vs Tideworks Mainsail for terminal operations across vessel, yard, gate, equipment, automation/integration, deployment, evidence coverage and known research gaps.
TechSelectAI compares Navis N4 TOS and Tideworks Mainsail using recorded product evidence rather than user-specific recommendation scoring. Navis N4 TOS currently has 17 supported, 29 conditional, 42 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 98% for Navis N4 TOS 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.
Navis N4 terminal operating system from Kaleris for complex container terminals, covering planning, execution, automation integration, optimization, operational visibility and enterprise terminal workflows.
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 | Navis N4 TOS | Tideworks Mainsail |
|---|---|---|
| Billing, Analytics & Operational Control | 9 / 9 known5 conditional · 0 research pending · 0 explicitly unsupported | 6 / 9 known2 conditional · 3 research pending · 0 explicitly unsupported |
| Equipment Dispatch & Automation | 8 / 10 known4 conditional · 2 research pending · 0 explicitly unsupported | 6 / 10 known6 conditional · 4 research pending · 0 explicitly unsupported |
| Gate, Truck & Landside Operations | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported | 3 / 11 known2 conditional · 8 research pending · 0 explicitly unsupported |
| Integration, Data & Ecosystem | 5 / 11 known2 conditional · 6 research pending · 0 explicitly unsupported | 6 / 11 known4 conditional · 5 research pending · 0 explicitly unsupported |
| Platform Architecture, Resilience & Security | 5 / 8 known2 conditional · 3 research pending · 0 explicitly unsupported | 3 / 8 known3 conditional · 5 research pending · 0 explicitly unsupported |
| Rail & Intermodal Operations | 0 / 7 known0 conditional · 7 research pending · 0 explicitly unsupported | 5 / 7 known5 conditional · 2 research pending · 0 explicitly unsupported |
| Reefer, DG & Special Cargo | 2 / 7 known2 conditional · 5 research pending · 0 explicitly unsupported | 1 / 7 known1 conditional · 6 research pending · 0 explicitly unsupported |
| Vessel & Berth Planning | 5 / 11 known4 conditional · 6 research pending · 0 explicitly unsupported | 6 / 11 known5 conditional · 5 research pending · 0 explicitly unsupported |
| Yard Strategy & Inventory | 6 / 11 known5 conditional · 5 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 | Navis N4 TOS | Tideworks Mainsail |
|---|---|---|
| Billing / tariff / financial integrationBilling, Analytics & Operational Control | Supported97% confidenceKaleris documents capture of billable terminal events and N4 billing/invoicing; detailed tariff scope depends on implementation. | 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 | 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. | 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 | 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. | Not Yet Verified0% confidence |
| Operational visibility, analytics & KPIsBilling, Analytics & Operational Control | Supported98% confidenceKaleris documents real-time operational data, productivity KPIs, control-room visibility and decision-support optimization. | Supported97% confidenceTideworks documents real-time operational visibility and data-driven planning across the Mainsail terminal platform. |
| Productivity & equipment KPIsBilling, Analytics & Operational Control | Supported97% confidenceKaleris documents N4 real-time operational visibility and performance/productivity insights used to improve terminal execution. | 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 | Supported98% confidenceN4 Control Room centralizes operational views and functions used to monitor and maintain terminal operations. | 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 | 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. | Not Yet Verified0% confidence |
| Storage, tariff & service billingBilling, Analytics & Operational Control | 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. | 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 | 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. | Not Yet Verified0% confidence |
| AGV / ASC automated-equipment integrationEquipment Dispatch & Automation | 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. | Not Yet Verified0% confidence |
| Equipment dispatch & controlEquipment Dispatch & Automation | Supported99% confidenceKaleris documents PrimeRoute, RTG/RMG optimization and VMT workflows for terminal handling equipment dispatch and execution. | Partially Supported95% confidenceTerminal equipment dispatch and control are documented through Tideworks Traffic Control, a companion product integrated with Mainsail. |
| Equipment position trackingEquipment Dispatch & Automation | Supported98% confidenceN4 Control Room visualizes where containers, cranes and trucks are in the yard, providing equipment/location visibility for operational control. | 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 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. | 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 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. | 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% confidenceKaleris documents N4 coordination of automated yard, transport, quay and gate operations through ECS integration for semi- and fully automated terminals. | Not Yet Verified0% confidence |
| Terminal tractor / straddle dispatchEquipment Dispatch & Automation | 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. | 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% 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. | 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% 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. | 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 | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Gate & truck operationsGate, Truck & Landside Operations | Supported98% confidenceKaleris documents terminal execution across the gate and truck workflows; exact optional optimization modules should be validated for the selected N4 package. | 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 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. | 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 | 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. | Not Yet Verified0% confidence |
| Truck turn-time & queue monitoringGate, Truck & Landside Operations | 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. | 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 | Partially Supported97% confidenceA live N4 implementation links container weighing systems to N4 for SOLAS VGM compliance. Universal weighbridge hardware/protocol coverage is not inferred. | 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 | Supported99% confidenceKaleris documents robust EDI and API integration for container terminal cargo and external systems/data streams. | 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 | 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. | 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 | 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. | 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 | Supported98% confidenceKaleris documents N4 integration with automated gate OCR/license-plate recognition and traffic-flow systems in production terminal operations. | 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 | Not Yet Verified0% confidence | 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 | Supported99% confidenceKaleris explicitly documents robust API integration for N4 with external systems and data streams. | 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 · 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 | Not Yet Verified0% confidence · mobile_webMobile availability has not yet been verified from first-party evidence. | 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 | Supported98% confidenceKaleris explicitly discusses N4 4.0 for existing on-premises customers and cloud adoption, supporting more than one enterprise deployment pattern. | Not Yet Verified0% confidence |
| Disaster recovery & RPO/RTO controlsPlatform Architecture, Resilience & Security | 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. | Not Yet Verified0% confidence |
| High availability architecturePlatform Architecture, Resilience & Security | 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. | Not Yet Verified0% confidence |
| Multi-terminal / multi-site operationPlatform Architecture, Resilience & Security | Supported98% confidenceTransnet documents operating multiple terminals on a single N4 system while standardizing processes across the terminal network. | 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% confidenceKaleris states N4 4.0 scales to very large container-terminal volumes, including published capacity up to 16 million TEU. | 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 | Not Yet Verified0% confidence | 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 | 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. | 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 | 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. | 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 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. | 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 | 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. | Not Yet Verified0% confidence |
| Discharge / load sequencingVessel & Berth Planning | Not Yet Verified0% confidence | 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 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. | Not Yet Verified0% confidence |
| Quay crane work queuesVessel & Berth Planning | Not Yet Verified0% confidence | 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 | Partially Supported99% confidenceN4 Vessel Autostow generates vessel stowage plans, but Autostow is an advanced optimization module and is not assumed in every N4 license. | 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 | Supported99% confidenceKaleris documents vessel planning support including N4 Vessel Autostow and terminal planning across berth, yard and quay workflows. | 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 | Not Yet Verified0% confidence | 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 | Partially Supported99% confidenceExpert Decking automatically distributes containers according to terminal-specific business rules, but Expert Decking is an optional N4 optimization module. | 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 | 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. | 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 | Not Yet Verified0% confidence | 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 | Not Yet Verified0% confidence | Not Yet Verified0% confidence |
| Import / export / prestack segregationYard Strategy & Inventory | Partially Supported97% confidenceExpert Decking explicitly automates decking decisions for import, export, reefer and empty containers; a distinct universal prestack workflow is not inferred. | Not Yet Verified0% confidence |
| Rehandle minimizationYard Strategy & Inventory | Partially Supported99% confidenceExpert Decking and Yard Intelligence explicitly target rehandle reduction, but the optimization capability depends on optional advanced modules. | 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 | 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. | 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 | Supported99% confidenceKaleris documents N4 yard planning, Expert Decking, yard utilization and real-time container/equipment visibility. | Partially Supported95% confidenceMainsail manages cargo and inventory, while advanced graphical yard planning is documented with the companion Spinnaker planning system. |
| Deployment model | Navis N4 TOS | 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