Load & electrical context
Approved historian exports of current, voltage, power, equipment identifiers, and operating state. Establish units and timestamp alignment before comparison.
SCOPED INPUT · HUMAN REVIEWRAIN / Power & Utilities
See the asset.Keep the grid in context.
Explore a read-only review of transformer loading, temperature, and maintenance history. Give an asset engineer a coherent event to investigate across scattered operating records.
Proposed application
INTELLIGENCE BELONGS WHERE THE DATA LIVES.
THE POWER & UTILITIES QUESTION
Which asset needs a closer look before the next maintenance window?
THE INPUTS THAT MATTER
Read the right signals.
Choose a source to see the context it adds to this proposed review.
Thermal behavior
Available winding or oil temperature and ambient measurements. Compare a specific asset under similar load and weather conditions.
SCOPED INPUT · HUMAN REVIEWWork-order history
Inspection dates, cooling-system work, and known sensor issues provide explanations that a trend alone cannot establish.
SCOPED INPUT · HUMAN REVIEWAN OPERATING PATTERN WORTH EXPLORING
A transformer’s temperature rises under familiar load.
An asset engineer wants to understand a recurring thermal excursion. A proposed pilot would align the existing historian and maintenance records for one transformer.
Power & utilities / PILOT SCENARIO01 — REVIEW NOTES
Inspect the pattern.
Separate high ambient temperature, missing telemetry, a changed cooling state, and a recurring load-adjusted deviation into inspectable hypotheses.
Bring it to the operator.
The engineer checks the underlying event and decides whether it warrants inspection through the utility’s existing maintenance process.
Illustrative investigation. RAIN has not been connected to a utility network or validated on transformer data.
Power & utilities / PROPOSED WORKFLOW
From operating context to review.
- 01
Choose an asset boundary
Start with one transformer or facility asset and approved exported history. Record the data owner and review owner.
- 02
Align the operating context
Match timestamps, loading, ambient conditions, and equipment states. Mark gaps instead of inventing missing observations.
- 03
Review a thermal episode
Present the observed departure alongside comparable periods and related maintenance notes.
- 04
Close the evidence loop
Record the engineer’s assessment and any later inspection findings. Evaluate usefulness before widening the scope.
WHAT A PILOT SHOULD PROVE
Define useful
before you measure it.
Suggested evaluation criteria. Set the baseline and acceptance thresholds with the sector team before a trial.
- 01Usable event coverage
- The share of review windows containing aligned load, temperature, and equipment-state records.
- 02Engineering review yield
- The proportion of surfaced events the asset team finds worth investigating, including reasons for dismissal.
- 03Evidence assembly time
- Time needed to reconstruct an event with the pilot versus the current historian and work-order workflow.
THE OPERATING BOUNDARY
Be precise about the scope.
Outside protection and switching
The proposed review does not change relays, protection settings, dispatch, or switching. Operational authority stays in existing utility systems.
An approved OT connection
Use a site-reviewed data path with explicit permissions and network boundaries. A local computer alone does not establish OT security.
RESEARCH & CONTEXT
The thinking behind
this use case.
Primary sources reviewed September 2026. These explain the sector context; the scenario and pilot measures are RAIN proposals, not reported customer results or source endorsements.
- 01
U.S. Department of Energy
Power System Data AnalyticsExplains why sensor quality, synchronized context, and operator-facing information matter in utility analytics.
- 02
NIST
Guide to Operational Technology Security, SP 800-82 Rev. 3Provides OT security context, including the need to account for reliability and safety when designing data access.
03 / A FEW DETAILS
Worth understanding.
Does RAIN dispatch power or control the grid?
No. The system is intended to observe telemetry and produce advisories. Dispatch, protection and equipment control remain outside its actuation boundary.
Which asset types are proven?
The current implementation runs against a simulated battery-storage plant. Solar and wind are proposed applications; no field deployment is claimed.
Power & Utilities / EXPLORE THE FIT
Bring the question.
Define the study.
Start with the records, the review team, and the evidence a useful outcome would need. RAIN’s current implementation is a battery-storage simulator; this sector workflow requires its own validation.