CargoTracking Cargo iQ Door to Door planning and visibility

Process Flow

Thank you for opportunity to participate at ONE Record hackatone 2023. The location is great and it’s very useful to have face to face experience and option to get direct support, mentorship and answers to the questions.

We have chosen to work on the Cargo IQ challenge and see a lot of value in solving that problem as it brings Enhanced Planning and Control for Cargo iQ:

CargoTracking.aero - A Solution for Information Sharing and Real-Time Updates and Documents Attachments with Members/Non-Members and Non-Monitored Sectors

Cargo iQ offers comprehensive shipment management capabilities, but faces challenges with non-monitored sectors and non-members. Our solution bridges this gap, enabling both Cargo iQ members and non-members to input shipment details through a ONE Record Standard API. This streamlines routemap creation and enhances efficiency.

Cargo iQ (as well as non Cargo iQ) members can share a URL/key with their unmonitored providers, ensuring collaboration and visibility.

By leveraging oneRecord's linked data structure and standard ontology, information sharing becomes seamless.

Our solution improves planning, control, and evaluation, providing real-time updates, predicted timings, and the ability to adapt to deviations.

We started from scratch: from integrating our Awery Total Cargo Management System to NE:ONE server, which is a great help to speed up the integration process. As its open source we hope and truly believe it will develop quickly by community and speed up the adoption of the ONE Record standard to the whole industry. We plan to make Awery fully compliant with ONE Record and offer it to our customers on ASAP basis.

What have we achieved:

Once the HAWB or AWB is created - it is automatically pushed to NE:ONE server instance, returns shipment unique ID/address which is stored in Awery ERP and also subscribes Awery to receive shipments updates notifications.

On the test scenario, we were working on the Airport to Door mode where the Freight forwarder needs to plan the events until POD. On the shipment is planned on flight/truck it automatically creates the planned events - ARR and NDF (which with 4 h offset from planned arrival time).

We created 3 apps with limited access required for specific features:

1st APP - For the Freight Forwarder to plan the events, we added a feature to check address over Google maps API and estimate the distance to delivery address and plan the POD event (distance/60km per hour + offset). In future we plan to add the control for works times, weekends and public holidays to the planning of the offset). Actions creates the events in ONE Record object with status planed. Also there is an option to generate QR code for the other parties to open shipment and update the possible actions.

2nd APP - For the Freight Forwarder and 3rd parties (truck companies, drivers, etc.) to put the actual event times (POD as example) and attach the supporting documents - app can be opened from QR code or by search of HAWB/AWB number. Once data is uploaded it pushes notification to TCM/ERP with event details and attachments.

3rd APP - For the Shipper/Consignee to see limited information on planned and actual events and their differences.

We built the solution using: NE:ONE, ONE Record API, AWERY ERP API, ANGULAR, MATERIAL DESIGN, PHP, MYSQL

We are proud of opportunity to work on common modern standard for the cargo industry, we this that is a good start and achievement for the 28 hours or intense brainstorming and work.

As a next step our solution has a great potential to solve the Cargo iQ challenge of planning and measuring the Door to Door activities with easy access sharing over ONE Record API. Incorporating our solution empowers all stakeholders, enhances shipment management, and optimises information accessibility.

Presentation: https://docs.google.com/presentation/d/e/2PACX-1vRG_rtyPthT7rYCYGholae6BEnvjgRsHgtsRjQSRx2a5HmuOytLEjImkBFlpcuGL_IAG9SFxOPIotq5/pub?start=false&loop=false&delayms=3000