1. Port & Terminal Management
  2. Data model
Reference

The tables behind Port & Terminal Management

Port & Terminal Management ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
14
Features
6
Change it
Add fields and tables in Proto

How the model is organised

Operating scope:

Organizations, team members, Users and transport partners identify the entity, people and counterparty behind work.

Freight work:

Loads carry owner, partner, status and delivery promise; load stops keep ordered service detail.

Terminal work:

Container moves connect container, yard, voyage, berth, custody and customs information to a parent load.

Dispatch resources:

Drivers, Vehicles, vehicle defects and load assignments describe eligibility, readiness and interval commitments.

Review trail:

Record attachments, review decisions and operation receipts preserve files, decisions and guarded action outcomes.

Every table, by feature

Load planning

5 tablesAbout this feature
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners
  • Organizations

    Operating organizations that own loads, partners and terminal operations.

  • Team members

    Named staff members with an authenticated platform identity and role scope.

    Linked to Organizations, Users
  • Transport partners

    Eligible carriers and terminal partners used as load counterparties.

    Linked to Organizations
  • Load stops

    Ordered pickup, delivery and service stops belonging to a load.

    Linked to Loads

Terminal container moves

6 tablesAbout this feature
  • Container moves

    Terminal container move extensions confirmed through independent review before gate release.

    Linked to Loads, Organizations
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners
  • Organizations

    Operating organizations that own loads, partners and terminal operations.

  • Record attachments

    Supporting documents and evidence files attached to a load.

    Linked to Loads, Team members
  • Review decisions

    Independent reviewer decisions recorded against a load revision.

    Linked to Loads, Team members
  • Operation receipts

    Durable receipts for guarded operations, keyed for idempotent retries.

    Linked to Loads

Dispatch assignments

5 tablesAbout this feature
  • Load assignments

    Driver and vehicle commitments to a load over a nonoverlapping interval.

    Linked to Loads, Drivers, Vehicles
  • Drivers

    Drivers with eligibility windows and external authority references.

  • Vehicles

    Tractors, chassis and terminal equipment with readiness state.

  • Vehicle defects

    Reported equipment defects with severity and repair release evidence.

    Linked to Vehicles
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners

Stops and delivery evidence

4 tablesAbout this feature
  • Load stops

    Ordered pickup, delivery and service stops belonging to a load.

    Linked to Loads
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners
  • Record attachments

    Supporting documents and evidence files attached to a load.

    Linked to Loads, Team members
  • Transport partners

    Eligible carriers and terminal partners used as load counterparties.

    Linked to Organizations

Partners and operating scope

6 tablesAbout this feature
  • Organizations

    Operating organizations that own loads, partners and terminal operations.

  • Team members

    Named staff members with an authenticated platform identity and role scope.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Transport partners

    Eligible carriers and terminal partners used as load counterparties.

    Linked to Organizations
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners
  • Container moves

    Terminal container move extensions confirmed through independent review before gate release.

    Linked to Loads, Organizations

Review and receipts

6 tablesAbout this feature
  • Container moves

    Terminal container move extensions confirmed through independent review before gate release.

    Linked to Loads, Organizations
  • Review decisions

    Independent reviewer decisions recorded against a load revision.

    Linked to Loads, Team members
  • Record attachments

    Supporting documents and evidence files attached to a load.

    Linked to Loads, Team members
  • Operation receipts

    Durable receipts for guarded operations, keyed for idempotent retries.

    Linked to Loads
  • Loads

    Freight and terminal loads moving through plan, dispatch, transit and delivery.

    Linked to Organizations, Team members, Transport partners
  • Team members

    Named staff members with an authenticated platform identity and role scope.

    Linked to Organizations, Users

Keys and references

Loads is the central parent for stops, terminal moves, attachments, decisions and operation receipts. Container moves also references Organizations. Load assignments points to Loads, Drivers and Vehicles. Team members links a person to Organizations and Users, while Loads points to its owner and transport counterparty. A decision’s source revision and an operation receipt’s expected revision identify the version being examined; the operation key distinguishes a retry from a new action.

Migration order

  1. Import Organizations and Users, then team members with the correct identity and scope.
  2. Import transport partners, Drivers and Vehicles, followed by vehicle defects where needed.
  3. Import Loads with organization, owner and counterparty references.
  4. Import load stops and load assignments against their parent loads and resources.
  5. Import container moves and their load evidence, preserving current status and revision.
  6. Reconcile review decisions and operation receipts only with their original source revision, operation key and outcome.

Set up Port & Terminal Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started