These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fleet Management System
- Fleet and load data model
The tables behind Fleet Management System
Fleet Management System ships with 18 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
- 18
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Load planning
Loads retains record number, Subject, Status, promised delivery at, freight amount USD and Revision, linked to Organizations, team members and transport partners. Load stops holds sequence, planned windows and actual stop evidence under Parent.
Driver and vehicle readiness
Drivers retains driver code, Active, eligibility until and external authority. Vehicles holds vehicle code, equipment class, capacity LB, Active, Readiness and external fleet ID. Vehicle defects links repair and release evidence to Vehicle.
Dispatch and delivery
Load assignments links Load, Driver and Vehicle with starts at, ends at and Status. Loads retains actual pickup at and actual delivery at, while load stops retains actual arrival at, actual departure at and proof reference.
Maintenance release
Maintenance plans links to Loads through Parent and to Organizations directly. Vehicle code, service type, odometer miles and next due describe the submitted scope under its own Revision and Status.
Exceptions and corrections
Review decisions links to the load and Reviewer in team members. Decision, source revision, Reason and operation key preserve the independent review context.
Operations evidence
Operation receipts holds operation key, Action, expected revision, result state and effect references under the load. Record attachments links evidence to the load and uploaded by team member, with Visibility and evidence type.
Organization and reference data
Team members maps the authenticated Users identity to the operating organization. Transport partners belongs to Organizations. Exchange rates retains effective currency rates for the app.
Every table, by feature
- Load planning7
- Driver and vehicle readiness5
- Dispatch and delivery7
- Maintenance release8
- Exceptions and corrections6
- Operations evidence6
- Shared and settings5
- Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load stops
Ordered load stops with planned windows and recorded actual arrivals and departures.
Linked to Loads - Transport partners
Transport partners with eligibility notes and linked load activity.
Linked to Organizations - Organizations
Logistics operating organizations with time zone, currency and active scope
- Team members
Fleet team members with their organization, platform user, role and time zone.
Linked to Organizations, Users - Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Linked to Loads - Record attachments
Evidence attachments linked to a load, with visibility and evidence type.
Linked to Loads, Team members
- Drivers
Fleet drivers with eligibility dates and external licensing authority, linked to their load assignments.
- Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id.
- Load assignments
Driver and vehicle assignments for a load over a start and end interval.
Linked to Loads, Drivers, Vehicles - Vehicle defects
Vehicle defects with severity, repair evidence and release time.
Linked to Vehicles - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners
- Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load assignments
Driver and vehicle assignments for a load over a start and end interval.
Linked to Loads, Drivers, Vehicles - Load stops
Ordered load stops with planned windows and recorded actual arrivals and departures.
Linked to Loads - Drivers
Fleet drivers with eligibility dates and external licensing authority, linked to their load assignments.
- Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id.
- Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Linked to Loads - Record attachments
Evidence attachments linked to a load, with visibility and evidence type.
Linked to Loads, Team members
- Maintenance plans
Maintenance plans supporting the release-a-vehicle-after-maintenance operation: Submitted revisions, independent review decisions, and the recorded physical evidence that authorizes release.
Linked to Loads, Organizations - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id.
- Vehicle defects
Vehicle defects with severity, repair evidence and release time.
Linked to Vehicles - Review decisions
Independent review decisions recorded against a load revision.
Linked to Loads, Team members - Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Linked to Loads - Record attachments
Evidence attachments linked to a load, with visibility and evidence type.
Linked to Loads, Team members - Team members
Fleet team members with their organization, platform user, role and time zone.
Linked to Organizations, Users
- Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Load stops
Ordered load stops with planned windows and recorded actual arrivals and departures.
Linked to Loads - Review decisions
Independent review decisions recorded against a load revision.
Linked to Loads, Team members - Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Linked to Loads - Record attachments
Evidence attachments linked to a load, with visibility and evidence type.
Linked to Loads, Team members - Load assignments
Driver and vehicle assignments for a load over a start and end interval.
Linked to Loads, Drivers, Vehicles
- Operation receipts
Idempotent operation receipts recording each fleet action, its expected revision and result state.
Linked to Loads - Record attachments
Evidence attachments linked to a load, with visibility and evidence type.
Linked to Loads, Team members - Review decisions
Independent review decisions recorded against a load revision.
Linked to Loads, Team members - Loads
Freight loads from pickup to delivery with promised windows, freight value and lifecycle
Linked to Organizations, Team members, Transport partners - Maintenance plans
Maintenance plans supporting the release-a-vehicle-after-maintenance operation: Submitted revisions, independent review decisions, and the recorded physical evidence that authorizes release.
Linked to Loads, Organizations - Team members
Fleet team members with their organization, platform user, role and time zone.
Linked to Organizations, Users
Keys and references
Preserve human load numbers, driver codes and vehicle codes separately from record identifiers. Load assignments uses direct references to Loads, Drivers and Vehicles. Maintenance plans instead records vehicle code as text; establish and verify the mapping to the intended vehicle before executing release.
Review decisions.Parent, operation receipts.Parent and record attachments.Parent identify Loads. Maintenance plans has its own Revision, while review decisions.source revision retains the load review context. The release action must check both current revisions and retain enough operation references to identify the intended maintenance plan. Operation key connects the decision and action investigation; effect references and external reference identify evidence to inspect.
Organizations.Currency does not change the explicit USD meaning of Loads.freight amount USD. Retain the original promised delivery at separately from actual pickup and delivery observations.
Migration order
- Establish Organizations and authenticated Users, then map team members with the correct active state and time zone.
- Load transport partners, Drivers and Vehicles, reconciling external authority and fleet identities.
- Load Loads with their original promised delivery times, owners, partners and revisions.
- Attach load stops and load assignments to the correct loads and validate driver and vehicle intervals.
- Bring maintenance plans and vehicle defect evidence into their correct vehicle and load context without inventing release dates.
- Import review decisions, action receipts and supporting files with original identifiers and revision evidence. Reconcile existing effects before enabling new operating actions.
Set up Fleet Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.