Last sprint we started introducing machine learning in some key areas of functionality. This sprint we are expanding our web services.
When we talk about being modular and having a modern architecture, these are things we mean - building automation and establishing micro services for our customers to easily plug in and leverage different parts of the platform that is best suited for them. Specifics on the release below. Lot's of multi sprint items being worked on simultaneously so we'll see portions of the functionality released over time.
1. This is a web service (API) rich release; we have 3 going into production:
- Users can pull data to compare what was sent to a carrier in terms of order details (delivery window - including retain/runout boundaries, product, qty. needed, load codes or contract to pull from, etc) and what the carrier actually did. We are getting asked more and more for transparency into carrier performance and we have much of this data - so we’ve made it available for our customers to fetch.
- Most of our customers manage driver credentials, licenses, certificates, badges/entry permissions via a 3rd party ERP system (often time this is done in an HR module). We need some of this data during load planning validation and it seems crazy to require that this data be re-keyed and maintained in two places. So let’s allow the customer to do this in the system where it makes the most sense and we’ll support that.
- Same thing for driver schedules, holidays, time off etc. We now have an API to support that too.
2. Delivery windows have been pulled forward into the main dispatch workbench (DSB). We have at least one large customer that uses the delivery window as the basis for scheduling and planning loads and this will make that workflow much easier. This presentation will support manual, automatic, and forecasted order/delivery requests.
3. And we have revamped our forecasting profile to better support the machine learning we have built into the engine. Lots more good stuff to come here.