Resilience — Aurevia Energy

Most microgrid projects are sold as equipment lists.

Aurevia sells the operational outcome the equipment is supposed to deliver.

For mission-critical facilities — federal installations, hyperscale data centers, crypto and HPC operations, and IPP-owned generation — the question is never whether the array produces the rated power on a clear day. The question is whether the facility stays online when the grid goes down, when one of two transformers fails, when a fire suppression event takes a string of batteries offline, or when a control loop detunes after a firmware update.

Those are architecture questions. They get answered up-front, in the resilience phase of the delivery model — or they get answered the wrong way, at 3 AM, by an operator with a phone in one hand and a paper one-line in the other.

Aurevia engineers the architecture so the second scenario doesn't happen.

Resilience Capabilities

What we engineer for, by design.

Every Aurevia microgrid project is architected around six resilience capabilities. The components — solar inverters, BESS containers, switchgear, controls — are selected to deliver against these capabilities, not the other way around.

Islanding

Seamless transition from grid-tied to islanded operation when the utility source fails or is intentionally disconnected. The facility continues to operate without dropping load. Reconnection is managed through synchronization control, not manual intervention.

Engineering InputsUtility tie point characterization · Anti-islanding protection coordination · Sync-check relay architecture · Load shedding plan

Black-Start Capability

The microgrid can re-energize itself from a fully de-energized state without external power. BESS-as-grid-former architecture provides the voltage and frequency reference; supplemental generation and solar synchronize behind it.

Engineering InputsGrid-forming inverter selection · BESS state-of-charge planning · Block-loading sequence · Auxiliary power for switchgear

Load Prioritization

During constrained operation, mission-critical loads stay online; non-essential loads shed in tiers. The prioritization logic is engineered into the microgrid controller, not negotiated during the event. Acceptance test verifies the prioritization works under simulated stress.

Engineering InputsFacility load survey by criticality tier · Sheddable load identification · Controller logic verification · Acceptance test scenarios

Redundancy & Single-Point-of-Failure Analysis

Critical equipment is identified and either redundantly provisioned, gracefully degradable, or rapidly replaceable depending on cost-benefit. SPOF analysis is documented as a deliverable so the customer can verify the redundancy posture matches the mission requirement.

Engineering InputsSPOF register · Redundancy posture per component · Spares strategy · Mean time to repair targets

Fuel & Energy Reserve Planning

For islanded operation through extended grid-down events, the BESS state-of-charge reserve, supplemental fuel inventory, and solar yield assumptions are modeled together. Operating envelopes are defined so the facility knows how long it can run independently under stated load and weather assumptions.

Engineering InputsOutage duration scenarios · BESS reserve policy · Fuel inventory and refill logistics · Weather sensitivity analysis

Cybersecurity & Controls Integrity

Resilience against cyber events sits alongside resilience against physical events. SCADA, microgrid controller, and inverter communications are segmented, access-controlled, and logged. Patch management is part of the operations plan, not a future agenda item.

Engineering InputsNetwork segmentation design · Access control policy · Patch management plan · Audit logging architecture

Operating Philosophy

How Aurevia thinks about uptime.

Resilience is engineered up-front, not commissioned in.

Decisions made in the resilience architecture phase — topology, grid-forming vs. grid-following, BESS sizing for reserve, redundancy posture — define what the microgrid can and cannot do. Trying to add resilience at commissioning means accepting whatever resilience the equipment selection happened to allow.

ii.

The microgrid controller is the most consequential piece of equipment on the project.

More than the inverters, more than the BESS chemistry, more than the switchgear, the microgrid controller defines whether the system actually behaves the way the architecture says it should. Aurevia evaluates controllers on a per-project basis and requires BESS subcontractors to demonstrate EMS integration compatibility before scope award.

iii.

Acceptance testing should stress the system, not just check that it powers up.

Islanding transition under load, black-start with cold equipment, sheddable load priority verification, and protection coordination tests are written into the commissioning protocol. If the facility's first real grid-down event is the first time the system has been exercised against that scenario, the test program failed.

iv.

Operational discipline outlasts the EPC.

A microgrid that performs at COD and degrades over five years because controls firmware was never updated, BESS augmentation was never planned, or operator training was never refreshed is a failed asset, regardless of its commissioning record. Aurevia structures the long-term operational support phase to address that problem directly.

Fixed-tilt and ballasted racking are usually right for resilience-first projects.

Single-axis trackers add yield. They also add moving parts, control complexity, and O&M failure modes. For a facility where uptime matters more than the marginal kWh, fixed-tilt and ballasted racking generally produce a better total-asset-lifetime answer. Aurevia evaluates this on a per-project basis and recommends accordingly.

Resilience is the deliverable. Solar and storage are the components.

What we engineer for, by design.

How Aurevia thinks about uptime.

If your facility cannot tolerate grid dependency, let's talk.