ONE Record is IATA's new data-sharing standard that will replace legacy EDI messaging. OnFlyGo is ONE Record compliant.
The Big Picture:
🗓️ Deadline: January 1, 2026 All IATA member airlines must be capable of exchanging data via ONE Record.
What It Replaces:
- Cargo-IMP (legacy messaging format from 1960s)
- EDI messages (Cargo-XML)
- Paper documents and manual processes
Key Concepts:
📦 Logistics Objects: Everything is a "Logistics Object" with a unique identifier:
- Shipment
- Piece (individual package)
- Booking
- Waybill
- Events (milestones)
- IoT devices (sensors)
🔗 Linked Data: Objects link to each other:
- Shipment → contains → Pieces
- Pieces → tracked by → IoT Device
- Booking → references → Shipment
🌐 API-Based:
- RESTful API (HTTP)
- JSON-LD format
- Standard CRUD operations
Why It Matters for OBC:
-
Real-Time Visibility:
- Track shipments across carriers
- Unified view of cargo journey
- No more calling for updates
-
Digital Documentation:
- Electronic air waybill (e-AWB)
- Digital customs data
- Instant document sharing
-
Faster Processing:
- Automated data exchange
- Reduced manual entry
- Fewer errors
OnFlyGo Implementation: ✅ ONE Record API endpoints ✅ Logistics Object creation ✅ Event publishing ✅ Real-time tracking integration ✅ Digital documentation flow