1. Outage Scheduling for Operations, Planning and Market Systems
2017 CIM User Group Meeting
Columbus, OH
November 8 – 9, 2017
David Bogen
Manager T & D Services – System Modeling
Oncor Electric Delivery, LLC

2. What is an Outage and why is it important?
An Outage is the Planned or Unplanned status change of an power system asset from its normal state of operation.
In-Service/Out-of-Service
Open/Closed
Available/Unavailable
Limited capability
Outage Scheduling is the notification interested parties that an asset will be changing its state of operations at a schedule time.
Parties include
Field personnel
Clearance coordination personnel
Transmission system operators
Market Schedulers
Reliability Coordinators

3. Impact of inadequate notifications of Outages
The above information is from T&D World (By Tip Goodwin, Oncor Electric Delivery Co. | Mar 04, 2014)

4. How does Outage Scheduling impact Operations
Determining transmission system reliability, current and future state.
Creating switching sequence to support implementing requested outage.
Coordinating outage plans between multiple operating entities.
Ability to manage system congestion as operating state of the transmission system changes.
Ability to monitor actual outages to planned outages.

5. Planning
Provides the ability to analysis future state of the transmission systems and develop any required mitigation plan need to support the outage.
Provides advance notice and the availability of generation resources so system impact can for analyzed.
Determine future transmission N-1 contingency impacts.

6. Market Systems
Information about Generators not available to the Market.
Transmission outages that would limit generation output.
Generation that has been limited do to system issues.

7. How does CIM support Outage Scheduling and Coordination?

8. So how does CIM support Outage Scheduling and Coordination?
In several manners
Messaging, the need to exchange and coordinate information about outages.
The ability to map outage information into topology models to support State Estimation, Real Time Contingency Analysis and Optimal Power Flow.
Asset Management and reporting.

9. Messaging (IEC 61968)
ERCOT perspective ERCOT identified a need to be able to use messaging exchange information to support outage scheduling before 2010 when ERCOT transitioned to a Nodal Market. To support this need ERCOT developed a set of XSDs just for outage Scheduling. Information about these messages is available on the ERCOT website

10. Example: Create Single Outage Request
<soapenv:Envelope xmlns:soapenv=" xmlns:mes=" <soapenv:Header/> <soapenv:Body> <RequestMessage xmlns:xsi=" xmlns:xsd=" xmlns:SOAP-ENV=" xmlns=" <Header> <Verb>create</Verb> <Noun>OutageSet</Noun> <ReplayDetection> <Nonce> D3433</Nonce> <Created> T16:08: :00</Created> </ReplayDetection> <Revision>1</Revision> <Source>TABC</Source> <UserID>USER1</UserID> <MessageID> </MessageID> <Comment/> </Header> <Payload> <OutageSet xmlns=" <Outage> <OutageInfo> <outageType>M1</outageType> <participant>TABC</participant> <lastModified> T10:58:00-05:00</lastModified> <lastModifiedBy>USER1</lastModifiedBy> <Requestor> <userFullName>John Smith</userFullName> <tertiaryContact> </tertiaryContact> </Requestor> <requestDate> T13:13:00-05:00</requestDate> <Disclaimer>Disclaimer0</Disclaimer> <disclaimerAck>true</disclaimerAck> </OutageInfo>

11. Example Continued
<TransmissionOutage> <operatingCompany>TABC</operatingCompany> <equipmentName>MOS_3333</equipmentName> <equipmentIdentifier>_{A1B234CD-A1A1-11AA-BB22-012A A}</equipmentIdentifier> <transmissionType>DSC</transmissionType> <fromStation>STATION1</fromStation> <normalState>C</normalState> <outageState>O</outageState> <voltage>138</voltage> <projectName>Project4</projectName> <emergencyRestorationTime>1</emergencyRestorationTime> <natureOfWork>RE</natureOfWork> </TransmissionOutage> <Schedule> <plannedStart> T08:00:00-05:00</plannedStart> <plannedEnd> T12:00:00-05:00</plannedEnd> <earliestStart> T08:00:00-05:00</earliestStart> <latestEnd> T13:00:00-05:00</latestEnd> </Schedule> </Outage> </OutageSet> </Payload> </RequestMessage> </soapenv:Body> </soapenv:Envelope>

