Flight care – sharing is caring!

Seamless coordination and data sharing between Airline and GHA/RAMP over ONERecord format providing real-time visibility of Cargo iQ Flight Related Milestones, their monitoring and measurements.

Comment

Inspiration

The lack of synchronization between GHA/Ramp Agent and Airline creates communication gaps that lead to delays and inefficiencies in cargo handling. With the help of ONE Record standard we attempted to break down the barriers and ensure that all stakeholders can access critical, real-time information seamlessly. Using ONE Record we see a more seamless integration and communication between Airline and GHA for easier adoption of Flight Milestones utilization as per Cargo iQ MOP 4.0 for measure of Carrier’s Operations.

What It Does:

  • Creation at ONE Record Servers: for Airline and GHA based on NE:ONE instances;
  • Setting up Publish & Subscribe model and how ONE record servers need to communicate between each other;
  • Different Access in Application to Airline and GHA use;
  • Creation of flights as 1R Transport Movement Object;
  • Creation of Flight Milestones as per Cargo iQ MOP 4.0 with allowed offsets as 1R Logistics Event.
  • Update of Milestones once Estimated time updates available
  • Input of Actual Milestones be each party separately: GHA at Origin submits: UWS, LIR, FOW, ALS, ALE. GHA at Origin submits: OFB, DEP, FFM, WDO, ARR, GHA at Destination submits: AUS, AUE, FIW

How We Built It

We built Flight Care with a main idea in our heads - tailor data across different organizations, ensuring that parties involved in the cargo supply chain could access the same data in real-time. The solution brings in:

  • Ability to plan, monitor and measure operational performance for the Cargo iQ Flight Related Milestones;
  • Two-way planning and updating by GHA/Ramp Agent and Airline their corresponding Flight Route Milestones based on Cargo iQ MOP 4.0;
  • GHA/Airline ONE Record push driven seamless exchanges of data;
  • User Friendly mapping, visualization and reporting of the exchanges between airlines and GHA Warehouse or RAMP for export or import activities.

Challenges We Ran Into

  • Data Standardization. Given many organizations are still relying on proprietary systems, inline with overall industry's fear of change, adopting 1R data model is the area where Flight Care Project has to invest most of the effort;
  • Real-Time Synchronization. Achieving real-time updates across multiple systems requires to carefully architect a solution that could handle the sheer volume of data being exchanged without latency;
  • Scalability. The air cargo industry operates on a global scale, and our solution needs to be able to support thousands of flights, handlers, and shipments simultaneously.
  • Understanding of the Publish & Subscribe model and how ONE record servers need to communicate between each other

What We Learned

  • Standardization is for overcoming the communication barriers that different systems and data models create;
  • Open-data sharing is the future of logistics, and solutions like Flight Care can lead the way.
  • Clear understanding of the Publish & Subscribe model for ONE record servers communications between each other
  • Cargo iQ’s concept of Flight Route map Milestones and their usage and importance to monitor the Carrier’s Operation

What's Next for Flight Care – Sharing Is Caring

  • Onboard AI-driven decision-making tools;
  • Engage as many stakeholders as possible, promoting standardization and encouraging the industry to adopt ONE Record as the new staple for data-sharing;
  • Have a ready to deploy Awery solution/product based on 1R for Airlines and GHA to measure the Carrier’s Operation for Flight Related Milestones

Access Details: User: admin Password: superSecret

Access for GHA: https://onerecordtr.awery.com/gha

Access for Airline: https://onerecordtr.awery.com/airline

Share this project:

Updates