CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

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

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

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

The problem

Why Fanuc data is hard to integrate

Fanuc controllers expose data through the FOCAS library and PMC addresses. Spindle speed, load and part counts come back as opaque register reads (PMC_R, D-addresses) that mean nothing to an AI agent until they're named.

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

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

MTConnectOPC UAModbus TCP

99%Field coverage

17Canonical CNC / machine tool fields

3,444Corpus mappings

Field coverage

What Forge resolves for Fanuc

Confirmed canonical fields your agent gets from Fanuc 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_Speed: 2200	→	spindle_speed_rpm: 2200	FOCAS actual spindle speed
spd_load: 85	→	spindle_load_pct: 85	spindle load %
actual_feed: 1200	→	feed_rate: 1200	actual cutting feed
prg_num: 1042	→	program_number: 1042	active O-program

30-second deployment

Add Fanuc to your agent with one call

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

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

# normalize raw Fanuc telemetry into the universal schema

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

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

-d '{"data": {"Spindle_Speed": 2200, "spd_load": 85, "actual_feed": 1200}, "oem": "fanuc"}'

{"spindle_speed_rpm": 2200, "spindle_load_pct": 85, "feed_rate": 1200, "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 Fanuc fits

Protocols
MTConnect OPC UA Modbus TCP

Vertical
CNC / machine tool

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

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

Also searched as ge_fanuc, ge fanuc, fanuc cnc

Fanuc 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 Modbus TCP vs MQTT / Sparkplug B