Choose the question
For example: why does one battery module run warmer than its neighbors under similar load? Define who would inspect the result and what evidence would help.
RAIN / Resources
A practical starting point for defining a RAIN design-partner pilot: data access, operating boundaries and evidence of usefulness.
Planning for a first field pilot
01 / THE IDEA
A pilot should resolve a specific uncertainty. Start with a question an operator already cares about, then work backward to the signals, access and evaluation needed to answer it. RAIN’s current evidence is from a simulated battery plant; the first real site is the next validation step.
For example: why does one battery module run warmer than its neighbors under similar load? Define who would inspect the result and what evidence would help.
List available measurements, sampling intervals, units, timestamps and equipment identifiers. Identify missing context and who can authorize read-only access.
Consider signal quality, alert usefulness, stable operation and operator review effort. Set the observation period and review criteria before the trial.
02 / IN PRACTICE
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
Capture the site, asset, operational question, telemetry sources and access boundary. The downloadable template keeps these decisions together.
Agree hardware needs, installation constraints, data retention and review responsibilities. Identify which integration work is still required.
Compare results against the original criteria. Document both useful observations and failures before deciding whether to refine, extend or stop the trial.
03 / A FEW DETAILS
No. The brief is a local planning document. It does not send an inquiry, reserve hardware or create a deployment agreement.
No. Hardware configuration and commercial terms depend on the agreed pilot scope. Production specifications and a standard deployment package have not been established.
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.