1. SCM with Container Tracking
  2. Data model
Reference

The tables behind SCM with Container Tracking

SCM with Container Tracking 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

Freight movement

Loads hold the shipment identity, promise, owner, carrier and status. Container bookings hold vessel and free-time details for a linked load.

Physical route

Load stops preserve planned windows and actual times. Load assignments connect each load to Drivers and Vehicles; vehicle defects describe fleet issues.

People and partners

Organizations scope work, team members identify owners and reviewers, and transport partners identify carriers.

Review and evidence

Review decisions, operation receipts and record attachments remain linked to Loads.

Every table, by feature

Loads and dispatch

7 tablesAbout this feature
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

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

    Tracks a container booked on a vessel, following its shipment from booking through arrival.

    Linked to Loads, Organizations
  • Load stops

    Captures one stop on a load's route, tracking planned times against what actually happened.

    Linked to Loads
  • Load assignments

    Assigns a driver and vehicle to a load, so dispatch knows who's hauling what and when.

    Linked to Loads, Drivers, Vehicles
  • Operation receipts

    Records the result of an action taken in the system, for audit and troubleshooting later.

    Linked to Loads
  • Record attachments

    Holds a file attached to a record, such as a photo or document, kept as supporting evidence.

    Linked to Loads, Team members
  • Review decisions

    Logs an approval or rejection made during a review, recording who decided what and why.

    Linked to Loads, Team members

Container bookings

4 tablesAbout this feature
  • Container bookings

    Tracks a container booked on a vessel, following its shipment from booking through arrival.

    Linked to Loads, Organizations
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

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

    Logs an approval or rejection made during a review, recording who decided what and why.

    Linked to Loads, Team members
  • Operation receipts

    Records the result of an action taken in the system, for audit and troubleshooting later.

    Linked to Loads

Routes and assignments

6 tablesAbout this feature
  • Load stops

    Captures one stop on a load's route, tracking planned times against what actually happened.

    Linked to Loads
  • Load assignments

    Assigns a driver and vehicle to a load, so dispatch knows who's hauling what and when.

    Linked to Loads, Drivers, Vehicles
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

    Linked to Organizations, Team members, Transport partners
  • Drivers

    Represents a driver, so dispatch can check who's active and eligible to run a load.

  • Vehicles

    Represents a truck or trailer, so dispatch can check its capacity and readiness before assigning it.

  • Vehicle defects

    Tracks a problem found on a vehicle so the team can confirm it's fixed before returning to service.

    Linked to Vehicles

Partners and organization

5 tablesAbout this feature
  • Organizations

    Represents a company or business unit that owns the teams, loads, and records in the app.

  • Team members

    Represents a person on the team, used to manage their role and access within the app.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Transport partners

    Represents a carrier or partner company the team works with to move freight.

    Linked to Organizations
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

    Linked to Organizations, Team members, Transport partners

Review and evidence

5 tablesAbout this feature
  • Review decisions

    Logs an approval or rejection made during a review, recording who decided what and why.

    Linked to Loads, Team members
  • Operation receipts

    Records the result of an action taken in the system, for audit and troubleshooting later.

    Linked to Loads
  • Record attachments

    Holds a file attached to a record, such as a photo or document, kept as supporting evidence.

    Linked to Loads, Team members
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

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

    Tracks a container booked on a vessel, following its shipment from booking through arrival.

    Linked to Loads, Organizations

Operations overview

5 tablesAbout this feature
  • Loads

    Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.

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

    Tracks a container booked on a vessel, following its shipment from booking through arrival.

    Linked to Loads, Organizations
  • Operation receipts

    Records the result of an action taken in the system, for audit and troubleshooting later.

    Linked to Loads
  • Review decisions

    Logs an approval or rejection made during a review, recording who decided what and why.

    Linked to Loads, Team members
  • Load assignments

    Assigns a driver and vehicle to a load, so dispatch knows who's hauling what and when.

    Linked to Loads, Drivers, Vehicles

Keys and references

Loads is the parent for container bookings, stops, receipts, attachments and review decisions. Assignments reference Loads, Drivers and Vehicles. Team members reference Organizations and Users. Keep original operation keys and expected revisions when importing action history, and preserve parent references so an exception can be traced back to its shipment.

Migration order

  1. Import Organizations and Users, then team members and transport partners.
  2. Import Drivers and Vehicles, followed by vehicle defects.
  3. Import Loads with their owner, organization and counterparty references.
  4. Import container bookings, load stops and load assignments against the correct load.
  5. Import review decisions, record attachments and operation receipts with their original links and dates.

Set up SCM with Container Tracking your way.

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

How to get started