In short. A setting philosophy is a written set of rules for how relays are set: what each function protects, the margins used, how speed is traded against selectivity and how changes are controlled. It makes settings consistent, reviewable and defensible.
Why write it down
- Different engineers choose different margins unless rules are defined.
- Settings can be reviewed against stated rules rather than preferences.
- Future changes can be assessed against the original intent.
Core principles
| Principle | Meaning |
|---|---|
| Dependability | Operates when it should |
| Security | Does not operate when it should not |
| Selectivity | Trips only the faulted section |
| Speed | Clears faults before damage grows |
| Simplicity | Fewer functions and settings that are understood and maintained |
These conflict. Faster settings can reduce security, and wider margins can reduce speed. The philosophy states how the site resolves these trade-offs.
Content of a philosophy document
- Scope and objectives: equipment protected, priorities (safety, equipment, supply continuity).
- System data and operating modes: utility, generator, parallel, island; fault levels in each.
- Function-by-function rules: pickup margins above load and inrush, time grading margins, instantaneous use, earth-fault levels.
- Setting groups: when alternate groups are used, such as for grid versus generator.
- Documentation: format for settings sheets and curves.
- Testing: acceptance tests for settings.
- Change control: who may change, review and record, with version control.
Setting groups on generator systems
Fault current differs between utility and generator supply. A relay can hold two groups, with automatic selection by the breaker status. A mistake in selection is a risk, so the logic needs testing. See coordination.
Review cycle
Review settings after system changes, incidents, relay replacements and at planned intervals. Compare as-found with documented values during maintenance tests.
Illustrative example
A site’s philosophy states: overload pickup at no less than a defined margin above full-load current; time margins graded by a fixed interval for electromechanical relays and a smaller interval for numerical relays; instantaneous elements disabled on incomers where selectivity is required, unless bus protection is installed; and every setting change requires a second engineer review. An audit then finds one relay whose pickup differs from the sheet, and corrects it.
A repeatable settings process
- Collect data: single-line diagram, equipment ratings, impedances, CT and VT data, manufacturer curves.
- Calculate: load currents, maximum and minimum fault levels, inrush and starting currents.
- Define goals: protect the equipment, clear faults fast, isolate the minimum area, avoid nuisance trips.
- Choose functions and curves.
- Set and coordinate from the load towards the source, with time margins.
- Review with the operator and manufacturer.
- Apply, test and document.
Core philosophy points
- Dependability: trip when required.
- Security: do not trip when not required.
- Selectivity: trip only the nearest device.
- Speed: clear quickly to limit damage.
These goals conflict, and settings are a balance.
Setting record
| Field | Content |
|---|---|
| Function | For example 51, 50, 51N, 27, 59 |
| Pickup and curve | Primary and secondary values |
| Time delay | Seconds |
| Basis | Why this value |
| Date and engineer | Responsibility trail |
Change control
Any setting change needs approval, a record and, where practical, a test. Store backup files securely. See coordination.
Settings are the work of a qualified protection engineer; guides like this explain method, not site-specific values.
Common mistakes
- Settings held only in the relay.
- No version control.
- Setting groups never tested.
What to send us
Send the existing settings and single-line diagram. Send your application details. See also maintenance and lifecycle testing.
Questions engineers ask
Is a philosophy needed for a small site?
A short version is still useful, to keep settings consistent and recoverable.
What is dependability versus security?
Dependability is operating when needed. Security is not operating unnecessarily.
How are settings kept safe?
With password control, version records and checks against the approved sheet.
When should settings be reviewed?
After changes, faults, new equipment and at planned intervals.
This guide gives general principles. Settings need studies for each system.
