Your Trusted Partner in Electrical Engineering and Power Systems
At Keentel Engineering, we deliver electrical power engineering services built on 30 years of experience and a commitment to excellence. Our clients include utilities, developers, EPCs, and public agencies across the U.S.
Unlike firms that sacrifice technical depth to chase billable hours, we prioritize precision, compliance, and value engineering. From transmission services and relay modeling to winterization and SCADA planning, we never compromise on quality.
At Keentel Engineering, we take pride in being the go-to electrical power engineering firm for power and utility system planning, substation design, protection, control, and power system analysis. The following attributes distinguish our team in utility-grade substation engineering and compliance-driven project delivery.
With three decades of hands-on project delivery, we bring unmatched expertise in substation layout design, substation electrical and civil engineering, relay protection, and grid-tie solutions. Our experience includes projects in complex terrain, urban retrofit environments, and utility-scale renewable integrations.
Our engineering process applies AutoCAD 3D, BIM modeling, and system-level substation design practices to ensure accurate planning, reduced errors, and efficient coordination across all project stakeholders.
Our workflow includes 3D substation design, enabling clash-free coordination between structural, electrical, and civil disciplines.
From grounding grid studies to relay protection settings, we engineer every detail to improve system reliability, performance, and operational safety. Our rigorous QA/QC process ensures compliance with IEEE, NFPA, and ISO/TSO interconnection standards.
Among leading electrical substation design companies, Keentel Engineering stands out for 30+ years of proven high-voltage and utility-grade project delivery.
First name, email and what you're interested in are all we need to get moving. Everything else, including drawings or an RFP, is optional.
Every significant system event is reconstructed from recorded data. Planners use it to validate models, protection engineers use it to confirm relays operated correctly, and event analysts use it to find out why a plant reduced output or tripped. Without time-aligned records from the right places, an event cannot be explained, and a misoperation or an unexpected inverter response cannot be corrected.
Two NERC standards set the recording obligations:
Confirm the versions in effect and their implementation plans for your registered functions and facilities before scoping work. PRC-028 in particular uses a phased implementation, and different facilities may reach their compliance dates at different times.
A recorder that is installed but not triggering, not time-synchronized or not retrievable is not compliance. Evidence starts with an engineered recording design and ends with data you can actually produce.
PRC-002 works in two tracks: SER and FR data at BES buses selected by a defined methodology, and DDR data at Elements identified by the Responsible Entity. Both tracks share requirements for time synchronization, data retention, data provision and restoration of failed capability.
The Transmission Owner applies the bus-selection methodology in the standard’s attachment to identify the BES buses where SER and FR data is required. The methodology is based on available short-circuit levels and ranks candidate buses so that recording is concentrated where faults have the greatest system significance. The TO then notifies the other owners of BES Elements connected to those buses — including Generator Owners — that recording is required for their Elements, and re-evaluates the list on the cycle the standard specifies.
Most findings in this area are procedural: a list that was never re-run after system changes, a missing short-circuit basis, or no record that a connected owner was notified. We rebuild the calculation from a current short-circuit model and keep the methodology, results and notifications together.
At identified buses, the owners of the applicable Elements must capture SER data for circuit breaker position changes and FR data for the electrical quantities the standard lists, with the recording characteristics and trigger conditions it specifies. Generator Owners are responsible where the notified Elements are theirs, typically GSU high-side breakers and associated quantities.
DDR captures slower, longer-duration phenomena — frequency and voltage excursions, power swings and oscillations — rather than fault waveforms. The Responsible Entity identified in the standard (the Planning Coordinator or Reliability Coordinator) identifies the BES Elements where DDR data is required and notifies the owners. Owners then install and maintain DDR capability for those Elements with the recording characteristics the standard specifies.
recorded data must be time-synchronized to Coordinated Universal Time within the tolerance the standard specifies (±2 ms in PRC-002-2 and later), with the local time offset documented
SER, FR and DDR data must be retained for the minimum period the standard specifies (10 calendar days in the current version), counted from the recorded event
data must be provided to the RC, Regional Entity or NERC within the time frame the standard sets, in the format the standard specifies
when recording capability fails, the owner must restore it within the time frame in the standard (90 calendar days in the current version) or submit a Corrective Action Plan and implement it
Confirm every numeric tolerance and timeline against the version in effect for your facilities; the values above reflect our reading of the current standard and are not a substitute for it.
Choosing the right source for each recording type is the first engineering decision. A modern substation or plant may meet all three from different devices, and the channel list must show which device satisfies which requirement.
| Recording type | What it captures | Typical source devices |
|---|---|---|
| Sequence of events (SER) | Time-stamped changes of state — breaker position, and where configured, relay trips, alarms and scheme operations — used to establish the order of events | Microprocessor relays, DFR digital inputs, RTACs and data concentrators with time-stamped status points |
| Fault recording (FR) | High-resolution voltage and current waveforms before, during and after a fault, triggered by defined conditions | Digital fault recorders (for example ERLPhase TESLA 4000), relay oscillography where it meets the required characteristics |
| Dynamic disturbance recording (DDR) | Continuous or long-duration records of frequency, voltage, current and power flows for swings, oscillations and frequency events | DFRs with continuous recording, phasor measurement units (PMUs), multifunction recorders |
| IBR plant-level recording (PRC-028) | Fault and disturbance records at the plant’s point of interconnection or main power transformer high side, as the standard specifies | Plant DFR, high-side relays, revenue-class or power-quality meters with recording, PPC data logs |
| Inverter-level data | Inverter fault codes, operating state, ride-through behavior and trip causes that explain plant response | Inverter and OEM data loggers, SCADA historians, plant controller event logs |
Relay oscillography can be a legitimate source — if you can prove it. Sample rate, record length, triggers, channels and time stamping all have to be documented against the standard for each device you rely on.
FERC Order No. 901 directed NERC to develop Reliability Standards for inverter-based resources covering disturbance monitoring, performance during disturbances, data sharing and model validation. PRC-028 came from the first phase of that work, alongside PRC-029 (ride-through) and PRC-030 (unexpected IBR event mitigation).
Repeated disturbance reports have shown that when IBRs reduce output or trip during grid events, the plant often lacks the recorded data needed to explain why. PRC-028 addresses that gap for Generator Owners of applicable IBRs.
PRC-030 requires Generator Owners to identify unexpected reductions in IBR output during system events, analyze the cause and develop corrective actions. That analysis depends entirely on PRC-028 data. We design recording at IBR plants so that the same records support event detection, root-cause analysis and model validation under the MOD standards.
Short-circuit-based application of the standard’s attachment methodology, results tables, owner notification letters and a re-evaluation schedule.
DFR versus relay-based recording versus PMU trade-offs for each location, considering channel count, sample rate, continuous recording and storage.
Voltage, current, residual and status channels mapped to each monitored Element, with trigger thresholds and record lengths documented against the standard.
GPS clocks, IRIG-B distribution and IEEE 1588 PTP architecture, holdover behavior, clock-failure alarms and the time-offset documentation auditors ask for.
SEL RTAC and data concentrator integration, automated record retrieval, secure remote access paths and central archiving sized for the required retention.
Test-trigger procedures, channel polarity and scaling checks, time-sync verification and as-left configuration records.
Gap assessment of plant recorders, inverter logging and PPC data against PRC-028, with an upgrade plan aligned to the phased implementation.
Written procedures, roles and file-format conversion so a request from the RC, Regional Entity or NERC can be answered within the required time frame.
Most disturbance-monitoring problems are designed in, not caused by equipment failure. The decisions below are where we spend engineering effort.
Fault recording needs enough samples per cycle and enough pre-fault and post-fault data to see the full event, including breaker failure and reclosing sequences. DDR needs long, continuous records at a lower resolution. We specify both against the standard’s minimum characteristics and against what your event analysts actually need, which is often more.
Undervoltage, overcurrent, neutral overcurrent, frequency and rate-of-change triggers must be set so real events are always captured without filling storage with nuisance records. For IBR plants, triggers also need to catch the short voltage dips that cause momentary cessation or inverter trips.
A single GPS clock with no monitoring is a common weak point. We design the time-distribution path — GPS receiver, IRIG-B or PTP distribution, device configuration and loss-of-sync alarms — and document the time offset and synchronization method, because time alignment is what lets records from different devices and different owners be compared.
Retention requirements only matter if records reach storage. Automatic retrieval through an RTAC or data concentrator, with alarms for failed downloads and a secure remote access path, is what turns a recorder into a compliant recording system.
Identify registered functions, applicable versions, facilities in scope and, for IBRs, where each plant sits in the phased implementation.
Run or review the bus-selection methodology, confirm DDR Elements identified by the Responsible Entity and gather owner notifications.
Document every recorder, relay, PMU and clock — model, firmware, channels, triggers, sample rate and time source — against the requirements.
Specify new devices, channel additions, trigger settings, time-source upgrades and retrieval architecture, with drawings and settings.
Test triggers, confirm channel scaling and polarity, verify time synchronization and retrieve sample records end to end.
Set up periodic verification, failure alarms, restoration tracking and data-request procedures so evidence stays current.
| Deliverable | Evidence it supports |
|---|---|
| Bus-selection calculation and results | Application of the attachment methodology from a current short-circuit model, with the basis for each identified bus |
| Owner notification records | Dated notifications to owners of Elements at identified buses and DDR Elements |
| Monitored-Element and channel matrix | Which device records which quantity for which Element, mapped to each recording requirement |
| Recorder configuration and settings records | Triggers, sample rates, record lengths and as-left settings for each device |
| Time-synchronization design and verification | Clock architecture, synchronization method, offset documentation and test results |
| Data retention and retrieval architecture | Storage design, retrieval automation and retention confirmation |
| PRC-028 gap assessment and upgrade plan | IBR plant and inverter-level recording status against the standard and phased dates |
| Data-request and restoration procedures | Response workflow for requests and tracking for restoring failed recording capability |
We design RTAC-based SCADA, DFR integration and time distribution as part of substation projects, so recording is engineered into the station, not added later.
Our protection engineers analyze relay and DFR records for PRC-004 and PRC-030, so we design recording around the questions event analysts actually ask.
We work with solar, wind and BESS plants on interconnection, EMT modeling and ride-through, which is where PRC-028 recording gaps usually sit.
Former NERC audit-team leadership and SMEs know how bus lists, notifications, time sync and data provision are examined.
Send us your bus list, recorder inventory and one-line diagrams. Keentel will check them against PRC-002 and PRC-028, design what is missing and document a recording system you can produce data from on request.
Serving utilities, EPCs, developers, and infrastructure organizations supporting critical power systems nationwide.
