INDUSTRIAL ROBOT · CANONICAL DATA MODEL

ABB Robotics canonical data model: connect your ABB Robotics equipment to any AI agent

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

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

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

The problem

Why ABB Robotics data is hard to integrate

ABB IRC5/OmniCore exposes joint angles and load through RAPID persistents and the Robot Web Services API (CJointT.rax_1, MechUnitLoad) that no agent understands without a map.

Typical ABB Robotics equipment communicates over OPC UA, EtherNet/IP, PROFINET / S7, ROS 2 (DDS). 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 ABB Robotics robot

Forge resolves ABB Robotics 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 robot, pass oem: "abb", and spindle speed is spindle_speed_rpm whether it came from a ABB Robotics controller or anything else on the floor.

OPC UAEtherNet/IPPROFINET / S7ROS 2 (DDS)

99%Field coverage

11Canonical industrial robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for ABB Robotics

Confirmed canonical fields your agent gets from ABB Robotics robots, drawn from Forge's 3,444-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
CJointT.rax_1: 42.7	→	robot.joint.position: 42.7	joint 1 angle (deg)
MechUnitLoad: 3.1	→	robot.payload: 3.1	mechanical unit load (kg)
OpMode: "AUTO"	→	robot.mode: "AUTO"	operating mode
MotorTemp1: 51	→	robot.joint.temperature: 51	axis 1 motor temp

30-second deployment

Add ABB Robotics to your agent with one call

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

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

# normalize raw ABB Robotics telemetry into the universal schema

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

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

-d '{"data": {"CJointT.rax_1": 42.7, "MechUnitLoad": 3.1, "OpMode": "AUTO"}, "oem": "abb"}'

{"robot.joint.position": 42.7, "robot.payload": 3.1, "robot.mode": "AUTO", "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 ABB Robotics fits

Protocols
OPC UA EtherNet/IP PROFINET / S7 ROS 2 (DDS)

Vertical
industrial robot

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

Same protocols, other industries
DMG Mori Fanuc Heidenhain Mazak

Also searched as abb, irc5, omnicore, abb robot