LUNEX is an open reference model that connects the standards you already use. One base object, 21 sub-models, one shared language — from a single sensor to the AI that adjusts the process. Ready for what comes next.
Control, safety, security, alarms and recipes were each written on their own, and none of them was written for AI. So the plant works, but its description does not. Every project pays for that, in meetings, in translation and in rework. LUNEX answers the question once, in the open.
Control, safety, security and data teams point at the same objects, with the same names.
Every change follows one lifecycle: who, what, why, approved by whom.
Access, vulnerabilities, incidents and zones are related, so you can see what a finding touches.
AI works within set limits and never overrules an interlock.
Open and free to use under CC BY 4.0. Use it as a tender checklist or an internal standard.
Let one engineer compare it with how your plant is described today. What fits, what is missing, what would need to change: whatever the outcome, you learn something about your own structure.
Layered Unified Namespace for Entities & eXtensibility
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.
LunexObject.Each band builds on the one before it. Foundation defines the object system; Safety & Security and the cross-cutting band add governed structure on top of it; the operator band adds real-time judgment; the autonomous band adds memory and closed-loop action. Five sub-models — Recipe & Execution, Identity & Access Management, Vulnerability & Patch Management, Security Incident Response, Management of Change — were added to the original sixteen without disturbing any of them.
"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."
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.