Updated 6 October 2026 • October 2026–September 2029 • 8 hours per week
Purpose and relationship to your existing plan
Build toward a practice that combines protection engineering, power-system studies, commissioning, event investigation, and operational technology (OT) cybersecurity. Your approximately eight years of P&C commissioning and BTech provide the starting point. The main development needs are independently deriving and defending designs, validating models, producing reviewable reports, and securing the systems that implement protection.
This is a service-development companion to your existing existing protection development plan, reviewed in its 2 October 2026 version. That document remains the detailed protection-topic reference. Use the schedule here to prioritize it; do not run both schedules as additional workloads. The calendar below is a planning estimate, not a prediction of professional competence or business income.
Recommended initial positioning: protection, commissioning, and event-analysis expertise with secure substation communications capability. Broader consulting can follow through supervised project delivery and collaboration with specialists. A small firm need not deliver every specialty through one person.
1. Translate the target services into evidence
NERX's website lists eight service areas. The cyber links and learning projects below are proposed additions for your development, not claims about NERX's cybersecurity offering. [1]
| Target service | Knowledge to develop | Portfolio evidence | Cybersecurity connection | Sequence |
|---|---|---|---|---|
| Protective relaying and testing | Settings rationale, coordination, CT/VT application, logic, test design | Reviewed feeder and transformer settings calculations with commissioning matrices | Approved settings baselines, access control, change tracking and recovery | First |
| Protection misoperation investigation | COMTRADE, phasors, digital chronology, relay logic and breaker behaviour | Three event reports distinguishing evidence, inference and unresolved questions | Correlate event, access and configuration records; distinguish cyber hypotheses from ordinary faults | First |
| One-lines and equipment sizing | Operating arrangements, load duty, fault duty, grounding, instrument transformers | One-line, equipment schedule, design assumptions and checks | Asset inventory and communication architecture derived from the physical design | First–second year |
| Power-system analysis | Load flow, short circuit, coordination, motor starting and stability | Validated model, scenarios, sensitivity study and engineering report | Protect model integrity and change history | Second year onward |
| Arc-flash analysis and mitigation | Fault and arcing-current models, clearing times, equipment geometry and operating modes | Supervised study with documented inputs, sensitivity and mitigation comparison | Control protection-setting changes that could alter clearing time | Second year onward |
| Power-quality investigation | Sags, interruptions, harmonics, unbalance, resonance and measurement quality | Measurement plan and synthetic/public-data diagnostic report | Separate process disturbances from communication and data-quality failures | Second year onward |
| Generator interconnection coordination | Utility requirements, model submissions, generator/IBR behaviour and studies | Fictional interconnection requirements and model-validation package | Secure plant-controller and utility communication interfaces | Third year onward |
| NERC compliance programs | Applicability, responsibilities, evidence, maintenance and corrective actions | Mock applicability register and evidence package | CIP assessment and evidence where applicable | Build gradually |
2. Workload and operating rules
Use eight hours a week over 48 active weeks per year, approximately 384 hours annually and 1,152 hours over three years. Reserve four weeks annually for outages, exams and recovery. Field learning supports this plan but is not automatically equivalent to study or independent design experience.
| Weekly block | Hours | Output |
|---|---|---|
| Power/protection theory and calculations | 2 | One worked calculation and its assumptions |
| Networking and cybersecurity | 2 | One configured, observed or documented control |
| Integrated project | 3 | A reproducible engineering artifact |
| Review and explanation | 1 | Error log, revision and five-minute technical explanation |
During heavy work or MEng periods, use four hours: 90 minutes power, 60 minutes cyber, 90 minutes integrated work. Count overlapping academic assignments toward the plan. Do not add eight hours on top of a full course workload.
Every project follows: predict → calculate → simulate/test → reconcile differences → document → obtain review. Use fictional systems and public or expressly permitted data. Keep workplace settings, drawings, credentials and event files inside authorized systems. Personal simulations do not authorize live-system tests or changes.
3. First 90 days: one system, twelve connected exercises
Use a fictional 115/13.8 kV substation with a 25 MVA grounded-wye/delta or delta/grounded-wye transformer selected explicitly for the case, a 13.8 kV bus, two feeders, and an RTU. State which winding is grounded; do not use an ambiguous vector group. Begin with one supply and no distributed generation. Add a BESS only after the base case is validated.
Choose and document source sequence impedances, transformer impedance/base, CT/VT ratios, loads, line impedances and breaker clearing assumptions. Invented inputs must be labelled training assumptions; no outputs are field settings.
| Week | Power/protection work | Cyber/network work | Deliverable |
|---|---|---|---|
| 1 | Draw zones, CTs, breakers, ground connections and trip boundaries; assess phasors and units | Draw devices and data flows; identify switch/router/firewall roles | One-line, network sketch and baseline skills assessment |
| 2 | Calculate transformer full-load currents, CT secondary values and impedance bases | IPv4 addressing, subnets and routing; plan three lab segments | Calculation sheet and IP-address plan |
| 3 | Compute a three-phase bus fault from an equivalent source | Inspect ARP, ICMP and TCP on your isolated lab | Hand calculation and annotated packet capture |
| 4 | Build sequence networks and calculate an earth fault | Separate engineering, station and monitoring roles in the lab design | Fault comparison and segmentation rationale |
| 5 | Establish feeder pickup constraints using load and minimum fault current | Accounts, least privilege and administrative access | Candidate settings rationale and access matrix |
| 6 | Coordinate two overcurrent devices using exact curve definitions and clearing assumptions | Configure a simple allowlist; prove one permitted and one denied flow | TCC plot and firewall verification record |
| 7 | Transformer differential: vector compensation, ratios and restraint definitions | Baseline a fictional configuration; compare and explain revisions | Differential calculation and settings-change record |
| 8 | Design internal/external fault, inrush-supervision and nonoperation tests | Back up and restore a lab configuration; verify behaviour afterward | Transformer test matrix and restore evidence |
| 9 | Learn COMTRADE configuration, channel scaling, sampling rates and digital states | File hashes, source provenance and protected evidence copies | Analyzer that plots channels with correct units/time |
| 10 | Add explicitly defined RMS/phasor calculations and sequence components | Compare device time sources and timestamp quality | Verified synthetic waveform results and time-quality note |
| 11 | Reconstruct pickup, trip, breaker indication and current interruption | Correlate mock engineering-workstation logs with an event timeline | Event-investigation report with competing explanations |
| 12 | Explain and defend the combined case; close review findings | Threat-model settings changes, remote access and loss of visibility | Versioned capstone and next-quarter gap list |
Use any remaining days for correction and review. If calculations or input scaling remain unreliable, repeat the relevant exercises before adding more automation.
First-quarter gate: explain ten representative calculation/input checks with correct units; reconcile a balanced and an unbalanced fault against a second method; explain protection sensitivity and coordination trade-offs; restore a lab configuration successfully; reproduce an event timeline without treating an indication as proof of current interruption. Any unresolved critical error blocks progression in that topic.
4. Months 4–12: deepen protection and operational security
| Period | Main learning | Required project | Completion evidence |
|---|---|---|---|
| Months 4–6 | Distance loops, residual-compensation convention, load encroachment, line differential, POTT/DCB/DTT, breaker failure, reclosing and synchronism check; networking and Security+ foundations | Line-protection application with communication-loss and failed-breaker cases; segmented network lab | Explain selectivity, backup timing, channel assumptions and deliberate nonoperation; demonstrate allowed/blocked network paths |
| Months 7–9 | Bus differential; motor/generator protection overview; CT saturation; DNP3 points/events/quality; IEC 61850 data models, SCL, MMS, GOOSE, Sampled Values; timing and redundancy | Fictional station integration design, point list and IEC 61850 signal map; cyber risk register | Trace a signal end to end and identify timing, configuration and quality dependencies; distinguish conceptual mapping from tested interoperability |
| Months 10–12 | Settings QA, model validation, protection event analysis; OT hardening, remote access, passive monitoring and recovery | Integrated substation package with settings rationale, FAT/SAT plans, event report and security design | Reproduce results, close reviewer comments and document untested limitations |
First-year success means stronger commissioning judgment and readiness for supervised settings/design/studies and OT assignments. It does not mean mastery of every relay family or independent readiness for the entire service catalogue.
Do not install a generic IT security appliance in a time-critical protection path simply because it is a security control. Learn the actual protocol, forwarding path, redundancy and latency requirements, then validate any proposed control's effect. Ordinary station GOOSE is a Layer-2 topic; treating every protection message as routed TCP traffic creates design errors.
5. Second year: studies, design and assessed OT security
| Quarter | Power work | Cybersecurity work | Client-style output |
|---|---|---|---|
| Q5 | Load-flow convergence, bus voltage, transformer taps, reactive power and normal/contingency operation | OT inventory, zones/conduits and risk assessment | Study report with assumptions, operating cases and prioritized OT risk register |
| Q6 | Maximum/minimum fault levels, breaker duty and coordination across source arrangements | Secure engineering access, account lifecycle, backup and recovery | Reviewed short-circuit/coordination package plus access-and-recovery design |
| Q7 | Arc-flash methodology and mitigation under experienced review; motor starting and PQ foundations | Logging, passive traffic baselines and incident-response tabletop | Mitigation comparison and incident playbook; separate validated results from training-only exercises |
| Q8 | One-lines, sizing basis, station DC/tripping requirements and design interfaces | Configuration management and procurement security requirements | Integrated design basis, equipment schedule and acceptance-test specification |
Aim for participation in at least two actual reviewed assignments in a chosen specialty, where access and role permit. Two projects are an exposure target, not a universal threshold of competence. Seek responsibility for complete deliverables and their revisions, rather than only executing someone else's checklist.
6. Third year: choose depth and establish repeatable delivery
Choose one primary commercial direction while maintaining the shared foundation:
- Utility protection and digital substations — recommended first fit: complex settings, scheme assurance, event analysis, station networks and OT security. It builds most directly on your field experience.
- Industrial reliability consultancy: short circuit, coordination, arc flash, motor starting, PQ and industrial control-system security. Requires more industrial equipment and operating-context exposure.
- Generation/BESS interconnection: load flow, dynamic models, inverter-based resources, protection interactions and secure plant communications. Add RMS/EMT distinctions, model limitations and project-specific interconnection requirements before offering independent study conclusions.
Across quarters 9–12, complete a specialist capstone, contribute to progressively more demanding reviewed projects, write a delivery procedure and build a reusable QA checklist. Learn scoping, assumptions, exclusions, change orders, estimates, schedule risk, peer review, records retention and professional liability arrangements alongside the technical work.
Expected horizon: three years can build substantial additional capability with consistent practice and relevant assignments. Broad independent consultancy may take longer, particularly for dynamics, interconnection and arc-flash work. Expand by demonstrated competence, not a launch-date promise.
7. Credential and training priorities
These are recommended investments, not a universal list of mandatory qualifications.
| Priority | Credential/training | Suggested timing | Decision rule |
|---|---|---|---|
| Ongoing | P.Eng. pathway and applicable practice authorization | Continue alongside all phases | Central to the engineering-service objective; eligibility and approval remain regulator decisions |
| 1 | Networking fundamentals at CCNA depth | Start now; exam optional in year 1–2 | Pass practical subnet/routing/segmentation/troubleshooting gates before advanced OT security |
| 2 | CompTIA Security+ | First cyber exam if a broad foundation is needed; roughly months 4–9 | Use current official objectives for the exam actually booked; this plan does not assume a SY0-801 launch date |
| 3 | Applied relay/vendor training | One targeted course in year 1 | Choose the course that addresses a measured settings/test gap on equipment you use |
| 4 | ISA/IEC 62443 fundamentals, then relevant assessment/design certificate | Year 2 | Prioritize when preparing risk assessments or security architectures; complete required prerequisites |
| 5 | GICSP | Year 2–3, preferably funded by employer | Worth considering after practical networking and OT work; connects IT, engineering and control-system security |
| Later | Specialist detection/response or project-management credential | Only when the intended service needs it | Avoid diverting first-year time from core engineering and networking competence |
Cisco's CCNA scope includes networking, connectivity, services, security and automation. ISA offers a staged industrial-security certificate program; it is distinct from professional engineering licensure. GICSP covers industrial systems security across the lifecycle. [3–5]
Do not purchase several exam vouchers or expensive study platforms at once. Begin with existing textbooks/manuals, official objectives and lab work. Take one funded specialist course after a concrete gap emerges.
8. Reference shelf and standards application
Use the protection textbooks already identified in your existing plan: *Power System Relaying*, fifth edition, and *Protective Relaying: Principles and Applications*, third edition. Pair every concept with the exact manual for the relay model, firmware, options and configured source. SEL ePROT 401 is a relevant engineer-oriented foundations option; ePROT 405 provides industrial applications and settings exercises. Neither substitutes for hands-on relay work. [6–7]
| Topic | Reading/reference family | How to use it |
|---|---|---|
| Measurement and protection | IEEE C37.110, C57.13, C37.2; relevant IEC 60255 and IEC 61869 parts | Connect measurement performance, function definitions and equipment requirements to the actual application |
| Equipment protection | IEEE C37.91, C37.113, C37.119 and equipment-specific guides | Develop application reasoning and test coverage, using the applicable editions |
| Arc flash and workplace electrical safety | IEEE 1584; CSA Z462 for Canadian context; NFPA 70E where relevant | Distinguish calculation method from work-practice requirements; verify project scope, edition and jurisdiction |
| Digital substation | IEC 61850 and relevant IEC 62351 parts | Separate communication/data-model requirements from security requirements and device support |
| OT cybersecurity | NIST SP 800-82 Rev. 3; ISA/IEC 62443 | Build an OT risk assessment, architecture and recovery approach that respects physical-process constraints |
| Reliability compliance | NERC PRC, CIP and, as needed, applicable MOD/TPL/FAC standards | Establish applicability, responsible entity, effective version and implementation dates before creating evidence |
This table is a reading map, not a complete compliance specification. NERC's current portal provides standards and implementation materials; PRC-004, PRC-005 and PRC-027 are particularly relevant to misoperations, maintenance and coordination respectively. NERC applicability is not established simply because a client owns a substation. [8]
Start the cyber reading with NIST SP 800-82 Rev. 3: OT architecture and characteristics, threats/vulnerabilities, risk, security architecture and operational controls. Turn each section into a page about your fictional station rather than reading it only for vocabulary. [2]
9. Laptop lab and software strategy
Use your current MSI laptop. Begin with a few modest virtual machines, a virtual firewall/router, a protocol client/server or simulator, packet capture and version-controlled project files. Start without buying relays, switches or another computer.
Maintain two connected learning models: an electrical model of the fictional station and an isolated communications model. Do not claim that a software simulation establishes real relay timing or hardware interoperability. If a protocol implementation or license is unavailable, document its interface and use public captures or a tabletop exercise until actual testing is possible.
For power studies, use a legally available tool appropriate to the calculation. Your previously reported school PSS/E access must be checked for current availability and permitted use. Choose one principal study tool initially; commercial project needs can later determine ETAP, SKM, ASPEN, CAPE or another platform. Learn model assumptions and independent checks before collecting software packages.
Develop the COMTRADE analyzer incrementally: channel/time display; correct scaling; declared phasor/RMS algorithms; sequence components; digital timeline; then carefully defined impedance loops. Record sampling-rate changes, window delay, frequency assumptions, missing values and trigger/time semantics. Validate synthetic balanced, unbalanced and changing-frequency signals and at least one independently interpreted public event. An automated narrative must be traceable to evidence and must not invent fault causes.
10. Portfolio and readiness review
Keep seven core artifacts: (1) one-line/design basis, (2) validated fault and load-flow model, (3) feeder/transformer settings rationale, (4) commissioning matrix, (5) event-investigation report, (6) station communications/security architecture, (7) recovery and change-control evidence.
Every artifact includes purpose, input provenance, assumptions, method, independent checks, scenarios, results, limitations, revision history and review findings. Public portfolio copies must contain only material you are authorized to disclose.
Use a four-stage skills record:
- Explain: describe the mechanism and assumptions clearly.
- Apply: solve a new exercise and independently check it.
- Deliver with review: produce usable work and close a qualified reviewer's findings.
- Lead within scope: show repeated sound decisions, handle exceptions and review others' work within your authority and competence.
Progression is topic-specific. A strong event analyst can still be a beginner in transient stability. Self-review and automated checks help learning but do not replace independent technical review for client engineering.
11. Path to offering services
Begin by building capability and reviewed experience within authorized employment or project arrangements. Your earliest prospective scope is likely commissioning planning, relay settings/test QA, event-analysis support and OT asset/configuration documentation. Classify the actual engagement before offering it; calling engineering “support” does not remove professional obligations.
In Ontario, a personal engineering licence and a firm's Certificate of Authorization serve different purposes: PEO states that offering or providing professional engineering services to the public requires a Certificate of Authorization. Plan the appropriate Ontario registration, responsible professional oversight and business authorization before marketing engineering services. Registration elsewhere does not by itself establish Ontario practice authority. [9]
Before independent delivery, have defined scope, competence evidence, applicable authorization, technical review, suitable contractual/insurance arrangements and approved access to tools/data. For employed side work, resolve employer conflict and outside-work requirements before accepting an engagement.
The eventual differentiator is practical: explain what a power system should do, why its protection operated, and how to secure and recover the digital systems that control it.
Sources and resource links
Checked 6 October 2026. Verify versions, course availability and requirements when booking training or commencing regulated work.
- NERX service and training overview: https://www.nerxpower.com/#services
- NIST SP 800-82 Rev. 3: https://csrc.nist.gov/pubs/sp/800/82/r3/final
- Cisco CCNA: https://www.cisco.com/site/us/en/learn/training-certifications/certifications/enterprise/ccna/index.html
- ISA/IEC 62443 certificate program: https://www.isa.org/certification/certificate-programs/isa-iec-62443-cybersecurity-certificate-program
- GIAC GICSP: https://www.giac.org/certifications/global-industrial-cyber-security-professional-gicsp
- SEL ePROT 401: https://selinc.com/selu/courses/eprot/401/
- SEL ePROT 405: https://selinc.com/selu/courses/eprot/405/
- NERC Reliability Standards: https://www.nerc.com/standards/reliability-standards
- PEO Certificate of Authorization: https://www.peo.on.ca/apply/certificate-authorization
Technical exercises, sequence, time estimates, deliverables and gates are recommendations tailored to your goal, not requirements asserted by these organizations.