We are hiringCome build the future of the grid with us.Find your role

Modules · Event analysis · Module 077

Event Data Ingestion

Relay, fault recorder, and plant operating data delivered, read, and grouped into one event per incident, with what each record shows and what to do next.

About this module

What this module covers.

Every compliance obligation that follows a grid event starts with the same work: collecting the recordings, reading them, and working out what happened. This module turns your plant's event recordings into one record per incident. Recordings arrive by upload or automatically: a relay gateway can push files over Secure File Transfer Protocol (SFTP), and any recorder, historian, or integration platform can post files to a representational state transfer (REST) endpoint. Every file lands in your plant's event folder, is read and screened against the requirements of the event-analysis modules your plant holds, and the event workspace states what the record shows and what to do next.

This module covers automated delivery of your plant's event recordings, reading them, grouping the recordings of one incident, and the per-event workspace that the event-analysis modules build on.

At a glance

Module: 077
Kind: Event analysis
Governing body: Any region
Applies to: Operating plants
Typical time: Days per event, not weeks

Dashboard capabilities

  • We read your recordings automatically in the formats your equipment produces: supervisory control and data acquisition (SCADA) workbooks, Common Format for Transient Data Exchange (COMTRADE) records (.cfg/.dat and .cff), and Schweitzer Engineering Laboratories (SEL) event reports (.cev) and compressed event reports (.evzip), including mixed SEL fleets such as the SEL-387A, archives that hold several reports, and dual-breaker records. A file we cannot read is listed with the reason, and a file in a format we do not support is kept and listed as unsupported.
  • The recordings of one incident are grouped into one event: a relay's event report beside its own COMTRADE record, two relays recording one fault, and a reclose sequence of up to 60 seconds. Each recording's role (tripped, picked up, recorded, or duplicate) is read from its own digital data, and a primary record is chosen by rule (the tripped record, else the highest voltage level, else the earliest). You can merge or separate recordings and change the primary record by hand; your edits are kept and logged.
  • Each event opens with a summary of what the record shows: the relay and its location, the trigger time in your plant's time zone, the elements that asserted and the first trip, the fault type from the phases that excursed, the clearing time, and whether the record sits at the point of interconnection or on a collector feeder. The summary is built from fixed rules, with no generated free text, and prefills the summary of event in any workflow you open from the event.
  • Each event lists what to do next from the screening results of the event-analysis modules you hold: open a standard's workflow when a check fails, request the point-of-interconnection record when only a feeder record is in hand, request turbine or inverter and plant controller data where items cannot be assessed, and restore time synchronization when a relay clock is implausible. Episodes found in your SCADA day exports are linked to the relay events that fall inside them.
  • Your relay gateway can push files over SFTP to your plant's intake account, and your recorders, historians, or integration platforms can post files to the REST endpoint under company-scoped credentials that we issue and revoke. Files become event records on your plant within a minute, a file sent twice yields one record, and a credential for one company can never place a file on another company's plant.
  • You receive documentation of the endpoint with an example request for each supported format (COMTRADE .cfg/.dat and .cff, SEL .evzip and .cev, and SCADA workbooks).

Support services

What GridStrong does inside this module.

Task 1: Event Data Onboarding

  • Confirm your plant's recorders, relays, and SCADA exports and the formats each one produces
  • Confirm the delivery method for each recording source (upload, SFTP, or the REST endpoint)
  • Set up the SFTP intake account mapping or issue endpoint credentials, and support your integrator with the endpoint documentation
  • Map relay identifiers and breakers in your plant profile so recordings resolve to their equipment
  • Load historical event recordings into your plant's event folder

Task 2: End-to-End Verification

  • Confirm that a delivered recording from each source appears in your plant's event list and is read as an upload of the same file would be

Task 3: Event Identification Support (for each event you identify)

  • Review the grouping and roles of the recordings for the event
  • Identify missing recordings and request them from you
  • Confirm which event-analysis requirements apply to the event

Final deliverables

  • Task 1: Event data onboarding summary listing your plant's recording sources, the delivery method and credentials or account mapping for each, the formats read, and any recordings that could not be read with the reason.
  • Task 2: Verification record listing a delivered recording from each source and the resulting event record.
  • Task 3: Event identification summary for each event you identify, in the event workspace.

What we need from you

  • Event recordings from your plant's relays, digital fault recorders, and SCADA or historian exports.
  • Plant profile relays with their identifiers and the breakers they trip.
  • Time synchronization source for each recorder, where known.
  • The list of plants and recording sources to connect.
  • Your technical contact for the gateway or integration.
  • Network or firewall changes needed on your side to reach the SFTP server or endpoint.

Assumptions and considerations

How the scope is bounded.

  • Delivered or uploaded files must be in a supported format to be read; other files are kept and listed as unsupported.
  • File delivery only; streaming and phasor measurement unit (PMU) feeds are out of scope.
  • You operate and maintain your own gateways and integration scripts.
  • Automatic grouping is a first pass; recordings from relays with unsynchronized clocks may need to be merged by hand.
  • Data is assumed to be time synchronized or to carry accurate time stamps across data sources.
  • We do not assume liability for any data or information you supply that is inaccurate or incorrect.

Run this module on one site.

Tell us the plant and the deadline. An engineer confirms the inputs, the schedule and what the Dashboard needs from you.