CNC / MACHINE TOOL · CANONICAL DATA MODEL

DMG Mori canonical data model: connect your DMG Mori equipment to any AI agent

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

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

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

The problem

Why DMG Mori data is hard to integrate

CELOS machines speak MTConnect and OPC UA, but tag names shift between CELOS versions and underlying Fanuc/Siemens cores, so a fleet of DMG Mori machines rarely presents one consistent schema.

Typical DMG Mori 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 DMG Mori machine

Forge resolves DMG Mori 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: "dmg", and spindle speed is spindle_speed_rpm whether it came from a DMG Mori 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 DMG Mori

Confirmed canonical fields your agent gets from DMG Mori 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
SpindleActualSpeed: 8000	→	spindle_speed_rpm: 8000	CELOS actual speed
SpindleLoad: 71	→	spindle_load_pct: 71	spindle load
NCProgram: "PART_A.NC"	→	program_name: "PART_A.NC"	NC program
FeedActual: 950	→	feed_rate: 950	actual feed

30-second deployment

Add DMG Mori to your agent with one call

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

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

# normalize raw DMG Mori telemetry into the universal schema

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

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

-d '{"data": {"SpindleActualSpeed": 8000, "SpindleLoad": 71, "NCProgram": "PART_A.NC"}, "oem": "dmg"}'

{"spindle_speed_rpm": 8000, "spindle_load_pct": 71, "program_name": "PART_A.NC", "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 DMG Mori fits

Protocols
MTConnect OPC UA

Vertical
CNC / machine tool

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

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

Also searched as dmg_mori, dmg, mori seiki, mori_seiki, celos