12. Example Create Single Outage Reply
<SOAP-ENV:Envelope xmlns:SOAP-ENV=" <SOAP-ENV:Body> <ns0:ResponseMessage xmlns:ns0=" <ns0:Header> <ns0:Verb>reply</ns0:Verb> <ns0:Noun>OutageSet</ns0:Noun> <ns0:ReplayDetection> <ns0:Nonce>fc905511aa9375e6de892c2fef72e72e</ns0:Nonce> <ns0:Created> T16:08: :00</ns0:Created> </ns0:ReplayDetection> <ns0:Revision>1</ns0:Revision> <ns0:Source>ERCOT</ns0:Source> <ns0:UserID>USER1</ns0:UserID> <ns0:MessageID> </ns0:MessageID> <ns0:Comment/> </ns0:Header> <ns0:Reply> <ns0:ReplyCode>OK</ns0:ReplyCode> <ns0:Timestamp> T16:08: :00</ns0:Timestamp> </ns0:Reply> <ns0:Payload> <ns1:OutageSet xmlns:ns0=" xmlns:ns1=" <ns1:Outage> <ns1:OutageInfo> <ns1:outageType>M1</ns1:outageType> <ns1:participant>TABC</ns1:participant> <ns1:versionId>1</ns1:versionId> <ns1:state>Recvd</ns1:state> <ns1:status>RatE</ns1:status> <ns1:previousState>ENYS</ns1:previousState> <ns1:Requestor> <ns1:name>USER1</ns1:name> <ns1:userFullName>John Smith</ns1:userFullName> <ns1:primaryContact/> <ns1:secondaryContact/> <ns1:tertiaryContact> </ns1:tertiaryContact> </ns1:Requestor> <ns1:requestDate> T16:08:00-05:00</ns1:requestDate> </ns1:OutageInfo>

13. Example Continued
<ns1:TransmissionOutage> <ns1:operatingCompany>TABC</ns1:operatingCompany> <ns1:equipmentType>DSC</ns1:equipmentType> <ns1:equipmentName>MOS_3333</ns1:equipmentName> <ns1:equipmentIdentifier>_{A1B234CD-A1A1-11AA-BB22-012A A}</ns1:equipmentIdentifier> <ns1:transmissionType>DSC</ns1:transmissionType> <ns1:fromStation>STATION1</ns1:fromStation> <ns1:outageState>O</ns1:outageState> <ns1:projectName>Project4</ns1:projectName> <ns1:emergencyRestorationTime>1</ns1:emergencyRestorationTime> <ns1:mRID>TABC.OTG.M1.Transmission.ABC </ns1:mRID> <ns1:natureOfWork>RE</ns1:natureOfWork> </ns1:TransmissionOutage> <ns1:Schedule> <ns1:plannedStart> T08:00:00-05:00</ns1:plannedStart> <ns1:plannedEnd> T12:00:00-05:00</ns1:plannedEnd> <ns1:earliestStart> T08:00:00-05:00</ns1:earliestStart> <ns1:latestEnd> T13:00:00-05:00</ns1:latestEnd> </ns1:Schedule> <ns1:OSNotes> <ns1:RequestorNotes/> <ns1:ReviewerNotes/> <ns1:SupportingNotes/> <ns1:RASPSNotes/> </ns1:OSNotes> </ns1:Outage> </ns1:OutageSet> </ns0:Payload> </ns0:ResponseMessage> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

14. Topology Model ( IEC 61970 augmented with IEC 61968 asset information)
What information does a Transmission Outage Management system requires to support the Outage Scheduling? Are outage Scheduling systems topology aware? Is outage information required to be correlated to any other systems?

15. Some of the applications/systems that use outage information
Real Time Contingency Analysis
Security Constrained Economic Dispatch
Look Ahead Contingency Analysis
Optimal Power Flow
Switching Procedure Management

16. Provides awareness of future state of transmission system.

17. System Reliability!

18. Outage Scheduling requires asset information that is a reflection of the Transmission Network Model that is being Operated
Station
Voltage Level
Switching Devices
Breakers
Disconnectors
Bus Bars
Shunt Devices
Capacitors
Reactors
Static Var Compensators
Transformers
Lines
AC Segements

