CNC / MACHINE TOOL · TELEMETRY NORMALIZATION
16,908 confirmed mappings·18 OEM families·14 protocols·99% field coverage
Forge turns raw Okuma tags into one clean, governed schema your AI agent already understands. One MCP call, no per-machine integration project.
Okuma's THINC-API is powerful but proprietary: SpindleRPM, SpLoadPct and MainPrg are exposed as THINC objects that each app has to translate before an agent can use them.
Typical Okuma 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 Okuma telemetry into Forge's canonical field set, the same 366 canonical fields used across all 18 manufacturers. Point Forge at the machine, pass oem: "okuma", and spindle speed is spindle_speed_rpm whether it came from a Okuma controller or anything else on the floor.
Confirmed canonical fields your agent gets from Okuma machines, drawn from Forge's 16,908-mapping corpus:
| Raw tag in | Canonical field out | Meaning | |
|---|---|---|---|
| SpindleRPM: 4500 | → | spindle_speed_rpm: 4500 | THINC spindle rpm |
| SpLoadPct: 66 | → | spindle_load_pct: 66 | spindle load |
| MainPrg: "OKU_45.MIN" | → | program_name: "OKU_45.MIN" | main program |
| PartsMachined: 1780 | → | part_count: 1780 | parts machined |
No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Okuma 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.