Nexus Foundry watches a live or replayed plant feed, marks the intervals worth a second look, and answers a question about any window you select. Every answer carries citations you can follow back and check.
Six widget regions on a grid. Select any region to see what it holds and where its contents come from.
Default layout
Illustration. The layout is the shipped default. The values are synthetic.
The tags the operator is holding in view for this shift, on one time axis. Shaded bands mark intervals worth a closer look. Dragging across the plot selects the window everything else on the board then refers to.
Shown live, or replayed from a past shift.
Supporting signals from the same equipment, kept on a second stack so the primary view stays readable. They share the time axis above, so a feature in one lines up with the other.
Shown live, or replayed from a past shift.
Conditions the system has been configured to raise. Severity arrives as a token the operator can act on. Alerts are advisory, and the plant's own alarm system still owns safety notification.
Configured with your team during commissioning.
Intervals that look worth a closer look but do not rise to an alert. A finding points at a window and leaves the judgement call to the operator. Opening one loads that window across the board.
Surfaced automatically as the shift runs.
A question about the selected window, or an empty request to explain it. The answer is assembled from what the system can actually show you, and every claim in it is checked before you see it.
Answered on-premise. No plant data leaves the site.
Select a region. Arrow keys move between them.
Five steps, in the order a shift actually runs. The console is organized around this sequence.
Live or replayed trends on the widget grid. Feed mode, source, and lag are shown on the banner at all times.
A shaded highlight band, or an alert. Severity arrives as a token the operator can act on.
Open the window on its own. Check the tags and the data quality before drawing a conclusion.
Drag a region and type a question about what the plant was doing in that window.
Acknowledge the alert, or save the window for deeper work. Nothing is written back to the plant.
A plant keeps its knowledge in separate systems that rarely line up with one another. Nexus Foundry integrates those levels of plant information into a single, holistic picture of the plant, and the AI reasons over that picture when it answers a question about your process.
Nexus Foundry is advisory. It sits beside the systems of record.
Not a historian
Long-term storage stays with the plant's historian. The console holds only a short live window.
Not a DCS or alarm system of record
Alerts are advisory. The plant's alarm system still owns safety notification.
Not the running controller
The console never presents its view of the control system as live controller state.
No control writes
The console does not trip, interlock, or set a setpoint. It runs on-premise, and your plant data stays in your environment.
We will walk you through the board and scope what a deployment on your plant looks like.