Simulation · Synthetic data

Investigate a Factory Event

Follow one machine problem from the alarm to the lesson the factory keeps.

  1. Factory event
  2. Context
  3. Evidence
  4. Expert knowledge
  5. Investigation
  6. Human decision
  7. Memory

The workflow in 30 seconds

From machine event to factory memory.

BR-204 · RUNNING
Synthetic demo
01Factory
REC · smart glasses

Capturing how an expert actually works

Synthetic demo
02Expert capture
Machine event
Operator note
Maintenance
Machine data
Procedure
NEOBRAIN
Synthetic demo
03Brain
Event
Investigation
Decision
Lesson learned

THE FACTORY REMEMBERS

Synthetic demo
04Learning
02What happened?
What you are seeingA reactor ran too hot for 7 minutes.
Reactor BR-204 in warning state
ATTENTION

17 SEP 2026 · 14:37

BR-204

TEMPERATURE DEVIATION

What happened?

Temperature exceeded the expected operating range for 7 minutes. KNOWN

14:37

TEMP_DEV_HI — 37.1 °C vs 34.0 °C target. Out of range for 7 minutes.

KNOWN
Every statement is labelled:KNOWNOBSERVEDINFERREDUNKNOWN
01

Looking for what happened before

14 relevant records3 historical events2 maintenance records1 operator observation2 procedures

Finding related records…

03What do we know?
What you are seeingThe records around the problem: machine data, work orders, shift notes.

Evidence graph

Connect the dots.

The Brain links what happened on the factory floor with the evidence around it.

BR-204

Temperature deviation

Direct: Measured on the event itselfCorroborating: Independent record pointing the same wayContextual: Background that explains, but does not prove
Every statement is labelled:KNOWNOBSERVEDINFERREDUNKNOWN

14

linked records

3

historical parallels

1

unresolved knowledge gap

04Who knows about it?
What you are seeingWhat an experienced technician has seen that the systems never recorded.
HUMAN KNOWLEDGESIMULATION · SYNTHETIC DATA

What the person who knows this machine says.

Synthetic portrait of technician Jens Müller

Jens Müller

Senior Production Technician

17 years experience

Jens has worked with BR-204 for 11 years.
214 batches supervised · 31 interventions logged on this asset

“BR-204 tends to recover slowly after cooling-loop maintenance.”

OBSERVED — UNVERIFIEDAn operator observation — not established fact.
First-person frame from the simulated capture sessionREC

SOURCE · CAPTURED SESSION

Captured during a simulated operator session.

Smart glasses · BR-204 inspection · 14:52 · 3 min 12 s

Why does this matter?

The Brain found that two previous events occurred after cooling-system maintenance — the same pattern Jens describes.

KNOWN The two events are on record.INFERRED That they share a cause with this one is not confirmed.

QR-2291 · Mar 2025

Slow recovery on BR-204 after cooling-loop actuator swap.

EV-1187 · Nov 2024

Temperature drift 2 days after cooling-system flushing.

Jens · observation · 2026QR-2291 · 2025EV-1187 · 20241 possible pattern
Human experienceEvidenceValidationOrganizational memory
KNOWLEDGE AT RISKSIMULATED KNOWLEDGE-RISK SCENARIO

Important knowledge exists. It just doesn't live anywhere yet.

Jens has operational knowledge about BR-204 that is not currently represented in the approved procedure.

Synthetic portrait of technician Jens Müller

Jens Müller

Senior Production Technician

17 years experience

Knowledge
BR-204 cooling behaviour after maintenance
Current state
OBSERVED — experienced technician
Documented
Partially
Validated
No
Used in
3 historical investigations
Risk
Knowledge depends on one experienced person
Capture it.
Validate it.
Connect it.
Reuse it.
CAPTURE THIS KNOWLEDGE
02

What does the evidence suggest?

05What does the evidence suggest?
What you are seeingA possible explanation based on the records. Not a confirmed cause.
INFERRED — NOT CONFIRMED

Recent cooling-system maintenance may have contributed to slower temperature recovery.

UNKNOWNRoot cause has not yet been confirmed. An actuator stroke test is needed.

Why?

03

What should happen next?

INFERRED Suggestions from the Brain. A person decides.

Verify cooling-loop response
Review valve actuator
Compare with previous maintenance event
04

What did we decide?

06What did we decide?
What you are seeingAn engineer reviews the evidence and makes the call.
Engineer reviewing the finding
Finding under reviewINFERRED

"Recent cooling-system maintenance may have contributed to slower temperature recovery."

What should happen next?

AI finding

Inferred — not confirmed

Human decision

Waiting for engineering…

Organizational memory

—

NeoFabrik does not replace the person making the decision. It shows them the evidence and keeps a record of what they decided.

07What did we learn?
What you are seeingThe lesson is saved, so the next shift does not start from zero.

05 · What did the factory learn?

The investigation becomes a record.

Step 1

Investigation

14 records read

Step 2

Engineering review

waiting

Step 3

Memory record

not written

No lesson written yet.

A memory record is only created after a person decides what the evidence means.

Go to engineering review

BR-204 operational memory

Every number below is a count of stored records. Open a tile and the records themselves appear — no scores.

Your factory just learned something.

NeoFabrik makes sure the next person doesn't have to learn it the hard way.

Synthetic demonstration · records shown are simulated for BR-204

NeoBrain logo
A product of NeoFabrik / XRPK Solutions

NeoFabrik

CVR: 37261637

Løjtegårdsvej 97c, 1.74, 2770 Kastrup, Denmark

Phone: +45 20 53 32 51

NeoBrain v0.4_pilotPlant Status: Online