Understanding 37 013 2015 Ieee Iec International Standard For
The standard sits in a gray area for a lot of people coming into protection engineering. It is not the most intuitive document, and the first time I went through it I spent more time cross-referencing IEC and IEEE tables than actually reading the text. The thing about 37 013 2015 Ieee Iec International Standard For is that it is primarily a guide, not a prescriptive rulebook. That distinction matters because you will find yourself making calls that the document itself leaves open. At its core, the standard addresses how protective relaying and automation systems should be designed when they interact with communication networks inside power substations. It pulls from both IEEE 37 and IEC 60255 families, which means you are working with two slightly different philosophical approaches to the same problem. One emphasizes relay modeling and performance criteria. The other leans into communication protocols and data exchange architecture. The 2015 update tried to reconcile those differences where possible. If you are looking at implementing fiber optic schemes between relay panels, this is the document you open first. Same with COFDM wireless links or Ethernet-based protection channel designs. It does not replace the specific protocol standards like IEC 61850, but it tells you how to think about integration before you pick a protocol.
How to approach the document in practice
I stopped trying to read this cover to cover years ago. It is structured in a way that rewards targeted looking up. Start with the system architecture section, find the chapter on timing and synchronization requirements, then jump to the implementation notes. The middle sections on electromagnetic compatibility and grounding for communication interfaces are dense and easy to skip unless you are specifically dealing with noise or grounding issues in your design. One thing the standard does well is give you a decision framework for selecting communication media based on application requirements. You map your protection scheme to one of several categories, then the standard narrows down which technologies are acceptable. The problem is that the categories sometimes overlap, and you end up picking between two equally valid options with no clear guidance on which one the author intended. I ran into this specifically when designing a differential protection channel for a 138 kV line with a fiber link between two substations. The standard allowed both direct fiber and Ethernet-based approaches. I spent about three days comparing loss budgets, latency figures, and redundancy options before realizing both were technically compliant. The workaround was straightforward: pick the option that matched equipment already on site from a previous project, document the technical justification, and move forward. Auditors usually accept that level of reasoning.
Common pitfalls and counter-intuitive points
Beginners often treat this standard as if it specifies exact component requirements. It does not. It specifies performance boundaries and gives guidance on achieving them. You will see engineers waste budget on over-specified transceivers or unnecessary EMI shielding because they misread the language. The standard says "shall be suitable for the environment" in several places, which is not the same as requiring industrial-grade components in every case. Another counter-intuitive point is that the standard actually permits certain non-standard communication topologies when justified by the application. Most engineers assume any topology outside a simple point-to-point or ring requires a formal deviation process. That is not true. You can use whatever topology fits your site constraints as long as you can demonstrate that the protection performance criteria are met. The documentation burden is real though, and that is where people get tripped up. There is also the matter of timing accuracy. The standard references sync requirements that are tighter than what most people think they need. If you are doing anything with time-stamped event recording or synchronized phasor measurement, budget for proper clock distribution early. Retrofitting timing infrastructure after the fiber is pulled is expensive and disruptive.
Get the Full Details
Where the standard falls short
The 2015 version still does not adequately address cybersecurity considerations for protection communication channels. You will find general references to integrity and availability but nothing that maps to NERC CIP or IEC 62351 requirements. If you are working in a regulated market, you need to supplement this document with those other standards regardless of what the scope statement says. The section on wireless communication options is also thin. COFDM is mentioned briefly, but modern alternatives like private LTE or microwave links are not covered. The standard was written with a particular set of technologies in mind, and the industry has moved beyond some of them. Use the principles rather than the specific technology recommendations for newer projects.
37 013 2015 Ieee Iec International Standard For practical usage tips
When you actually have the document, the tables in the annexes are more useful than the main text. The comparison tables for communication media options, the grounding recommendations, and the timing accuracy matrices give you quick reference points during design reviews. Print those sections out. I keep mine in a binder at my desk because flipping back and forth between PDF pages during a meeting is slow and frustrating. Also pay attention to the normative references at the front of the document. The standard deliberately points you to other IEEE and IEC documents for detailed specifications. Those cross-references are where the actual technical meat lives. IEC 60255-13, IEEE C37.94, and IEC 61850-9-2 are the ones you will return to most often. The main standard is the roadmap. The referenced documents are the territory. For download access, the standard is available through the IEEE Xplore digital library and the IEC webstore. IEEE members get a significant discount. If you are purchasing for a firm, check whether your organization already has an institutional subscription before buying individual copies. A single copy license runs steep, and many engineering firms do not realize they may already have access through their university partnerships or IEEE corporate membership programs.
The standard is a solid reference for anyone working on substation protection communication design, but it demands that you think through the application rather than simply copying a recommendation. That is the same for most standards in the 37 series. The ones that try to be prescriptive tend to become outdated quickly. The ones that teach you how to think hold up better over decades of use. This falls into the latter category, which is why it still gets referenced even twenty years after publication.
