Inspiration
We have been inspired by clear and conscise business challenge provided by Holcim, and the fact that the desired goal is achievable.
What it does
Reverso is fairly simple and straight to the point.
Once the user provides source and destination points for the cement delivery, Reverso analyses the destination and suggests optimal backhauling option based on the deviation from the delivery route and truck utilisation. Reverso provides suggestions on new and already existing backhauling options, making it a bit easier for the decision making person to make the right choice.
Reverso provides both UI and API integration options.
How we built it
We have designed Reverso keeping it future proof in mind - utilising the same API for direct calls for retrieving prospective backhauling trips, and for the UI.
Challenges we ran into
As for the challenges, there were quite some. First we've found some data inconsistencies we had to figure out and cleanse. Then the SQL queries which eventually became quite advanced. We also didn't have a frontend developer this time so we had to master our JS skills in a rapid manner.
Accomplishments that we're proud of
Geo analyses using PostGIS extension of PostgreSQL database.
What we learned
We've learned a lot about cement industry and Holcim operational model thanks to Holcim/Santiago inputs.
What's next for Reverso
- Tuning the algorithm to consider multi-segment backhauling routes
- Tuning the algorithm to consider different trucks configuration
- Provide CO2 reduction and cost optimisation for each of the backhauling routes
- Data visualization on the map
Built With
- fastapi
- postgis
- postgresql
- python
- react
Log in or sign up for Devpost to join the conversation.