VERSION 0.1 — DRAFT SPECIFICATION

One object model for everything OT.

Process control, functional safety, cybersecurity, alarm management, and the AI layer — usually five separate concerns — modeled as one consistent, addressable system, from a single sensor to the AI that adjusts the process.

lunex-object-model.svg
LunexObject «abstract» Device Interlock Zone Sensor CtrlUnit Actuator one base class — sixteen sub-models built on it
01 — What LUNEX is

Five standards, one gap between them.

PackML describes machine state behavior. ISA-88 describes batch structure. ISA-95 describes the enterprise-to-control hierarchy. IEC 61508/61511 describe functional safety. IEC 62443 describes cybersecurity. ISA-18.2 describes alarm management. Each is authoritative in its own scope — and none of them talk to each other, or to the AI layer that's now a first-class part of the system, not an add-on.

LUNEX doesn't replace any of them. It reuses what each already gets right — SIL, SIF, Security Levels, ISA-18.2's alarm states — and provides the missing part: one object model, from a single sensor up to the closed-loop AI model adjusting the process, built on a single base class throughout.

  • Completeness over minimalism. Process control, safety, security, alarms and AI/data as one connected model, not five bolted together.
  • Reuse before invention. A term is only renamed when it already collides with something else in the model. Sub-model 8 documents every decision.
  • One base class, no exceptions. A pressure sensor and an AI-generated recommendation are both a LunexObject.
  • AI as a structural citizen. Digital twins, prediction, and closed-loop control — governed with the same rigor as a safety interlock.
02 — The specification

Sixteen sub-models, four layers.

Each layer builds on the one before it. Foundation defines the object system; capability adds safety, security and data; operator layers add real-time judgment; the autonomous layer adds memory and closed-loop action.

01–04 Foundation what an object is, where it lives, how it behaves
01
Object / Class Model
LunexObject, five universal device classes, function-interfaces
object-model.svg
02
Asset Hierarchy / Namespace
Realm → Domain → Location → Area → Cell → System → Assembly
asset-hierarchy.svg
03
Topology Model
Integrated, Point-to-Point, Star, Mesh — plus HA and Cloud flags
topology-model.svg
04
Behavioral / State Model
the universal state machine behind every object
state-model.svg
05–08 Capability safety, security, data — and the register that keeps it honest
05
Safety
Interlock as a first-class object, SIF Assemblies, IEC 60204-1
safety-model.svg
06
Security
Zone, Conduit — IEC 62443
security-model.svg
07
Data / AI Layer
Telemetry Envelope, Context Layer, Digital Twin
data-ai-model.svg
08
Naming & Terminology
the living register of every naming decision, and why
naming-model.svg
09–13 Operator capability status, alarms, guidance, awareness — in real time
09
Collective Status (Rollup)
severity tiers, worstTier, bubbling up a hierarchy
rollup-model.svg
10
Alarm Management
ISA-18.2 — priority = severity × actionability
alarm-model.svg
11
Alarm Response Guidance
reusable response procedures, per alarm type
arp-model.svg
12
Scenario Simulation
tested on the digital twin before an operator commits
scenario-model.svg
13
Situational Awareness
one navigation contract, jumpToWorst()
sa-model.svg
14–16 Autonomous layer memory, prediction, and closed-loop AI — all governed
14
Historian & Analytics
what the state was, not just what it is
historian-model.svg
15
Predictive Maintenance
predictions join the alarm system; changes always need approval
predictive-model.svg
16
Closed-Loop AI Control
an AI model as an ordinary, bounded Control Unit
ai-control-model.svg
"Rename a term only when it already carries a conflicting meaning elsewhere in the model, or in an adjacent standard LUNEX must interoperate with. Otherwise, reuse established vocabulary — inventing a new word is not innovation if the old one wasn't actually broken."
— The naming principle, Sub-model 8. Every renamed term in LUNEX is tested against this one sentence.

Early draft. Built to be argued with.

LUNEX is authored by a single contributor and hasn't been reviewed by an independent working group yet. If you work in OT, process safety, or industrial cybersecurity and see something wrong, missing, or overcomplicated — that's more useful right now than agreement.

Read the spec (PDF) View on GitHub