FoundryNet / OEMs / Haas

CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

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

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

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


The problem

Why Haas data is hard to integrate

Haas Next Gen Control publishes over MTConnect, but production state lives in Q-variables and macro registers (macro_1102, Q600) that need decoding before an agent can reason about the cut.

Typical Haas equipment communicates over MTConnect, Modbus TCP, 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 Haas machine

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

MTConnectModbus TCPHTTP / REST
99%Field coverage
17Canonical CNC / machine tool fields
3,444Corpus mappings

Field coverage

What Forge resolves for Haas

Confirmed canonical fields your agent gets from Haas 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 inCanonical field outMeaning
Q600_1: 3400→spindle_speed_rpm: 3400NGC spindle rpm
macro_1102: 78→spindle_load_pct: 78spindle load macro
prog_active: "O00012"→program_name: "O00012"active program
parts_counter: 4821→part_count: 4821M30 parts counter

30-second deployment

Add Haas to your agent with one call

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

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'
# normalize raw Haas telemetry into the universal schema
curl -s https://forge.foundrynet.io/v1/normalize \
  -H 'Content-Type: application/json' \
  -d '{"data": {"Q600_1": 3400, "macro_1102": 78, "prog_active": "O00012"}, "oem": "haas"}'
{"spindle_speed_rpm": 3400, "spindle_load_pct": 78, "program_name": "O00012", "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 →

Related

Where Haas fits

Protocols
MTConnect Modbus TCP HTTP / REST

Vertical
CNC / machine tool

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

Same protocols, other industries
Yaskawa Motoman Universal Robots Chemical process Food & beverage process

Also searched as haas automation, haas ngc, haas cnc


Haas in the canonical schema

For platforms Want this normalization inside your platform? License the engine and ship cross-vendor support as your own feature. 1,027-field canonical schema, 366 resolvable from vendor tags today, 2,461 mappings, your brand. Platform licensing →
Why does a cross-vendor canonical data model matter? The Machine Agent breaks it down weekly. Read it →
Get the thesis behind this infrastructure: The Machine Agent, weekly.