Beyond Purdue

Beyond Purdue  /  an authority model for industrial control

Purdue sorts devices by where they sit. Beyond Purdue sorts them by what they are allowed to do.

Eight laws decide who is allowed to act on a plant. Protection comes first and stays hardwired. The operator decides. Data lives in small, named, independent nodes, and the data diode keeps every lane one way.

1  The main principle

The Laws of Authority

A lower-numbered law always overrides a higher one, as in Asimov's laws of robotics. Everything else on this site follows from them.

Meta-law

No level acts outside these laws.

  1. Law Zero

    Protection

    No harm to people or the environment, by action or inaction. Nothing is allowed to weaken protection. A lock outranks every level.

  2. First Law

    Independence

    If every level above fails, protection still acts.

  3. Second Law

    Obedience

    The controller obeys the operator, unless that breaks Law Zero or the First Law.

  4. Third Law

    Self-preservation

    The machine protects itself, but people come first.

  5. Fourth Law

    The gate

    Out channels carry data out, in channels carry commands in. They never mix and never originate an action.

  6. Fifth Law

    The record

    Data nodes process, store and present data on demand. They record every command, permit, lock and bypass. They grant no access and take no action.

  7. Sixth Law

    The human decides

    The operator can always ignore, override or stop any advice.

  8. Seventh Law

    See everything, touch nothing

    AI analyzes, interprets and supports. It reaches an actuator only through a human decision.

  9. Eighth Law

    Authority flows down only

    Information rises, authority descends. Failure never grants authority.

Who is allowed to do what

Six levels, sorted by authority rather than by network position.

LevelAuthorityAllowed toNever allowed to
L0Protection and isolationAbsoluteTrip. Veto over every level. Hold the lock.Be overridden, or depend on any other level.
L1ControllerActsActuators, within its logic and protection limits. Shouts every command it executes.Act outside protection limits.
L2ChannelsGatekeeperWhat crosses, and in which direction. Every level speaks only through L2. Data diodes, passive by preference.Originate a command. Mix data and commands.
L3Data nodesHolds and servesNothing. It processes, stores and presents data on demand, and holds every command given and executed.Grant access. Act on the plant. Pass a command.
L4OperatorDecidesCommands to controllers, each one shouted to L3 as given. Override and stop of any advice.Disable protection.
L5AIVoice, no voteNothing. It analyzes, interprets and supports the operator.Touch an actuator.

Only L0 and L1 touch the process. L4 is the operator. L5 is the AI. Protection stays hardwired.

2  Data in independent nodes

Every signal is a small page of its own

Data does not live in one big database. Each signal, asset or record is an independent node with its own name, its own data and its own meaning. All that follows is a result of it.

The nodes are the L3 Data nodes of the data plane. They hold and serve; they command nothing. The technology works with the humans: DNS, IPv6, multicast and OPC UA, all of it familiar.

Drawing D: the data plane as a name space
Drawing D. The data plane as a name space.
hp-steam.u1.plant.example          the node
10LBA10CT001.kks.plant.example     alias: KKS code
te114.vendor.plant.example         alias: vendor tag
hp-steam-temp.hmi.plant.example    alias: HMI name
asset-20417.cmms.plant.example     alias: asset number

dd01.u1.plant.example              a data diode
asset-4711.cmms.plant.example      alias of dd01

3  Names and asset management

Naming is always the big issue

Every node has a DNS-style name, because people already read names like these. Aliases let every name a plant already uses find the same node.

A name is updated automatically when a node is born, by a person, or by a shout from equipment. Every data diode is named the same way, as an asset.

At least two copies

Every node lives on different hardware, power and rooms. Both copies listen to the same shouts, so losing one loses nothing.

Commands leave two marks

Every command is recorded as given by the operator and as executed by the controller. The record grants nothing; it remembers.

People work inside the plant

Maintenance is part of operation. While someone works, L0 holds the lock, and no level commands a locked machine.

4  The enabler

The levels hold because the diode holds

The isolator lets light pass one way only, so data and commands cannot mix. A passive data diode has no power, no firmware and nothing to configure. It is as predictable as a relay or a padlock.

Each diode is an L3 asset with a name. dd04 and dd05 carry data to the readers on two separate paths; commands come in on their own lane, dd11.

Drawing M: the enablers, every data diode is a named asset
Drawing M. The enablers: every data diode is a named asset.

The Works

The whole model, in order

The narrated video and the overview slides follow the same order: the laws, the nodes, the names, then everything else. The documents carry the full wording and sources.

Start here

Beyond Purdue and the diode

The channel idea, the passive data diode, and why isolation works where detection cannot.

The newsletter

Three at random

A different three on every visit, from all 54 stories from real plants: legacy that still works, data diodes explained without jargon, and the cost of trusting the wrong layer.