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.
- Tire Management
- Data model and import order
The tables behind Tire Management
Tire Management ships with 15 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
- 15
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Tire inspections
Tire inspections records tire serial, inspected at, tread depth32nds, Position, Revision and Status with Parent referencing Loads and Organization referencing Organizations.
Rotation and replacement review
Review decisions records the Reviewer, source revision, Decision, Reason and operation key on the parent Loads record; tire inspections retains its own inspection revision and decision date.
Fleet readiness
Vehicles supplies equipment identity and Readiness, Drivers supplies eligibility until and external authority, and vehicle defects references Vehicles with severity and repair evidence.
Load coordination
Loads references Organizations, team members and transport partners. Load assignments links Loads, Drivers and Vehicles with starts at and ends at; load stops belongs to Loads through Parent.
Evidence and reconciliation
Record attachments and operation receipts reference Loads. Uploaded by references team members; operation keys and effect references identify the action being investigated.
Organization and access
Organizations, team members, Users and transport partners establish operating identity. Exchange rates holds read-only effective currency rates; Loads.freight amount USD remains explicitly denominated in USD.
Every table, by feature
- Tire inspections5
- Rotation and replacement review5
- Fleet readiness5
- Load coordination7
- Evidence and reconciliation5
- Organization and access5
- Tire inspections
Tire inspection records supporting approval of a tire rotation or replacement, with tire serial lineage and vehicle position history
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 - Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Record attachments
Evidence files attached to loads with visibility and evidence type
Linked to Loads, Team members
- Tire inspections
Tire inspection records supporting approval of a tire rotation or replacement, with tire serial lineage and vehicle position history
Linked to Loads, Organizations - Review decisions
Independent approval, rejection or return decisions on a source revision
Linked to Loads, Team members - Operation receipts
Idempotent operation receipts recording executed or failed actions with stable keys
Linked to Loads - Record attachments
Evidence files attached to loads with visibility and evidence type
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
- Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Vehicle defects
Reported vehicle defects with severity, repair evidence and release time
Linked to Vehicles - Drivers
Driver roster with eligibility expiry and external authority reference
- Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Tire inspections
Tire inspection records supporting approval of a tire rotation or replacement, with tire serial lineage and vehicle position history
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 - Load assignments
Driver and vehicle assignments to loads with committed start and end times
Linked to Loads, Drivers, Vehicles - Load stops
Ordered pickup and delivery stops within a load with appointment windows
Linked to Loads - Transport partners
Eligible carriers and transport partners with contact and eligibility notes
Linked to Organizations - Drivers
Driver roster with eligibility expiry and external authority reference
- Vehicles
Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Operation receipts
Idempotent operation receipts recording executed or failed actions with stable keys
Linked to Loads
- Operation receipts
Idempotent operation receipts recording executed or failed actions with stable keys
Linked to Loads - Record attachments
Evidence files attached to loads with visibility and evidence type
Linked to Loads, Team members - Review decisions
Independent approval, rejection or return decisions on a source revision
Linked to Loads, Team members - Tire inspections
Tire inspection records supporting approval of a tire rotation or replacement, with tire serial lineage and vehicle position history
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
- Organizations
Logistics operating organizations with time zone, currency and active scope
- Team members
Staff membership linking platform users to organizations with operational roles
Linked to Organizations, Users - Users
Users
Linked to Users - Transport partners
Eligible carriers and transport partners with contact and eligibility notes
Linked to Organizations - Exchange rates
Read-only effective exchange rates for this app.
Keys and references
Preserve the exact source identity when importing a record. A display name can change and should not substitute for a reference. Team members.User links staff to platform users; Loads.Owner points to team members. Resolve that mapping before configuring Loads Default List for the signed-in user.
Tire inspections.Parent identifies a load. Establish vehicle context from the relevant load assignments rather than assigning every inspection to every vehicle on that load. Keep each dated tire observation separate so a later position does not replace an earlier reading.
Distinguish tire inspections.Revision from Loads.Revision. Review decisions.source revision identifies the reviewed parent revision. Confirm the exact inspection and its frozen revision through the operation evidence, retaining operation key and effect references. A shared Parent alone cannot distinguish several inspections or actions on the same load.
Migration order
- Load Organizations and the authorized Users identities, then resolve the Users.User references.
- Load team members with Organization and User references, then transport partners, Drivers and Vehicles.
- Load Loads with Organization, Owner and Counterparty, followed by load assignments, load stops and vehicle defects.
- Load tire inspections with the parent load and organization; retain original serial, dated reading and revision history.
- Import record attachments, review decisions and operation receipts with stable source references, preserving historic outcomes without repeating operations; verify exchange rates against its owning source.
- Reconcile parent references, decision scope and operation identity before opening the pilot for new work.
Set up Tire Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.