Project Spotlight · No. 03
A Hospital Microgrid Financed as Resilience Infrastructure
When the investment case is measured in avoided disruption rather than energy savings
This project is illustrative. It is not a real project and no owner, operator, or site is identified. It is published to show how the variables interact.
GRIDSTROM did not participate in this project. Analysis is independent commentary.
The Intelligent Infrastructure Review · August 1, 2026 · 9 min read
Project overview
A regional medical center on a distribution feeder with a history of multi-hour outages replaces an aging emergency-generation arrangement with an integrated microgrid. The system serves the full campus rather than only life-safety circuits, operates in parallel with the utility during normal conditions, and islands automatically. The case was underwritten primarily on continuity of clinical operations, with energy cost savings as a secondary contribution.
- Asset type
- Regional medical center campus
- Configuration
- Grid-parallel microgrid with automatic islanding
- Scope served
- Full campus load, not only life-safety branch
- Driver
- Continuity of clinical operations
- Nature
- Illustrative composite
Business and infrastructure challenge
Code-minimum backup protects life safety, not operations
Emergency systems designed to code keep egress, life-safety, and critical branch circuits energized. They do not keep imaging, sterile processing, laboratories, HVAC for the full campus, or clinical IT running. Each outage therefore produced cancelled procedures, transferred patients, and revenue loss even though the hospital never lost life-safety power.
- Aging generation approaching end of service life
- Feeder outage history documented over several years
- Clinical service lines that cannot pause mid-procedure
- Fuel supply and run-time assumptions untested against long outages
Project map
Who holds what on this project
Project map
Direction · Delivery · Enablement · Outcome
01Direction
Sets the requirement and controls whether the project can proceed
Owner
Hospital system
Defines clinical continuity requirements; approves capital.
Developer
In-house facilities with an energy-as-a-service option
Structure decided before scope was fixed.
Utility
Distribution utility
Parallel operation agreement and protection requirements.
02Delivery
Converts the requirement into a built, commissioned system
EPC
Design-build contractor
Live-campus phasing without loss of backup capability.
Engineers
Consulting engineers and health-care code consultant
Design reconciled with essential electrical system code.
Contractors
Electrical and mechanical trades
Switchgear, generation, storage installation.
03Enablement
Supplies the equipment, the capital, and the public authority
Technology providers
Generation, storage, switchgear, and controller vendors
Controller defines islanding and load-shed order.
Capital providers
Hospital capital, tax-exempt financing, resilience programs
Or third-party ownership under availability terms.
Public stakeholders
Authority having jurisdiction and accreditation bodies
Compliance review of essential systems.
04Outcome
What the surrounding area actually receives
Community outcomes
Regional population served
Hospital remains operational; campus available during regional events.
Stakeholders
Each party and what it controls
Owner
Hospital system
Defines clinical continuity requirements and approves capital.
Facilities and clinical engineering
In-house team
Operating requirements, maintenance capability, transition testing.
Utility
Distribution utility
Parallel operation agreement, protection requirements, any export terms.
Engineers
Consulting engineers and code consultant
System design and reconciliation with health-care electrical code.
EPC
Design-build contractor
Delivery under a live-campus phasing plan.
Technology providers
Generation, storage, switchgear, and controls vendors
Equipment and the microgrid control layer.
Capital
Hospital capital plan and an energy-as-a-service provider
Two structures evaluated against balance-sheet and covenant constraints.
Regulators
Health-care accreditation and authority having jurisdiction
Compliance review of any system serving essential electrical loads.
Energy and infrastructure requirements
Stated as obligations, not preferences
- Islanding transition
- Sub-cycle to seconds by circuit class
- Different clinical loads tolerate very different transition times.
- Island duration
- Multi-day target
- Set by regional event history rather than a code minimum.
- Storage
- Sized for transition plus load-following
- Covers the gap before generation stabilizes and smooths step loads.
- Generation
- Dual-fuel or firm-fuel arrangement
- Fuel supply, not equipment, is usually the limit on island duration.
- Code compliance
- Essential electrical system preserved
- The microgrid is additive; code-required systems remain intact.
- Testing
- Scheduled live transition tests
- A microgrid that has never been tested under load is an assumption.
Delivery model
Design-build on a live campus, with an energy-as-a-service option evaluated in parallel
Delivery had to occur without interrupting clinical operations, so phasing and temporary provisions carried as much weight as the final design. The hospital evaluated owning the system outright against an energy-as-a-service structure in which a third party finances, owns, and operates the assets under an availability-based agreement.
- Step 01
Requirements definition
Clinical service lines mapped to circuits and tolerable transition times.
- Step 02
Code reconciliation
Microgrid design reviewed against health-care electrical code and accreditation requirements.
- Step 03
Structure decision
Owned versus energy-as-a-service compared on cost of capital, covenants, and operating capability.
- Step 04
Phased construction
Temporary provisions maintain full backup capability throughout the switchover.
- Step 05
Commissioning
Staged transition testing by circuit class, witnessed by clinical engineering.
- Step 06
Operations
Scheduled testing, fuel contract verification, and annual review against outage history.
Technology and systems architecture
Layer by layer, and how they interact
- 01
Point of common coupling
Protection and controls that allow parallel operation and automatic separation without utility involvement at the moment of an event.
- 02
Generation
Firm on-site generation with a fuel arrangement that matches the island-duration target.
- 03
Battery storage
Covers the transition instant, smooths step loads, and reduces generator cycling during normal operation.
- 04
Distribution and transfer
Circuit classes separated so different transition tolerances can be met with different equipment.
- 05
Microgrid controller
Defines priorities, sheds non-essential load in a stated order, and manages resynchronization to the utility.
- 06
Monitoring
Continuous verification of readiness — fuel, state of charge, breaker positions — reported to facilities and clinical leadership.
Capital structure
Where it comes from, and what each source does
Disclosure
Illustrative structure. Hospital capital and energy-as-a-service terms vary widely; no figures are attributed to any real institution.
Hospital capital plan
Direct funding where balance-sheet capacity and covenants allow.
Energy-as-a-service provider
Third-party ownership under an availability-based service agreement.
Tax-exempt financing
Available to qualifying non-profit systems for eligible infrastructure.
Resilience or hazard-mitigation programs
Where a jurisdiction funds critical-facility resilience, disclosed publicly.
Utility programs
Demand-response or storage participation, where the tariff permits it for essential facilities.
Community considerations
What the surrounding area experiences
The hospital stays open
During a regional event, continuity of a medical center is a public outcome before it is an institutional one.
Community sheltering
A campus that can island is frequently the de facto shelter and coordination point, which changes the load assumptions.
Grid support in normal conditions
Where tariffs allow, storage and flexible load can support the local system during peaks rather than sitting idle for years between events.
Emissions and neighbors
Generation runs far more often than legacy emergency equipment, so emissions, noise, and fuel deliveries become ongoing neighborhood matters rather than rare events.
Risks and constraints
What can go wrong, and who holds it
- Code conflict discovered late
- ResponseCode consultant engaged at concept, not at permit; essential electrical system kept intact and separable.
- Transition failure during a real event
- ResponseStaged live testing by circuit class, repeated on schedule, with documented results.
- Fuel supply fails in a regional event
- ResponseFirm contracts with priority terms plus on-site storage sized to the target duration.
- Construction disrupts clinical operations
- ResponseTemporary provisions maintain full backup capability at every stage of phasing.
- Operating capability is not sustained
- ResponseTraining and vendor support obligations written into the delivery contract, with responsibilities named.
- Service-agreement terms diverge from clinical needs
- ResponseAvailability defined in clinical terms, with remedies tied to those definitions.
Lessons for future projects
What transfers to the next site
- 01
Define resilience by what clinical operations require, not by what code requires.
- 02
The limit on island duration is almost always fuel, not equipment.
- 03
Separating circuits by tolerable transition time reduces cost more than oversizing a single system.
- 04
A microgrid that has not been tested under real load is an assumption, not a capability.
- 05
Ownership structure changes who carries performance risk — decide that before selecting equipment.
GRIDSTROM perspective
Resilience is measurable, so underwrite it
Continuity projects stall when the benefit stays qualitative. Outage history, cancelled procedures, transfer costs, and staffing disruption are all recorded somewhere in the institution. Once those are assembled, the investment case usually stands on its own and the technical scope follows from stated requirements rather than from a vendor's standard package.
GRIDSTROM did not participate in this project. Analysis is independent commentary.
- Quantify disruption before evaluating equipment.
- Map circuits to clinical tolerance and design to that map.
- Verify fuel arrangements against the island-duration target, in writing.
- Require live transition testing as a condition of acceptance.
Structure your project with GRIDSTROM
GRIDSTROM engineers and delivers integrated energy systems for data centers, AI and robotics facilities, fleets, commercial portfolios, and public infrastructure. Bring a site, a load, or a structure you are working through.
Follow Project Spotlight
Each spotlight is sent as it publishes — one project, fully structured.