Phasor Data Concentrator (PDC)

The foundational function of a PDC is data alignment. It buffers incoming synchrophasor frames from multiple PMUs and correlates them based on their GPS timestamps (typically to the microsecond). The PDC waits a configurable maximum latency period for delayed frames, then outputs a time-coherent, simultaneous snapshot of the entire monitored grid. This process handles network jitter and varying communication latencies, ensuring that downstream applications like Linear State Estimation (LSE) receive a consistent dataset representing a single moment in time.

A PDC ingests multiple raw IEEE C37.118 or IEC 61850-90-5 streams and performs real-time aggregation. Key processing functions include:

• Frame sorting: Reordering out-of-sequence packets by timestamp.
• Rate conversion: Down-sampling high-reporting-rate data (e.g., 60 frames/sec) to a lower, uniform rate (e.g., 30 frames/sec) for specific applications.
• Data validation: Applying checks for Total Vector Error (TVE) compliance, stuck values, and time jumps before forwarding.
• Stream duplication: Fanning out a single input stream to multiple subscribers without burdening the PMU.

PDCs implement a critical maximum wait time parameter to balance data completeness against real-time delivery. The PDC holds a buffer for each time tag, waiting for all configured PMU streams to report. If a stream fails to arrive within the wait time, the PDC can either:

• Output an incomplete dataset with a flag indicating missing data.
• Insert a placeholder with a quality flag set to invalid. This deterministic behavior is essential for Wide-Area Monitoring, Protection, and Control (WAMPAC) schemes where a delayed decision is as dangerous as an incorrect one.

A PDC acts as a protocol gateway, decoupling PMU input formats from application output requirements. It can ingest IEEE C37.118 streams and retransmit the aggregated data via:

• IEC 61850-90-5 routable GOOSE or Sampled Values over IP multicast.
• IEEE C37.118.2 for forwarding to a super-PDC or control center.
• Streaming to a Time-Series Database (TSDB) like OpenHistorian for archival.
• Publishing to an enterprise message bus (e.g., Kafka) for integration with non-operational analytics platforms.

Before forwarding data to mission-critical applications, the PDC performs a synchrophasor data validation stage. This includes:

• Timestamp sanity checks: Detecting GPS time jumps or GPS spoofing anomalies.
• Stuck value detection: Identifying PMUs that are reporting frozen measurements.
• TVE thresholding: Flagging measurements exceeding accuracy limits.
• Completeness checks: Verifying all expected streams are present. The PDC appends standardized quality flags to each measurement, allowing downstream Oscillation Detection algorithms to automatically exclude corrupted data.

In large interconnections, PDCs are deployed in a hierarchical topology. Local PDCs at substations aggregate PMU data within a single facility. These feed Regional PDCs at control centers, which in turn feed a Super PDC at the reliability coordinator level. This architecture:

• Reduces wide-area network bandwidth by filtering and down-sampling data at each layer.
• Provides local survivability, allowing substation-level applications to function even if the WAN link to the control center fails.
• Enables controlled islanding schemes to operate on a localized, coherent dataset.

The source device that a PDC aggregates. A PMU samples AC waveforms at high speed (typically 30-60 frames per second), calculates synchrophasors, and time-stamps them using a GPS-disciplined oscillator. The PDC receives these raw, time-tagged streams from dozens or hundreds of PMUs as its primary input.

The core function of a PDC. It buffers incoming streams and correlates synchrophasor frames from multiple PMUs based on their GPS timestamps.

• Waits for data with identical time-tags to arrive from all configured sources
• Outputs a single, coherent, system-wide snapshot
• Handles late-arriving data via configurable wait times
• Compensates for network latency jitter

The foundational communication standard defining how PMUs format and transmit synchrophasor data to a PDC. Specifies:

• Data frame structure (configuration, header, data, command)
• Total Vector Error (TVE) accuracy requirements
• TCP, UDP, and serial communication modes
• Real-time streaming rates (10, 12, 15, 20, 30, 60 fps) A PDC must parse and validate incoming C37.118 streams before alignment.

A critical pre-processing stage within a PDC that ensures only high-quality measurements are forwarded to mission-critical applications. Checks include:

• Time quality flags: Verifying GPS lock and time accuracy
• Stuck value detection: Identifying frozen measurements
• Range and rate-of-change limits: Flagging physically impossible jumps
• Timestamp consistency: Detecting duplicated or out-of-sequence frames Bad data is flagged or discarded before alignment.

The downstream consumer of a PDC's output. A WAMS ingests the time-aligned, system-wide dataset to provide:

• Real-time angle difference monitoring across corridors
• Oscillation detection and modal analysis
• Voltage stability margin visualization
• Post-event disturbance replay and forensic analysis The PDC serves as the data backbone enabling situational awareness across an entire interconnection.