Workflow: Manage

Manage is the workflow a customer enters when they have decided a specific asset matters. The screening signal pointed somewhere, and now they need to understand the asset in depth — to build a defensible underwriting view, a bankability forecast, an insurance structure, a stress-test against scenarios the legacy tools cannot price.

This is the workflow that does the most analytical work and where the platform's underlying model depth becomes most visible to the customer.

Asset-level hazard composition

For each asset, the platform decomposes total expected annual loss across the active hazard types and surfaces the dominant contributors. You see not just a number ("EAL = $58,762") but a structured view: hail contributes 67.9%, hurricane 16.4%, strong wind 9.2%, with the remainder distributed across the secondary hazards. The decomposition is presented at multiple return periods (100-year, 200-year, 500-year PML) so you can see how the dominant hazard shifts as you move from the body of the loss distribution into the tail.

Performance + bankability forecast

The platform translates the weather and price simulation engine's hourly scenario paths into generation forecasts at the asset level — using calibrated physics-based models for solar (pvlib with CEC module and inverter specifications) and wind (PyWake-based wake modeling, using actual turbine layouts from USWTDB). Generation is multiplied against co-sampled hourly price scenarios from nodal LMP history to produce a probabilistic revenue forecast: P50, P90, P99 distributions over horizons of 1 to 36 months.

These revenue forecasts feed directly into a financial schedule you can configure against debt assumptions — loan size, rate, principal structure, covenant thresholds. The output is a year-by-year forecast of revenue, OpEx, CFADS, debt service, principal balance, and minimum DSCR — with covenant breaches surfaced explicitly and visualized against the probabilistic CFADS distribution. You can see not just whether the asset clears its covenants under base case, but how close the P10 path comes to a breach, where in the lifecycle the stress concentrates, and how that stress moves under different leverage assumptions.

Insurance gap analysis

For each asset, the platform compares modeled hazard exposure against actual policy terms — limits, sublimits, deductibles, exclusions, business-interruption coverage — and surfaces the gap by hazard, by coverage layer, and by return period. The view distinguishes between physical damage gaps and revenue impact gaps (forced outage loss, recovery loss) and presents both alongside a benchmark premium range so you can see whether your current coverage is structurally inadequate, structurally over-purchased, or appropriately matched to the exposure. Policy terms can be uploaded directly; the platform extracts the relevant parameters and runs the comparison against modeled loss.

Scenario configuration

Manage is where you run what-if analyses against the asset. What happens to expected annual loss if the panel technology changes? What is the DSCR impact of adding battery storage? What is the value of an upgraded inverter, a hail-resistant module, a flood wall, or a vegetation management program? The configuration changes flow through the model stack and update every downstream output — performance, financial schedule, insurance gap, comparison view. You are not running a separate analysis; you are configuring the same asset and seeing the platform re-compute coherently.

Granular comparison

Where Evaluate's comparison was high-level — InfraRisk score, revenue delta, hazard heatmap — Manage's comparison is asset-detail. You can place two configured assets side by side and compare their hazard composition, their forecast performance, their bankability under matched debt assumptions, their insurance positioning. This is the comparison view that gets used inside investment committees, not the one that gets used in pipeline triage.

What you get out

Manage is where the customer builds the underwriting view they will defend in front of an investment committee, a credit committee, a reinsurance counterparty, or an LP. The output is not a score. The output is a position — a coherent, defensible read of the asset's economics and risk profile that the customer can act on.

What you do with that position is the next workflow — Mitigate.

See also

• Workflow: Evaluate — top-of-funnel screening that feeds into Manage.
• Workflow: Mitigate — next step: turn the position into action.
• Methodology + validation — how the underlying models are calibrated + validated.