PLC · ALLEN-BRADLEY LOGIX
2,461 mappings·1,027-field schema·ISA-95 categorized·deterministic
Rockwell tags are whatever the integrator named them, which makes this the hardest vendor to curate and the most honest one to report on.
Fanuc and SunSpec have vendor-defined names. ControlLogix does not: the tag database is authored by whoever commissioned the line. Conveyor1_Speed_FPM, BearingTemp_DegC and Discharge_PSI are conventions, not a specification, and the next plant will have named them differently.
So we will not claim exhaustive Rockwell coverage. The pack currently carries 43 curated tags: the naming patterns seen most often, with units embedded in the name parsed and converted. Tags outside that set fall to the signal layer, which resolves on structure and unit evidence, or are reported unresolved by name. An unresolved tag reported honestly is worth more than a confident wrong mapping.
Unit suffixes in the tag name are parsed and converted: _PSI to kPa, _GPM to L/min, _FPM to m/s, and the conversion is reported.
| Raw vendor tag | Canonical field | ISA-95 category | |
|---|---|---|---|
| BearingTemp_DegC | → | bearing_temperature | equipment_condition |
| Compressor_PSI | → | pressure_kpa | equipment_performance |
| Conveyor1_Speed_FPM | → | conveyor_speed_m_s | equipment_performance |
| Coolant_Flow_GPM | → | flow_rate_lpm | equipment_performance |
| Efficiency_Pct | → | pump_efficiency_pct | production_performance |
Every row above is produced by the shipping engine, not written by hand. This page fails to build if any of them stops resolving to the field shown.
Resolution is a lookup, not an inference. A tag is matched against a curated corpus of 2,461 confirmed vendor mappings; only if that misses does it fall to weaker layers: a normalized fold that strips unit suffixes and separators, then a signal classifier that reads structure and unit evidence. Each layer carries a lower confidence, and the layer that answered is named in the response. A mapping you disagree with is visible rather than buried.
Below a confidence threshold the engine abstains. An evidence gate refuses a match it cannot justify and reports the tag unresolved, by name, with the score and the reasons, because a wrong field at high confidence is far more expensive than an honest miss. Six read-time validators then check what survives: sentinel detection, physics bounds, stuck sensors, dropout, operating mode and correlation.
Units are converted to SI where the source unit is known, and every conversion is reported with its factor. A value that fails a physics bound is nulled with the bound it violated attached, not silently dropped.
It does not invent fields. A tag outside the corpus that the signal layer cannot justify comes back unresolved and counted, and those names feed the roadmap for the next pack rather than a plausible guess in your data. It is a translation layer, not a historian: it holds no time series and replaces no SCADA system. And the container is a sandbox: it ships the deterministic layers and the canonical schema, not the production embedding, research and corpus-learning layers.
No key, no account, no sales call. The sandbox runs locally and answers with the same canonical schema production does.
Send your actual ControlLogix tag list. What resolves, resolves; what does not comes back named, counted and unresolved, and those names feed the corpus roadmap directly.
Unresolved tags from real deployments are what the next pack is built from. See platform licensing for embedding the canonical data model in your own product, or pricing for usage-based API access.