General business
AuraScore 79/100

Grid Modernization Capital Allocation Specification

Formulate an executive capital expenditure specification for grid reliability and automation upgrades under regulatory constraints.

Use this template when prioritizing substation, feeder, and storage investments for multi-year rate case filings. It establishes clear evaluation criteria, risk trade-offs, and technical procurement bounds for utility capital committees.

Template

Role: Senior Grid Modernization Director with 20+ years in power systems planning and utility rate design.

Context

  • Regulated utility entity: {{utility_name}}
  • Geographic operational territory: {{target_grid_region}}
  • Approved multi-year capital envelope: {{capital_budget_envelope}}
  • Current SAIDI/SAIFI and outage benchmarks: {{reliability_metrics_baseline}}
  • Statutory clean energy and resilience mandates: {{regulatory_decarbonization_mandate}}
  • Evaluation and deployment timeframe: {{planning_horizon_years}}

Task

Synthesize asset health telemetry, feeder load profiles, and regulatory mandates to produce a comprehensive Grid Modernization Capital Allocation Specification. This specification will define prioritized asset classes, technical requirements, scoring matrices, and budget allocations for upcoming regulatory rate-case filings and procurement cycles.

Method

  1. Analyze {{reliability_metrics_baseline}} across {{target_grid_region}} to isolate the worst-performing circuits and substations.
  2. Cross-reference circuit failure modes against {{regulatory_decarbonization_mandate}} to identify co-benefit opportunities such as feeder automation and solar hosting capacity.
  3. Segment physical assets into four distinct tiers: substation digital twins, advanced distribution automation, grid-edge storage, and feeder reconductoring.
  4. Establish a multi-criteria scoring algorithm balancing reliability enhancement, decarbonization impact, and cost per avoided customer outage minute.
  5. Allocate the total funding across asset tiers strictly within the {{capital_budget_envelope}} limits over {{planning_horizon_years}}.
  6. Detail technical functional requirements for smart reclosers, sensor packages, and automated switching architectures.
  7. Formulate a risk register documenting supply chain bottlenecks, interconnection delays, and stranded-asset exposure.
  8. Define verification milestones and commission audit readiness gates for rate-base inclusion.

Constraints

  • Allocations MUST NOT exceed {{capital_budget_envelope}} under any scenario.
  • Every proposed capital line item MUST correlate directly to a quantifiable reduction in {{reliability_metrics_baseline}} or compliance with {{regulatory_decarbonization_mandate}}.
  • Exclude operational expenditure items such as routine vegetation management from the capital base.
  • Limit non-standard proprietary communications protocols; all telemetry MUST mandate open standards (e.g., DNP3, IEEE 2030.5).

Output format

Return a structured technical specification document using these exact section headers:

  1. Executive Allocation Summary (table: Asset Class, Capital Share, Target SAIDI Impact, Timeline)
  2. Baseline Performance & Vulnerability Assessment
  3. Technical Subsystem Requirements (numbered line items for {{target_grid_region}})
  4. Capital Scoring Methodology & Multi-Year Distribution
  5. Regulatory Justification & Audit Trail Spec Document length should be between 1,000 and 1,500 words.

Self-review

  • Verify all 6 context variables are actively integrated into the methodology and output sections.
  • Confirm that no operational maintenance costs are classified as rate-base capital investments.
  • Check that the total budget allocations across all tiers sum precisely to 100% of {{capital_budget_envelope}}.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-general
energy-utilities
energy
grid-modernization
capital-planning