Substation Event Record Acceptance: COMTRADE Files, Retrieval Tests and EPC Handover

Substation event record acceptance should prove that the operator can retrieve the correct disturbance record, open it in the agreed software and connect its channels and timestamps to the installed equipment. A folder containing waveform files is useful only when the next engineer can identify what happened, where the record came from and whether the data are complete.

For EPC handover, treat this as a defined evidence package with an owner, acceptance criteria and a witnessed retrieval exercise. The objective is to hand over a working recording and retrieval process. This guide proposes project controls that should be adapted to the owner’s requirements, device manuals and approved commissioning procedures.

Contents

• 1. Define the recording boundary
• 2. Establish file and equipment identity
• 3. Set the acceptance evidence
• 4. Witness end-to-end retrieval
• 5. Check channel meaning and time context
• 6. Transfer the archive and operating procedure
• Frequently asked questions

1. Define the substation event record acceptance boundary

List the devices that are expected to produce disturbance records, including protective relays, dedicated recorders or meters where they fall within the contract. Identify the bay, equipment tag, device model, software or firmware reference, retrieval method and destination archive. Mark any devices that provide only event lists rather than the required waveform records.

Agree whether acceptance covers local retrieval, automatic collection, control-center access or a combination. A successful laptop download does not demonstrate that the automatic collection service works. Likewise, a file arriving at a server does not prove the operator’s approved analysis tool can interpret it. Define the full path that the project promises to deliver.

Keep related handover packages coordinated

Link the recording configuration to the approved relay settings handover. Reference the separate time synchronization acceptance records for clock sources and timing performance. Event-record acceptance checks that the resulting files remain usable within that documented context; it does not replace either of those packages.

Assign a commissioning owner, an automation or communications contact, a protection reviewer and an operations representative. One person should coordinate open issues across those disciplines. Otherwise a missing file may be passed between teams without anyone establishing whether the cause lies in recording, collection, storage or the analysis workstation.

2. Establish file and equipment identity

IEC 60255-24:2013 defines COMTRADE as an exchange format for transient waveform and event data. Its published scope includes a single-file CFF option in addition to separate-file arrangements. Therefore, specify the supported format and revision in the handover requirements instead of assuming that every device exports an identical collection of files.

SEL’s event-analysis technical paper explains the distinction between configuration information used for scaling, sampling and timing, and the recorded data values. For project acceptance, preserve the complete export required by the selected format and software. A screenshot of a waveform should accompany the evidence where useful, but it should not replace the original analysis files.

Create a record manifest

Use a manifest with an acceptance-test identifier, equipment tag, recording device, original filename, export format, collection time, test reference and archive location. Distinguish the event’s time from the time at which somebody copied the file. Add the responsible reviewer and disposition so an operator can trace a record back to its commissioning purpose.

Keep original exports unchanged. If the project uses standardized folder names, place the original files within those folders and retain their original names in the manifest. Converted files, annotated plots and analysis notes should be identifiable as derived material. This avoids a later reviewer mistaking a presentation copy for the original device output.

3. Agree the acceptance evidence before testing

The following matrix is a suggested EPC acceptance structure. It does not set universal sampling rates, recording durations or timing tolerances. Those values must come from the approved functional requirements and the equipment’s supported capabilities.

Define the acceptance population explicitly. Where the contract requires every device to be demonstrated, track each device. If a documented sampling approach is approved, record its rationale, coverage and exceptions. Never label an entire station accepted merely because a single convenient relay produced a readable file.

4. Witness retrieval from a known test event

Prepare an approved test that creates an identifiable record without compromising operational protection. The commissioning team should determine the permitted test mode, isolation boundaries and restoration steps. Do not initiate a real system fault or alter live trip logic merely to obtain an example file.

Record the test reference before retrieving the result. The witness should be able to connect the expected event with the resulting device record and its archived copy. Preserve enough context to distinguish the current demonstration from older commissioning attempts or factory sample files already stored in the relay.

Test each required delivery path

For local retrieval, demonstrate the approved connection method, export operation and opening of the file on the designated workstation. For automatic collection, demonstrate that the newly created record reaches the specified archive and can be found through the operator’s normal workflow. Record delays against the project’s agreed requirements rather than inventing an arbitrary universal time limit.

SEL’s introduction to power-system event report data describes a chain involving devices, information-management software and file storage. This separation provides a useful basis for acceptance responsibilities: generating a record, collecting it and retaining it are distinct functions, and each required function needs visible evidence.

Where the approved scope includes collection interruptions, use a controlled test to demonstrate the specified recovery behavior. Record which files were generated, which were retained and which reached the archive after recovery. Do not assume that buffering, retry or duplicate handling works identically across different devices and collectors.

Preserve failed-test evidence

If retrieval fails, keep the relevant non-sensitive error message, test identifier and device context. Assign the defect to an owner and define the retest. The final dossier should show both the issue and its closure evidence. Removing every failed record makes the history cleaner visually but weakens the explanation of what was corrected.

