10Entity Types
118Properties
19Relationships
4Design Principles

Long-Haul Trucking Ontology

A domain ontology for fleet management — terminals, trucks, trailers, drivers, customers, routes, loads, trips, maintenance, and service tickets. The Trip entity coordinates all five operational resources into a single dispatch unit, with FMCSA regulatory compliance embedded in the data model.

Source: github.com/hzmarrou/truck-ontology-bench

Knowledge Graph🔗

Class Edge
⚙ Display Settings
Appearance
1.00
9px
Linking

10 Entity Types🔗

Key Relationships🔗

Design Principles🔗

🔧 Trip as Central Dispatch Record

The Trip entity links all five operational entities — driver, truck, trailer, load, and route — into a single coordinated dispatch unit. It is the atomic unit of work in trucking.

🔄 Status State Machines

Every operational entity carries enumerated status fields — enabling dashboards that surface available resources, in-progress work, and items needing attention.

📝 FMCSA Compliance Built-In

CDL endorsements, DOT inspection dates, HOS supervisor alerts, and ELD logging are modeled alongside operational data — not siloed separately.

🌎 Geospatial Awareness

Terminals carry GPS coordinates. Routes include waypoints and distance. Trips track current position — enabling tracking without external GIS.

How to Implement the Ontology🔗

Frequently Asked Questions🔗

Glossary🔗