A critical incident is left without a technician

Goal Warn the maintenance manager as soon as a critical incident has no technician.

A CMMS exports its incidents as CSV. The conveyor on the gummy candy line has stopped, with no technician. The CMMS warns no one.

a Workflow tracks each incident's status
a Process flags the critical unassigned incident
one decision only; the assignment moves it forward.

lumnik Open
Manufacturing
Maintenance
Connector
Workflow
Process

incidents-declared.csv

incident_id,line_id,line_name,equipment_id,equipment_name,severity,status,technician_id,reported_at,summary
INC-2026-0042,CANDY-LINE-07,Gummy candy moulding line,CNV-07-TRANSFER,Transfer conveyor,CRITICAL,DECLARED,UNASSIGNED,2026-10-19T06:15:00Z,Transfer conveyor stopped and the moulding line cannot discharge trays

incident_id	line_id	line_name	equipment_id	equipment_name	severity	status	technician_id	reported_at	summary
INC-2026-0042	CANDY-LINE-07	Gummy candy moulding line	CNV-07-TRANSFER	Transfer conveyor	CRITICAL	DECLARED	UNASSIGNED	2026-10-19T06:15:00Z	Transfer conveyor stopped and the moulding line cannot discharge trays

evidence: incidents-declared.csv · transform v1

calibration.csv

incident_id,line_id,line_name,equipment_id,equipment_name,severity,status,technician_id,reported_at,summary
CAL-0001,CANDY-LINE-00,Calibration line,EQ-CAL-01,Calibration conveyor,CRITICAL,ASSIGNED,TECH-CAL,2026-10-19T05:00:00Z,Critical severity domain witness
CAL-0002,CANDY-LINE-00,Calibration line,EQ-CAL-02,Calibration motor,INFO,DECLARED,TECH-CAL,2026-10-19T05:01:00Z,Declared status domain witness
CAL-0003,CANDY-LINE-00,Calibration line,EQ-CAL-03,Calibration sensor,INFO,ASSIGNED,UNASSIGNED,2026-10-19T05:02:00Z,Unassigned technician domain witness

manifests/10-incidents.yaml

apiVersion: connectors.lumnik.io/v1kind: Connectormetadata:  name: scenario-gmao-incidents  connector_type: csv-file  scopes: [maintenance]spec:  transport:    kind: local    path: /tmp/lumnik-scenario/gmao-candy-line-incident/incidents.csv  parser:    has_header: true  after_process: none  refresh:    max_removed: "off"

$ lm validate -f manifests/10-incidents.yaml
✓ 10-incidents.yaml — valid

$ lm apply -f manifests/10-incidents.yaml -o json
{
  "name": "scenario-gmao-incidents",
  "connectorId": "e9f784ee-d05c-4756-adc4-a0e239684a0d",
  "endpointsApplied": 1
}

$ lm connector run scenario-gmao-incidents
run scheduled: 918c8c2b-f165-4559-86ee-801e290b5d2e

$ lm run get 918c8c2b-f165-4559-86ee-801e290b5d2e
ID        CONNECTOR                    ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
918c8c2b  scenario-gmao-incidents      default   Completed  3   3    0        0             2026-10-28 17:14  2026-10-28 17:14  no

manifests/20-incident-workflow.yaml

apiVersion: apps.lumnik.io/v1kind: Workflowmetadata:  name: scenario-gmao-incident-lifecyclespec:  scope: maintenance  provenance: declared  on:    table: connector.t_scenario_gmao_incidents    column: status    key: incident_id  dormancy:    after: 1m  states:    - code: DECLARED      label: Declared      initial: true    - code: ASSIGNED      label: Assigned    - code: IN_PROGRESS      label: In progress    - code: RESOLVED      label: Resolved    - code: CLOSED      label: Closed      terminal: true

$ lm workflow apply -f manifests/20-incident-workflow.yaml -o json
{
  "name": "scenario-gmao-incident-lifecycle",
  "scope": "maintenance",
  "table": "connector.t_scenario_gmao_incidents",
  "column": "status",
  "dataTruth": {
    "undeclared": [],
    "unobserved": [
      "IN_PROGRESS",
      "RESOLVED",
      "CLOSED"
    ],
    "nullOrBlank": 0,
    "tableMissing": false,
    "keyColumnMissing": false,
    "keyNullOrBlank": 0,
    "checkUnavailable": false,
    "unavailableReason": null,
    "dueProblem": null,
    "invalidOrderValues": null,
    "keysWithSeveralRows": null,
    "columnsUnverified": []
  }
}

manifests/30-unassigned-critical-process.yaml

apiVersion: apps.lumnik.io/v1kind: Processmetadata:  name: scenario-gmao-critical-unassignedspec:  scope: maintenance  on:    event: data.row.changed    table: connector.t_scenario_gmao_incidents  when:    - severity=CRITICAL    - status=DECLARED    - technician_id=UNASSIGNED  emit:    type: decision.gmao-critical-unassigned    message: "Critical incident {incident_id}: {equipment_name} stopped on {line_name}; no technician is assigned"