5. Check channel meaning, scale and time context

Opening a file is only the first check. Ask the protection reviewer to reconcile the relevant analog and digital channels with the approved configuration and test plan. Channel labels should identify the intended equipment and quantity clearly enough for operations to use them without relying on the installer’s memory.

For selected known test conditions, record the expected quantity, displayed quantity, unit convention and disposition. Confirm whether the presentation uses primary or secondary quantities according to the device export and analysis-tool configuration. An unexplained difference should be resolved by the responsible specialist rather than corrected by editing the original data file.

Match the record to its intended use

Review the configured capture window, trigger conditions and available channels against the project requirement. A readable record may still omit a required status or the part of the sequence needed for later investigation. Document such limitations explicitly, along with the agreed correction or acceptance decision.

Record the software and version used for the acceptance demonstration. If more than one tool is required by the owner, demonstrate the agreed compatibility scope. Avoid promising that a file has been validated in every COMTRADE application merely because it opened successfully in the supplier’s preferred viewer.

Keep event time and file handling time separate

Reconcile the event timestamp with the project’s declared time basis and the applicable clock-acceptance evidence. File creation or copy timestamps can reflect handling rather than the original event. The manifest should explain the distinction wherever it could confuse a later investigation.

Where records from several devices are compared, preserve the documented timing limitations. A tidy set of aligned plots is not independent proof of clock performance. If a known discrepancy remains, include it in the acceptance disposition and identify whether it limits the intended use of the combined records.

6. Transfer the archive, access and operating procedure

Place the accepted files, manifest, test sheets and approved configuration references within the substation system turnover package. Use a stable folder structure that separates original exports, derived analysis and acceptance records. Include enough references to identify the installed equipment without duplicating uncontrolled copies of every project document.

Define archive ownership, backup responsibility, retention rules and the escalation route for collection failures. These are owner decisions, supported by the supplier’s capacity and operating guidance. The handover should not create an implied promise of unlimited device storage or indefinite server retention.

Demonstrate operator independence

Ask an authorized operations representative to locate an accepted record and open it using the delivered procedure. This simple exercise can expose unclear folder names, missing software access or instructions that depend on knowledge held only by the contractor. Record the exercise and resolve gaps before final turnover.

Coordinate accounts, approved permissions and software access with the digital access handover. Keep passwords and other credentials out of the article, acceptance screenshots and general document register. Use the owner’s approved credential-transfer process for any access material that must be handed over.

Finally, define what reopens substation event record acceptance. Examples include a changed recording configuration, device replacement, collector migration, modified channel mapping or a software change that affects import. The engineering owner should identify the necessary regression checks, while the document controller preserves the accepted baseline and subsequent revisions.

Frequently asked questions

Is a waveform screenshot sufficient for EPC handover?

No. A screenshot may help explain a result, but the agreed original record files and their identity should be retained. Acceptance should demonstrate that the operator can retrieve and open the supported export, with enough context to understand its channels, time basis and test purpose.

Must every export contain separate CFG and DAT files?

Follow the specified format, revision and device implementation. Separate-file exports commonly include configuration and data files, while IEC 60255-24:2013 also describes a combined CFF option. Confirm the complete file set required by the selected export and analysis software rather than enforcing a filename checklist without that context.

Does this replace relay protection testing?

No. Substation event record acceptance verifies the agreed recording, retrieval and handover functions. Protection testing establishes the behavior required by its own approved scope. Link the relevant evidence packages, but keep their acceptance decisions and limitations identifiable.

What if the local download works but automatic collection fails?

Record the local path as demonstrated and the required automatic path as unresolved. Assign a defect, preserve the test context and repeat the affected acceptance case after correction. A partial success should not be reported as completion of the entire contracted delivery path.

Should the handover include a real fault record?

An approved, identifiable commissioning test can demonstrate the required functions without creating a real fault. Clearly label test records and keep them distinguishable from operational disturbances. The commissioning authority determines the safe and appropriate test method for the installed system.

Build the event-record requirement into the EPC enquiry

When preparing a transformer and substation enquiry with Zisheng Electric, provide the equipment and protection scope, device list, recording requirements, owner’s analysis tools and intended archive arrangement. Identify which party owns relay configuration, collection infrastructure and acceptance witnessing. Request a coordinated document and interface schedule so substation event record acceptance can be completed with the wider EPC handover.

Equipment references for EPC interface review

When the event-record scope sits within a packaged station, review the project configuration alongside Zisheng Electric’s prefabricated substation and medium-voltage switchgear product information. These pages help identify the equipment package and protection interfaces; they do not establish that a particular relay, recorder, COMTRADE export, or collection feature is included. Confirm the supplied IEDs, firmware, communications, archive path, and acceptance responsibilities against the project documents.