JettHansa Industries

Mapping ULD tracking events to handling steps of the shipment, validate against Cargo iQ planning times and show exceptions in a dashboard including the customs and screening state.

Comment

Inspiration

There are many blind spots in the common air cargo environment where it is not clear what the exact position or state of the shipment is. As the data is already available through tracking tags on the ULD, our goal was to derive additional process data like time stamps and geo positions instead of forcing ground handling personal to enter this data. With this, our solution can validate Cargo iQ handling times and raise exceptions as OneRecord events and display them in a frontend.

What it does

By integrating data from the handling systems, tracking devices, and other sources within OneRecord, we gain a comprehensive view of the cargo's journey. This enables us to identify deviations, measure idle time between each step, and engage in productive discussions with our customers.
To store the tracking data we are using the newest ONE Record model with the class "Measurement" which can hold the geo location and a flexible measurement-value. This class can be updated without the need for a change request.
By automating the measurement of time between "freight out of warehouse" and aircraft arrival, we can obtain reliable data, facilitating meaningful performance discussions with our ground handling providers. Furthermore, we eliminate human errors while capturing and entering data.
This data-driven approach empowers us to evaluate our own performance and provide accurate and transparent reporting to our valued customers. For example, we can determine how long the shipment was exposed to outdoor conditions, potentially impacting its temperature and humidity levels. To complete the process chain we included the customs and screening states in the ONE Record model and show the state in our frontend.

Addressed challenges:

  • e-Commerce Challenge: customs and screening in ONE Record
  • ONE Record Challenge: Usage of Measurements in a combination with ULDs and IoT devices
  • Cargo iQ Challenge: Mapping Logistic events to Cargo iQ planning times
  • Open Challenge: The whole solution

How we built it

  1. Ideas and the general concept were drafted using a miro board before the hackathon began.
  2. Tasks were distributed according to the individual expertise
  3. Working on our packages at the same time
    1. ONE Record Data Model preparation and data feeding
    2. Process walkthrough and story line
    3. Backend development
    4. Frontend development
    5. Video production

Backend
To implement our solution we used the common technologies: At the core we use the ONE Record Open Source Java Server in combination with a GraphDB database and Keycloak authentication, containerized with Dockers. This gave us the chance to use some of the benefits of ONE Record out of the box:

  1. The variety of one record objects such as IoT Devices, Sensors, Measurements and Waybills/Shipments
  2. JSON-LD as the data standard which is easy to share and extend
  3. ONE Record events and Linked Data to realize real-time visibility by storing logistic events and Cargo iQ planned times in one record and consume them with our frontend

WebFrontend
We created different ReactJS views for the 2 roles which can benefit from this solution. The Airline Support Center can view a list of active shipments. This list shows the state including the derived BLE timestamps and raises exceptions if a Cargo iQ plan is violated. The ground handler can inspect a specific shipment and identify all related ULD’s on a map. If one ULD has raised an exception a “Find ULD” button appears to search for the ULD on the airport.

Challenges we ran into

  • Parallelizing development on the frontend without live data until the backend was ready 🧑🏻‍💻
  • Correct usage of stacked JSON objects 😉
  • The Wifi Log-In 🛜

Accomplishments that we're proud of

  • 100% ONE Record native backend
  • 100% ONE Record native frontend
  • Running end to end integration from a mobile app to the backend via a ONE Record Server to the Web Frontend (Dashboard)

What we learned

  • Working in an interdisciplinary team and with a broad tech stack is challenging but fun!
  • Time is always short

What's next for JettHansa Industries

  • Implement a productive version of our solution to offer our customers an easy platform to optimize their processes
  • Return at the next hackathon 🔜

Built With

Share this project:

Updates