IEEE C37.118 is a comprehensive standard that defines the measurement of synchrophasors, specifying the methods for evaluating the magnitude, phase angle, frequency, and Rate of Change of Frequency (ROCOF) of electrical waveforms. It establishes strict performance classes (P and M) that dictate the steady-state and dynamic filtering requirements a Phasor Measurement Unit (PMU) must meet to ensure interoperability across different vendors.
Glossary
IEEE C37.118
The foundational IEEE standard defining synchrophasor measurement, data transfer protocols, and performance requirements for ensuring interoperability among phasor measurement units in power system synchronization.
SYNCHROPHASOR STANDARD
What is IEEE C37.118?
The foundational protocol defining synchronized phasor measurement, data formatting, and performance requirements for power system monitoring.
The standard also prescribes the communication framework for real-time data transfer, including the message structure, frame format, and reporting rates for streaming synchrophasor data to a Phasor Data Concentrator (PDC). By defining the Total Vector Error (TVE) metric, IEEE C37.118 provides a quantifiable limit for measurement accuracy under both static and dynamic system conditions, forming the bedrock of modern Wide-Area Monitoring Systems (WAMS).
IEEE C37.118 STANDARD CLARIFICATIONS
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the synchrophasor standard governing measurement, performance, and data communication for power system synchronization.
IEEE C37.118 is the foundational standard that defines synchronized phasor measurement, performance requirements, and data transfer protocols for power system monitoring. It ensures that Phasor Measurement Units (PMUs) from different manufacturers produce interoperable, time-aligned data streams essential for wide-area visibility. The standard is critical because it specifies the Total Vector Error (TVE) limits under both steady-state and dynamic conditions, guaranteeing that a synchrophasor measured by one vendor's device matches the accuracy of another's. Without this strict compliance framework, grid operators could not reliably compare phase angles across interconnections to detect inter-area oscillations or execute Remedial Action Schemes (RAS). The standard was split in 2011: IEEE C37.118.1 covers measurement aspects, while IEEE C37.118.2 defines the data communication protocol, including configuration frames, header frames, and command frames sent over TCP/IP or serial links.
IEEE C37.118
Core Components of the Standard
The foundational architecture defining how synchrophasor measurements are generated, formatted, and transmitted to ensure interoperability across vendor platforms.
01
Synchrophasor Measurement Definition
Defines the mathematical framework for a synchrophasor, representing a sinusoidal waveform's magnitude and phase angle relative to a Coordinated Universal Time (UTC) reference. The standard specifies the phasor estimation process, requiring the reporting rate to be an integer multiple of the nominal system frequency. It establishes the convention for phase angle representation, where a cosine waveform at nominal frequency synchronized to UTC has a 0-degree phase angle.
02
Total Vector Error (TVE) Compliance
Establishes Total Vector Error (TVE) as the primary metric for quantifying measurement accuracy. TVE combines magnitude and phase angle error into a single scalar value, comparing the measured phasor against a theoretical reference. The standard defines two performance classes:
- P-class (Protection): Fast response with minimal filtering, tolerating higher overshoot for rapid triggering.
- M-class (Measurement): Strong out-of-band interference rejection for high-accuracy analytical applications.
03
Data Framing and Communication Protocol
Specifies the binary message structure for streaming synchrophasor data over serial or Ethernet networks. The protocol defines four frame types:
- Data Frame: Carries the actual synchrophasor estimates, frequency, and ROCOF.
- Configuration Frame: Machine-readable metadata describing the PMU's calibration factors and reporting rate.
- Header Frame: Human-readable station and source identifier information.
- Command Frame: Machine-to-machine instructions for remote control. All frames include a time quality flag and a CRC-CCITT checksum for data integrity.
04
Time Synchronization Requirements
Mandates that all measurements be tagged with a UTC timestamp derived from a reliable time source, typically a GPS-disciplined clock. The standard specifies the SOC (Second of Century) and Fraction of Second fields to achieve sub-microsecond alignment. It defines the Time Quality Flag bits to indicate synchronization status, leap second events, and time transfer accuracy, allowing downstream Phasor Data Concentrators to reject or adjust data from PMUs that have lost lock.
05
Reporting Rate and Frequency Tracking
Standardizes nominal reporting rates (e.g., 10, 12, 15, 20, 30, 50, 60 frames per second for 50 Hz or 60 Hz systems). The PMU must dynamically track the actual power system frequency and adjust its internal sampling rate to prevent spectral leakage during off-nominal conditions. This ensures accurate phasor estimation even during frequency excursions, maintaining TVE compliance across a defined frequency range.
06
Performance Testing and Steady-State Criteria
Defines rigorous test signals for verifying PMU compliance, including steady-state magnitude sweeps, phase angle sweeps, frequency ramp tests, and harmonic distortion tests. The standard specifies maximum allowable TVE, Frequency Error (FE), and ROCOF Error (RFE) limits under each test condition. This ensures that PMUs from different manufacturers produce consistent results during both normal operation and dynamic grid events.
SYNCHROPHASOR COMMUNICATION STANDARDS
IEEE C37.118 vs. IEC 61850-90-5
Comparison of the legacy IEEE C37.118 protocol with the modern IEC 61850-90-5 framework for synchrophasor data transmission in wide-area monitoring systems.
| Feature | IEEE C37.118 | IEC 61850-90-5 |
|---|---|---|
Primary scope | Synchrophasor measurement, data framing, and real-time streaming | Synchrophasor data encapsulation within IEC 61850 substation automation framework |
Data transport protocol | TCP/UDP over IP with custom frame format | Routable GOOSE or Sampled Values over UDP/IP with session protocol |
Time synchronization | GPS-based UTC timestamp embedded in each frame | IEEE 1588 PTP or GPS with timestamp in session header |
Message encoding | Binary fixed-format frames defined by configuration | Abstract syntax using ASN.1 BER encoding for flexible schema |
Configuration method | CFG-1, CFG-2, CFG-3 binary configuration frames | Substation Configuration Language (SCL) with IED capability description |
Cybersecurity | ||
Multi-rate streaming | ||
Backward compatibility with IEC 61850 | ||
Typical reporting rate | 10, 12, 15, 20, 30, 60 frames/sec | Configurable up to 60 frames/sec for 60 Hz systems |
Total Vector Error compliance | TVE < 1% under steady-state conditions | TVE < 1% under steady-state conditions |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.
Enterprise searchRAGPermissions
Read more
Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.
AI agentsWorkflow automationGovernance
Read more
Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
AI integrationDecision supportModel routing
Read more
About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
LinkedIn
Limited slotsGet a Free AI Consultation
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us