CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

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

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

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

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

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

The problem

Why Heidenhain data is hard to integrate

TNC controls expose data over DNC/OPC UA with Klartext program references and S_actual style tags that differ from the ISO-code world most integrations assume.

Typical Heidenhain equipment communicates over OPC UA, MTConnect. 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 Heidenhain machine

Forge resolves Heidenhain 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 machine, pass oem: "heidenhain", and spindle speed is spindle_speed_rpm whether it came from a Heidenhain controller or anything else on the floor.

OPC UAMTConnect

99%Field coverage

17Canonical CNC / machine tool fields

3,444Corpus mappings

Field coverage

What Forge resolves for Heidenhain

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

spindle_speed_rpmspindle_load_pctspindle_current_ampsaxes.0.position_actualaxes.0.load_percentaxes.0.temperature_cfeed_ratecnc.path.feedrateprogram_nameprogram_numberpart_counttool_id

Sample normalization

Raw tag in		Canonical field out	Meaning
S_actual: 9000	→	spindle_speed_rpm: 9000	actual spindle speed
spindleLoadPct: 60	→	spindle_load_pct: 60	spindle load
activeProgram: "TNC_1.H"	→	program_name: "TNC_1.H"	Klartext program
feedActual: 800	→	feed_rate: 800	actual feed

30-second deployment

Add Heidenhain to your agent with one call

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

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

# normalize raw Heidenhain telemetry into the universal schema

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

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

-d '{"data": {"S_actual": 9000, "spindleLoadPct": 60, "activeProgram": "TNC_1.H"}, "oem": "heidenhain"}'

{"spindle_speed_rpm": 9000, "spindle_load_pct": 60, "program_name": "TNC_1.H", "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 Heidenhain fits

Protocols
OPC UA MTConnect

Vertical
CNC / machine tool

Other CNC / machine tool vendors
DMG Mori Fanuc Haas Mazak Okuma Siemens Sinumerik

Same protocols, other industries
ABB Robotics KUKA Universal Robots Chemical process

Also searched as heidenhain, tnc, tnc640