CONE.TCP – Terminal Customer Portal (TCP)
Structured External Access Without Disrupting Core Systems
A terminal-controlled portal for customers, agents, and carriers — handling document workflows, requests, approvals, and visibility without exposing operational systems.
What Port Community Systems do for ports, TCP does for individual terminals
Customer visibility and status tracking
Cargo and order status, milestones, and exceptions - visible in real time. Access controlled by role and relevance, giving customers the transparency they expect.
Self-service requests and interaction
Enable customers to submit requests, upload and receive documents, track approvals, and receive notifications - paperless, with no manual emails, calls, or ad-hoc coordination.
External user management
Companies, users, and roles managed outside the TOS. Supports self-registration, invite flows, and modern authentication (SSO/MFA) - secure and low-maintenance.
Document management and workflow orchestration
Acts as a document workflow layer on top of the TOS - closing document-handling gaps in the out-of-the-box product and reducing human errors through structured processes.
Responsibility, traceability, and dispute reduction
Establish a clear responsibility model defining who provides, validates, and approves data — supported by audit logs, timestamps, and full end-to-end traceability.
Reduces load on core systems
External users work through the portal, not directly in the TOS - reducing load to core systems. Asynchronous workflows keep users productive even when terminal connectivity is limited.
How the Terminal Customer Portal Fits Into Your Systems
The Terminal Customer Portal sits between core execution systems and external parties. It exposes selected data and workflows without taking ownership of operational control or master data.
Does not replace core terminal systems
The portal does not replace TOS, GOS, WMS, or other core systems. Planning, execution, and control remain in the systems that already run the terminal.
No new system of record
Routes information from existing systems based on defined rules. Supports its own master data when needed, but doesn't require it.
Used for external coordination
Customer communication, document exchange, requests, and approvals are handled outside execution systems, keeping operational logic unchanged.
Controlled access for external users
Customers see and act only on what is relevant to them, governed by roles, permissions, and approval rules defined by the terminal.
Works Alongside
Existing Systems
Operates alongside existing terminal operating system and other operational systems without requiring system replacement.
System-agnostic by design
"We launched a multipurpose terminal on Cone's platform from day one — TOS, GOS and TCS. The systems have scaled with us as throughput has grown, and when we expand the Ro-Ro yard, it will be built into the same environment. That continuity matters when you are running mixed cargo operations."
– Head of Operations at the Terminal
