RAIN / Resources

Useful advice.Clear boundaries.

How RAIN approaches separation from plant controls, evaluated model changes and evidence for operator review.

Design principles · simulation stage

INTELLIGENCE BELONGS WHERE THE DATA LIVES.

01 / THE IDEA

Begin with what the system may do.

RAIN reads operational telemetry and produces advisories. Equipment control and safety systems remain separate. This boundary shapes the product: a model can suggest something to inspect, while the operator retains authority over any action.

01

Read-only by design

Define a telemetry connection that cannot issue equipment commands. Review that boundary for each proposed site before a pilot begins.

02

Updates have to earn promotion

The simulator compares a candidate with the incumbent on held-out data. A rejected candidate does not replace the active model; its evaluation still belongs in the history.

03

Evidence travels with advice

Model versions and recorded events give operators context for an advisory. A history of model changes supports investigation without making the model a safety controller.

02 / IN PRACTICE

Put the thinking into practice.

Define the scope, preserve the boundary, and make the outcome something a person can inspect.

  1. 01

    Set the permitted use

    Name the operational question, the telemetry source and who reviews advisories. Keep equipment actuation outside the integration.

  2. 02

    Challenge the assumptions

    Include missing signals, stale readings and changing operating conditions in the proposed evaluation. Agree when an output should be withheld or reviewed.

  3. 03

    Verify at the site

    Test signal quality, alert usefulness and sustained operation on the target hardware. Simulation results alone cannot establish field readiness.

03 / A FEW DETAILS

Worth understanding.

Is RAIN a plant safety system?

No. It is an observe-only intelligence system under development. Existing control systems, safety procedures and operator responsibilities remain separate.

Does a signed history certify the system?

No. Recorded history is evidence to inspect. RAIN does not claim a safety certification, and hardware-backed signing remains unfinished product work.

BUILD WITH RAIN

One site. One question.
A useful next step.

RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.

Build your pilot brief