Inspiration
Within fragmented global transportation chains, the ability to detect, communicate and act on exceptions, is crucial.
Currently the lack of timely exchange of information…
- ...prohibits pro-active correction measures
- ...leads to unnecessary escalations and process waste
- ...demands excess buffer capacity and drives up resource consumption
- ...results in stock-outs, missed sales, production lines standing still
- ...prevents serious performance management
What it does
The Logistics Event Hub provides a light-weight toolset, for any two or more parties to securely share the specific exception information needed to solve a particular process issue, including
- Event API Management, discovery, and subscription management
- Transformation services
- Sharing policies
- Security and traffic traceability
How we built it
- Exception Event API – Java Spring
- Le Hub – Using webhookie
- Transformation feature – Used JSLT
- Dashboards to show incoming exceptions – Java Spring
Challenges we ran into
- Cutting down the many relevant use cases to something meaningful which can be covered in the hackathon
- Combining hackathon schedule with daughters' soccer practice
- Not forgetting the chicken burning on the barbie
Accomplishments that we're proud of
- Great spirit of collaboration across a very diverse set of expertise and personalities, allowing each of us to play to our strengths
- The high engagement and interest from veteran industry practitioners, namely, David, RJ, Hendrik
- Being able to tackle a real and persistent industry challenge, without just putting lipstick on a pig (we like pigs as they are)
- Le Hub – the best thing since sliced French bread!
What we learned
- JSLT enabled transformation feature providing high business value
- Event-driven architecture being well aligned with the underlying industry processes
- Logistics events providing a low-barrier entry point into ONE Record
What's next for Le Hub
- Continue engagement with industry stakeholders to apply the solution in a real-life setting
- Continue working in small increments to understand how we can extend the solution (e.g. with respect to sharing policies) without creating unnecessary complexity
- Leverage the underlying logic to go beyond exceptions and also support related event-driven workflows
- Further investigate how we can use Le Hub to overcome ONE Record implementation challenges


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