Table of contents
Open Table of contents
The Assignment
The meeting room slowly emptied as laptops snapped shut and coffee cups disappeared into winter jackets. Heinrich remained seated for a moment, staring at the final line of the Statement of Work (SOW) projected on the screen:
Provide three complete electrical power system options for the Aurora Mill project, including preliminary cost estimates, operating assumptions, construction sequencing, and performance tradeoffs.
Six months earlier, Heinrich had graduated with a degree in electrical engineering. He could derive transmission line equations, solve phasor diagrams, and explain electromagnetic induction well enough to survive final exams. Yet none of his textbooks had explained how to power a remote industrial mill surrounded by mountains, environmental regulations, limited infrastructure, and a customer expecting reliable operation within twenty-four months. James gathered the remaining drawings into a folder and slid them across the table. “Start with the load estimates,” James said. “Everything in power systems begins there.”
Go With What You Know
Heinrich left the meeting with a clear constraint triangle forming in his mind: scope defined by the SOW, schedule fixed at six months, and cost assumptions still unknown but implicitly bounded by “commercial feasibility.” The ambiguity was uncomfortable, but not unfamiliar. What was new was the scale of system thinking required.
Back at his desk, Heinrich opened a fresh project folder and began building what he knew best: structure.
Project Charter and Scope Definition
Heinrich started by translating the Statement of Work (SOW) into a working project charter draft, even though James had already implicitly approved the scope. He still needed a baseline reference.
Key elements he defined:
Project Objective
- Develop three end-to-end electrical power system options for the Aurora Mill and camp
- Include preliminary capital cost estimates (Class 5 to Class 4 accuracy)
- Provide operating assumptions and lifecycle considerations
- Compare performance tradeoffs across reliability, cost, and emissions
In-Scope
- Load estimation (mill + camp + construction phase)
- Transmission study options
- Substation and distribution design concepts
- High-level protection and grounding philosophy
- Conceptual single line diagrams
Out-of-Scope
- Detailed construction drawings
- Procurement execution
- Final permitting submissions
He tagged this as a living scope baseline, expecting James would refine it.
Work Breakdown Structure (WBS)
Heinrich then moved into the core planning artifact: the WBS decomposition, starting at Level 1.
Level 1: Aurora Mill Power System Study
He broke it into major deliverables:
- 1.0 Requirements & Load Definition
- 2.0 Utility and Grid Assessment
- 3.0 Power System Option Development
- 4.0 Transmission Concept Design
- 5.0 Substation & Distribution Concepts
- 6.0 Protection & Reliability Conceptualization
- 7.0 Cost Estimation & Economic Comparison
- 8.0 Reporting & Client Deliverables
Each Level 1 item was further decomposed. For example:
- 1.0 Requirements & Load Definition
- 1.1 Construction phase load profile (1,000-person camp)
- 1.2 Operational mill load model (kWh/t basis)
- 1.3 Peak demand estimation
- 1.4 Load factor and diversity assumptions
- 1.5 Future expansion allowance
Heinrich paused at 1.3. Everything downstream depended on that number. He added a note to the WBS dictionary: “Load estimation is the primary uncertainty driver for all subsequent system design decisions.”
Project Schedule (Preliminary)
He sketched a rough milestone-based schedule across six months:
- Month 1: Requirements + load modelling
- Month 2: Utility engagement + transmission screening
- Month 3–4: Option development (3 system architectures)
- Month 5: Costing + tradeoff analysis
- Month 6: Final report + stakeholder review cycle
He flagged this as a Level 2 schedule baseline candidate, pending James’ approval. With a short project schedule, Heinrich knew it was important to identify the critical path. The Project Management software would identify it once the task order and duraction was provided. But for now, Heinrich noted the likely critical path: Load definition → transmission feasibility → system architecture selection → cost model → final comparison report
Stakeholder Register Draft
Stakeholder Identification
Heinrich realized the technical work would fail without stakeholder alignment. He started building a preliminary stakeholder register, even if incomplete.
| Stakeholder | Role | Influence | Primary Focus |
|---|---|---|---|
| Thomas | Customer project sponsor | High influence, high interest | Cost, schedule, reliability |
| James | Internal project lead | High influence, high control | Technical defensibility, assumptions, risk |
| Georg | Utility / vendor interface | Medium influence, high information control | Interconnection requirements, pricing constraints |
| Alessandro | Field engineering input | Medium influence | Constructability, real-world installation constraints |
| André | Protection and controls input | High technical influence | Fault scenarios, relay coordination, system stability |
He marked communication preferences as unknown, but essential to confirm within the week.
Risk Register (Initial Draft)
Heinrich added a preliminary risk log, mostly derived from experience gaps.
| Risk ID | Description |
|---|---|
| R1 | Load estimate uncertainty leads to oversized infrastructure |
| R2 | Transmission corridor constraints increase capital cost |
| R3 | Utility interconnection delays exceed schedule buffer |
| R4 | Environmental permitting impacts selected design option |
| R5 | Lack of stakeholder alignment causes redesign loop |
Each risk would later include:
- Probability (TBD)
- Impact assessment
- Mitigation strategy
- Risk owner
- Target resolution date
James would likely expect formal risk scoring before the first customer review.
Communication Plan (Draft)
Heinrich structured a basic communication management plan.
| Communication Activity | Frequency | Participants |
|---|---|---|
| Technical sync meetings | Weekly | Heinrich, James |
| Stakeholder consultations | Ad-hoc | Georg, Alessandro, André |
| Milestone review meetings | End of each project phase | Internal + customer stakeholders |
| Consolidated technical report | Month 6 | Customer delivery |
He added a question mark beside one line in his notes:
Preferred level of formal documentation versus iterative updates?
He suspected James would have a strong opinion on that.
End of Week Preparation
By the third day, Heinrich had assembled:
- Draft Project Charter
- Level 1 and Level 2 WBS
- Preliminary schedule and milestone plan
- Initial stakeholder register
- Risk log (Phase 0 version)
- Draft communication management plan
- List of open assumptions and dependencies
He compiled a final slide titled:
Aurora Mill Power System Study – Project Planning Draft (v0.1)
At the bottom, he added a final section.
Open Questions for James
- What level of design fidelity is expected for each of the three system options?
- Are we optimizing for lowest capital cost, lowest lifecycle cost, or balanced risk?
- What reliability standard should be assumed?
- N-1
- N-1-1
- Utility-specific criteria
- Should carbon intensity be treated as:
- a hard constraint, or
- a comparison metric?
- Are preferred utility contacts already established?
- What communication cadence does the customer expect during option development?
Heinrich closed his laptop. Three days was not much time. But for the first time, the problem had structure. And structure, he suspected, was where engineering actually began.