About the Client
Business Challenge
- Target Pay (low-end cost)
- Suggested Offer (predicted cost to offer a specific carrier)
- Max Pay (high-end cost)
- Estimated Carrier Cost (estimated cost of a load before adding margin and quoting a customer)
- Estimated Margin (mark-up to add to an Estimated Carrier Cost to quote a customer)
- Cost of Accessorial
- Extra Stop Charge
Trigent Solution
Trigent’s Amoeba Business Framework
Discovery
Trigent’s team expeditiously participated in a knowledge transfer effort to fully understand the organization’s internal processes and data flows. The intense 2-week discovery further included a series of collaborative discussions on the technical stack and platform architecture with regard to its pricing model.
This phase of the engagement was led by a product manager, working with experts in the Logistics industry and AI/ML tech to ensure a well-rounded assessment of the business requirements..

Design
With the inputs gathered from the discovery phase, Trigent team hit the ground running and developed an ML technology for price prediction. Based on the requirements defined in Discovery, the AI/ML experts assisted the in-house engineering team in designing data structures and refining algorithm models for accurate price predictions.
Trigent designed an enterprise-grade ML solution that was well-integrated, seamless, and agile. Python was used to build prototypes, thereby providing the organization with an idea of the custom solution.

Development
Leveraging Trigent’s capabilities in disruptive technologies, the team developed an ML solution for price prediction. The ML model was a Python-based solution, and Jupyter Notebook was added as an interface for the convenient testing of the blocks of code. Additionally, techniques such as bagging and boosting were used to reduce prediction variance. Open-source software such as Pytorch and Sklearn were leveraged to build the ML models.
As a part of data preparation, analysis and management, the team added all the historical pricing data from 37 different internal data fields. In addition, APIs were built in the ML model to capture additional data. Freightwaves was used to capture market intelligence and forecasting intelligence information from DAT, EIA, and McLeod, to name a few. The team built a database leveraging MS SQL. The captured data was then ingested by the predictive engine that provided pricing predictions/outputs. Transformation logic was applied to generate predictive pricing options to a customer quote response.
The Quality Engineering resources were aligned with the Development sprints to ensure bugs were trapped early and performance roadblocks were pre-emptively handled. The DevOps framework was customized for the customer-specific operational environment.

Deployment
Azure Machine Learning was used to train, score, deploy, and manage the AI/ML model at scale rapidly and with ease. Azure Blob services was leveraged to build data lakes storing petabytes of data. Additionally, Redis was used to cache prevalent data to improve prediction latency..
Once thoroughly tested in the QA environment, the model was further deployed into the production environment with the help of Azure Kubernetes Service to further manage critical tasks such as model health and maintenance.

Monitor and Manage
Azure monitoring was leveraged for model management. The process of monitoring and retraining the ML model was done in an asynchronous manner. Retaining was triggered on a schedule or when new data would become available by referring to the published pipeline REST endpoint from the previous step. MLFlow was used for the end-to-end management of the ML lifecycle..
The Operations team took the lead at this phase of the engagement, thereby bringing Trigent’s Amoeba framework to a full circle.

Client Benefits:
- Become self-disruptive and stay competitive in the market, thereby leading to an acceptance rate of 98.3%
- Maintain 18.59 average annual loads per carrier