Inspiration
The challenge we are addressing is the Modernizing Cargo Distribution and Sustainability. Warehouse process starts to get digitalize but we seem to lack improvement on the pick up process and the excessive use of paper. In the current situation, delivery receipt gets printed for drivers to claim a shipment. In CDG alone, one of our clients would need to use 700,000 papers per year for printing the delivery receipt. There is also inefficiency on pick up planning by lacking digital communication to drivers which results to wasted time waiting outside the warehouse. Can they get their coffee while waiting? Can the waiting time be used on a more valuable task ? Or will they just wait without knowing what time a shipment will actually be released?
What it does
Express Pick Up Service Mobile app is a cost saving, paperless pick up that promotes efficient warehouse service and sustainability. Key features of the app is as follow:
- Paperless - instead of printing a hard copy delivery receipt, this would be a downloadable file in the mobile device.
- Schedule Pick Up Time - enable truck driver to schedule the pick up time in advance upon generation of Pick Up Order.
- Door Assignment - efficiently plan and assign to which door the shipments would be picked up by the truck driver
- Pick Up Queueing - queueing of shipments per door and allowing warehouse handler to provide updated estimate pick up date / time to the truck driver
Disclaimer: The mobile application is not yet fully functional where some of the data are hard coded in the screen. It is needed to simulate the desired end to end business scenario where a truck driver is able to provide a scheduled pick up date / time, ground handler execute door assignment, and until the shipment is confirmed as picked up . The API used is currently functional on the display of Pick Up Order list screen where AWBs are displayed.
How we built it
Idea was conceptualized and then the process flow was built. From there, the visual design is created and we mapped the possible APIs for each function.
- In order to make the OneRecord API work, we need to install the MongoDB using a Docker Container.
- We follow the instructions in the OneRecord read me documentation to make OneRecord server up and running.
- We did a lot of troubleshooting and hacking just to insert records in our database using POST method and GET to retrieve it.
- UI Development
- Our application connects with IATA’s One Record API
- With the use of its Ontology and Logical Data Model, we were able to map and integrate the available API to our application.
- We primarily used the Logistics Object (LO) endpoint which includes the following models: Waybill, Shipment, ULD and Piece.
- Since One Record promotes building a plug and play environment, we have maximized the use of the available API’s without changing the existing implementation.
- One Record is flexible enough and has plenty of available resources to support the application we built.
Challenges we ran into
- Encountered an issue on the existing One Record APIs where we are unable to write data on the database
- Difficulty on machine configuration where server port are inaccessible.
- It's been 4 days with no rice. For an Asian, it is already a challenge itself :)
Accomplishments that we're proud of
- Despite that one of the team member is working remotely, we were still able to collaborate and build the solution as one team.
- Able to contribute individual ideas starting from ideation phase up to the creation of the final presentation.
- All members of the team is a first time joiner of hackathon
- Proud of how we did our presentation
- Was able to travel by bike from hotel to the Start Up Village
What we learned
- That it is always a good thing to delegate and share tasks with the team and let everyone be able to contribute
- There's no such thing as a bug free code. Learn to be resourceful on what is available.
- In our industry, innovation is a never ending process and there is always something new.
- Francis finally learned how to use the Nespresso
What's next for Express Pick Up Service Mobile App
In case the app would actually be developed as a solution, below would be the features to be implemented as a next step:
- For further improvement to support the AWB level pick up. Currently, the solution only covers the pick up through a single reference Pick Up Order number which contains several AWBs. Due to the lack of time in this event, we opted to focus on bulk pick up which could be later enhanced to cover other business case scenarios.
- Use of IOT device to enable auto transport of shipment from warehouse location to the assigned door once the warehouse handler assigned the door for shipment pick up.
- Truck Tracking capability for drivers to send out his / her ETA back to the warehouse operator.
Built With
- api
- docker
- docker-compose
- ionic
- java
- javascript
- maven
- mongodb
- node.js
- npm
- one-record-api
- swagger-ui
- typescript







Log in or sign up for Devpost to join the conversation.