Inspiration
One Record Data exchange will become an industry standard starting from 2026, the challenge is big and we expect a cohabitation between One Record data sharing and IATA Cargo XML Messaging for a certain period.
We, as an airline, our objective is to be able to exchange data with our supply chain partners (Forwarders, Handlers, Authorities) whatever their technical maturity and readiness will be, while driving the change and pushing them to go to a more modern standard.
That is why we are tackling Challenge : Developer Experience / Development Empowerment Challenge
What it does
During this IATA ONE Record Hackathon we developed : SWITCARGO , the aircargo switch .
It is THE SOLUTION every airline needs during the transition phase to One Record, it offers on top of a core shipment master inventory, an IATA messaging Layer, a One record server and a Shipment execution portal. During the Hackathon, we want to show how by using our solution, we execute one shipment with different partners some using One record and others using IATA messaging.
How we built it
The system was built using an open source code generator named skeleton generator (https://github.com/skeleton-software-community/skeleton-generator), which build data model and it's related components also includes Angular user interfaces.
We also implemented a lite version of One Record server so that we do not store the data in One Record server but inside our own Back-End.
Challenges we ran into
Connecting and running the NE:ONE Server Building a realistic end-to-end scenario with consistent data, dates, and all events.
Accomplishments that we're proud of
Be able to prove that OneRecord and Messaging can work together and to tackle a real and future industry challenge Add the Carrier Validation Rules (Standard MIP codes) in the One record API. They are the same as in messaging Prove that ONE Record is the future of digital air cargo and that it is a robust and extensible foundation to solve real world industry challenges Great teamwork and spirit
What we learned
How to use ONE Record resources, both on the API's and ONE Record data model. Challenges in sharing data across omnichannel supply chain
What's next for SWITCARGO : THE AIR CARGO SWITCH
Continue working in small increments to understand how we can extend the solution and make a pilot Further investigate how we can use SWITCARGO to overcome ONE Record implementation challenges Create all the needed API to execute a Shipment
Built With
- angular.js
- java
- material
- maven
- ne:one
- onerecord
- postgresql
- skeleton
- springboot


Log in or sign up for Devpost to join the conversation.