$ lm process apply -f manifests/30-unassigned-critical-process.yaml -o json
{
  "name": "scenario-gmao-critical-unassigned",
  "table": "connector.t_scenario_gmao_incidents",
  "emit": "decision.gmao-critical-unassigned"
}

$ lm connector run scenario-gmao-incidents
run scheduled: 0ce7bdc1-aadf-40b9-83e9-64e15e34149b

$ lm run get 0ce7bdc1-aadf-40b9-83e9-64e15e34149b
ID        CONNECTOR                    ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
0ce7bdc1  scenario-gmao-incidents      default   Completed  1   1    0        0             2026-10-28 17:14  2026-10-28 17:14  no
• 2 row(s) removed — the source no longer holds them

$ lm inbox
ID     WHEN      PROCESS                                MESSAGE                                                                                                             ENTITY_KEY
20195  just now  scenario-gmao-critical-unassigned      Critical incident INC-2026-0042: Transfer conveyor stopped on Gummy candy moulding line; no technician is assigned  eec42296b829179a0aef09aafbd52bd1fb2a72983d66e5b507f2748c393ac404

$ lm observations list --limit 1000
WORKFLOW                              DOC            STATE      SINCE             ALERTED
scenario-gmao-incident-lifecycle      INC-2026-0042  DECLARED   2026-10-28 17:14

incidents-assigned.csv

incident_id,line_id,line_name,equipment_id,equipment_name,severity,status,technician_id,reported_at,summary
INC-2026-0042,CANDY-LINE-07,Gummy candy moulding line,CNV-07-TRANSFER,Transfer conveyor,CRITICAL,ASSIGNED,TECH-SMARTIN,2026-10-19T06:15:00Z,Transfer conveyor stopped and the moulding line cannot discharge trays

$ lm connector run scenario-gmao-incidents
run scheduled: efa05ac5-d29f-4cbb-8bab-4f39d84546fe

$ lm run get efa05ac5-d29f-4cbb-8bab-4f39d84546fe
ID        CONNECTOR                    ENDPOINT  STATUS     IN  OUT  SKIPPED  DEAD-LETTERS  STARTED           ENDED             EVALUATED
efa05ac5  scenario-gmao-incidents      default   Completed  1   1    0        0             2026-10-28 17:14  2026-10-28 17:14  no

$ lm observations list --limit 1000
WORKFLOW                              DOC            STATE      SINCE             ALERTED
scenario-gmao-incident-lifecycle      INC-2026-0042  ASSIGNED   2026-10-28 17:15  

$ lm inbox
ID     WHEN      PROCESS                                MESSAGE                                                                                                             ENTITY_KEY
20195  just now  scenario-gmao-critical-unassigned      Critical incident INC-2026-0042: Transfer conveyor stopped on Gummy candy moulding line; no technician is assigned  eec42296b829179a0aef09aafbd52bd1fb2a72983d66e5b507f2748c393ac404

$ lm observations transitions --workflow scenario-gmao-incident-lifecycle --doc INC-2026-0042
WORKFLOW                              DOC            FROM      TO        ENTERED           OBSERVED          IN_FROM_S
scenario-gmao-incident-lifecycle      INC-2026-0042  DECLARED  ASSIGNED  2026-10-28 17:14  2026-10-28 17:15  5

Limits

Read-only: no assignment written back to the CMMS.
Process flags. It does not dispatch or remind anyone.
Dormancy threshold declared, dormancy alert not shown.
Synthetic data.

Maintenance · CMMS

A conveyor stops. The manager is not told.

Critical incident, declared, no technician.

Gummy candy moulding line.

Fictional plant · synthetic data

The problem

The CMMS records. It does not alert.

The incident is in the CSV export.
No technician is assigned.
The maintenance manager does not know.

Nothing is changed

The CMMS stays as it is.

lumnik reads the export.
It does not write to the CMMS.
The rule is declared in lumnik.

What had to be written

when:
  - severity=CRITICAL
  - status=DECLARED
  - technician_id=UNASSIGNED

Three conditions, one decision.

The whole scenario fits in 3 declaration files, 57 lines.

What the manager receives

One decision, only one.

Decision inbox

Critical incident INC-2026-0042: Transfer conveyor stopped on Gummy candy moulding line; no technician is assigned

Real message, replay of 28 October 2026.

The next export

Technician assigned. No second alert.

The incident moves from DECLARED to ASSIGNED.
lumnik observes the move.
The Process stays silent.

The limits

lumnik flags. People act.

No assignment written to the CMMS.
No technician dispatched or reminded.

Try it

The scenario replays end to end.

Export, declaration, decision, assignment: each step is published with its output.

This scenario runs on lumnik Open, free and open source.

Try lumnik Open →