6 River Systems canonical data model: connect your 6 River Systems equipment to any AI agent

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

Forge turns raw 6 River Systems tags into one clean, governed schema your AI agent already understands. One MCP call, no per-AMR integration project.

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

Paste your 6 River Systems data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your 6 River Systems data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why 6 River Systems data is hard to integrate

Fleet state (battery, pose, velocity, e-stop) is published over ROS 2 topics or a proprietary REST fleet API, and no two vendors agree on the topic names.

Typical 6 River Systems equipment communicates over HTTP / REST, 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 6 River Systems AMR

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

HTTP / RESTROS 2 (DDS)

91%Field coverage

10Canonical autonomous mobile robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for 6 River Systems

Confirmed canonical fields your agent gets from 6 River Systems AMRs, drawn from Forge's 3,444-mapping corpus:

amr.battery.chargeamr.battery.voltageamr.battery.chargingamr.position.xamr.position.yamr.position.thetaamr.velocity.linearamr.velocity.angularamr.operating_modeamr.safety.estop

Sample normalization

Raw tag in		Canonical field out	Meaning
battery_pct: 76	→	amr.battery.charge: 76	battery %
pose_x: 5.2	→	amr.position.x: 5.2	pose X
lin_vel: 0.9	→	amr.velocity.linear: 0.9	linear velocity
mode: "MOVING"	→	amr.operating_mode: "MOVING"	operating mode