Crowley Logistics expanded its use of 3Gtms to inland shipments in 2017. A Crowley announcement tied that expansion to planning, execution and carrier onboarding. In January 2018, 3Gtms reported a related selection to support Crowley’s U.S. Department of Defense transportation work. The two announcements describe how a system used to expand commercial transport could also support a contract with more demanding reporting requirements.
From order allocation to carrier exception
For an inland shipment, a transport management system ties the order to a load, proposes a route or carrier and sends a tender. When a carrier rejects a tender or misses a pickup, dispatch needs the original shipment commitment, available replacement capacity and a way to notify the customer. Plan quality only matters if execution teams can see and respond to that exception.
A 3Gtms case study on Crowley’s defense work describes information arriving from carriers, shippers, government systems, mobile tools and finance systems. It says Crowley used a carrier portal to give parties another way to report incidents and exchange transport information. The case study reports that implementation milestones were met. It does not provide an independently audited savings figure for the earlier inland expansion.
What the ERP still needs to know
In a similar deployment, define which application owns the order number, shipment status and financial posting before building the interfaces. The TMS may update estimated delivery and freight cost throughout a journey, while finance needs the charge attributable to the underlying order. Test a partial shipment, a carrier change and a revised invoice separately. If either application creates a new record without a link back to the original order, operations may appear to be on schedule while finance is reconciling duplicate charges.










