Defense Energy & Microgrid Resilience
Commercial referenceDEF-016
When contacting BivectorAI, quote DEF-016 — Defense Energy & Microgrid Resilience.
Who this is for
Installation energy resilience leads and microgrid program managers responsible for storage, islanding, and black-start continuity.
The problem you already have
Storage, islanding and black-start get reviewed as three separate questions
Mission power depends on storage capacity, islanding behavior and black-start readiness holding together as one continuity story — but they're usually reviewed independently, so nobody sees the combination that determines whether the mission keeps running through an outage.
Two generators that look redundant can share the one thing that actually decides if they run
Two generators can be wired as fully separate electrical sources and still both draw from the same fuel tank through the same transfer pump — a shared dependency that doesn't show up on an electrical single-line diagram at all. If that pump fails, "two independent generators" becomes zero generators at the same moment.
Reviewing continuity doesn't require live grid-control access
Never requested, and structurally rejected if submitted: live grid-control access, classified installation power-topology data, or control-system credentials.
Real-World Operational Scenario: The Battery That Was 90% Charged and Still Not Enough
Scenario: A microgrid's battery storage reports 90% state of charge after a grid outage.
Plenty of energy on paper. But the batteries have been running hot under sustained load, and thermal derating limits how fast that stored energy can actually be delivered — the inverters connected to them also have a power ceiling independent of how much energy is stored behind them.
WITHOUT this check: The dashboard shows "90% SOC — GOOD," and mission planners assume the full critical-load list can be sustained. When a cooling unit and two priority radios all draw peak power at once, delivered power falls short of what SOC alone promised — because energy stored and power deliverable right now are two different numbers.
WITH this check: The energy resilience certificate reports assured capacity based on real-time thermal derating and inverter limits, not raw SOC. The facility is certified CRITICAL_LOADS_ONLY rather than full mission power — so the review shows exactly which loads are actually protected before the outage tests it for real.
What you provide
Redacted power-state, storage-capacity, and islanding-event telemetry already logged by your microgrid control system.
What BivectorAI Provides
Assured Power, Not Nameplate or State of Charge
Certified capacity reflects real-time thermal state, inverter limits, and protection coordination — not the generation rating on a spec sheet or a battery's raw charge percentage.
Hidden Fuel, Bus, and Controller Dependencies Made Explicit
Shared fuel tanks, transfer pumps, transformers, and controllers that don't appear on an electrical single-line diagram are tracked, so "independent" sources are only counted as independent when they actually are.
A Named State for Every Stage, Not Just Up/Down
Continuity is reported as one of several named states — NOMINAL, ISLANDED_ASSURED, DEGRADED_ASSURED, BLACK_START_IN_PROGRESS, CRITICAL_LOADS_ONLY, or NO_CERTIFIED_MISSION_POWER — reflecting exactly what's currently supported.
Hash-Sealed Certificates for Post-Event Review
Every continuity classification traces back to the exact storage, thermal, and dependency evidence that justified it at the time.
What we will never ask you for
Never requested, and structurally rejected if submitted: live grid-control access, classified installation power-topology data, or control-system credentials, or your system's core design data. Every submission is checked against this rejection list before any evidence logic runs — a malformed or over-broad submission is blocked and reported back to you, not silently processed.
How it actually runs
Engagement path & current acquisition terms
DEF-016 · Tier B — Mission Software
Secures a defined diligence and exclusive-negotiation period. Any option credit is agreed in writing as part of the signed commercial terms.
Starting integration engineering, customer-safe adaptation, local/private deployment work, validation and acceptance evidence for the agreed environment.
Scope-dependent consideration for negotiated exclusivity in a defined field, program, platform class, territory and rights scope.
Engineering support, update access, security maintenance, evidence infrastructure and agreed sustainment services.
Applied to attributable net program revenue under the definitive agreement, subject to negotiated exclusions and accounting rules.
Commercial boundary. These are indicative starting terms, not a binding offer. Final price depends on exclusivity scope, field of use, territory, sublicensing, technical-data rights, integration obligations, export-control review, support requirements and definitive agreement.
IP boundary. Exclusive FOU does not automatically transfer ownership of BivectorAI Background IP. Worldwide/all-defense rights, sublicensing, source-level technical-data rights or assignment require separate negotiated consideration.
Scope the DEF-016 diligence and integration boundary
Request DEF-016 Acquisition Discussion →Email fallback: contact@bivectorai.com
Defense technology is integrated through qualified local/private engagement. No public Defense API and no automated Defense checkout are provided.