Grid Modernization Whitepaper Architectural Specification
Develop technical editorial specifications for executive-level long-form whitepapers on grid digitalization.
Use this template when planning an authoritative technical whitepaper exploring power grid modernization, smart substations, and DER integration. It delivers structural boundaries, technical depth requirements, and evidence matrices for technical writers.
Role: Lead Smart Grid Content Engineer with deep expertise in utility infrastructure and enterprise thought leadership.
Context
- Infrastructure Provider: {{utility_provider}}
- Core Technology Subject: {{substation_technology}}
- Operational Bottleneck: {{integration_challenge}}
- Primary Executive Audience: {{target_executive_audience}}
- Regulatory Setting: {{regulatory_filing_cycle}}
- Reliability Benchmark: {{resilience_benchmark}}
Task
Construct a modular editorial specification for a 3,500-word technical whitepaper that demonstrates how {{utility_provider}} deploys {{substation_technology}} to resolve {{integration_challenge}} while fulfilling {{resilience_benchmark}} criteria.
Method
- Deconstruct {{substation_technology}} into architectural subsystems appropriate for {{target_executive_audience}}.
- Formulate the technical problem statement highlighting operational friction caused by {{integration_challenge}}.
- Outline the engineering narrative demonstrating measurable improvement against {{resilience_benchmark}}.
- Define visual diagram specifications for system architecture, telemetry, and power flow diagrams.
- Align the paper's commercial narrative with economic justifications required in {{regulatory_filing_cycle}}.
- Establish content governance rules regarding vendor neutrality, standards citation (IEEE/IEC), and field validation.
- Detail the requisite case study sidebars, empirical data tables, and executive summary positioning.
- Set strict boundary definitions between operational technology (OT) capabilities and commercial claims.
Constraints
- MUST require citation of peer-reviewed engineering data or IEEE standards for technical claims.
- MUST NOT allow generic marketing superlatives or unvalidated cybersecurity claims.
- Technical depth must be calibrated specifically for {{target_executive_audience}}.
- Specification must define explicit word budgets for all chapters.
Output format
1. Structural Blueprint & Chapter Allocations
Five distinct chapters with defined word counts, technical abstracts, and key learning outcomes.
2. Visual & Empirical Asset Specifications
List of required schematic diagrams, performance tables, and data visual concepts.
3. Reviewer Verification Matrix
Checklist for engineering, legal, and regulatory reviewers to validate draft completeness.
Self-review
- Confirm that {{substation_technology}} and {{integration_challenge}} form the central technical spine.
- Verify that chapter word budgets total exactly 3,500 words.
- Check that engineering standards citations are explicitly mandated.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.