Industrial Intelligence System

The brain behind industrial automation.

Nexus reads the logic, configuration, and documentation behind your machines and reasons over all of it, in plain English, cited to the exact rung. It is where Nodeblue's research into operational intelligence runs on a working floor.

Request access
Validated

4,386 real PLC project files parsed, zero parser errors.

Cross vendor

Rockwell, Siemens, Ignition, and the CODESYS family, plus 500+ more brands through PLCopen.

Deployment

On premise and air gap capable, with a persistent memory of the operation.

Ask it something hard.

Three questions off a real plant floor. Nexus runs the same tools an engineer would, against the live controller, and shows its work. Pick one and watch the trace.

NexusDiagnose live
Live controller
Question

A production line went down right after a product changeover. Why is it down, and where do we start?

Tools, live controller
correlate_trace_tag Filler2/FillWeight to Program:Filler.FillWeight
read_live_tag FillWeight 48.2 g, setpoint 50.0 g, out of band
diagnose_tag fault latches in rung 31, regulator check not cleared
Answer

The line is down because rung 31 latched the fill fault, and it latched because the regulator check in rung 29 never cleared after the changeover. That rung needs RegPressure at 42 psi before filling can arm, and it is reading 33 live. The logic and the changeover are fine. The feed skid is not building pressure, so the fault is the regulator or its supply, not the filler.

Every answer cites the source it came from

SCADA shows you the line went down. It has never understood the program behind it.

SCADA is the eyes of your operation: it acquires live values, and when something breaks it flashes an alarm. Working out why still falls to whoever can read the program, and on most floors that is one person, one retirement away. Nexus is the brain: it reads the logic, configuration, and documentation behind every value, and reasons over the whole thing.

LINE 3 OVERVIEWALARMSPEED 122PRESS 33.1

SCADA, the eyes

  • Acquires and visualizes tag values, trends, and alarms.
  • Flashes an alarm when the line stops or a machine faults.
  • Assumes a human is reading and knows what it means.
R31ROOT CAUSEInfeed_PE blocked 3.0 slatched Jam_Alarm · R31

Nexus, the brain

  • Reads the PLC logic, device configs, manuals, and history behind every value.
  • Traces the fault through nested logic and names the root cause, cited.
  • Assumes an agent in the loop, and answers for the operation itself.

Built to model everything the operation knows about itself.

Operations do not have a model problem, they have a context problem. Nexus gathers the right engineering context on demand, so answers come from your actual equipment behavior, not generic internet knowledge.

PROGRAMSDEVICESLIVE DATADOCUMENTSHISTORYRECORDSQUERYCONTEXTNEXUS ENGINEEXACT. CITED. REPRODUCIBLE.AI AGENTS · ANY LLMUNDERSTANDDIAGNOSEDOCUMENTGENERATEVERIFYQUESTIONCITED ANSWER
Programs

PLC logic, AOIs, structured text, SCADA views

Devices

Controllers, robots, drives, cameras, I/O

Live data

OPC UA reads, subscriptions, alarms

Documents

Manuals, specs, descriptions, device configs

History

Work orders, faults, jams, OEE

Records

MES, ERP, WMS, and CMMS

The layer SCADA never had.

Point an agent at your operation and it can do the work that used to wait on the one engineer who remembered how the system fit together.

Understand

Ask what a 3,000-rung legacy program actually does and get a plain-language answer, cited to the rung.

TONR14

Document

Generate routine descriptions, I/O lists, and tag documentation from the code itself.

Correlate

Follow a signal from the operator screen through OPC to the rung that drives it, both sides at once.

Diagnose live

Read the running controller, pair the live value with the logic, and name the blocking root cause, cited to the rung.

SP 42.033.1 PSIPT ≥ SPREG_OK33.1 < 42.0OFF

Generate

Scaffold an AOI, routine, or script from a description, as a reviewable artifact you approve, never auto-applied.

Verify the docs

Flag where the site's own specification contradicts the logic that is actually running.

Continuous learning

Nexus holds a persistent, on-premise memory of your operation and never stops building it. Every export, fault, answer, and correction sharpens the next one, so the system gets more useful the longer it runs, and it flags a source the moment it goes stale.

What it gives back, role by role.

The knowledge that runs an operation is trapped in vendor tools and a few senior heads. Nexus makes all of it instantly answerable, by anyone, with receipts.

Engineering

Understand any program without the engineer who wrote it.

Trace a tag to its root cause in about 150 milliseconds, not an afternoon of grepping exports. The answer comes back cited to the exact rung.

Maintenance

Know why the line is down right now.

Nexus pairs the live value with the logic and names the blocking root cause. Downtime is dollars per minute, and the first place to look should not be a guess.

Operations

Know if the line is hitting its numbers.

