Territory · Substrate signal

01Acquired-entity overlay.

14 acquisitions in five years across US + Netherlands + UK + Indonesia. The internal AI & Data Science team's #1 stated job: "single version of truth" across multi-TMS, customer-mapping, and exception-routing.

Where Caddie sits

Above the acquired-entity stacks.

Customers · myAIT portal · Compass Cargo · acquired-entity portals

↓

CADDIE · agentic execution · cross-stack reconciliation · exception orchestration

↓

CargoWise (Compass Cargo + standardized acquisitions)

Acquired-entity legacy TMS

EDI / API integration layer

Power BI + Validaide

Caddie reads across the heterogeneous stack, drafts cross-system actions, executes on operator approval with audit trail.

What we read

The acquired-entity reality.

14 acquisitions in 5 years

AIT did 14 acquisitions and grew gross revenue >300% under TJC ownership (2021-2026). Each carries its own TMS, customer portals, SOPs.

DC Velocity

AI team stated job

"Redefining core domains" and "single version of truth" across the data layer is the AI & Data Science team's first task. Patrick Chew (VP, AI & Data Science) leads.

AIT newsroom

Greenbriar incoming

February 2026: Greenbriar Equity Group signed to acquire AIT from TJC. Stated intent: accelerated organic + M&A growth toward 2030 plan with technology investment named explicitly.

AIT newsroom

What Enmovil delivers here

Three moves · one orchestration layer.

Cross-system read

Reads across CargoWise + acquired-entity TMS + customer portals + EDI / API layer into one shipment view.

Cross-stack action drafting

When an exception fires in one acquired entity, Caddie drafts the cross-stack action (re-route, escalate, reassign) for operator approval.

Audit trail per action

Every drafted + executed action carries the data lineage — which systems were read, what was returned, what was changed.

Proof anchor

Where we have shipped this shape.

14 entities

Read across in one query · same pattern shipped at a Fortune 500 manufacturer

40% / 30%

Fewer client inquiries · faster exception resolution · global lead-logistics provider

8-15%

Logistics cost savings · across deployments

For the conversation

Questions, fence, timeline.

Is CargoWise enterprise-wide, or only Compass Cargo + recent acquisitions? What runs the legacy AIT-US book?
How are 14 acquired-entity TMS / WMS instances being consolidated — and on what timeline post-Greenbriar?
Where does the AI & Data Science team's first shipped product land — internal operations co-pilot or customer-facing?

We would touch

Cross-system read across CargoWise + acquired-entity TMS.
Drafted cross-stack action + operator approval + audit trail.
Conversational query into the systems of record.
Exception orchestration above the heterogeneous stack.

We would not

CargoWise replacement.
Acquired-entity TMS replacement (coexistence only).
Core BI / data platform (Patrick Chew's org owns it).
Customer-facing portal replacement (myAIT stays).

8-12 weeks · one cross-stack flow

First lane: one operational flow that traverses CargoWise + at least one acquired-entity legacy stack, instrumented with audit trail. Cloud-native CargoWise integration runs longer than legacy SAP.