INDUSTRIAL ROBOT · CANONICAL DATA MODEL

Stäubli canonical data model: connect your Stäubli equipment to any AI agent

2,086 mappings·19 verticals·13 protocols

Forge turns raw Stäubli tags into one clean, governed schema your AI agent already understands. One MCP call, no per-robot integration project.

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

Paste your Stäubli data and see it normalized in 30 seconds. No POC required.

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

The problem

Why Stäubli data is hard to integrate

Joint angles, TCP pose, payload and safety bits are buried behind vendor-specific system variables and controller SDKs, so a single robot cell can take weeks to expose over a common schema.

Typical Stäubli equipment communicates over OPC UA, ROS 2 (DDS), PROFINET / S7. 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 Stäubli robot

Forge resolves Stäubli telemetry into Forge's canonical field set, the same 985 canonical fields defined, used across 45 vendor packs. Point Forge at the robot, pass oem: "staubli", and spindle speed is spindle_speed_rpm whether it came from a Stäubli controller or anything else on the floor.

OPC UAROS 2 (DDS)PROFINET / S7

45OEM packs in production

11Canonical industrial robot fields

2,086Mappings in production

Field coverage

What Forge resolves for Stäubli

Confirmed canonical fields your agent gets from Stäubli robots, drawn from Forge's 2,086-mapping corpus:

robot.joint.positionrobot.joint.velocityrobot.joint.effortrobot.joint.currentrobot.joint.temperaturerobot.tcp.poserobot.tcp.speedrobot.tcp.forcerobot.payloadrobot.moderobot.safety.status_bits

Sample normalization

Raw tag in		Canonical field out	Meaning
joint_1_deg: 37.4	→	robot.joint.position: 37.4	joint 1 angle
tcp_speed: 250	→	robot.tcp.speed: 250	TCP speed
payload_kg: 7.5	→	robot.payload: 7.5	payload
op_mode: "AUTO"	→	robot.mode: "AUTO"	operating mode

30-second deployment

Add Stäubli to your agent with one call

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

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

# normalize raw Stäubli telemetry into the universal schema

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

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

-d '{"data": {"joint_1_deg": 37.4, "tcp_speed": 250, "payload_kg": 7.5}, "oem": "staubli"}'

{"robot.joint.position": 37.4, "robot.tcp.speed": 250, "robot.payload": 7.5, "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 Stäubli fits

Protocols
OPC UA ROS 2 (DDS) PROFINET / S7

Vertical
industrial robot

Other industrial robot vendors
ABB Robotics KUKA Universal Robots Fanuc Robotics Yaskawa Motoman Doosan Robotics

Same protocols, other industries
DMG Mori Fanuc Heidenhain Mazak

Also searched as staubli, stäubli, cs9, val3