Application integration at electric utilities - System interfaces for distribution management - Part 3: Interface for network operations
Sprache: EN-FR - zweisprachig englisch/französisch
Seitenzahl: 756 VDE-Artnr.: 249901
IEC 61968-3:2021 provides utilities with the means to supervise main substation topology (breaker and switch state), feeder topology and control equipment status through SCADA, AMI and other data sources. It also provides the means for handling network connectivity and loading conditions. Finally, it makes it possible for utilities to locate customer telephone complaints and coordinate activities of field crews with respect to planned and unplanned outages.
IEC 61968-3 specifies the information content of a set of message payloads that can be used to support many of the business functions related to network operations. Typical uses of the message payloads defined in IEC 61968-3 include data acquisition by external systems, fault isolation, fault restoration, trouble management and coordination of the real-time state of the network.
The scope illustrates the possibility of implementing IEC 61968-3 functionality as either a single integrated advanced distribution management system or as a set of separate functions Í OMS, DMS and SCADA. Utilities may choose to buy these systems from different vendors and integrate them using the IEC 61968-3 messages. Alternatively, a single vendor could provide two or all of these components as a single integrated system. In the case of more than one system being provided by the same vendor, the vendor may choose to use either extensions of the IEC 61968 messages or a proprietary integration mechanism to provide enhanced functionality over and above what is required/supported by the IEC 61968-3 specification. While this is a possible implementation, Subclause 4.3 defines the scope in terms of business functions that are implemented in common vendor offerings.
Annexes in this document detail integration scenarios or use cases, which are informative examples showing typical ways of using the message payloads defined in this document as well as message payloads to be defined in other parts of the IEC 61968 series
This third edition cancels and replaces the second edition published in 2017. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) major rework of Switch Order related profiles and Outage related profiles;
b) documented profiles in more detail as a result of the analysis of end-to-end use cases;
c) separated Measurement and Control profile into two profiles: PSRMeasurements and PSRControls;
d) replaced Temporary Network Change profile with SwitchingEvents profile;
e) added MeasurementAction, ControlAction, GenericAction and VerificationAction to SwitchingPlans profile. Added examples;
f) added SwitchingActions profile to support the coordination of SwitchingPlan execution between control room and the field crew;
g) added ClampAction to SwitchingPlan, SwitchingAction and SwitchingEvent profiles, to allow clamps to be placed and removed independently of jumpers;
h) separated OutagesAndFaults profile into UnplannedOutages, PlannedOutages, EquipmentFaults, LineFaults;
i) added list of energized and de-energized UsagePoints to the UnplannedOutages profile;
j) added PlannedOutages profile;
k) added PlannedOutageNotifications profile;
l) added SwitchingPlanRequest profile to replace OutageSchedules profile;
m) expanded TroubleOrders profile to include UnplannedOutages and TroubleTickets and to allow crews to be scheduled to individual tasks within the TroubleOrder;
n) expanded use cases and sequence diagrams;
o) sequence diagrams updated to use IEC 61968-100 message patterns;
p) use cases in IEC 62559-2 use case template;
q) added example XML for profiles;
r) replaced xsd in Annex with tables to document the profiles in a serialisation-independent form;
s) clarified FLISR use case to include interactions between DSO and TSO per review comments from Edition 2.
t) removed OperationalTags since it is now part of the TagAction in the SwitchingEvents payload