iValid8OR by IBS Software

Validating and correcting 1R data will be essential when the industry takes this to production at scale - iValid8OR is here to help accelerate it!

Comment

The Problem & Challenges being addressed

Inconsistencies in shipment data is one of the biggest problems that the logistics industry faces, mainly due to the large number of stakeholders involved in transporting a single shipment – from the shipper, forwarder, trucking company, airline, ground handling agent, etc.

This inconsistency has a direct impact on the number + length of delays and amount of manual intervention + effort needed at every stage of the shipment journey / whenever a handover occurs - thus driving up both the handling costs as well as waiting times for the shipment.

Challenges addressed -

  • Challenge 1: Develop a solution that Leverages IATA ONE Record to pre-validate, including corrective shipper actions of documentation for special handling cargo, aiming to expedite the acceptance process and reduce customer wait times

  • Challenge 4: CiQ

  • Challenge 5: Participants will develop deployable solutions for air cargo, focusing on seamless integration with Amazon Web Services (AWS). The goal is to create practical, scalable applications ready for immediate deployment on AWS, addressing key challenges in the air cargo industry

The Solution

IBS Software’s iValid8OR solution looks to address this problem at its root / source – i.e., at the point of shipment data creation / update by shipper / forwarder into the ONE Record server.

How we built it

iValid8OR leverages ONE Record Data Model 3.0 and API model 2.0. The frontend is built using React, with the server side on Spring/Java. The rules/validations are currently hardcoded - if and when we take this to production, we will use a suitable NoSQL DB for the same. As mentioned earlier, iValid8OR is designed to be connected to any 1R server (in this case NEONE 1R).

Challenges we ran into

  1. The main challenge was for deciding whether to use the 1R Data Model LOs (Check LO) or 1R API model (Action Requests) to maintain and distribute tasks / corrective actions for shipment LOs.

  2. The LO ID returned as the POST response for LO creation couldn't be used to GET LO data from the server. We had to manually remove the port numbers in the LO ID to get it to work for the GET LO API - which impacted the integration of iValid8OR demo.

Accomplishments that we're proud of

  1. We managed to combine 3 hackathon challenges together with a use case - which we weren't expecting initially.

  2. We got very good feedback from mentors about the iValid8OR concept, and are excited to consider this as one of our use cases to take to production.

  3. We managed to integrate with an external (NEONE) ONE Record server and process / validate information retrieved from the same.

What we learned

We got some of our doubts specifically regarding LOs to be mapped for tasks and CIQ milestones clarified - which will definitely come of use, when we take this forward internally within IBS.

Built With

Share this project:

Updates