HEAVY VEHICLE / OFF-HIGHWAY · CANONICAL DATA MODEL

Caterpillar canonical data model: connect your Caterpillar equipment to any AI agent

2,461 confirmed mappings·12 protocols·99% field coverage

Forge turns raw Caterpillar tags into one clean, governed schema your AI agent already understands. One MCP call, no per-vehicle integration project.

Try it free: 3 machines, no credit card → See it work →

Paste your Caterpillar data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your Caterpillar data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why Caterpillar data is hard to integrate

Cat engines and mining trucks broadcast everything as J1939 SPNs on the CAN bus, SPN 100 (oil pressure), SPN 175 (oil temp), plus proprietary parameter groups that VIMS and third-party telematics each decode differently.

Typical Caterpillar equipment communicates over J1939 (CAN), HTTP / REST. Each firmware revision, model line and integrator names the same physical quantity differently, so every AI or analytics project pays the integration tax again, the tax that cancels 40% of industrial AI deployments before they ship.

The solution

One universal schema for every Caterpillar vehicle

Forge resolves Caterpillar telemetry into Forge's canonical field set, the same 1,027-field canonical schema (366 resolvable from vendor tags today), used across all 47 vendor packs. Point Forge at the vehicle, pass oem: "caterpillar", and spindle speed is spindle_speed_rpm whether it came from a Caterpillar controller or anything else on the floor.

J1939 (CAN)HTTP / REST

99%Field coverage

11Canonical heavy vehicle / off-highway fields

3,444Corpus mappings

Field coverage

What Forge resolves for Caterpillar

Confirmed canonical fields your agent gets from Caterpillar vehicles, drawn from Forge's 3,444-mapping corpus:

vehicle.engine.oil_pressurevehicle.engine.oil_tempvehicle.engine.fuel_rail_pressurevehicle.engine.intake_manifold_pressurevehicle.turbocharger.rpmvehicle.transmission.oil_tempvehicle.brake.air_pressurevehicle.brake.primary_air_pressurevehicle.wheel_speed_flvehicle.tire_pressure_flvehicle.dtc_description

Sample normalization

Raw tag in		Canonical field out	Meaning
SPN_100: 55	→	vehicle.engine.oil_pressure: 55	engine oil pressure (psi)
SPN_175: 98	→	vehicle.engine.oil_temp: 98	engine oil temp (°C)
SPN_103: 78000	→	vehicle.turbocharger.rpm: 78000	turbo speed
SPN_1636: "P0087"	→	vehicle.dtc_description: "Fuel rail pressure low"	active DTC

30-second deployment

Add Caterpillar to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Caterpillar data:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'

# normalize raw Caterpillar telemetry into the universal schema

curl -s https://forge.foundrynet.io/v1/normalize \

-H 'Content-Type: application/json' \

-d '{"data": {"SPN_100": 55, "SPN_175": 98, "SPN_103": 78000}, "oem": "caterpillar"}'

{"vehicle.engine.oil_pressure": 55, "vehicle.engine.oil_temp": 98, "vehicle.turbocharger.rpm": 78000, "coverage": "100%", "confidence": 0.97}

Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.

Start free: Forge API, 3 machines → See the full demo →

Where Caterpillar fits

Protocols
J1939 (CAN) HTTP / REST

Vertical
heavy vehicle / off-highway

Other heavy vehicle / off-highway vendors
Cummins Detroit Diesel Freightliner John Deere Kenworth Mack Trucks

Same protocols, other industries
Haas MiR (Mobile Industrial Robots) Universal Robots OTTO Motors

Also searched as cat, caterpillar, cat mining, 793, c15