FoundryNet / OEMs / DMG Mori

CNC / MACHINE TOOL · CANONICAL DATA MODEL

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

OEM-specific corpus coverage·1,031-field schema·12 protocols

Forge turns raw DMG Mori tags into one governed schema your AI agent can read, and says plainly which tags it could not map.

Try it free: 3 machines, no credit card → See it work →

Paste your DMG Mori data and see what Forge returns.

Read-only. Forge reads your DMG Mori data through standard industrial protocols. It does not write to the machine unless you deploy and enable the bridge.


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 cost again.


Coverage on prod

What Forge supports for DMG Mori today

Forge's corpus has DMG Mori-specific tag mappings (corpus tag dmg_mori), so DMG Mori tags are matched against DMG Mori's own rows before anything generic. Passing oem: "dmg_mori" routes the request to the CNC vertical, which turns on that vertical's cross-vertical gate. Every mapping says how it was made in match_type; a tag no layer can place comes back abstained instead of forced onto a field.

MTConnectOPC UA
OEM-specific corpus coverageProd support tier
CNCRoutes to vertical

Canonical CNC / machine tool fields in Forge's registry (all present on prod). Which DMG Mori tags reach them depends on the tag; Forge does not force a mapping.

spindle_speed_rpmspindle_load_pctspindle_current_ampsaxes.0.position_actualaxes.0.load_percentaxes.0.temperature_cfeed_ratecnc.path.feedrateprogram_nameprogram_numberpart_counttool_idmachining_statealarm_code

Source: prod /v1/coverage and /health, read 2026-10-27 (build 238a6b3). Forge does not publish a per-OEM coverage percentage, so this page does not show one.


Try it

Send DMG Mori data to Forge

Connect the MCP server, or call the REST API directly:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'
# normalize raw DMG Mori telemetry into the canonical schema
curl -s https://forge.foundrynet.io/v1/normalize \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"data": {"SpindleActualSpeed": 8000, "SpindleLoad": 71, "NCProgram": "PART_A.NC"}, "oem": "dmg_mori"}'

The response lists each tag's canonical field, match_type and confidence. Tags Forge cannot place come back abstained, and physically impossible values come back as null with a reason.

Start free: Forge API, 3 machines → See the full demo →

Related

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


DMG Mori in the canonical schema

For platforms Want this normalization inside your platform? License the engine and ship cross-vendor support as your own feature. 1,031-field canonical schema, 2,478 mappings, your brand. Platform licensing →
Why does a cross-vendor canonical data model matter? The Machine Agent breaks it down weekly. Read it →
Get the thesis behind this infrastructure: The Machine Agent, weekly.