FoundryNet / Verticals / process / batch
Vertical

Process / Batch telemetry, one schema

Every process / batch vendor names the same measurement differently. Forge maps 3 of them into one canonical field set so your agent reads one shape.

3OEMs in this vertical
4protocols in this vertical
985Canonical fields defined
Start free All protocols

Coverage

3 process / batch OEMs

OEMVerticalProtocolsCoverageMapped
Chemical processprocess / batchOPC UA Modbus TCP MQTT Sparkplug B BACnet/IP96%10 fields
Food & beverage processprocess / batchOPC UA Modbus TCP MQTT Sparkplug B BACnet/IP96%10 fields
Pharma process (GMP)process / batchOPC UA Modbus TCP MQTT Sparkplug B BACnet/IP96%10 fields

Mappings

Same field, different vendors

One real example per vendor: the clearest illustration of why a per-vendor parser does not scale.

Raw tag inCanonical field outSource
RX_PRESS: 3.4→process.reactor.pressure_bar: 3.4Chemical process
CIP_STATE: "RINSE"→process.cip_state: "RINSE"Food & beverage process
BATCH_ID: "LOT-2291"→process.batch_id: "LOT-2291"Pharma process (GMP)

Protocols

How process / batch equipment is read

OPC UA (3) Modbus TCP (3) MQTT Sparkplug B (3) BACnet/IP (3)


Canonical fields

Shared across process / batch equipment

process.agitator_rpmprocess.batch_idprocess.cip_stateprocess.flow_rateprocess.jacket.temp_cprocess.level_pctprocess.phprocess.phase_stateprocess.reactor.pressure_barprocess.reactor.temp_c

Full schema: FoundryNet/canonical-schema (MIT, all 985 fields).

Get the thesis behind this infrastructure: The Machine Agent, weekly.