CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

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

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

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

The problem

Why Mazak data is hard to integrate

Mazak SmartBox and SMOOTH controls stream over MTConnect, but Mazatrol program state and multi-spindle load values arrive as vendor tags (S1speed, Sload) that need normalizing per model.

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

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

MTConnectOPC UA

99%Field coverage

17Canonical CNC / machine tool fields

3,444Corpus mappings

Field coverage

What Forge resolves for Mazak

Confirmed canonical fields your agent gets from Mazak 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
S1speed: 12000	→	spindle_speed_rpm: 12000	spindle 1 speed
Sload: 55	→	spindle_load_pct: 55	spindle load
main_program: "MZK1200"	→	program_name: "MZK1200"	Mazatrol program
partcount: 2210	→	part_count: 2210	part count

30-second deployment

Add Mazak to your agent with one call

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

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

# normalize raw Mazak telemetry into the universal schema

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

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

-d '{"data": {"S1speed": 12000, "Sload": 55, "main_program": "MZK1200"}, "oem": "mazak"}'

{"spindle_speed_rpm": 12000, "spindle_load_pct": 55, "program_name": "MZK1200", "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 Mazak fits

Protocols
MTConnect OPC UA

Vertical
CNC / machine tool

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

Same protocols, other industries
Yaskawa Motoman ABB Robotics KUKA Universal Robots

Also searched as mazak, smooth, smartbox, mazatrol

Mazak in the canonical schema

Canonical fields this OEM maps

spindle_speed_rpm spindle_load_pct axes.0.position_actual axes.0.load_percent axes.0.temperature_c feed_rate program_name part_count All fields →

Protocol comparisons

MTConnect vs OPC UA Modbus TCP vs OPC UA MQTT / Sparkplug B vs OPC UA J1939 (CAN) vs OPC UA