Data arrives
Sensors, laboratory systems, historians and business systems describe what they believe is happening.
Independent Elemenos IPA standalone governance architecture that also integrates with Elemenos Adapt and third-party industrial systems.
Olerib Vision™
The governance gate between a decision and physical action.
Olerib Vision checks whether a requested industrial action is permitted and whether the available evidence supports it before local control executes. It does not replace the PLC, SCADA, DCS, operator or independent safety system.
01REQUESTHuman · software · AI
→02OLERIBPolicy + identity + evidence
→03LOCAL CONTROLPLC executes · safety may veto
DENY / ESCALATEThe problem in plain language
Industrial systems can recommend and execute—but who checks whether the action is actually allowed?
Data, recommendations, operator approval and control execution are normally separate activities. Olerib adds a governed checkpoint between the proposed action and physical execution.
Someone proposes an action
An operator, control application, optimisation service or AI suggests a change.
Olerib checks permission
Identity, policy, requested action, current state, route and available reality evidence are evaluated together.
Local control decides execution
A permitted request still passes PLC permissives and allocated safeguards. A denied or incomplete request does not proceed.
A concrete example
A request to open a transfer valve.
The same pattern applies to a setpoint change, recipe transition, route change, remote request or AI-generated recommendation.
01RequestOpen valve V-204 to receiver B
02IdentityIs this actor and role permitted?
03PolicyIs the action allowed in this state?
04RealityRoute, receiver and physical state supported?
05DecisionPermit, deny or escalate—with reason
06ExecutionPLC checks local permissives and acts
| Question Olerib asks | Example evidence | If the evidence is false or missing |
|---|---|---|
| Is the requester authorised? | Identity, role, session and approved action class | Deny or accountable escalation |
| Is the requested route permitted? | Released configuration, valve route, receiver identity and capacity | Deny; keep the transfer isolated |
| Does physical reality support the request? | Sensor witness, equipment feedback and relevant passive Vision observation | Deny or request new evidence |
| Are local protections ready? | PLC permissives, route feedback and allocated SIS / ESD state | Local control blocks; safety retains veto |
| Can the decision be reconstructed? | Request, evidence version, policy version, result, reason and time | No governed release |
What the product consists of
Olerib governs. Vision observes. Foresight advises. Local control executes.
The names describe different responsibilities. Keeping them separate is the point of the architecture.
Olerib
Deterministic governance engineEvaluates the requested action against the applicable policy, identity, context and evidence. Produces a permit, deny or escalation decision with a reasoned record.
No generic process or final-element actuationVision
Passive visual verificationUses an independent, read-only camera-based observation layer to compare visible physical reality with the expected operating state where that evidence is relevant.
No PLC writes · no feedback control · no setpoint changesForesight
Bounded deterministic advisoryEvaluates a small, frozen future horizon around a questioned signal and can propose advice. Its output is evidence for review—not permission and never a plant command.
Advises only · cannot authorise or executeWitness record
Decision traceabilityLinks the request, source data, reality evidence, applicable policy, configuration version, decision, reason and available outcome evidence.
Reviewable evidence; retention and security require project designLocal automation
PLC · HMI · SCADA / DCSReceives a governed release where implemented, applies local permissives and executes the normal sequence through the engineered control system.
Physical execution remains localSIS / ESD
Independent protectionRetains its allocated trip, veto or de-energise authority and does not wait for Foresight, Olerib or cloud connectivity.
Not replaced by digital governanceOlerib Foresight · 3 × 3
Three critical signals. Three discrete future steps. One bounded advisory.
Foresight is designed to add collective context without turning the advisory layer into an optimiser or controller. The active application defines the three signals and the approved deterministic model used for the bounded evaluation.
3 × 3T + 1T + 2T + 3
Signal 1Bounded stateBounded stateBounded state
Signal 2Bounded stateBounded stateBounded state
Signal 3Bounded stateBounded stateBounded state
Evaluate collectively
Use the approved context around the event: related signals, active Kit/configuration, route, current state and evidence quality.
Judge locally
Return advice only for the questioned signal or action. Do not globally optimise or silently move multiple control variables.
Require a clearly better case
A candidate advisory must satisfy the frozen decision rules and evidence threshold; uncertainty or conflict does not become approval.
Record the basis
The input snapshot, model/configuration version, result and reason remain linked so the advisory can be replayed and reviewed.
What a customer gets
A visible reason for every governed decision.
The value is not another dashboard. It is a defined authority boundary and an evidence package that can be reviewed by operations, engineering, safety, quality and audit roles.
| Customer need | Olerib contribution | Required project evidence |
|---|---|---|
| Control AI and optimisation recommendations | Treat every recommendation as an unauthorised request until policy and reality evidence support it | Approved action classes, policy rules, interfaces and negative testing |
| Prevent invalid remote or operator actions | Verify identity, role, current state and the exact requested action before release | Access-control design, operating procedures and accountable escalation |
| Detect belief-versus-reality mismatch | Combine control-system evidence with independent Vision observation where suitable | Camera coverage, observation criteria, validation and failure response |
| Explain why an action was allowed or blocked | Create a structured decision record tied to source evidence and policy version | Time, identity, retention, cyber-security and record-integrity design |
| Integrate without replacing the plant controls | Provide a bounded governance interface above or around the existing automation | Released interface contract, cause/effect, FAT / SAT and site acceptance |
Can / cannot
Clear authority boundaries.
OLERIB CAN
- Evaluate a specific request against deterministic policy
- Use identified evidence and context in that evaluation
- Permit, deny or escalate through a defined interface
- Record the decision basis for later review
- Integrate with existing industrial data and control environments
OLERIB CANNOT
- Replace the PLC, SCADA, DCS or independent safety system
- Turn an advisory output into automatic plant authority
- Invent missing physical evidence or assume stale data is valid
- Guarantee cyber-security, safety integrity or regulatory compliance by architecture alone
- Directly drive a valve, motor or other final control element
Olerib evaluatesVision observesForesight advisesPLC executesSIS / ESD may veto
Independent intellectual property
Olerib Vision is its own product and patent family.
It originated while Elemenos Adapt was being developed, but it is not limited to Elemenos equipment. The governance architecture can be engineered as a standalone layer, integrated with third-party control environments or embedded in a new EPC project.
| IP / product | Primary subject | Relationship to Elemenos Adapt | Public status |
|---|---|---|---|
| Olerib Vision™ | Deterministic governance and execution-authorisation boundary | Governs selected Adapt requests and can also be deployed independently | Independent IP · patent pending |
| Vision™ | Passive visual reality-verification subsystem | Optional independent observation source where the project validates it | Subsystem of Olerib Vision |
| Olerib Foresight | Bounded advisory evaluation across three evidence horizons | Advises Olerib; has no permission or process-write authority | Controlled architecture · release evidence required |
Application areas
Where Olerib Vision is relevant.
These are target environments where proposed actions may need a defined policy, evidence and authorisation check before execution. They are not claims of completed deployments, certification or suitability for a particular safety function.
Critical infrastructure
National infrastructure systems: power grids, water networks, transport control and telecommunications; nuclear generation, fuel processing, enrichment and waste handling.
Energy & power systems
Thermal, renewable and distributed generation; power distribution; upstream oil and gas, midstream transport and downstream refining.
Chemical processing
Specialty and industrial chemistry, batch and continuous plants, hazardous-material and reaction management; pharmaceutical and aseptic manufacturing.
Industrial AI deployments
AI-assisted operations in physical-process environments and regulated AI environments such as finance, healthcare and defence.
Water & destruction systems
Municipal and industrial water treatment; PFAS destruction, hazardous-waste treatment and environmental remediation.
Regulated process industries
Food and beverage processing; semiconductor and precision manufacturing.
Mining & hydrometallurgy
Critical minerals, solvometallurgy, rare-earth recovery and acid-based extraction.
Autonomous & remote systems
Remote operations, distributed and offshore assets; defence and sovereign infrastructure.
Deployment context
Born inside Elemenos Adapt. Applicable beyond Elemenos equipment.
Olerib Vision originated from the need to govern Kit changes, routes and execution in Elemenos Adapt. Its authority model can also be engineered around third-party industrial systems where a separate execution-governance boundary is needed.
| Deployment | How Olerib is used | What remains local |
|---|---|---|
| Elemenos Adapt | Govern Kit identity, released recipes, route evidence and requested transitions | Module PLCs, HMI, physical equipment and allocated protection |
| Existing industrial plant | Add a governed checkpoint around selected action classes and evidence sources | Existing PLC / SCADA / DCS and safety architecture |
| New EPC project | Engineer the authority and evidence boundary into the project interfaces from the start | Project control, protection, procedures and accountable operations |
Olerib Vision™
Explore the dedicated Olerib site—or see its place in the Elemenos ecosystem.
The dedicated site explains the broader product origin, architecture, Vision subsystem and industrial application context. The Elemenos Digital Ecosystem page shows how Olerib relates to Runtime, Foresight, connected services and local plant authority.