The method
In brief
- 01A hundred prospects do not justify a hundred deep dives. The first job is to put the working set on one comparable basis and find where deeper work can change a decision.
- 02InfraSure connects five steps: screen, prioritize, deepen, test, and decide. Each step has its own product surface, output, and maturity boundary.
- 03The differentiation appears when engineering, climate and quantitative science, and finance resolve the same asset and scenario—so a physical signal is not mistaken for a financial conclusion.
- 04The useful result is a defensible diligence queue and a supported handoff: advance, defer, monitor, or retrieve the evidence that controls the decision.
The daily problem is not a lack of possible analysis
An owner evaluating acquisition or development candidates—or a lender reviewing a borrowing set—usually has more possible questions than time to investigate them. Treating every asset as a bespoke study is slow and expensive. Treating every asset as one score hides why the risk matters.
The working question is simpler:
Which assets deserve deeper diligence now—and what evidence must be resolved before we advance, defer, or monitor them?
InfraSure's role is to help the user move from a broad working set to a justified use of depth. The screen is not the conclusion. It is the beginning of an evidence path.
Five connected steps, one working set
One client job across five connected InfraSure steps
Figure 01Screen
Put the opportunity set on one comparable basis.
- InfraSure surface
- Explore + Evaluate
- Risk process
- Assess broadly
- Produces
- Working set + evidence gaps
Available for supported US plant and prospect scopes.
Prioritize
Focus limited diligence where it can change the decision.
- InfraSure surface
- Evaluate · Comparisons
- Risk process
- Create the queue
- Produces
- Explainable priority + question
Available as a decision aid in supported screens.
Deepen
Resolve the material mechanism and value basis.
- InfraSure surface
- Asset detail · Risk composition
- Risk process
- Connect physical + financial
- Produces
- Asset-specific mechanism
Proven in bounded cases; breadth varies.
Test
Change an assumption, scenario, configuration, or response.
- InfraSure surface
- Scenarios · Variants
- Risk process
- Compare what changes
- Produces
- Sensitivity + residual uncertainty
Bounded demonstrations are real; reusable breadth remains in build.
Decide
Advance, defer, monitor, reject, or request evidence.
- InfraSure surface
- Evaluate → Manage
- Risk process
- Carry the position forward
- Produces
- Supported action + rationale
The handoff is available; formal optimization remains vision.
1. Screen the opportunity set
Use Explore and Evaluate to assemble or load the prospect group, establish coverage, and put supported assets on a comparable basis. The output is a working set with broad signals and visible gaps—not a final investment or operating decision.
2. Prioritize the diligence queue
Compare InfraRisk views, hazard and revenue indicators, and explainable red flags to identify where limited diligence time should go first. A high-priority asset should carry a reason: the question, dependency, or missing term that makes deeper work worthwhile.
3. Deepen selected assets
On the short list, move from broad exposure into the mechanism. Resolve the asset and subsystem, the delivered condition, performance or interruption path, dependencies, and the contract or value basis that determines actor relevance. This depth is proven in bounded cases; its breadth varies by asset, model, and evidence.
4. Test what changes
Change an assumption, scenario, configuration, or response and inspect the sensitivity and residual uncertainty. Scenario comparison is real in bounded demonstrations; broader reusable response comparison remains in build. The output may be a preferred next step—or a missing fact that blocks approval.
5. Decide and carry forward
Advance, retain, defer, monitor, reject, or request evidence. When an asset advances, the current product can move it from Evaluate into Manage so the rationale does not disappear at the handoff. That handoff is available. Formal portfolio optimization remains a vision, not a present-tense promise.
For whom—and what changes by role
The same five steps support different decisions. The evidence spine can be shared; the governing operating, financing, contract, and value terms cannot.
| Stage | Owners and operators | Lenders and investors |
|---|---|---|
| Screen | Assemble acquisition or development candidates on one supported basis. | Assemble the borrowing or investment set and expose uneven coverage. |
| Prioritize | Focus engineering and commercial diligence where it can change portfolio fit or operating readiness. | Focus review where physical risk can reach cash flow, collateral, or bankability. |
| Deepen | Resolve component condition, dependencies, recovery, contract shape, and operating responsibility. | Retrieve the covenant, reserve, guaranty, coverage, and value term controlling the consequence. |
| Test | Compare a material scenario, configuration, or response on the short list. | Stress downside, timing, liquidity, and assumptions without turning a screen into a credit verdict. |
| Decide | Advance, defer, request evidence, or move the supported asset into Manage. | Approve, condition, defer, price for further work, or monitor. |
For the owner, the operating result is a documented allocation of diligence effort and a clearer transition from pre-commitment evaluation to ongoing ownership. For the lender, it is an auditable reason to deepen, condition, or hold a decision rather than treating every red flag as equivalent.
Where InfraSure goes deeper
The screen creates speed and scale. The deeper steps protect accuracy by connecting specialties around the same subject.
| Discipline | What it resolves |
|---|---|
| Engineering | asset configuration, subsystem response, dependencies, function, and recovery feasibility |
| Climate and quantitative science | event state, delivered condition, uncertainty, dependence, temporal grain, and tail behavior |
| Finance | baseline and value basis, contract shape, ownership, coverage, timing, liquidity, covenant, and valuation relevance |
One evidence trail connects engineering and finance
Figure 02Condition
What event, regime, or operating state is being tested?
Produces
Bounded scenario + time window
Asset + subsystem
Which configuration, component, or dependency receives it?
Produces
Delivered condition + failure path
Performance + recovery
What function, output, interruption, or restoration changes?
Produces
Natural-unit consequence
Contract + value basis
Which ownership, price, coverage, timing, or obligation governs?
Produces
Actor-specific cash-flow path
Decision consequence
What can now be supported—and what evidence still blocks action?
Produces
Condition, deepen, advance, or monitor
This is the depth available to the Workflow; it is not a claim that every engine is equally mature for every asset today. The important discipline is that finance is not added as a dollar sign after a hazard score. It constrains the same scenario and evidence trail.
The handoff is part of the decision
Many diligence processes lose context when a selected opportunity becomes an owned or monitored asset. InfraSure's Evaluate-to-Manage handoff is meant to preserve the thread: which risks were material, which assumptions were tested, which evidence remained open, and why the asset advanced.
The handoff carries the decision record—not only the asset
Figure 03Evaluate record
What did the comparison and deeper review establish?
Produces
Priority + material mechanism + evidence gaps
Decision package
Why did the asset advance, pause, or require a condition?
Produces
Rationale + assumptions + unresolved conditions
Manage context
What must remain visible after the commitment decision?
Produces
Continuing monitoring + follow-up + deeper analysis
The handoff is a current product action. The richer future is to let the same evidence support ongoing response comparison, residual-risk views, and portfolio decisions without reassembling the subject from scratch.
See the deeper steps under pressure
Winter Storm Uri is the first companion replay because it shows why prioritization cannot stop at a weather signal. The FERC/NERC system investigation traces connected equipment, fuel, and grid failures. At one named wind project, a production shortfall and replacement-power obligation reached a $39.49 million invoice in the later Shannon Wind court record.
Review the Winter Storm Uri Historical Risk Replay.
The replay demonstrates the deepen and test steps: retrieve the contract shape, connect it to operating and market conditions, and stress the joint scenario. It does not prove that InfraSure would have predicted the exact event, prevented it, or avoided a quantified loss.
What is available—and what remains ahead
| Object | Public posture |
|---|---|
| Explore / Evaluate working-set screen | Available for supported US plant and prospect scopes |
| Comparisons, supported indicators, and red flags | Available as decision aids; not automated verdicts |
| Connected asset-level engineering and financial depth | Proven in bounded cases; coverage varies |
| Scenario and response comparison | Experimental / in build beyond bounded demonstrations |
| Evaluate-to-Manage handoff | Available |
| Formal portfolio response optimization | Vision |
Evidence register
Sources and method boundaries
- 01InfraSure application routes and workflow interfaces, reviewed 9 August 2026. Used to ground the current working-set, Evaluate comparison, Evaluate-to-Manage promotion, and portfolio-management surfaces described in this draft.
- 02InfraSure Energy Infrastructure Risk Framework discussion and risk-response method, reviewed 9 August 2026. Used for the screen-prioritize-deepen-test-decide journey, connected engineering/science/finance depth, actor-specific value basis, and maturity boundaries.
- 03InfraSure Workflow recipe method, reviewed 9 August 2026. Used for job-level workflow grain, evidence handoffs, bounded outputs, and downgrade discipline.
- 04FERC, NERC, and Regional Entity staff, final February 2021 cold-weather report and release. Issued 16 November 2021; accessed 9 August 2026. Used only to ground the companion Uri replay's connected equipment, fuel, grid, and emergency-load-shed mechanisms. Companion source.
- 05In re Shannon Wind, LLC, Case No. 26-90124, First Day Declaration of John Shepherd. Filed 26 January 2026; accessed 9 August 2026. Used for the companion replay's fixed-quantity hedge, production problem, replacement-market purchase requirement, and $39,486,641.34 March 2021 invoice.
