Delivery Model
Microgrid projects fail at the interfaces — between engineering and procurement, between OEMs and integrators, between commissioning and operations. Aurevia's delivery model is structured to manage those interfaces as a discipline, not as an afterthought.
The methodology below describes how Aurevia executes a typical solar, BESS, or microgrid project — from first site walk through long-term operational support. It is the same framework Aurevia applies whether the project is a federal critical facility, a hyperscale data center, or a utility-scale grid-tied asset.
Each phase has defined deliverables, defined ownership, and defined acceptance criteria. Where Aurevia self-performs the scope, that is stated. Where Aurevia coordinates execution through engineering, technology, or construction partners, that is stated as well. There is no diffusion of accountability across the partner ecosystem — Aurevia holds the EPC scope and the EPC performance record.
Compliance posture (FEOC, NDAA Section 841, IRA domestic content, Buy American, UL/IEEE standards, and cybersecurity for federal-adjacent work) is engineered into the relevant phases, not retrofitted at acceptance testing.
Site walk, utility one-line review, load profile capture (interval data preferred), parcel constraints, soil and racking assumptions, AHJ research, and grid interconnection feasibility. The output is a project framing memo that defines what is technically feasible at the site, what is not, and where the largest cost or schedule risks sit.
Translation of mission requirements into system architecture. Islanding philosophy, black-start strategy, load prioritization, redundancy posture, and the topology decision (DC-coupled vs. AC-coupled, grid-forming BESS topology vs. grid-tied augmentation). This is the most consequential phase — every downstream decision flows from it.
Utility interconnection application, system impact study coordination, distribution or transmission interface design, and AHJ permit pathway. For islanded systems, this phase governs the disconnection logic and protection coordination. For grid-tied systems, this phase governs schedule risk more than any other.
Microgrid controller selection from established industry platforms, EMS/SCADA architecture, communications backbone, cybersecurity posture, and the integration plan between solar inverters, BESS PCS, switchgear, and supplemental generation. Aurevia requires BESS subcontractors to demonstrate EMS integration compatibility before scope award — controls integration is engineered up-front, not at commissioning.
FEOC-compliant supplier qualification under NDAA Section 841 — suppliers identified as Foreign Entities of Concern under the statutory framework are excluded by Aurevia procurement policy. IRA domestic content tracking at the bill-of-materials level, Buy American flowdowns where applicable, and long-lead procurement strategy for transformers, switchgear, BESS containers, and inverters. Lock prices and lead times before engineering goes to IFC where the schedule allows.
Civil, structural, electrical, and protection engineering coordinated under licensed PE seal — issued for review, then issued for construction. Aurevia integrates engineering deliverables with the procurement schedule and the construction sequence. PE-of-Record relationships are maintained on a per-project basis under standing engineering agreements.
Mobilization, civil and racking install, electrical install, BESS positioning and termination, switchgear and protection install, and SCADA cabling. Aurevia governs schedule, quality, safety, and subcontract scope through a dedicated project management team. Subcontractors execute under Aurevia-issued subcontract agreements with FAR/DFARS flowdowns where required.
Pre-energization checks, point-to-point verification, protection relay testing, BESS commissioning under OEM field engineering, microgrid controller tuning, islanding test, and performance acceptance. For federal projects, performance documentation is produced to support government acceptance testing under the relevant CDRL.
Warranty management, OEM coordination, performance monitoring against the design baseline, scheduled preventive maintenance, BESS augmentation planning, and long-term controls platform updates. Aurevia maintains a documented relationship with the asset owner well past commissioning — operational performance over years, not just at energization, is the deliverable.
Federal acceptance testing, IRA bonus credit qualification, and bankability all share one feature: they are documentation-driven. Aurevia treats compliance as a procurement and engineering discipline applied at project initiation — not a clearance step before COD.
BESS, PCS, and inverter procurement screened against NDAA Section 841 requirements. Suppliers identified as Foreign Entities of Concern under the statutory framework are excluded by Aurevia procurement policy. Country-of-origin documentation maintained at the cell, module, and rack level.
Domestic content qualification calculated and documented at the BOM level for solar, BESS, and balance-of-system equipment. Bonus credit pathways evaluated and engineered into procurement strategy from day one.
Where federal funding or federal customers apply, Buy American Act flowdowns and waiver pathways tracked throughout procurement. FAR/DFARS flowdowns embedded in subcontract agreements.
UL 1741, UL 9540, UL 9540A, IEEE 1547, IEEE 519, and NFPA 855 referenced in equipment specifications and verified during commissioning. Documentation produced to the level required for federal acceptance.
SCADA and microgrid controller architectures designed with network segmentation, access control, and patch management as engineered requirements. Cybersecurity posture is built into the controls architecture from project initiation, not added during commissioning.
Engineering deliverables, procurement records, commissioning protocols, and performance acceptance packages produced to the standard a project finance review requires — not produced as an afterthought during closing.
If you'd like to walk through how Aurevia would apply this framework to a specific project, we'll respond directly. For our procurement and compliance posture in detail, see the compliance page.
Discuss Your Project