{
  "id": "iec-61850",
  "title": "IEC 61850",
  "lang": "en",
  "source_lang": "en",
  "summary": "IEC 61850 is a standards series defining information models, communication services, and engineering methods for power utility automation.",
  "category": "technology",
  "subcategory": "energy",
  "type": "concept",
  "aliases": [
    "IEC 61850 series",
    "Communication networks and systems for power utility automation"
  ],
  "generated_at": "2026-11-05",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/iec-61850/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/iec-61850/",
      "json": "https://aiwiki.page/zh/iec-61850.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "IEC 61850 is a series of international standards for exchanging information among devices and software used in electric power systems. Developed by the International Electrotechnical Commission, it defines standardized representations of power-system equipment and functions, communication services for accessing those representations, and machine-readable descriptions for engineering complete systems. Originally centered on substation automation, its scope has expanded to include distributed generation, hydropower, distribution automation, and communication between utility installations.\n\nThe series is more than a network protocol. It separates the meaning of information from the communication technology used to carry it, allowing a circuit-breaker position, protection operation, or measured current to retain a standardized interpretation across equipment from different manufacturers. Its principal communication mechanisms include client–server exchanges, high-speed event distribution, and transmission of sampled measurements. These mechanisms support applications ranging from operator displays to protection schemes that must exchange information within milliseconds.\n\nIEC 61850 also standardizes important aspects of system engineering. Devices describe their capabilities and configurations through a common language, enabling engineering tools to exchange information about functions, data, communications, and electrical topology. Successful implementation nevertheless depends on coordinated application design, network performance, configuration management, and testing: conformance to the series does not by itself make any two products interchangeable."
    },
    {
      "heading": "Origins, development, and organization of the series",
      "text": "Before IEC 61850, substation automation commonly combined extensive point-to-point wiring with manufacturer-specific communication systems. A protective relay might communicate with an operator workstation through one protocol while exchanging interlocking signals with neighboring equipment through hardwired contacts. Integrating products from several suppliers required gateways, custom signal lists, and detailed agreements about the meaning of individual addresses. Even where a protocol standardized message transport, the interpretation of a particular numerical register or status bit often remained project-specific.\n\nIEC Technical Committee 57 developed IEC 61850 against this background. Its work drew on earlier international and regional efforts, including the Utility Communications Architecture, particularly UCA 2.0. The first-edition core documents appeared principally between 2002 and 2005. They addressed requirements, engineering, information models, communication mappings, and conformance testing as related parts of a single architecture. A second generation of core documents followed around 2010–2012, with later amendments and additional parts extending the framework. Edition numbers and publication dates apply to individual documents rather than to one simultaneously released package.\n\nThe series’ title evolved from a focus on communication networks and systems in substations to “Communication networks and systems for power utility automation.” This change reflected its wider application, but the substation remains a useful setting for understanding its organization. Part 3 addresses general requirements, including environmental and electromagnetic conditions for equipment. Part 5 addresses communication requirements associated with functions and device models. Part 6 defines the system configuration description language. The Part 7 family specifies the abstract communication services and the principal information-modeling rules.\n\nOther parts define how these abstractions are implemented. Part 8-1 maps services to the Manufacturing Message Specification and to Ethernet-based communication mechanisms. Part 9-2 addresses transmission of sampled values over Ethernet. Part 10 concerns conformance testing. Further numbered parts provide domain-specific models, technical reports, engineering guidance, or additional communication arrangements. A document designated as a technical report does not have the same status as an International Standard, even when it strongly influences implementation practice.\n\nThis modular organization is central to the design. An application model can describe a breaker or a protection function without defining the byte layout of every network message. A communication mapping can then carry those models using a specified technology. The separation supports technological evolution, although it does not eliminate compatibility work: projects must still identify the exact editions, amendments, supported services, and modeling options used by each device and engineering tool."
    },
    {
      "heading": "Information models and the representation of power-system functions",
      "text": "The defining feature of IEC 61850 is its standardized information model. Rather than presenting equipment as an arbitrary list of numbered points, it organizes information into a hierarchy of server, logical device, logical node, data object, and data attribute. A physical intelligent electronic device, or IED, may contain several logical devices, each grouping related application functions. Within them, logical nodes provide standardized representations of particular functions or equipment roles.\n\nLogical-node class names identify their general meaning. XCBR represents a circuit breaker, XSWI a switching device, MMXU a measurement function, PTOC time-overcurrent protection, and PDIF differential protection. CSWI represents switch-control functionality, while CILO represents interlocking. These distinctions separate functions that may be combined inside one physical product. A relay can therefore contain protection, measurement, breaker-control, and communication-related logical nodes without pretending that all these functions are one undifferentiated device.\n\nLogical nodes contain named data objects. In an XCBR instance, Pos represents breaker position; its attributes can include the status value, quality, and timestamp. An illustrative object reference such as Bay1/XCBR1.Pos.stVal identifies a particular status attribute within a logical device and logical-node instance. Actual references depend on the engineered names. The important point is that the standardized components describe the information’s meaning, while project-specific components identify its location or instance.\n\nData objects use common data classes, which define reusable structures for concepts such as single-point status, double-point status, measured value, and controllable position. Functional constraints distinguish categories of attributes, including status, measurement, configuration, and control. Quality attributes are especially important: a numerical measurement can be present but invalid, questionable, substituted, or affected by a failure. Applications that consider only the numerical value and ignore its quality can make incorrect decisions even when communication is functioning normally.\n\nThe model also distinguishes electrical assets from automation functions. A power transformer is a primary-system asset, while differential protection is an algorithmic function acting on measurements associated with that asset. Part 6 can describe the electrical arrangement and associate logical nodes with the relevant equipment. This association helps engineering software understand not merely that a current measurement exists, but which bay or apparatus it concerns.\n\nStandardized names reduce semantic ambiguity, but they do not specify the complete behavior of every application. Vendors can support different logical nodes, optional data, or permitted extensions. Two devices implementing PTOC may offer different protection characteristics and setting ranges. IEC 61850 standardizes how much of that functionality is represented and communicated; it does not make the underlying protection algorithms identical."
    },
    {
      "heading": "Abstract services and client–server communication",
      "text": "IEC 61850-7-2 defines the Abstract Communication Service Interface, usually abbreviated ACSI. It describes operations in terms of their intended effects rather than a particular packet format. Services include discovering the server’s organization, reading and writing data, reporting changes, controlling equipment, transferring files, and accessing logs. A mapping document then specifies how those abstract operations are realized through an actual communication stack.\n\nFor conventional station-level client–server communication, IEC 61850-8-1 uses the Manufacturing Message Specification, or MMS, through a profile operating over TCP/IP and Ethernet. A station computer, gateway, or SCADA interface can act as a client, while a protection relay or bay controller provides server functions. This arrangement is suitable for supervisory measurements, alarms, settings-related interactions, and control operations. It is not the mechanism normally chosen for the fastest peer-to-peer protection signals.\n\nReporting reduces the need for continuous polling. An engineered dataset collects selected data attributes, and a report control block determines how reports are generated and delivered. Trigger conditions can include a change in value, a change in quality, or a data update. Periodic integrity reports provide a complete view of the dataset, while general interrogation allows a client to request a report of its current contents. Deadbands for analog quantities can limit traffic caused by insignificant fluctuations.\n\nBuffered and unbuffered reporting address different communication requirements. A buffered report control block can retain events during a temporary interruption, subject to the device’s buffer capacity and the applicable recovery procedures. An unbuffered report control block does not provide the same event-retention behavior. Buffering can preserve useful event history, but it is not unlimited storage: an extended outage or excessive event rate can exhaust available capacity, and clients must handle the resulting indications.\n\nControl services provide more than a remote write to a Boolean variable. IEC 61850 defines direct-control and select-before-operate arrangements, with normal-security and enhanced-security variants. Here, “security” concerns the control procedure and supervision of command execution; it does not mean cryptographic protection. Select-before-operate can reserve a controllable object before operation, while enhanced control procedures provide additional information about command completion. The application must still enforce relevant permissions, interlocks, and equipment constraints.\n\nFor example, an operator’s request to close a breaker can pass through a client–server control service to a switch-control function, which evaluates the request in conjunction with interlocking and switching conditions. The eventual breaker indication returns as status information. Communication acknowledgment, command acceptance, and confirmed physical operation are distinct events. Treating them as interchangeable can cause an operator display to show success before the primary equipment has actually changed state."
    },
    {
      "heading": "GOOSE and time-critical event exchange",
      "text": "Generic Object Oriented Substation Event, or GOOSE, is an IEC 61850 mechanism for distributing event information among devices. Its familiar mapping in IEC 61850-8-1 uses Ethernet multicast frames directly rather than a TCP connection. A publisher transmits a dataset, and configured subscribers receive and interpret it. This supports one-to-many communication without requiring the publisher to establish a separate session with every receiving relay.\n\nGOOSE commonly carries protection trips, interlocking states, breaker-failure initiation, blocking signals, and other information that must move quickly between devices. In a busbar protection application, for example, several relays may need to exchange indications that determine whether a fault lies inside or outside a protected zone. In a switching application, bay controllers can distribute the states required to evaluate whether an operation is permissible. Replacing individual copper signal circuits with messages can reduce wiring, but transfers part of the system’s dependency to networks and configuration.\n\nIts reliability mechanism combines immediate transmission after a state change with repeated publication. When a dataset state changes, the publisher sends the new state and initially repeats it at short intervals. The repetition interval then increases toward a configured steady-state interval. State and sequence counters help subscribers distinguish a new event from retransmissions. A time-allowed-to-live field enables a subscriber to detect that expected updates have ceased.\n\nThis is not the same as acknowledged delivery. A publisher does not receive an application acknowledgment from every subscriber, and retransmission does not guarantee that a particular receiver has acted correctly. Network failure, incorrect multicast filtering, mismatched dataset configuration, or a failed subscriber can still prevent the intended operation. Supervision identifies some such conditions, while the protection application determines the appropriate response to lost or invalid information.\n\nTiming requirements are application-specific. IEC 61850 defines performance categories for different kinds of messages and functions; a 3 ms transfer-time requirement is frequently associated with the most demanding trip-related exchanges. That figure is not a universal deadline for all IEC 61850 traffic, nor is it simply an Ethernet-switch latency specification. Transfer-time evaluation includes the relevant communication processing at the publishing and subscribing devices, as well as transmission through the network.\n\nGOOSE datasets also require careful change management. A subscriber must know the expected publisher, dataset structure, configuration revision, and communication parameters. Changing the order or type of dataset members without updating subscribers can invalidate the exchange. Test and simulation indications support controlled verification, but their interpretation must be coordinated with device operating modes. A frame that reaches a network interface is not necessarily a valid operational input to the receiving protection function."
    },
    {
      "heading": "Sampled values and the digital process interface",
      "text": "Sampled values provide a standardized means of transmitting digitized electrical measurements. In a conventional substation, current and voltage transformers deliver analog secondary signals through copper wiring to protection and measurement devices. In a digital arrangement, a merging unit or comparable process-interface device samples these signals and publishes a stream that several subscribers can use. IEC 61850-9-2 defines a principal Ethernet mapping for this communication.\n\nThe term “merging unit” reflects the combination of multiple measurement channels into a coordinated digital output. Inputs may originate in conventional instrument transformers or in sensors with different physical operating principles. Standardization of the instrument-transformer interface is also addressed by the IEC 61869 series, including IEC 61869-9 for digital communication. These standards complement IEC 61850; they should not be treated as alternative names for the same document.\n\nAn influential implementation guideline known as IEC 61850-9-2LE helped early products adopt a restricted, common set of choices. Its familiar protection profile used 80 samples per nominal power-frequency cycle, corresponding to 4,000 samples per second at 50 Hz and 4,800 at 60 Hz. These figures describe that profile, not a universal sampling rate imposed on every IEC 61850 application. Other profiles and applications use different rates and stream arrangements.\n\nSampled-value traffic differs fundamentally from event-driven GOOSE. It normally forms a continuous flow whose bandwidth is determined by the sampling rate, number of channels, frame structure, and publication arrangement. If \\(N\\) streams each produce \\(f\\) frames per second and each frame occupies \\(L\\) bytes on the medium, an initial bandwidth estimate is\n\n\\[R = 8NfL.\\]\n\nPractical calculations must account for all link overhead, redundant copies, engineering margins, and other traffic. A network that handles occasional alarms easily can still become unsuitable when many continuous measurement streams converge on one link.\n\nSample timing is essential when algorithms compare measurements from different locations. Differential protection, for example, depends on comparing currents that correspond to sufficiently aligned instants. Sample counters, synchronization indications, channel quality, and configured timing behavior help receiving devices interpret the stream. Synchronization accuracy and analog measurement accuracy remain separate properties: excellent clock alignment cannot correct a saturated current transformer or an incorrectly scaled channel.\n\nDigital process interfaces reduce some secondary copper wiring and allow multiple applications to share measurements. They also introduce failure modes involving merging units, network paths, time distribution, and stream configuration. Missing samples, unexpected sampling rates, or degraded synchronization can require an application to block, fall back, or change behavior according to its design. Such responses belong to the protection and measurement application, not merely to the packet transport mechanism."
    },
    {
      "heading": "System engineering and the configuration language",
      "text": "IEC 61850-6 defines the Substation Configuration Language, generally known as SCL. It is based on Extensible Markup Language and provides a structured description of device capabilities, configured functions, communication relationships, and aspects of the electrical installation. Its purpose is to make engineering information exchangeable between tools rather than leaving it embedded solely in proprietary project databases.\n\nSCL describes several related views. The substation section can represent voltage levels, bays, conducting equipment, and electrical connectivity. The IED section describes logical devices, logical nodes, datasets, control blocks, and other device-related information. A communication section records parameters such as access points and network addresses. Data-type templates define the structures needed to interpret the modeled objects. Associations between logical nodes and primary equipment connect the functional and electrical views.\n\nDifferent file types support different engineering stages. An IED Capability Description, or ICD, describes the capabilities offered by a device type. A System Specification Description, or SSD, can express aspects of the intended system before final device allocation. A Substation Configuration Description, or SCD, brings together the engineered system configuration. A Configured IED Description, or CID, contains configuration information relevant to an individual IED. Other defined exchange types, including IID and SED files, support additional device and inter-system workflows.\n\nA typical project begins with functional requirements and an electrical design. Device capabilities are imported into a system configuration tool, logical nodes are associated with equipment, and datasets and communication subscriptions are established. Device-specific tools then complete settings and produce the configurations to be loaded into IEDs. This workflow is not always a simple one-way sequence: project changes, replacement devices, and tool constraints can require controlled exchanges between system-level and device-level engineering.\n\nSCL reduces transcription errors by allowing communication relationships to be represented explicitly. A GOOSE subscriber can be engineered against a defined publisher and dataset rather than an informal spreadsheet entry. However, valid XML is only the first level of correctness. A file can satisfy its schema while still describing an incorrect protection relationship, an inconsistent dataset, or a network address that conflicts with another device.\n\nConfiguration management therefore extends beyond keeping a final file. The project needs traceability among requirements, SCL revisions, device firmware, protection settings, downloaded configurations, and test records. Configuration-revision fields help detect certain mismatches, but they do not replace a complete record of change. During commissioning, the installed system must be checked against the engineered design, including actual subscriptions and application behavior. The mere presence of matching file names does not establish that all devices are running matching configurations."
    },
    {
      "heading": "Network architecture, redundancy, and synchronization",
      "text": "IEC 61850 installations are often described in terms of station, bay, and process levels. The station level includes operator interfaces, gateways, and station-wide functions. Bay-level devices provide protection and control for a particular circuit or equipment group. The process level interfaces with primary equipment through measurement acquisition, breaker inputs, and operating outputs. These are functional distinctions; they do not require every installation to use three physically separate networks.\n\nA station bus typically supports communication among bay devices and station-level systems, including client–server traffic and GOOSE. A process bus carries digitized process information, especially sampled values and associated event exchanges. Some projects separate these networks physically; others use shared infrastructure with logical separation and engineered traffic control. Optical fiber is widely used because it supports electrical isolation and avoids some electromagnetic-interference problems associated with conductive communication paths.\n\nEthernet does not automatically provide suitable performance simply because its nominal data rate is high. Switch forwarding behavior, queueing, multicast handling, link utilization, and failure recovery all matter. Virtual local area networks and priority markings can separate traffic and support preferential treatment, but they are not substitutes for capacity analysis. Incorrect multicast filtering can either flood unnecessary traffic across the network or prevent required messages from reaching subscribers.\n\nRedundancy is commonly implemented using mechanisms standardized in IEC 62439-3. The Parallel Redundancy Protocol, or PRP, sends duplicate frames over two independent networks, with the receiver accepting one copy and discarding the duplicate. High-availability Seamless Redundancy, or HSR, uses duplicate transmission in opposite directions through a ring or related arrangement. These approaches avoid the reconvergence interval associated with some conventional network recovery methods for the failures they cover. They do not eliminate common-mode failures, defective endpoint software, or incorrect configuration.\n\nAccurate time supports sequence-of-events analysis and measurement alignment. Network Time Protocol can serve applications with less demanding timing requirements, while the Precision Time Protocol, defined by IEEE 1588, supports tighter synchronization. IEC/IEEE 61850-9-3 specifies a power-utility profile of that protocol. Time-aware switches, including transparent or boundary clocks, help control the effects of network residence time and topology.\n\nA time source may derive its reference from the Global Positioning System or another satellite-navigation system, but distribution quality depends on the whole timing chain. Antenna faults, reference loss, oscillator drift, and incorrect clock selection can degrade synchronization. Devices therefore need to communicate time quality and synchronization status, not just timestamps. Event logs from different devices can otherwise appear precisely ordered while actually referring to clocks with different errors."
    },
    {
      "heading": "Cybersecurity, conformance, and lifecycle assurance",
      "text": "IEC 61850 equipment belongs to operational technology, where communication failures can affect physical processes. Its cybersecurity requirements consequently include availability and integrity as well as confidentiality. Unauthorized breaker commands are an obvious concern, but forged status indications, manipulated sampled measurements, altered engineering files, and denial of service can be equally significant. A protection scheme can be disrupted without an attacker ever issuing a direct switching command.\n\nThe IEC 62351 series provides security specifications relevant to power-system communications, including protocols and services used with IEC 61850. Its parts address subjects such as protection of TCP/IP-based communication, MMS security, security for peer-to-peer exchanges, role-based access control, and key management. Applying these mechanisms requires attention to the actual device capabilities and deployment profile. Support for “IEC 61850” alone does not imply support for a particular IEC 62351 feature.\n\nCryptographic protection also interacts with operational constraints. Keys and certificates must be provisioned, renewed, and revoked over equipment lifetimes that may span decades. Time-sensitive multicast exchanges require security processing compatible with application performance. Engineering workstations and configuration repositories need protection because a legitimate-looking configuration change can alter how devices interpret traffic. Network segmentation, authenticated access, and controlled maintenance complement protocol-level mechanisms rather than being replaced by them.\n\nConformance testing under IEC 61850-10 evaluates specified aspects of an implementation against the standard. Device documentation, including protocol implementation and model-conformance statements, identifies supported services, models, and options. Testing can expose incorrect protocol behavior or unsupported claims, but a certificate has a defined scope. It does not prove that a device implements every part of the series or that a complete installation will perform its intended protection function.\n\nInteroperability testing addresses whether products exchange and use information correctly together. System acceptance testing goes further, checking the engineered application under realistic conditions. Relevant cases include simultaneous events, loss of a publisher, interrupted client connections, redundant-network failures, restoration after power loss, time-source degradation, and configuration mismatch. For a protection scheme, the decisive question is whether the correct equipment operates—or remains restrained—under the specified electrical and communication conditions.\n\nLifecycle assurance also requires control over firmware upgrades and replacements. A newer relay can retain a familiar model name while changing supported services or engineering-tool behavior. Mixed editions of IEC 61850 documents can coexist, but compatibility must be assessed rather than presumed. Archived configuration files, reproducible tests, and documented dependencies allow a maintenance change to be evaluated against the installed system. Device interchangeability is therefore a stronger requirement than basic protocol interoperability."
    },
    {
      "heading": "Applications beyond substations and relationships with other standards",
      "text": "IEC 61850 has expanded beyond its original substation setting through additional models and communication guidance. IEC 61850-7-410 addresses hydroelectric power plants, while IEC 61850-7-420 addresses distributed energy resources and distribution automation. These extensions retain the core modeling approach while representing functions associated with different equipment and operating environments. The objective is consistent information exchange, not the assumption that every power installation behaves like a conventional transmission substation.\n\nDistributed-energy applications illustrate the importance of richer models. A photovoltaic installation, battery system, or controllable generator may need to communicate its operating state, available capacity, active- and reactive-power behavior, limits, and control capabilities. A standardized information model can make these attributes more explicit than a list of unexplained registers. Integration still depends on the relevant equipment profile, controller behavior, and agreement about which functions are remotely controlled.\n\nIEC 61850-7-420 is relevant to systems containing power inverters, energy storage, and other resources, while the IEC 61400-25 series applies related modeling and communication principles to wind power plants. Such relationships demonstrate reuse of the architecture without making the document families identical. A wind turbine implementation, a substation relay, and a battery controller can share modeling concepts while supporting quite different sets of objects and services.\n\nWide-area applications raise additional questions. Local Ethernet multicast assumptions do not automatically hold across routed utility networks. The technical report IEC 61850-90-5 describes communication arrangements for applications such as exchanging synchrophasor information, including routable forms of event and sampled-data communication. Wide-area use introduces path delay, jitter, packet loss, security, and network-management conditions different from those inside a single substation. An application suitable for a local process bus cannot simply be extended across a regional network without reassessing those conditions.\n\nIEC 61850 also coexists with other information standards. The Common Information Model, developed principally in the IEC 61970 and IEC 61968 families, describes utility network and enterprise information at a different level of abstraction. IEC 61850 is particularly concerned with operational functions, devices, and their communications. Mapping between these representations can connect a substation’s detailed automation model with network-analysis or asset-management systems, but equivalent concepts do not always have a one-to-one correspondence.\n\nGateways likewise connect IEC 61850 installations to established telecontrol systems and protocols such as IEC 60870-5-104 or DNP3. Such translation can preserve values and basic indications while losing richer distinctions, including quality detail, control semantics, or object relationships. The engineering task is therefore not merely to convert message formats. It is to decide which meanings must survive the boundary and how the receiving system will represent them."
    }
  ],
  "links": [
    "electrical-grid",
    "electrical-substation",
    "circuit-breaker",
    "electrical-transformer",
    "scada",
    "commissioning",
    "optical-fiber",
    "global-positioning-system",
    "operational-technology",
    "cybersecurity",
    "distributed-energy-resources",
    "reactive-power",
    "power-inverter",
    "energy-storage",
    "wind-power"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}