CNC / MACHINE TOOL · TELEMETRY NORMALIZATION
16,908 confirmed mappings·18 OEM families·14 protocols·95% field coverage
Forge turns raw Makino tags into one clean, governed schema your AI agent already understands. One MCP call, no per-machine integration project.
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 Makino 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.
Forge normalizes Makino telemetry into Forge's canonical field set, the same 366 canonical fields used across all 18 manufacturers. Point Forge at the machine, pass oem: "makino", and spindle speed is spindle_speed_rpm whether it came from a Makino controller or anything else on the floor.
Confirmed canonical fields your agent gets from Makino machines, drawn from Forge's 16,908-mapping corpus:
| Raw tag in | Canonical field out | Meaning | |
|---|---|---|---|
| spindle_rpm_act: 15000 | → | spindle_speed_rpm: 15000 | actual spindle rpm |
| sp_load: 48 | → | spindle_load_pct: 48 | spindle load |
| nc_prog: "MAK-77" | → | program_name: "MAK-77" | NC program |
| feed_act: 1100 | → | feed_rate: 1100 | actual feed |
No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Makino data:
Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.