FoundryNet / OEMs / Hitachi Seiki

CNC / MACHINE TOOL · CANONICAL DATA MODEL

Hitachi Seiki canonical data model: connect your Hitachi Seiki equipment to any AI agent

Routed: OEM coverage in development·1,031-field schema·12 protocols

Forge turns raw Hitachi Seiki 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 Hitachi Seiki data and see what Forge returns.

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


The problem

Why Hitachi Seiki data is hard to integrate

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 Hitachi Seiki equipment communicates over MTConnect, Modbus TCP. 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 Hitachi Seiki today

Passing oem: "hitachi" routes the request to the CNC vertical, which turns on that vertical's cross-vertical gate. Forge has no Hitachi Seiki-specific mappings yet: Hitachi Seiki tags resolve only where they match names Forge already knows for that vertical. 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. OEM coverage is in development.

MTConnectModbus TCP
Routed: OEM coverage in developmentProd support tier
CNCRoutes to vertical

Canonical CNC / machine tool fields in Forge's registry (all present on prod). Which Hitachi Seiki 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 Hitachi Seiki 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 Hitachi Seiki 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": {"spindle_rpm": 4200, "sp_load_pct": 63, "active_prog": "HITACHI-01"}, "oem": "hitachi"}'

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 Hitachi Seiki fits

Protocols
MTConnect Modbus TCP

Vertical
CNC / machine tool

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

Same protocols, other industries
Yaskawa Motoman Universal Robots Chemical process Food & beverage process

Also searched as hitachi, hitachi seiki


Hitachi Seiki 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.