19. How Oncor is supporting Transmission Outage Application data requirement

20. Vendor was not CIM savvy
The outage scheduling application did not support true RDF/XML CIM topology model.
Wanted to leverage existing transmission model that is already maintained by a CIM complaint application.
Get away from having to maintain a separate model to support outage scheduling
Existing system requires manual entry of data and mapping to ERCOT systems.
Oncor’s existing CIM model already aligned with the ERCOT CIM model.
Had to teach Transmission Outage Application vendor the CIM for this implementation.
This did require extending the Oncor Name Space with additional CIM extensions. Primarily to support additional asset information

21. Example of CIM/XML for a Breaker
<cim:Breaker rdf:ID="_{D0F3EB16-85CA-4E65-B E0C3F9}"> <cim:IdentifiedObject.name>6080</cim:IdentifiedObject.name> <cim:Breaker.ampRating></cim:Breaker.ampRating> <spc:Breaker.BreakerType rdf:resource=" <spc:Switch.ContinuousRating>0</spc:Switch.ContinuousRating> <spc:Switch.NetworkMappingSense rdf:resource=" <cim:Switch.normalOpen>false</cim:Switch.normalOpen> <spc:Switch.RatingUnits rdf:resource=" <spc:Switch.ReliabilityIndexZone rdf:resource=" <spc:ConductingEquipment.protectedEnd rdf:resource=" <spc:Equipment.NAFlag>true</spc:Equipment.NAFlag> <etx:Equipment.psseid></etx:Equipment.psseid> <sp3:PowerSystemResource.Spectrum3xName>ALNSW/345/LN6080/CB</sp3:PowerSystemResource.Spectrum3xName> <etx:PowerSystemResource.teid>117724</etx:PowerSystemResource.teid> <cim:IdentifiedObject.aliasName></cim:IdentifiedObject.aliasName> <cim:IdentifiedObject.description></cim:IdentifiedObject.description> <cim:IdentifiedObject.localName>Breaker, ALLEN SWITCH, BKR 6080</cim:IdentifiedObject.localName> <cim:IdentifiedObject.mRID></cim:IdentifiedObject.mRID> <cim:IdentifiedObject.pathName></cim:IdentifiedObject.pathName> <oncor:Domain.Relevant>true</oncor:Domain.Relevant> <cim:ConductingEquipment.BaseVoltage rdf:resource="#_{403AF767-C33E A1-17F5B }"/> <etx:PowerSystemResource.Ownership rdf:resource="#_{526B28F CA-991B-4774BAAEA33D}"/> <etx:PowerSystemResource.Operatorship rdf:resource="#_{6C3C866D-D38B AA9669A152}"/> <spc:Switch.ParentOf rdf:resource="#_{9519D199-B D-A56E-379C561803DE}"/> <cim:Equipment.MemberOf_EquipmentContainer rdf:resource="#_{9519D199-B D-A56E-379C561803DE}"/> <oncor:Domain.TOAEnabledFlag>1</oncor:Domain.TOAEnabledFlag> <oncor:Doman.PrimaryWorkCenter>_{D0F3EB16-85CA-4E65-B E0C3F9}</oncor:Doman.PrimaryWorkCenter> <oncor:Domain.TIRSEnabledFlag>1</oncor:Domain.TIRSEnabledFlag> </cim:Breaker>

22. Some of the question asked about the CIM mapping
Where is the voltage level for the breaker?
What is a Terminal?
What station does the breaker belong to?
Where are the associated disconnects for the breaker?
What is a Bay?
How do you identify what stations does a AC Segment terminate in to?
How do you identify a capacitor or reactor?
How is the location for the Station/Equipment identified?

23. Eventually got to the MOST important question
Is there an existing standard
CIM Profile
for Outage Scheduling?

24. Asset Management
Needs information about the outage and the facilities being impacted.
Duration of outage.
Classification of outage.
Support FERC/NERC TADS outage reporting.
The purpose of the Transmission Availability Data System is the implement a uniform approach to reporting and measuring transmission availability, performance and other related reliability data.