Metered end uses
Chiller, pump and air-handler electricity, with meter identity and interval boundaries. Separate equipment loads instead of interpreting only a whole-hospital total.
SCOPED INPUT · HUMAN REVIEWRAIN / Healthcare
Understand the plantbehind the hospital.
A hospital’s energy profile is shaped by cooling, reheat, fans, pumps and the requirements of the spaces they serve. A proposed RAIN pilot would help facilities engineers investigate equipment trends in context, using operational telemetry without patient records or clinical decision-making.
Exploratory use case
INTELLIGENCE BELONGS WHERE THE DATA LIVES.
THE HEALTHCARE FACILITIES QUESTION
Central plant, air handling and facilities engineering
THE INPUTS THAT MATTER
Read the right signals.
Choose a source to see the context it adds to this proposed review.
Air-handler context
Available fan state, airflow, temperatures and pressure measurements from approved building-system points. Preserve each sensor’s units, calibration context and quality flags.
SCOPED INPUT · HUMAN REVIEWOperating conditions
Outdoor conditions and the facility team’s approved system modes. A continuously served area cannot be compared with an intermittently used office as if they had the same duty.
SCOPED INPUT · HUMAN REVIEWMaintenance history
Equipment IDs, filter-service dates, work orders and authorized configuration changes. These provide context for a trend; they do not establish its cause.
SCOPED INPUT · HUMAN REVIEWAN OPERATING PATTERN WORTH EXPLORING
One air handler is working harder.
Proposed scenario: a facilities engineer selects one air handler with reliable metering and documented operating modes. Existing building alarms and hospital procedures remain in place.
Healthcare facilities / PILOT SCENARIO01 — REVIEW NOTES
Inspect the pattern.
A read-only comparison could identify higher fan electricity during periods with similar recorded airflow and operating conditions, then show the accompanying pressure and maintenance history.
Bring it to the operator.
The engineer checks sensor validity, recent service, approved configuration changes and the actual equipment. The observation becomes a maintenance question, not an instruction to lower airflow or alter room pressure.
Illustrative pilot design, not a clinical application or deployed RAIN result. Hospital facilities and infection-prevention teams determine any relevant operating constraints.
Healthcare facilities / PROPOSED WORKFLOW
From operating context to review.
- 01
Choose one equipment boundary
Start with a named air handler or plant subsystem, identify its served spaces and record the approved operating modes with the facility owner.
- 02
Verify the instrumentation
Confirm meter mapping, timing, sensor quality and available operating context before proposing a comparison. Mark missing values rather than treating them as normal operation.
- 03
Compare like operating periods
Separate service events and mode changes. Use a fixed evaluation period to test whether contextual trends add value beyond the existing building-system view.
- 04
Review through facilities engineering
Route findings into the existing investigation process. Count useful, inconclusive and unnecessary reviews; any equipment change follows hospital procedures.
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.
- 01Comparable-operation coverage
- Share of the evaluation period with valid, synchronized power, airflow and operating-mode data. Report missing and incomparable periods separately.
- 02Engineering review yield
- Engineer-confirmed observations worth investigating divided by all reviewed observations, with dismissed and inconclusive cases retained.
- 03Evidence preparation time
- Time an engineer needs to assemble the source trend, operating context and maintenance record for a sampled investigation, compared with the existing workflow.
THE OPERATING BOUNDARY
Be precise about the scope.
Facilities data only
The proposed scope excludes patient identifiers, clinical records, diagnosis, treatment and medical-device control. Connections would need review by the hospital’s facilities and IT owners.
Ventilation authority stays with the hospital
RAIN would not change fan speeds, room pressure, ventilation targets or alarm thresholds. Existing engineering, infection-prevention and emergency processes remain authoritative.
No safety or savings conclusion from a trend
Energy and equipment observations need engineering interpretation. The proposed pilot would not establish infection-control performance, patient outcomes or verified energy savings.
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
Researching Energy Use in HospitalsDOE’s end-use monitoring work separates hospital loads such as heating, reheat, cooling, fans and pumps. It motivates the proposed equipment-level comparison rather than a generic whole-building anomaly score.
- 02
Centers for Disease Control and Prevention
Environmental Infection Control: AirCDC describes the special role of healthcare ventilation, maintenance and pressure relationships. That context informs this proposal’s strict separation between observation and hospital-controlled ventilation decisions.
03 / A FEW DETAILS
Worth understanding.
Is this intended for diagnosis or treatment?
No. The proposed scope is facility operations. Clinical interpretation, patient monitoring and treatment decisions are outside this concept.
Would RAIN control building or medical equipment?
The proposed access is read-only. Equipment controls and operational decisions would remain with the facility’s existing systems and responsible staff.
Healthcare / 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.