Know what the relay sees.
Start with CT ratios, residual current and the source-to-trip path. Then build the transformer protection depth you need for T60 work.
A practical route from P&C commissioning to protection design, power-system studies and OT security.
Start with CT ratios, residual current and the source-to-trip path. Then build the transformer protection depth you need for T60 work.
Busy week? Use four hours: 1.5 h theory, 2 h practice and 30 min review.
Explain the fault. Derive the expected result. Trace the implementation. Design a discriminating test. Defend the conclusion.
48 teaching weeks plus four catch-up weeks. Expand a module for its weekly work, deliverable and readiness check. Advance on evidence; move dates around outages and coursework.
CT/VT ratios, phasors, zones and the complete source-to-trip path.
Labelled one-line, ten conversion examples and a source-to-trip diagram.
Readiness checkGiven a new CT ratio, predict metering and explain what a pickup test does not prove.
Understand differential stability before designing operating tests.
Transformer application note, source map and test matrix.
Readiness checkExplain how a CT-ratio change can affect differential behaviour even if the 87 settings fields are unchanged.
Connect fault physics to the quantities a relay actually measures.
Fault-study memo with balanced and unbalanced cases.
Readiness checkDistinguish total bus fault current from the current through a particular relay.
Explain why a setting is appropriate, then verify it.
Coordination plot with settings rationale and limitations.
Readiness checkDiagnose miscoordination caused by pickup, timing, curve shape or system changes.
Translate system impedance into reach and meaningful test phasors.
R-X plot, reach calculations and boundary-test matrix.
Readiness checkExplain why a point inside the apparent zone may still be blocked or not operate.
Follow protection across terminals and through the breaker.
Logic diagrams, trip matrix and deliberate nonoperation cases.
Readiness checkExplain which terminals trip for internal/external faults with healthy and failed channels.
Build a small defensible study and check the model.
Study memo with base case, variations, checks and a recommendation.
Readiness checkFind an incorrect impedance or unit and distinguish power flow, fault and dynamic studies.
Translate protection philosophy into a coherent bay design.
Fictional transformer-bay design package and acceptance-test outline.
Readiness checkFind wrong CT allocation, missing trip-supply supervision and inconsistent source names.
Build conclusions from measurements and a defensible timeline.
Annotated plots, timing tables and two concise incident reports.
Readiness checkState the evidence for your conclusion and what the available data cannot establish.
Understand the network, protocol and timing paths.
Lab network drawing, point list, packet explanation and failure matrix.
Readiness checkDistinguish connectivity, mapping, timestamp and application-logic failures.
Build security around availability, engineering access and recovery.
OT architecture, risk register and demonstrated restore record.
Readiness checkExplain how each control affects protection availability and how recovery is verified.
Defend an integrated design and its trade-offs.
Capstone package and two-page decision memo.
Readiness checkExplain an acceptable alternative, why you chose your approach and what evidence would change it.
Build readiness for supervised protection design and studies. SME standing develops through repeated delivery, review and experience with unusual conditions.
Use fictional systems and permitted public data. Label every piece as training work.
Check your school access in week one. Begin a small model alongside the foundations; don’t wait until Module 7 if access may expire.
Continue your P.Eng work separately. Choose one additional exam when it supports a specific role and fits the workload.
A dated research snapshot, with Ontario first and selected international developments. Source dates and project stages are explicit. Learning applications are suggested exercises, not claims about a utility’s installed protection scheme.
Hydro One and HOSSM filed a joint leave-to-construct application for a proposed 230 kV line between Mississagi and Third Line stations, with related station work. Filing is a project milestone; it is not construction approval.
Create a fictional line-terminal trip matrix. Compare channel failure, breaker failure and backup-clearing paths.
Modules 5 · 6 · 8Hydro One lists an ongoing Class Environmental Assessment, four route alternatives and September 2026 open houses. Its current project page targets service in 2032; dates remain subject to change.
Build a load-growth scenario in your small power-flow model. Explain when voltage or thermal limits justify reinforcement.
Modules 3 · 7 · 8A September report quotes Hydro One targeting phase-one energization by the end of 2026 and phase two by the end of 2027. The utility’s project page still carries an older phase-one target, so the dates are not fully reconciled.
Draft an energization-readiness checklist linking CT polarity, settings revisions, trip paths and end-to-end timing evidence.
Modules 1 · 5 · 6National Grid announced Triton, developed with Atos, to combine network datasets and support demand scenarios and reinforcement planning. This is a planning tool, not a claim of virtualized protection deployment.
Model two demand futures and an outage. Document which inputs dominate your recommendation and how you validate them.
Modules 7 · 12DOE reported that a University of Arkansas collaboration with Bastazo and Network Perception produced V-INT, addressing asset exposure and complex firewall-policy assessment. The toolset was integrated with commercial platforms.
Draw an isolated lab’s allowed data flows. Identify an overly broad firewall rule, explain its consequence and document a correction.
Modules 10 · 11GE Vernova discusses software-defined protection and control and the need to integrate cybersecurity with IT/OT coordination. This is technical context, not evidence that a named utility has commissioned a new installation.
Compare a conventional IED architecture with a virtualized concept: timing, redundancy, failure domains, rollback and acceptance testing.
Modules 10 · 11 · 12This edition does not refresh automatically. Waasigan schedule context: Hydro One project overview. The 2025 entries are supporting technology context, not new September 2026 announcements.
Use your existing text in module order: foundations, transformer, overcurrent, distance, pilot protection and events. Use Blackburn & Domin for a second explanation.
For the reported 7.43 platform, match the 7.4x manual to actual hardware and options. Verify source mapping and the manufacturer’s restraint definitions.
Published OT security guidance. Start with architecture, operational constraints and recovery. Distinguish published guidance from draft revisions.
Optional structured theory from your plan. Substitute it for overlapping study blocks; do not stack it onto the full eight-hour week.
Learn the purpose of PRC-004, PRC-005 and PRC-027. Confirm current versions and facility applicability before using a requirement.
Use jurisdictional enforcement information alongside the relevant standard. A publication date alone does not establish applicability.
Use fictional settings and isolated training systems. Keep employer drawings, configurations and event data in approved systems. Physical relay work follows authorized isolation, testing and restoration procedures; never open an energized CT secondary.