Connect without taking control
Scope a read-only path from site telemetry to the node. Existing plant control and safety systems retain their own responsibilities.
RAIN / Hardware
The planned home for local compute, storage, and read-only equipment connectivity. Configure the node around the question your site needs to answer.
Concept under validation
01 / THE IDEA
RAIN Node is the hardware direction behind the on-site architecture. The software loop currently runs against a battery-storage simulator. A field pilot will establish the equipment, environmental requirements, and operating envelope for a physical deployment.
Scope a read-only path from site telemetry to the node. Existing plant control and safety systems retain their own responsibilities.
Plan local resources for inference, candidate training, and evaluation. Workload measurements should determine the configuration.
Define local retention for telemetry, model versions, and recorded outcomes. Storage needs follow signal volume and the agreed review period.
02 / IN PRACTICE
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
Start with one asset and an observable condition, such as a battery module running warmer than its neighbors.
Identify signals, access permissions, connectivity constraints, and the equipment that must remain outside the learning loop.
Measure the intended workload and agree how signal quality, stability, and operator usefulness will be assessed.
03 / A FEW DETAILS
A production configuration and general availability have not been announced. The next step is a scoped pilot conversation, not a hardware checkout.
The local inference and learning loop is designed to operate without runtime network egress. Production uplink transport remains unfinished work; a pilot must define its full network boundary.
BUILD WITH RAIN
RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.