As-found are the settings and performance of a relay as it was found, before touching it. As-left are the settings it was left with at the end. Between the two there must be an authorized, recorded change, or none. The record of each intervention, with its date, who did it and why, allows comparison and shows that the protection was left as the study ordered.
Short answer
As-found are the settings and performance of a relay as it was found, before touching it. As-left are the settings it was left with at the end. Between the two there must be an authorized, recorded change, or no change. Each intervention produces three records: the as-found, the authorized change (if any) and the as-left. Today’s as-left is the next visit’s as-found; if they do not match, someone changed something in between. It does not describe how a relay is programmed: that depends on each device and manufacturer.
What it is for
A protection relay is the last control of an installation, and its settings are the result of a study. Over time it is tested, changed for a plant modification, replaced or restored from a backup. Each time there is a risk that the setting left is not the one the study orders. The as-found and as-left record answers three questions: how was it?, what was changed, who authorized it and why?, how was it left? It is also part of the traceability that an auditor or a grid operator may ask for. See what to ask for in a protection test report.
What each record contains
As-found record. Before any test or change, the relay’s state is read and saved. It must carry: relay identification (location, make, model, serial number, firmware version), date and time, who read it, the settings as they were (the file exported from the relay and a table of the critical settings), and the results of the tests made on that state (for example, the measured pickup value). If the relay has setting groups, the active one is recorded; see SGCB setting groups.
Authorized change. If a setting must be changed, it is done with a change request that states: which setting, from what value to what value, why (study, review, fault), who authorizes it and the date. Without this authorization the change is not made, however small.
As-left record. After the change and the final tests, the relay is read again and saved: the final settings, the result of the later tests, the list of differences from the as-found and the sign-off. If there were no changes, the as-left is made all the same and «no changes» is noted.
Minimum format
A table per relay with these columns works well:
| Setting | Unit | As-found | Authorized change | As-left | Remark |
|---|
One row is filled for each critical setting (pickups, curves, times, blocks, measuring transformer ratios) and the complete exported file of the relay is attached, because the table covers only the critical settings and the file covers all of them.
Change control
- One request per change, with number, date, reason, setting and values before and after.
- Authorization by whoever answers for the protection, normally the owner’s protection engineer, and not whoever runs the test.
- Backup before and after. The as-found file is saved before the change, and the as-left after it. See backup and recovery of IED settings and the case of settings lost when replacing a relay without a backup.
- Controlled access. Who may change settings must be defined; see account and password management in IEDs.
- Automatic comparison. An as-left compared with the as-found by file differences detects changes the table does not show.
Worked example: a feeder 51 relay
Example data. Assumed data for illustration. A feeder with a current transformer ratio of 200/5 A, that is 40. The relay uses the IEC 60255-151 normal inverse curve, with t = TMS × 0.14 / ((I / Is)^0.02 − 1). On arrival the relay has: pickup 1.60 A secondary, TMS 0.30 and instantaneous 12.0 A secondary. The study orders TMS 0.25 and leaves the rest unchanged. The pickup tolerance is assumed to be ±5 % for this example.
Step 1. As-found in primary values. Pickup: 1.60 × 40 = 64 A. Instantaneous: 12.0 × 40 = 480 A.
Step 2. As-found test. Current is injected and the relay picks up at 1.64 A. The error against the setting is (1.64 − 1.60) / 1.60 = 2.5 %, within the assumed tolerance of ±5 %. It is recorded in the as-found.
Step 3. Authorized change. Change request: TMS from 0.30 to 0.25. The variation is (0.25 − 0.30) / 0.30 = −16.7 %.
Step 4. Effect of the change. For a current of 8 times the pickup, the curve gives 0.14 / (8^0.02 − 1) = 3.297 s with TMS = 1. With TMS = 0.30 the time was 0.989 s. With TMS = 0.25 the time is 0.824 s. The relay now operates 0.165 s sooner for that current.
Step 5. As-left. The change is loaded, the time test is repeated and the file is saved. The table ends up like this:
| Setting | Unit | As-found | Authorized change | As-left |
|---|---|---|---|---|
| 51 pickup | A sec. | 1.60 | no | 1.60 |
| 51 TMS | — | 0.30 | yes, to 0.25 | 0.25 |
| 50 instantaneous | A sec. | 12.0 | no | 12.0 |
Step 6. Check. Of three critical settings, one changed: 1 / 3 = 33 %. The other two are equal in as-found and as-left, and the TMS change matches the authorized request. At the next visit, the as-found must be TMS 0.25.
Reading. If at the next visit the relay is found with TMS 0.30, comparison with this as-left shows that someone put it back to the previous value, and it can be asked when and why. Without a record, that finding would go unnoticed.
Frequent mistakes
- Changing a setting first and recording the as-found afterward. Then there is no as-found.
- Noting only the table and not saving the exported file.
- Mixing secondary and primary values without saying so.
- Keeping the record on the computer of whoever ran the test and not in the plant’s file.
- Not comparing the as-found with the as-left of the previous visit.
Checklist
- Before touching the relay, I read and saved the as-found file and table.
- I recorded identification, date, who and firmware version.
- I recorded which setting group was active.
- I compared the as-found with the as-left of the previous visit.
- Each change has a request with values before and after, reason and authorization.
- After the change I repeated the tests of the affected functions.
- I saved the as-left file and the list of differences.
- I stated the unit of each value, secondary or primary.
- The record went into the plant’s file.
Related guides
- Backup and recovery of IED settings
- Case: settings lost when replacing a relay without a backup
- What to ask for in a protection test report
- SGCB setting groups: how they are changed in IEC 61850
- Account and password management in IEDs
- Test blocks and bay isolation
When to call us
Do you need this record? We define the format and the change control with you from engineering design and studies, for plants and substations in any country. Contact us.
References
- IEC 60255-151, Measuring relays and protection equipment, Part 151: Functional requirements for over/under current protection (normal inverse curve formula used in the example).
Frequently asked questions
What is the difference between as-found and as-left?
As-found is the state in which the relay was found, with the settings it had and how it responded to the tests. As-left is the state in which it was left: the final settings and the result of the later tests. If there were no changes, the two settings are equal, but both records are made all the same.
Why record the as-found even if nothing is going to be changed?
Because it is the only evidence of how the protection stood. If a relay was found with a setting different from the one the study orders, the record shows since when and allows an investigation. Without an as-found there is no way to know whether there was drift or an unauthorized change.
How often is the as-left compared with the previous as-found?
At every intervention. The as-left of the last intervention must be the as-found of the next one. If they do not match, someone changed the settings between the two visits and it must be found out who and why.