Throughput, rates, and downtime against target, answered from the live line instead of a report that lands after the shift ends. When the numbers slip, Nexus points at where.

Quality and assurance

Keep defects inside the margin.

Defect and scrap data tied back to the process values and logic that produced it. When quality drifts, you get the cause while parts are still on the line, not a surprise in the audit.

Trace any signal end to end.

The correlation engine walks a screen binding through its OPC path into the controller and back. When something misbehaves, Nexus explains where the state started, not just where it surfaced. Every hop is named, every claim is cited.

SCADAwhat the operator seesOPCthe path between worldsPLCwhere the value is bornScreens/Scale2DetailScale2/PackWeight486 g[Line2]Program:Scale.PackWeightScale_ControlMUL LoadCell_RawPackWeight →LIM PackWeightTON 3sLPack_At_ScaleWeight_Fault142231
NexusRoot cause · Scale_Control, rung 31

Weight_Fault latched on rung 31: a pack was on the scale and its weight stayed out of tolerance for 3 seconds. That weight is the same PackWeight the screen shows as 486 g. It is born at the load cell on rung 14 and reaches the screen over OPC - one signal, traced end to end.

Validated on real industrial data, not synthetic demos.

Nexus is tested where it has to work: real production controllers pulled straight off live production floors, including exports too large to open in any chatbot. Not toy demos, and not numbers we made up.

4,386
PLC files parsed, zero errors

Real exports from live operations, spanning Rockwell, Siemens, Ignition, and the CODESYS family.

11 / 11
Frontier models corrected

Every model failed to tell which live controller edit was actually running. With Nexus underneath, all eleven got it right, cited to the rung.

~17x
Fewer tokens per answer

About 9.5x faster than a frontier model grepping the raw export, and the identical cited answer on every run.

137 / 137
Documents graded rung-accurate

Zero errors found by three independent Controls Engineers grading every document against the running logic.

From the review notes
“It breaks down the functionality to each rung. Even through nested AOIs, it never lost track of a variable. That’s the part I didn’t expect it to get right.”
We hired three independent Controls Engineers with no stake in Nexus to grade the program documentation it wrote, all 137 documents, rung by rung against the running logic. They found zero errors. The line above is from one of their reviews.

Built in the open

Nexus started in the open. The early connectors the engine was built on are public under MIT, so any engineer can see exactly how we handle SCADA access, PLC parsing, and cross-system correlation. The connectors that ship in Nexus today have gone well beyond them, deeply engineered and in-house, but the open originals are still how we show we do not hide behind a black box.

Why it holds up

Positioned where a bigger model cannot follow.

Yes, you ask Nexus a question in plain English and it answers. That part is easy, and everyone has it. What makes the answer right is underneath: a deterministic engine that reads the logic exactly, reaches the live controller, and cites what it used. Point a frontier model at a raw export and it is confidently wrong. Put the same model on top of Nexus and it is right, every run.

01

Determinism is trust

The engine resolves the logic the same way every time, so the same question comes back with the same cited answer on every run. A system that is right most of the time is not one you hand a maintenance tech at 2am with the line down.

02

Live access to the floor

Reading a running controller and diagnosing a live fault is physical, on premise, safety-gated work. No context window touches it.

03

The document to logic join

Linking your own specs, manuals, and tickets to the live model, and flagging contradictions, compounds with every document. Pure retrieval cannot.

04

Neutral and on premise

One standard for breadth, air-gap capable by default. The deployment shape defense, utilities, and pharma actually buy.

Cross vendor by design

Studio 5000 and RSLogix 5000, Siemens TIA Portal and STEP 7, Ignition, and the CODESYS family directly, plus one PLCopen parser reaching 500+ OEM brands. Current IDEs and the legacy ones still running plants. A vendor is a module, not a rewrite.

Studio 5000 / RSLogix 5000Siemens TIA Portal / STEP 7NewIgnitionCODESYS family500+ OEM brands via PLCopen

One system, released in stages, all available today.

From the engine to the full operation, the brain behind every engineering and operations decision in your facility. Each release is useful on its own, and builds on the one before.

v0.1

The engine

Deterministic comprehension across Studio 5000 and RSLogix 5000, Siemens TIA Portal and STEP 7, Ignition, and the CODESYS family, plus read-only live diagnosis. Built and validated on real production data.

v0.2

Connected intelligence

One view over the whole operation: every controller, device, and server, logic currency and health, top faults and OEE, watch and alert on any tag.

v1.0

Full industrial intelligence

Every device on the wire, every manual and spec ingested, operations and engineering together, anomaly agents, and document versus logic verification across the whole site.

Get into Nexus

See it on your own operation.

The product demo at nexus.nodeblue.ai is locked while we onboard by hand. Request access, or book a walkthrough and we will run Nexus against a project like yours.

We read every request by hand. No newsletter, no spam.