Ports & Terminals

One live picture of every vessel, berth and box, from sea to gate.

Vessels wait while berths, cranes, rail and customs are planned in separate systems.

The question it answers

“Which berths will be overloaded in the next 48 hours, and which customers are affected?”

What changes: Shorter vessel turnaround, fewer demurrage disputes, one picture from sea to gate.

All seven layers

How ForgeOrbis works for ports and terminals.

  1. 01

    Connect

    Ingest

    Data sources

    • Terminal Operating System
    • Port Community System
    • Shipping-line EDI (e.g., BAPLIE bay plans)
    • Customs filings
    • Gate OCR cameras
    • Crane/equipment telemetry
    • AIS vessel positions
    • ERP
  2. 02

    Understand

    Extract

    Facts from unstructured data

    • Bills of lading and manifests (PDF/scans)
    • Container and truck numbers from gate cameras
    • ETA changes from emails
    • Damage photos
  3. 03

    Unify

    Resolve

    What must be matched

    • Same vessel across AIS, TOS and agent records (IMO, name, call sign)
    • Shipper/consignee name variants
    • Container numbers validated by ISO 6346 check digit
  4. 04

    Relate

    Model

    Objects and links (the ontology)

    • Vessel
    • Voyage
    • Berth
    • Crane
    • Container
    • Yard Block
    • Truck
    • Rake
    • Shipper
    • Customs Case

    e.g. Vessel berths_at Berth · Container loaded_on Vessel · Container held_by Customs Case

  5. 05

    Decide

    Ask

    Example question

    “Which berths will be overloaded in the next 48 hours, and which customers are affected?”

  6. 06

    Execute

    Act

    Approved actions

    • Propose berth/crane reassignment
    • Flag container for inspection
    • Notify shipping line
    Supervisor approves
  7. 07

    Trust

    Govern

    Trust and compliance

    • Access by terminal operator and agency
    • Customs data segregated
    • Audit of every reassignment

What a pilot measures

Each pilot measures 2 to 3 KPIs you already track, before and after. We publish no benefit numbers until a customer has measured them.

  • Vessel turnaround time
  • Berth occupancy
  • Crane moves/hour
  • Container dwell time
  • Truck gate time

Who it is for

  • Port authority operations head
  • Terminal operator COO

Where it stands today

What runs today, and what we are still building.

We would rather tell you up front than discover it in week three. A pilot starts with what runs today.

The platform

  • 01ConnectIngestPartly live
  • 02UnderstandExtractPartly live
  • 03UnifyResolveRoadmap
  • 04RelateModelPartly live
  • 05DecideAskLive
  • 06ExecuteActLive
  • 07TrustGovernPartly live

Still to build for ports and terminals

  • Industry message standardsLayer 1EDIFACT/shipping EDI, customs filings, other sector standards
  • Document extractionLayer 2OCR + layout, forms, tables, scanned records, stamps
  • Video/image extractionLayer 2Object detection/tracking, number plates, drone and CCTV imagery
  • Entity resolution (assets/things)Layer 3Vessels, parts, equipment tags, SKUs, sites across systems
  • Geospatial/mapLayer 4Map-native objects, routes, areas, proximity questions
  • Optimization/schedulingLayer 5Berth, crew, production and dispatch planning engines

Live means shipping in the product today. Partly live means part of the layer ships today and the rest is being built. Roadmap means being built and not available yet. We never show it as available.

Book a pilot

One site, one problem, measured in weeks.

Each pilot measures 2 to 3 KPIs you already track, before and after. We publish no benefit numbers until a customer has measured them.