Challenge 02

Changes to the electrical network

New transformers, generation, motors or supply arrangements change fault levels and power flows — and settings designed for the old system may no longer fit.

Discuss a network change
Illustrative system Not connected to any installation
Illustrative single-line diagram of an industrial switchboard Illustrative system, not a real installation. An incoming supply feeds breaker Q0 and transformer T1, then main breaker Q1 and a busbar with two outgoing feeders, each with its own breaker (Q2, Q3). Relay R1 protects the transformer, R2 the incomer, R3 and R4 the feeders. A voltage transformer on the busbar and a station control link to R2 are also shown. Incoming supply upstream network Q0 T1 transformer Q1 main busbar VT M Q2 Feeder 1 process load Q3 Feeder 2 distribution G New generation illustrative change illustrated fault R1 87T · 50/51 R2 51 · 51N Station control R3 50/51 R4 50/51
  1. Illustrative change — new on-site generation (dashed)
  2. R4 feeder relay — may now see fault current in either direction
  3. Busbar fault level may increase with the added source
  4. R2 incomer relay — grading with downstream devices may need rechecking

Actual protection behaviour depends on system data, settings, equipment and fault conditions.

Protection settings are calculated for a particular system. When that system changes — a larger transformer, a new generator or battery system, an additional supply, new motors or reconfigured feeders — fault levels and current paths change with it. Settings that were correct before the change may become insensitive, mis-coordinated or no longer suitable for the direction of fault current.

Typical signs

  • A transformer has been replaced or uprated.
  • On-site generation, energy storage or a second supply has been connected.
  • Large motors or new feeders have been added.
  • The utility has advised a change in available fault level.
  • Settings have not been reviewed since the system was modified.

What may need investigation

  • Updated short-circuit levels at the relevant points, for maximum and minimum conditions.
  • Whether existing pickup settings remain sensitive enough for minimum fault conditions.
  • Grading margins between devices after the change.
  • Whether new sources create reverse or bidirectional fault current that calls for directional elements.
  • Equipment ratings and CT performance at the new fault levels.

Which of these apply depends on the installation and on what the available records show.

Information that helps

  • Updated single-line diagram showing the change
  • Data for new equipment: transformer impedance, generator or inverter data, motor data
  • Utility fault level information
  • Existing relay settings
  • The operating configurations you need to cover

You do not need all of this to start a conversation. We will agree how to share drawings and records after first contact.

Possible deliverables

What the engineering work could produce

Protection study and coordination report

Fault levels, the coordination between protective devices and the reasoning behind each recommended setting — with the data and assumptions stated.

Typically contains

  • System data, sources and assumptions
  • Short-circuit results for the agreed operating cases
  • Time–current plots for each protection path
  • Grading margins checked against the agreed criteria
  • Issues found and recommended changes

What it is not. A study documents calculations and recommendations. It is not field commissioning and does not confirm how installed relays are actually set.

Illustrative deliverable — not a client project.
Study report Example document · layout only

4.2 · Coordination: Feeder 1 → Incomer

CheckCriterionStatus
Margin at max. faultAgreed CTISee §4.3
Margin at min. faultAgreed CTISee §4.4

Relay settings schedule

Function-by-function settings for each relay, each traced to a documented calculation or criterion.

Typically contains

  • Enabled functions and setting values per relay
  • Reference to the calculation or criterion behind each value
  • Setting groups and conditions for their use
  • Notes for implementation and checking

What it is not. A settings schedule is not necessarily a manufacturer-native configuration file. Native files can be prepared only where the relay platform, software tools and information available allow, and when they are in scope.

Illustrative deliverable — not a client project.
Settings schedule Example document · layout only

3 · Settings schedule — Feeder 1 and incomer

RelayFunctionParameterValueBasis
R351I>400 ACalc. 3.1
R351Curve · TMSIEC SI · 0.10Calc. 3.2
R350I>>OffNote 2
R251I>800 ACalc. 3.4
R251Curve · TMSIEC SI · 0.25Calc. 3.5
R251NIN>120 ACalc. 3.7

Values in primary amperes. Conversion to relay-native settings files depends on the platform and is a separate step.

Technical findings and recommendations

A concise record of what was reviewed, what was observed, what it may mean, and what we recommend — including where the evidence is incomplete.

Typically contains

  • Scope of the review and information used
  • Observations with supporting evidence
  • Likely implications, with their confidence
  • Recommendations and suggested next steps

What it is not. Findings reflect the data reviewed. Where records are incomplete, the report says so rather than presenting a single definitive cause.

Illustrative deliverable — not a client project.
Findings Example document · layout only

Finding F1 · Feeder 1 and incomer grading

Observation
From the settings provided, the R2/R3 margin is below the agreed criterion at the higher fault levels.
Implication
Q1 may trip before Q2 for close-in faults on Feeder 1.
Recommendation
Revise R2 time multiplier; confirm CT data before implementation.
Confidence
Medium — disturbance record incomplete.

Scope and boundaries

  • A study covers the configurations and data agreed at scoping. Other operating modes may need separate assessment.
  • A study does not change relay settings by itself — implementation and testing remain separate, controlled activities.

Start a conversation

Tell us what your system is doing — and what you need it to do.

A few lines are enough to start. We will ask for drawings, settings or records later, through a channel agreed with you — there is no need to send them with your first message.