CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

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

Forge turns raw Tormach 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 Tormach data and see it normalized in 30 seconds. No POC required.

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

The problem

Why Tormach data is hard to integrate

Every controller names the same physical quantity differently (spindle speed alone ships as a dozen tag names across firmware revisions), and most shops still bridge it through MTConnect or a hand-rolled OPC UA server.

Typical Tormach equipment communicates over MTConnect, 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 Tormach machine

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

MTConnectHTTP / REST

91%Field coverage

17Canonical CNC / machine tool fields

3,444Corpus mappings

Field coverage

What Forge resolves for Tormach

Confirmed canonical fields your agent gets from Tormach 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
spindle_rpm: 4200	→	spindle_speed_rpm: 4200	actual spindle speed
sp_load_pct: 63	→	spindle_load_pct: 63	spindle load
active_prog: "TORMACH-01"	→	program_name: "TORMACH-01"	active program
part_ct: 1540	→	part_count: 1540	part count

30-second deployment

Add Tormach to your agent with one call

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

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

# normalize raw Tormach telemetry into the universal schema

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

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

-d '{"data": {"spindle_rpm": 4200, "sp_load_pct": 63, "active_prog": "TORMACH-01"}, "oem": "tormach"}'

{"spindle_speed_rpm": 4200, "spindle_load_pct": 63, "program_name": "TORMACH-01", "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 Tormach fits

Protocols
MTConnect HTTP / REST

Vertical
CNC / machine tool

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

Same protocols, other industries
Yaskawa Motoman Caterpillar Cummins MiR (Mobile Industrial Robots)

Also searched as tormach, pathpilot