General business
AuraScore 81/100

Smart Grid and Advanced Metering Infrastructure Rollout Plan

Structure an end-to-end capital deployment plan for utility-wide AMI meters and digital substation upgrades.

Deploy this template when designing execution and governance plans for advanced grid technology upgrades. It standardizes field deployment, telecommunications integration, customer opt-out handling, and cyber-physical security.

Template

Role: Principal Energy Infrastructure Program Director

Context

  • Electric distribution company: {{energy_distributor}}
  • Geographic coverage and customer density: {{service_territory}}
  • Existing metering fleet: {{legacy_meter_footprint}}
  • Total approved capital envelope: {{capital_budget_allocation}}
  • Distribution automation objectives: {{substation_automation_targets}}
  • Program duration: {{deployment_timeline_months}}

Task

Produce an enterprise-grade capital deployment and operations plan for {{energy_distributor}} to replace {{legacy_meter_footprint}} with smart grid infrastructure and execute {{substation_automation_targets}} within {{capital_budget_allocation}} across a {{deployment_timeline_months}} schedule.

Method

  1. Establish the geographical wave schedule based on substation feeder topologies, communication backhaul availability, and density in {{service_territory}}.
  2. Design the RF mesh and cellular backhaul architecture required for bi-directional smart meter telemetry.
  3. Formulate the field logistics workflow: inventory staging, field technician routing, legacy meter recycling, and safety protocols.
  4. Define meter data management system (MDMS) and customer billing integration pathways to prevent billing cutover errors.
  5. Detail the distribution automation roadmap to achieve {{substation_automation_targets}} (FLISR, smart reclosers, volt-VAR optimization).
  6. Establish customer communications, notification sequences, access issue resolutions, and opt-out management protocols.
  7. Structure a cybersecurity and operational technology resilience plan meeting NERC CIP and regional utility cybersecurity standards.
  8. Build the program governance framework covering contractor SLA oversight, variance tracking, and regulatory audit reporting.

Constraints

  • MUST stay within the total financial boundary of {{capital_budget_allocation}} without unallocated contingency.
  • Field installation sequences MUST NOT exceed the window set by {{deployment_timeline_months}}.
  • Customer notification protocols must define at least three touchpoints prior to physical meter exchange.
  • Telemetry specifications must address dead zones and terrain anomalies in {{service_territory}}.

Output format

  1. Program Governance & Architecture Blueprint (300 words)
  2. Phased Deployment Schedule (table: Wave Number, Feeder Group, Meter Count, Start-End Months, Milestones)
  3. Grid Modernization & Automation Framework (300-400 words detailing {{substation_automation_targets}})
  4. Field Operations & Workforce Staging Plan (250-350 words)
  5. Consumer Engagement & Exception Handling Protocol (process steps with timelines)
  6. Capital Allocation & Cost Control Ledger (cost breakdown by technology, labor, contingency)

Self-review

  • Ensure every phase aligns with the total scope of {{legacy_meter_footprint}}.
  • Verify all cost line items aggregate precisely to {{capital_budget_allocation}}.
  • Validate that backhaul and field routing reflect the distinct topography of {{service_territory}}.
AuraScore breakdown
81/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 engineering12/12 · Strong

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
smart-grid
ami
infrastructure