Lumina 1.4 is here — smarter root cause reasoning and faster evidence indexing.

Incident intelligence OS

Incident intelligence for production lines

Lumina opens the case around live signals, linked evidence, approved recovery, and plant memory before the incident repeats.

See Platform

WorkspaceEvidenceActionsMemory

Live signal windowCase opened

PLCPT-IMM-02

QualityQH-2184

MemoryMLD-CR-104

Likely cause

Cavity pressure fell 208 bar below learned baseline.

Pressure: 612 bar
Deviation: -208 bar
State: Case opened

Agent activityNow

SensePT-IMM-02 crossed learned pressure envelope
QualityShort-shot risk rising in same window
WorkspaceIncident case opened with first trace

Case stateSignal live

Incident opened

Lumina is holding the signal window while evidence sources attach.

PLC pressure traceshort-shot defect spikecheck-ring wear note

Incident intelligence OS

The operating layer for production incidents

Lumina connects live machine signals, operator notes, maintenance history, and verified fixes so teams move from alert noise to shared operational memory.

Production incidents rarely live in one system.

A pressure drop may start in the PLC, appear as defects in quality data, get explained in a maintenance note, and only become useful after a supervisor approves the fix. Lumina connects those fragments into one incident case.

Signal awareLive OT signals are structured and monitored so drift is detected before it becomes a defect.

Context firstLive signals, notes, quality holds, and maintenance history are gathered before the team starts investigating.

Evidence groundedRecommendations carry the signal trace, record, note, or prior incident that shaped them.

Memory that compoundsVerified fixes become reusable operating knowledge instead of disappearing after shift handoff.

OverviewEvidenceGraphActionsRecoveryMemory

Live eventSignal deviation detected

M-IMM-02 cavity pressure fell 208 bar below learned baseline. Lumina opens a case instead of leaving another loose alarm.

Cavity pressure612 bar-208 below baseline

Pressure612 bar

Deviation-208 bar

StateCase opened

Governed agents

Four agent jobs.
One incident workspace.

Lumina agents do not operate as isolated chatbots. They work on the same case object with shared evidence, approval state, and memory.

Current handoffSense

Signal captured

INC-ERL-MOULD-SHORTSHOT / M-IMM-02Shared incident workspace

Signal capturedSense opened the case from a pressure drift on M-IMM-02 and attached the first signal evidence.

Status: Signal captured
Owner: Sense
Confidence: 42%

PT-IMM-02 below learned baseline
Vision event attached
Incident case opened

Signal detectedEvidence packingCause ranking queued

Sense AgentSignal detection

Signal captured

Detects drift across live signals and links the first evidence.

monitors signal deviation
detects anomaly clusters
attaches PLC or camera context

Explore Sense

Intelligence AgentCause ranking

Ranking

Ranks likely causes from evidence, traces, and prior cases.

builds evidence pack
compares prior incidents
explains confidence

Explore Intelligence

Act/Control AgentGoverned recovery

Gated

Stages recovery actions for human approval.

drafts response plan
links SOP or work order
records approval trail

Explore Act/Control

Memory AgentPlant memory

Storing

Stores resolved incidents as reusable operational memory.

archives pattern
links verified outcome
improves future investigations

Explore Memory

Context layer

Signals, evidence, and prior context become one operational layer.

Lumina connects OT signals, historian data, SAP PM records, quality evidence, operator notes, and approved fixes into one governed incident case.

INC-ERL-MOULD-SHORTSHOTSignal intakeM-IMM-02 / pressure recovery

OT SOURCESLive signals

Machine signals, historian windows, and industrial protocols.

Siemens S7PLC tags

MQTTSparkplug B

RockwellPLC events

AVEVA

AVEVA PIhistorian

InfluxDBtime-series

Timescalehistorian SQL

EVIDENCE SYSTEMSOperational evidence

Maintenance, quality, notes, logs, and system records.

SAP PMwork history

PostgreSQLMES records

MySQLquality tables

Splunkevent logs

CMMS

CMMSmaintenance

NOTE

Operator notesshift context

Lumina Context LayerOperational intelligence compiler

Signal intake

Live plant data enters one case.

Lumina normalizes OT tags, historian windows, protocol streams, and machine events into an incident object.

UNS path mappedIncident case openedEvidence objects linkedRecovery state trackedFuture match enabled

OT sources7

UNS paths4

Open caseM-IMM-02

PRIOR CONTEXTResolved knowledge

A compact reference, not the full plant-memory story.

INC

Prior pressure case0.86 similar

FIX

Approved fixMLD-CR-104

Verified outcomepressure restored

WORKFLOW OUTPUTSGoverned action

Approval-ready work produced from source-linked context.

Work orderMLD-CR-104

APV

Supervisor approvalrequired

SOP

SOP updateattached

AUD

Audit trailrecorded

Field notes

Thinking from the incident intelligence floor.

View all field notes

Incident playbook6 min

Why recurring line stops rarely have one cause

Production incidents look simpler than they are. A single pressure drop involves signal drift, a quality hold from two shifts ago, a maintenance note nobody indexed, and a fix that worked once but was never written down. Here is how to separate those layers before you act.

Read article

Governed agents7 min

What agents should be allowed to do in a plant

Autonomous action in a production environment is not a software question — it is a governance question. How approval loops, escalation paths, and audit trails turn agents from liabilities into assets that shift leads actually trust.

Read article

Plant memory4 min

The shift handoff problem and what it costs

At every shift change, production knowledge moves from one person's head to another's — imperfectly. What gets lost, how repeated incidents trace back to this gap, and what structured plant memory changes about the economics of downtime.

Read article

Common questions

Straight answers to important questions.

01Does Lumina replace SCADA?

No. Lumina sits above SCADA, historians, MES, and CMMS as an incident intelligence layer. Those systems stay in place while Lumina connects their evidence into one investigation workspace.

02Can it run on-prem?

03Are agent actions automatic?

04Do we need labeled data?

05What does a pilot look like?

06How does Lumina handle production data security?

07Is Lumina GDPR compliant?

08What compliance certifications does Lumina have?

09Can Lumina run on our own infrastructure?

Bring one incident. We show the command layer.

See how Lumina turns your evidence into intelligence that prevents the next one.

One line
One recurring incident
Your evidence sources

See Platform

Incident intelligence for production lines

The operating layer for production incidents

Production incidents rarely live in one system.

Four agent jobs.One incident workspace.

Signals, evidence, and prior context become one operational layer.

Live plant data enters one case.

Thinking from the incident intelligence floor.

Why recurring line stops rarely have one cause

What agents should be allowed to do in a plant

The shift handoff problem and what it costs

Straight answers to important questions.

Bring one incident. We show the command layer.

Four agent jobs.
One incident workspace.