OneCheck by LX

The problem your project solves, including which One Record challenges are addressed.

The transport of temperature controlled goods in refrigerated containers is an important corner stone in the airfreight industry. The safe transport of these goods within the requisite temperature bandwidth greatly depends on a robust, efficient and timely capture of data. The whole process starts with the acceptance of these shipments in the warehouse where they are mostly received as shipper built temperature controlled units. Today, to ensure that the requirements of the shipment transport and condition of the active units are correct, handling agents perform manual checks on a paper ‘Check sheet’, which accompanies the unit from origin to destination.

Manually captured data in a paper driven process come with many problems and pose challenges:

1) Physical integrity of paper documents is never guaranteed. Quality of print, legibility of hand captured data, torn and damaged documents are common basic issues.

2) Paper check sheets remain within the handling agent domain unless asked for by the air carrier.

3) Data captured on manual check sheets remains unused and unavailable till the shipment physically arrives as the documents travel with the shipment. Visibility is a problem.

4) Manual data remains difficult to consume as it is not digital.

Swiss WorldCargo hopes to fulfill the following 1R hackathon challenges.

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 # 6 IATA Open Challenge

Your solution and what it does

The Swiss WorldCargo solution allows easy capturing of active temperature-controlled container check sheet data’ and stores the data in the 1R format making it instantly available to subscribed stake holders. It allows a registered and authenticated user to log-in, select a process flow (export, transit or import) and scan an Airwaybill bar code. In the background makes a call to the air carrier system which checks if a booking exists for the called Airwaybill number and returns an appropriate check sheet (based on the shipment flags) and the process flow selected by the user. The carrier system validates the AWB number against the ULD serial number and populates available shipment data in the check sheet before making it available to the user over the app.

The user can easily fill in the sheet data valid for his / her process flow and save the data. The captured data is recorded and stored in the carriers 1R domain and is made available instantly to all subscribed stake holders. In addition to ‘Capture New data’ the app allows for easy ‘Edit’, ‘Modify’ and ‘Upload picture’ functionalities to round off the flexibility of the app.

How did you build it?

On the back end we have created an API written in .Net 8 implementing CQRS pattern, which is used as a 'Back end' for the 'Front end'. It maps the business object we use in our application to the 1 Record data model, and our API calls the Ne:One server to store the data used in the application. The logic in the API creates or updates the Checks relate to Logistics Objects in our case ULDs.

The Frontend App is built with the Ionic UI Library and the Capacitor Framework for mobile App Development. We can build iOS and Android apps out of a single repository. The front end business logic itself is using the Angular Framework.

What are you proud of?

We are extremely proud to have been able to bring a LX team for the first time to the IATA 1R Hackathon. Moreover, we are proud that our IT colleagues took this challenge although none of them have any aircargo background. Despite the limited on-boarding and preparation time we take pride in our energy, commitment, dedication and the keen desire to achieve something out of the box.

What is next step for your solution and how will you take that step?

The next logical step for us to further our new development would be to demonstrate it in house at Swiss. The aim will be to win over our colleagues and draw our management attention to the potential of our solution. We would hope to convert the idea into a project which we will be able to eventually implement in production. And last but not the least we would like to encourage the industry to look into standardizing data collection protocols / standards in order to enable exchange of ‘Check sheet data’ across multiple stakeholders in the industry using standardized applications.