ONE Record uses a standardized data model based on "Logistics Objects". Understanding these helps you work with the system.
4 Design Principles:
-
Piece-Centric
- Each physical piece has unique identity
- Based on IATA RP 1689
- Track at package level, not just shipment
-
Physics-Oriented (Digital Twin)
- Data mirrors the physical world
- If it exists physically, it has a digital representation
- Events reflect real-world actions
-
Single Source of Truth
- Data stored at origin
- Clear ownership
- No duplicate records
-
Data-Driven (not Document-Driven)
- Designed around data elements
- Not around traditional documents
- More flexible and queryable
Core Logistics Objects:
Physical Chain:
Item → Piece → Shipment → Waybill → Booking
Transport Chain:
Transport Means → Transport Segment → ULD → Piece
Key Objects Explained:
| Object | What It Represents |
|---|---|
| Piece | Single physical package |
| Shipment | Collection of pieces going together |
| Waybill | Contract of carriage (AWB equivalent) |
| Booking | Capacity reservation |
| Event | Something that happened (milestone) |
| IoT Device | Sensor/tracker attached to piece |
| Product | Service offering (mandatory) |
Ontology Extensions:
The core "Airline Core Ontology" covers general cargo. Extensions exist for:
- Dangerous Goods (DG)
- Pharmaceuticals (Pharma/GDP)
- Customs (PLACI, ICS2)
- ULD Tracking
- Interactive Cargo (sensors)
- e-CMR (road transport link)
- Ground Handling
For OBC Context: When you carry a package as OBC, in ONE Record terms:
- You are a "Transport Means" (the courier)
- The package is a "Piece"
- Your flight is a "Transport Segment"
- Check-in, boarding, landing are "Events"
- The AirTag is an "IoT Device"
- All linked to the customer's "Shipment"