iso interface specification - california iso · iso interface specification outage management ......

Owner: Nallagangu, Sunil Program Office

ISO Public

Doc ID: GNFDMDEHU6BB-46-46 of 135

ISO Interface Specification

Outage Management System Document Version: 1.91.10

Date Created: 9/29/201511/30/2015

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10

Outage Management System ISO Interface Specification Date Created: 9/29/201511/30/2015

Location of Document

<Add Documentum path or URL here>

Revision History

Date Version Description Author

9/29/201511/30/2015

0.1 Document creation Sean Crimmins

01/08/2014 1.0 Initial document with Generation submit/retrieve Sean Crimmins

1/27/2014 1.1 Updated with Transmission submit/retrieve Sean Crimmins

2/7/2014 1.2 Added common services and facility outage definition Sean Crimmins

2/7/2014 1.2 Added outage status update Sean Crimmins

4/7/2014 1.2 Updated WSDLs and sample XSDs to reflect latest XSD modifications

Sunil Nallagangu

4/15/2014 1.2 Updated spec to accommodate changes in ResourceOutageResults_v1.xsd

Sunil Nallagangu

5/29/2014 1.3 Updated spec to accommodate latest changes in XSDs Sunil Nallagangu

7/21/2014 1.4 Added SOAP Header and MTOM attachment Info Sunil Nallagangu

08/01/2014 1.4 Updated spec to reflect latest XSDs Sunil Nallagangu

08/28/2014 1.5 1.Updated spec to reflect latest XSDs

TransmissionOutage: Relaxed length restriction Equipment MRID from 32 to 40 chars Relaxed length restriction Equipment Name from 32 to 80 chars Added Enumeration for Equipment NameType

ResourceOutage:

Sunil Nallagangu

Formatted Table

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Relaxed Resource(Generator/Intertie/Load) name from 32 to 40 chars.

10/10/2014 1.6 Updated retrieve resource outage , retrieve transmission outage, retrieve availability and retrieve facility outage definition sections to include tables that describe how the different request criteria can be used.

Yinka Ajede

11/10/2014 1.6 TransmissionOutageResults (B2B) - Adding enumerations (CONFORMLOAD, NONCONFORMLOAD and STATICVARCOMPENSATOR) to equipment type.

FacilityOutageDefinitionResults (B2B) - Adding only “STATICVARCOMPENSATOR” enumeration to equipment type (already has ConformLoad and NonConformLoad in the enumerations)

Sunil Nallagangu

11/11/2014 1.6 Added list of primary and secondary cause codes that are required for forced transmission outages

Yinka Ajede

11/11/2014 1.6 RequestFacilityOutageDefinition updated to enable search by Participant market organisation

Sunil Nallagangu

11/17/2014 1.7 Added enumerations to be used for primary and secondary codes that are required for forced transmission outages

Yinka Ajede

04/16/2015 1.8 Added appendix with enumerated communication equipment and list of errors and warnings

Updated section 5.6.1 with details about rangePeriodType option added to Retrieve Resource Outage

Updated section 7.6.1 with details about rangePeriodType option added to Retrieve Transmission Outage

Yinka Ajede

09/29/2015 1.9 OutageStatusUpdate changes include: Outage/MktOrganisation/mrid - add,

optional Outage/OperatingParticipant/mrid - add, optional ResourceOutageResults changes include: RegisteredResourceOutage/isInvalid - Add,

optional RegisteredResourceOutage/isInconsistent - Add,

optional TransmissionOutageData changes include:

Yinka Ajede

Formatted Table

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



TransmissionOutage/Work/kind - Added enumerations (RIMS_OUTAGE, RIMS_TESTING)

TransmissionOutageResults changes include: TransmissionOutage/Equipments/PSRType/type

- Added enumerations (SYNCHRONOUSMACHINE) TransmissionOutage/Work/kind

- Added enumerations (RIMS_OUTAGE, RIMS_TESTING)

11/30/2015 1.10 ResourceOutageData XSD changed to version 2. Updates include: ResourceOutage/Work/kind

- Added enumerations (ANNUAL_USE_LIMIT_REACHED, MONTHLY_USE_LIMIT_REACHED OTHER_USE_LIMIT_REACHED, SHORT_TERM_USE_LIMIT_REACHED, AMBIENT_DUE_TO_FUEL_INSUFFICIENCY, RIMS_OUTAGE, RIMS_TESTING)

ResourceOutageResults XSD changed to version 2. Updates include: ResourceOutage/Work/kind

- Added enumerations ((ANNUAL_USE_LIMIT_REACHED, MONTHLY_USE_LIMIT_REACHED OTHER_USE_LIMIT_REACHED, SHORT_TERM_USE_LIMIT_REACHED, AMBIENT_DUE_TO_FUEL_INSUFFICIENCY,RIMS_OUTAGE, RIMS_TESTING)

Mandatory isSCPExempt flag changed to optional RequestResourceOutage XSD changed to version 2 to match ResourceOutageResults XSD RequestTransmissionOutage XSD changed to version 2 to match TransmissionOutageResults XSD

Yinka Ajede

Versioning should be as follows:

1. Draft – When a document is still in its developing stages and is not ready for review and sign off. 2. V 0.n – When changes are made before the document is ready for initial review. 3. V 1.0 – When a document is ready for review and sign off. It remains as v 1.0 after sign off if no

changes are made. 4. V 1.n – When changes are made after the initial review. “n” represents the number of iterations of

changes until the official signoff.

Formatted Table

Formatted: Font: 12 pt, Font color: Text 1

Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0" + Indent at: 0.25"




cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


5. V 2.0 – When additional changes are requested after initial sign off and Change Request is approved. The Change Request that initiated the revision must be referenced in the Revision History Description.

6. V2.n – When changes are made after the second sign off where the changes do not affect downstream/related documents or system code (i.e.: grammar changes, etc.)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Table of Contents OUTAGE MANAGEMENT SYSTEM .......................................................................................................................... 1

DOCUMENT VERSION: 1.9 .......................................................................................................................................... 1

DATE CREATED: 9/29/2015 .......................................................................................................................................... 1

LOCATION OF DOCUMENT ....................................................................................................................................... 2

REVISION HISTORY ...................................................................................................................................................... 2

TABLE OF CONTENTS ................................................................................................................................................65

1. INTRODUCTION..............................................................................................................................................1110

1.1 PURPOSE .........................................................................................................................................................1110 1.2 CONTACT INFORMATION ..................................................................................................................................1110 1.3 RELATED DOCUMENTS ....................................................................................................................................1110

FIGURE 1 – ISO MARKET WEB SERVICES INTERFACE SPECIFICATION DOCUMENT SET ..............1110

1.4 RELEASE NOTES ..............................................................................................................................................1211 1.5 API TRANSITION SUPPORT ...............................................................................................................................1211 1.6 MTOM & DOC STYLE ATTACHMENTS .............................................................................................................1211 1.7 DATE TIME DATA TYPE ELEMENTS .................................................................................................................1312

2. SOAP HEADER ELEMENTS & MTOM ATTACHMENTS .......................................................................1312

2.1 IDENTITY OF MESSAGE PRODUCER ..................................................................................................................1312 2.1.1 Identity ...................................................................................................................................................1412 2.1.2 Timestamp ..............................................................................................................................................1413 2.1.3 Message Freshness ................................................................................................................................1413

2.2 MTOM ATTACHMENTS ...................................................................................................................................1413

3. STANDARD XSDS ............................................................................................................................................1615

3.1 STANDARD ATTACHMENT INFORMATION ........................................................................................................1615 1.1.1 Element table .........................................................................................................................................1615 3.1.1 Schema (StandardAttachmentInfor.xsd) ................................................................................................1716 1.1.2 Example XML File (StandardAttachmentInfor.xml) ..............................................................................1716

3.2 FAULT RETURN ................................................................................................................................................1817 3.2.1 Element Table ........................................................................................................................................1817 3.2.2 Schema (StandardOutput.xsd) ...............................................................................................................1918 3.2.3 Example XML File (StandardOutput.xml) .............................................................................................1918

4. SUBMIT RESOURCE OUTAGE {CHANGE REQUESTS} BUSINESS SCENARIO ...............................2119

4.1 OVERVIEW .......................................................................................................................................................2119 4.2 SERVICE LEVEL AGREEMENT ...........................................................................................................................2119 4.3 USE MODEL .....................................................................................................................................................2119

4.3.1 Submit New Outage ...............................................................................................................................2119 4.3.2 Submit Change to Existing Outage ........................................................................................................2220

4.4 OPERATIONAL DETAILS ...................................................................................................................................2220 4.4.1 Submit Resource Outage........................................................................................................................2220

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


4.4.2 Submit Resource Outage Change Request .............................................................................................2220 4.5 WSDL .............................................................................................................................................................2320

4.5.1 submitResourceOutage_v1.wsdl / submitResourceOutage_v1_DocAttach.wsdl ...................................2320 4.5.2 submitResourceOutageChangeRequest_v1.wsdl /

submitResourceOutageChangeRequest_v1_DocAttach.wsdl ..............................................................................2320 4.6 SUBMIT RESOURCE OUTAGE {CHANGE REQUEST} ..........................................................................................2321

4.6.1 Element Table ........................................................................................................................................2321 4.6.2 Schema (ResourceOutageData_v1.xsd) .................................................................................................3128 4.6.3 Example XML File (SubmitResourceOutageData_v1.xml) ...................................................................3128 4.6.4 Example XML File (SubmitResourceOutageChangeRequest_v1.xml) ..................................................3431

4.7 SUBMIT RESOURCE OUTAGE {CHANGE REQUEST} RESPONSE .........................................................................3633 4.7.1 Element Table ........................................................................................................................................3633 4.7.2 Schema (OutageStandardOutput_v1.xsd) ..............................................................................................3734 4.7.3 Example XML File (ResourceOutageStandardOutput.xml) ..................................................................3734

5. RETRIEVE OUTAGE/CHANGE REQUESTS BUSINESS SCENARIO....................................................4138


5.3.1 Retrieve Generation Outages ................................................................................................................4138 5.3.2 Retrieve Resource Outage Change Requests .........................................................................................4239

5.4 OPERATIONAL DETAILS ...................................................................................................................................4239 5.4.1 Retrieve Resource Outage .....................................................................................................................4239 5.4.2 Retrieve Resource Outage Change Request ..........................................................................................4239

5.5 WSDL .............................................................................................................................................................4339 5.5.1 retrieveResourceOutage_v1.wsdl / retrieveResourceOutage_v1_DocAttach.wsdl ...............................4339 5.5.2 retrieveResourceOutageChangeRequest_v1.wsdl /

retrieveResourceOutageChangeRequest_v1_DocAttach.wsdl .............................................................................4340 5.6 RETRIEVE RESOURCE OUTAGE {CHANGE REQUEST} ......................................................................................4340

5.6.1 Element Table ........................................................................................................................................4340 5.6.2 Schema (RequestResourceOutage_v1.xsd) ............................................................................................4541 5.6.3 Example XML File (RequestResourceOutage_v1.xml) ..........................................................................4541 5.6.4 Example XML file (RequestResourceOutageChangeRequest.xml) ........................................................4542

5.7 RETRIEVE RESOURCE OUTAGE {CHANGE REQUEST} RESPONSE .....................................................................4642 5.7.1 Element Table ........................................................................................................................................4642 5.7.2 Schema (ResourceOutageResults_v1.xsd) .............................................................................................5551 5.7.3 Example XML File (ResourceOutageResults_v1.xml) ...........................................................................5551 5.7.4 Example XML file (ResourceOutageChangeRequestResults_v1.xml) ...................................................5854

5.8 FAULT RETURN ................................................................................................................................................6258

6. SUBMIT TRANSMISSION OUTAGE {CHANGE REQUESTS} BUSINESS SCENARIO ......................6359


6.3.1 Submit New Transmission Outage .........................................................................................................6359 6.3.2 Submit Change to Existing Transmission Outage .................................................................................6460

6.4 OPERATIONAL DETAILS ...................................................................................................................................6460 6.4.1 Submit Transmission Outage .................................................................................................................6460 6.4.2 Submit Transmission Outage Change Request ......................................................................................6460

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


6.5 WSDL .............................................................................................................................................................6560 6.5.1 submitTransmissionOutage_v2.wsdl / submitTransmissionOutage_v2_DocAttach.wsdl ......................6560 6.5.2 SubmitTransmissionOutageChangeRequest_v2.wsdl/

SubmitTransmissionOutageChangeRequest_v2_DocAttach.wsdl .......................................................................6561 6.6 SUBMIT TRANSMISSION OUTAGE {CHANGE REQUEST} ...................................................................................6561

6.6.1 Element Table ........................................................................................................................................6762 6.6.2 Schema (TransmissionOutageData_v2.xsd) ..........................................................................................7065 6.6.3 Example XML File (SubmitTransmissionOutageData_v2.xml) .............................................................7065 6.6.4 Example XML File (SubmitTransmissionOutageChangeRequest_v2.xml) ............................................7267

6.7 SUBMIT TRANSMISSIONOUTAGE {CHANGE REQUEST} RESPONSE ...................................................................7469 6.7.1 Element Table ........................................................................................................................................7469 6.7.2 Schema (OutageStandardOutput_v1.xsd) ..............................................................................................7571 6.7.3 Example XML File (TransmissionOutageStandardOutput_v1.xml) ......................................................7571

7. RETRIEVE TRANSMISSION OUTAGE/CHANGE REQUESTS ..............................................................7873


7.3.1 Retrieve Transmission Outages .............................................................................................................7873 7.3.2 Retrieve Transmission Outage Change Requests ..................................................................................7974

7.4 OPERATIONAL DETAILS ...................................................................................................................................7974 7.4.1 Retrieve Transmission Outage ...............................................................................................................7974 7.4.2 Retrieve Transmission Outage Change Request ....................................................................................7974

7.5 WSDL .............................................................................................................................................................8074 7.5.1 retrieveTransmissionOutage_v2.wsdl / retrieveTransmissionOutage_v2_DocAttach.wsdl ..................8074 7.5.2 retrieveTransmissionOutageChangeRequest_v2.wsdl /

retrieveTransmissionOutageChangeRequest_v2_DocAttach.wsdl ......................................................................8075 7.6 RETRIEVE TRANSMISSION OUTAGE {CHANGE REQUEST}................................................................................8075

7.6.1 Element Table ........................................................................................................................................8075 7.6.2 Schema (RequestTransmissionOutage_v1.xsd) .....................................................................................8276 7.6.3 Example XML File (RequestTransmissionOutage_v1.xml) ...................................................................8277 7.6.4 Example XML file (RequestTransmissionOutageChangeRequest_v1.xml) ...........................................8377

7.7 RETRIEVE TRANSMISSION OUTAGE {CHANGE REQUEST} RESPONSE ..............................................................8378 7.7.1 Element Table ........................................................................................................................................8378 7.7.2 Schema (TransmissionOutageResults_v2.xsd) ......................................................................................8782 7.7.3 Example XML File (TransmissionOutageResults_v2.xml) ....................................................................8782 7.7.4 Example XML file (TransmissionOutageResultsChangeRequests_v2.xml) ...........................................9185

7.8 FAULT RETURN ................................................................................................................................................9589

8. RETRIEVE AVAILABILITY ..........................................................................................................................9690


8.3.1 Retrieve Availability ..............................................................................................................................9690 8.4 OPERATIONAL DETAILS ...................................................................................................................................9791

8.4.1 Retrieve Availability ..............................................................................................................................9791 8.5 WSDL .............................................................................................................................................................9791

8.5.1 retrieveAvailability_v1.wsdl / retrieveAvailability_v1_DocAttach.wsdl ...............................................9791 8.6 RETRIEVE AVAILABILITY .................................................................................................................................9791

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


8.6.1 Element Table ........................................................................................................................................9891 8.6.2 Schema (RequestAvailability_v1.xsd) ....................................................................................................9892 8.6.3 Example XML File (RequestAvailability_v1.xml) ..................................................................................9892

8.7 REQUEST AVAILABILITY RESPONSE .................................................................................................................9993 8.7.1 Element Table ........................................................................................................................................9993 8.7.2 Schema (AvailabilityResults_v1.xsd) ................................................................................................... 10093 8.7.3 Example XML File (AvailabilityResults_v1.xml) ................................................................................. 10093

8.8 FAULT RETURN .............................................................................................................................................. 10195

9. RETRIEVE FACILITY OUTAGE DEFINITION ....................................................................................... 10296

9.1 OVERVIEW ..................................................................................................................................................... 10296 9.2 SERVICE LEVEL AGREEMENT ......................................................................................................................... 10296 9.3 USE MODEL ................................................................................................................................................... 10296

9.3.1 Retrieve Facility Outage Definition ..................................................................................................... 10296 9.4 OPERATIONAL DETAILS ................................................................................................................................. 10397

9.4.1 Retrieve Facility Outage Definition ..................................................................................................... 10397 9.5 WSDL ........................................................................................................................................................... 10397

9.5.1 retrieveFacilityOutageDefinition_v1.wsdl / retrieveFacilityOutageDefinition_v1_DocAttach.wsdl .. 10397 9.6 RETRIEVE FACILITY OUTAGE DEFINITION ..................................................................................................... 10397

9.6.1 Element Table ...................................................................................................................................... 10497 9.6.2 Schema (requestFacilityOutageDefinition_v1.xsd) ............................................................................. 10498 9.6.3 Example XML File (RequestFacilityOutageDefinition_v1.xml) .......................................................... 10498

9.7 REQUEST FACILITY OUTAGE RESPONSE ........................................................................................................ 10599 9.7.1 Element Table ...................................................................................................................................... 10599 9.7.2 Schema (FacilityOutageDefinitionResults_v1.xsd) ........................................................................... 106100 9.7.3 Example XML File (FacilityOutageDefinitionResults_v1.xml) ......................................................... 106100

9.8 FAULT RETURN ............................................................................................................................................ 107101

10. WITHDRAW OUTAGE CHANGE REQUEST ......................................................................................... 108102

10.1 OVERVIEW .............................................................................................................................................. 108102 10.2 SERVICE LEVEL AGREEMENT .................................................................................................................. 108102 10.3 USE MODEL ............................................................................................................................................ 108102

10.3.1 Retrieve Facility Outage Definition .............................................................................................. 108102 10.4 OPERATIONAL DETAILS .......................................................................................................................... 109103

10.4.1 Retrieve Facility Outage Definition .............................................................................................. 109103 10.5 WSDL..................................................................................................................................................... 109103

10.5.1 withdrawOutageChangeRequest_v1.wsdl ..................................................................................... 109103 10.6 WITHDRAW OUTAGE CHANGEREQUEST ................................................................................................. 109103

10.6.1 Element Table ............................................................................................................................... 109103 10.6.2 Schema (WithdrawOutageChangeRequest_v1.xsd) ...................................................................... 110103 10.6.3 Example XML File (WithdrawOutageChangeRequest_v1.xml) .................................................... 110103

10.7 WITHDRAW OUTAGE CHANGE REQUEST STANDARD OUTPUT ................................................................ 110104 10.7.1 Element Table ............................................................................................................................... 110104 10.7.2 Schema (StandardOutput_v1.xsd) ................................................................................................. 110104 10.7.3 Example XML File (WithdrawOutageChangeRequestStandardOutput_v1.xml) .......................... 110104

10.8 FAULT RETURN ....................................................................................................................................... 111105

11. ACKNOWLEDGE OUTAGE WARNING ................................................................................................. 112106

11.1 OVERVIEW .............................................................................................................................................. 112106

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


11.2 SERVICE LEVEL AGREEMENT .................................................................................................................. 112106 11.3 USE MODEL ............................................................................................................................................ 112106

11.3.1 Acknowledge Outage Warning...................................................................................................... 112106 11.4 OPERATIONAL DETAILS .......................................................................................................................... 113107

11.4.1 Retrieve Facility Outage Definition .............................................................................................. 113107 11.5 WSDL..................................................................................................................................................... 113107 11.6 ACKNOWLEDGE OUTAGE WARNING ....................................................................................................... 113107

11.6.1 Element Table ............................................................................................................................... 113107 11.6.2 Schema (AcknowledgeOutageWarning_v1.xsd)............................................................................ 113107 11.6.3 Example XML File (AcknowledgeOutageWarning_v1.xml) ......................................................... 113107

11.7 ACKNOWLEDGE OUTAGE WARNING STANDARD OUTPUT ....................................................................... 114108 11.7.1 Element Table ............................................................................................................................... 114108 11.7.2 Schema (StandardOutput_v1.xsd) ................................................................................................. 114108 11.7.3 Example XML File (AcknowledgeOutageWarningStandardOutput_v1.xml) ................................ 114108

12. OUTAGE STATUS UPDATE ...................................................................................................................... 116110

12.1 OVERVIEW .............................................................................................................................................. 116110 12.2 SERVICE LEVEL AGREEMENT .................................................................................................................. 116110 12.3 USE MODEL ............................................................................................................................................ 116110

12.3.1 Acknowledge Outage Warning...................................................................................................... 116110 12.4 OPERATIONAL DETAILS .......................................................................................................................... 117111

12.4.1 Outage Status Update ................................................................................................................... 117111 12.5 WSDL..................................................................................................................................................... 117111

12.5.1 OutageStatusUpdate_v1.wsdl ....................................................................................................... 117111 12.6 OUTAGE STATUS UPDATE ....................................................................................................................... 117111

12.6.1 Schema (OutageStatusUpdate_v1.xsd) ......................................................................................... 118112 12.6.2 Example XML File (OutageStatusUpdate_v1.xml) for a Generation Outage............................... 118112 12.6.3 Example XML File (OutageStatusUpdate_v1.xml) for a Transmission Outage ........................... 119113

12.7 STANDARD OUTPUT ................................................................................................................................ 120114 12.7.1 Element Table ............................................................................................................................... 120114 12.7.2 Schema (StandardOutput_v1.xsd) ................................................................................................. 120114 12.7.3 Example XML File ........................................................................................................................ 120114

12.8 FAULT RETURN ....................................................................................................................................... 120114

13. APPENDIX ..................................................................................................................................................... 121115

13.1 COMMUNICATION EQUIPMENT ................................................................................................................ 121115 13.2 WEBOMS ERROR CODES ........................................................................................................................ 122116

13.2.1 Transmission Error Codes ............................................................................................................ 122116 13.2.2 Generation Error Codes ............................................................................................................... 125119 13.2.3 Warning Codes ............................................................................................................................. 134128

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


1. Introduction

1.1 Purpose

This document describes the Market Participant interface to CAISO’s Outage Management System (OMS) web services. It provides the WSDL, XSD, and XML information required by application programmers to create and send messages and to process response messages.

1.2 Contact Information

For any questions regarding this document or technical questions related to integrating applications with

CAISO’s Outage Management System web services, please send email to [email protected]

1.3 Related Documents

CAISO’s ISO MARKET program has produced a set of documents describing its web services architecture and associated interfaces to the Bidding, Market Results, Trades, Outage Management and Sandbox services. CASIO’s ISO MARKET Web Services Architecture & Integration Specification is the top-level

document in this set; Market Participants and their application programmers should read this document to gain an overall understanding of CASIO’s web services architecture prior to reading any of the detailed documents shown below.

Figure 1 – ISO MARKET Web Services Interface Specification Document Set

The ISO MARKET Web Services Interface Specification Document Set is available online at the locations

indicated below.

B2B Security Specification (CAISO ISS)

CAISO’s Web Services Architecture & Integration Specification

Client Public/Private Key Instructions (CAISO ISS)

Interface Specification for Bidding Services

Interface Specification for Inter-SC Trade Services

Interface Specification for Market Result Services

Interface Specification for Outage Management Services

Sandbox Services & Test Client Guide

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Doc. No. Document Name Location

1

ISO MARKET B2B Security

Specification

https://portal.caiso.com

(you must have access to the Market Participant

Portal)

2 Client Public/Private Key

Instructions

ClientPublic_PrivateKeyGuidelines.pdf

3

ISO MARKET Interface

Specification for Bidding Services

http://www.caiso.com/participate/Pages/ApplicationAccess/Default.aspx

4


Specification for Inter-SC Trade

Services


5


Specification for Market Results

Services


6

ISO Interface Specification for

Outage Management Services

http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx

7 ISO Acceptable Use Guidelines http://www.caiso.com/Documents/ISO_Servi

cesAcceptableUseGuidelinesApr9_2013.pdf

1.4 Release Notes

This document release 1.0 will be the first release for the new ISO Outage Management System (OMS), to be released in the Fall of 2014 with the Energy Imbalance Market (EIM). All SLIC web services will be replaced by the services in this document.

1.5 API Transition Support

Due to the extensive changes in required fields and implementing technology the ISO will not support the existing services after go-live. All clients will need to transition to the new services.

1.6 MTOM & Doc style Attachments

All services support both MTOM/XOP style attachments and document literal with an attachment (doc-attach). Doc style attachments are supported by WSDLs that have suffix _DocAttach in their name, this Doc style attachment is mainly intended for .Net clients. Example:

1. submitResourceOutage_v1.wsdl supports MTOM style attachments 2. submitResourceOutage_v1_DocAttach.wsdl supports Doc style attachments.

https://portal.caiso.com/

http://www.caiso.com/Documents/ClientPublic_PrivateKeyGuidelines.pdf









http://www.caiso.com/Documents/ISO_ServicesAcceptableUseGuidelinesApr9_2013.pdf

http://www.caiso.com/Documents/ISO_ServicesAcceptableUseGuidelinesApr9_2013.pdf

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Attachments will still be zipped and Base64 encoded. The previous style of rpc literal will not be supported.

1.7 Date Time Data Type Elements

The dateTime data type is used to specify a date and a time. The dateTime is specified in the following form: "YYYY-MM-DDThh:mm:ss"

where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second Note: All components are required.

To specify a time zone, you must enter a dateTime in Universal Time Coordinate (UTC) time by adding a "Z" behind the time, for example: <startdate>2002-05-30T07:00:00Z</startdate>

2. SOAP Header Elements & MTOM Attachments

This section specifies how the identity of the message producer and the message signature is specified in the SOAP message header section.

2.1 Identity of Message Producer

Identify of the message producer is specified in CAISO custom element <CAISOUsernameToken > encapsulated in <CAISOWSHeader>. The following fragment illustrates the use of this element

<ns1:CAISOWSHeader

xmlns:ns1="http://www.caiso.com/soa/2006-09-30/CAISOWSHeader.xsd">

<ns1:CAISOUsernameToken>

<ns1:Username>LNP Tester40</ns1:Username>

<Nonce>3433lfff23</Nonce>

<Created>2014-04-22T16:30:45.0 PDT</Created>

</ns1:CAISOUsernameToken>

</ns1:CAISOWSHeader>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


2.1.1 Identity

Identity of the message producer is specified by the <Username> element, which allows any string that does not contain line feeds, carriage returns, tabs, leading or trailing spaces, or multiple spaces.

2.1.2 Timestamp

The Security Timestamp is encapsulated via the <created> element in the <CAISOUsernameToken> and indicates when the token was created .

2.1.3 Message Freshness

This specification uses a Nonce as a measure to thwart replay attacks. The Nonce is a unique, randomly generated number. The nonce is encapsulated via the <wsse:nonce> element in the <cwsh:CAISOUsernameToken>

2.2 MTOM Attachments

All large messages are sent in MTOM style attachments or as document literal with an attachment (doc-attach). The previous style of rpc literal will not be supported. Attachments will still be zipped and Base64 encoded=. The attachment hash value is is encapsulated in <attchmentHash> element that goes in to SOAP header section as illustrated below: The content-id(cid) of the MTOM attachment is referred in attachmentData1 element encapsulated by AttachmentInfor. This section goes in SOAP Body as shown below: Here is a complete example of SOAP message.

<ns1:attachmentHash xmlns:ns1="http://www.caiso.com/mrtu/soa/schemas/2005/09/attachmenthash">

<hashValue>ErPtrFX6a288DMBy+jG61jpbfAY=</hashValue>

</ns1:attachmentHash>

<att:AttachmentInfor>

<att:attachmentData1>cid:255629815578</att:attachmentData1>

</att:AttachmentInfor>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:stan="http://www.caiso.com/soa/2006-06-13/StandardAttachmentInfor.xsd" xmlns:att="http://www.caiso.com/soa/AttachmentInfor_v1.xsd"> <soapenv:Header> <ns1:CAISOWSHeader xmlns:ns1="http://www.caiso.com/soa/2006-09-30/CAISOWSHeader.xsd"> <ns1:CAISOUsernameToken> <ns1:Username>LNP Tester40</ns1:Username> <Nonce>3433lfff23</Nonce> <Created>2014-04-22T16:30:45.0 PDT</Created> </ns1:CAISOUsernameToken> </ns1:CAISOWSHeader> <ns1:attachmentHash xmlns:ns1="http://www.caiso.com/mrtu/soa/schemas/2005/09/attachmenthash"> <hashValue>ErPtrFX6a288DMBy+jG61jpbfAY=</hashValue> </ns1:attachmentHash>  <stan:standardAttachmentInfor> <stan:Attachment> <stan:id>?</stan:id> <stan:name>?</stan:name> <stan:description>?</stan:description> <stan:version>?</stan:version> <stan:sequenceNumber>?</stan:sequenceNumber> <stan:type>?</stan:type> <stan:size>?</stan:size> <stan:source>?</stan:source> <stan:tool>?</stan:tool> <stan:creationTime>?</stan:creationTime> <stan:compressFlag>?</stan:compressFlag> <stan:compressMethod>?</stan:compressMethod> <stan:AttributeList> <stan:Value>?</stan:Value> </stan:AttributeList> </stan:Attachment> </stan:standardAttachmentInfor> </soapenv:Header> <soapenv:Body> <att:AttachmentInfor>

<att:attachmentData1><inc:Include href="cid:255629815578" xmlns:inc="http://www.w3.org/2004/08/xop/include"/>

</att:attachmentData1> </att:AttachmentInfor> </soapenv:Body> </soapenv:Envelope>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


In above example content-id cid:255629815578 refers to actual attachment data in binary format that follows above SOAP message.

3. Standard XSDs

3.1 Standard Attachment Information

The attachment information schema, StandardAttachmentInfor.xsd, is used to provide general information for a SOAP attachment. The root element in the schema is standardAttachmentInfor, which can contain one or more attachment elements.

1.1.1 Element table

Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: <255629815578> Content-Disposition: attachment; name="2e132f20-6499-4714-808b-55b9f7a08fbf.uue" H4sIAAAAAAAAAL1W30/jOBB+7v4VVe+5dcICCyhkhQq3VwnaqgmLeFqZZNr6SOyc7bTw3+84P9o

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Element Data Description Type Req’d

id Globally unique identifier. string No

name Attachment filename. string No

description Description of attachment. string No

version Version ID of attachment file string No

sequenceNumber Sequence number if there are multiple attachments.

string No

type Attachments file type, zip string No

size Size of attachment file. string No

source Source of attachment file. string No

tool Tool used to generate attachment. string No

creationTime Time attachment file was created. dateTime No

compressFlag Indicates whether or not attachment has been compressed (YES or NO).

string No

compressMethod Compress method used (if attachment file compressed).

string No

AttributeList.Sequence Attribute list sequence number. string No

AttributeList.Name Name of an attribute string No

AttributeList.Value Value of an attribute string No

3.1.1 Schema (StandardAttachmentInfor.xsd)

Each service bundle will contain the same StandardAttachmentInfor.xsd

1.1.2 Example XML File (StandardAttachmentInfor.xml)

<?xml version="1.0" encoding="UTF-8" ?>



<standardAttachmentInfor xmlns="http://www.caiso.com/soa/2006-06-

13/StandardAttachmentInfor.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-

instance" xsi:schemaLocation="http://www.caiso.com/soa/2006-06-

13/StandardAttachmentInfor.xsd">

<Attachment>

<id>123456789</id>

<name>Out1</name>

<description>OUTAGE_ATTACHEMENT</description>

<version>1.1</version>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<sequenceNumber>12</sequenceNumber>

<type>ZIP</type>

<size>180</size>

<source>GWED</source>

<tool>GZIP</tool>

<creationTime>2006-06-17T09:30:47.0Z</creationTime>

<compressFlag>yes</compressFlag>

<compressMethod>ZIP</compressMethod>

<AttributeList>

<Sequence>2</Sequence>

<Name>GWED</Name>

<Value>1</Value>

</AttributeList>

</Attachment>

</standardAttachmentInfor>

3.2 Fault Return

Any error in consuming the service will result in the fault return of the standardOutput. This section is applicable to all services.

3.2.1 Element Table

Element Data Description Type/ Length

Format/ Length

Req’d

OutputDataType.EventLog

id Event log identifier. string No

name Event log name. string No

description Event log description. string No

type Event log type. string No

creationTime Event log creation time. date No

collectionType Event log collection type. string No

collectionQuantity Event log collection quantity. string No

Event.result Event result. string No

Event.id Event identifier. string No

Event.name Event name. string No

Event.description Event description. string No

Event.creationTime Event creation time. dateTime No

Event.severity Event severity. string No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Event.priority Event priority. string No

Event.sequence Number Event sequence number. string No

Event.eventType Event type. string No

Service.id Service identifier. string No

Service.name Service name. string No

Service.description Service description. string No

Service.comments Service comments. string No

3.2.2 Schema (StandardOutput.xsd)

Each service bundle will have the same StandardOutput.xsd file.

3.2.3 Example XML File (StandardOutput.xml)

<?xml version="1.0" encoding="UTF-8"?>  <m:outputDataType xsi:schemaLocation="http://www.caiso.com/soa/2006-06-13/StandardOutput.xsd StandardOutput.xsd" xmlns:m="http://www.caiso.com/soa/2006-06-13/StandardOutput.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <m:EventLog> <m:id>Event-123</m:id> <m:name>Event Name</m:name> <m:description>The Event Description</m:description> <m:type>Error Event</m:type> <m:creationTime>2014-01-03T11:00:00Z</m:creationTime> <m:collectionType>Submit Generator Outage</m:collectionType> <m:collectionQuantity>1</m:collectionQuantity> <m:Event> <m:result>Invalid Value Found in Field XX</m:result> <m:id>1234</m:id> <m:name>Error Event 1234</m:name> <m:description>An invalid data value was presented</m:description> <m:creationTime>2014-01-03T11:00:00Z</m:creationTime> <m:severity>High</m:severity> <m:priority>High</m:priority> <m:sequenceNumber>1</m:sequenceNumber> <m:eventType>Initiated by OMS API</m:eventType> </m:Event> <m:Service> <m:id>1234567</m:id> <m:name>Submit Intertie Update</m:name> <m:description>Having problems - Invalid data has been presented</m:description> <m:comments>Some one needs to fix the data and resubmit</m:comments>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


</m:Service> </m:EventLog>

</m:outputDataType>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


4. Submit Resource Outage {Change Requests} Business Scenario

4.1 Overview

Outage coordinators can submit outages or changes to previously submitted outages (Outage Change Requests) for affiliated generators.

4.2 Service Level Agreement

Service availability Service level goal is 99.9%.

Expected size of payload (average and maximum)

Variable (1KB to 1MB+)

Expected frequency (average and maximum)

On demand (50/day – 200/day).

Longest time the service can be unavailable before business is impacted

30 minutes

Business impact if is unavailable Outage Coordinators can call the ISO directly with critical near-term outages.

Expected response time for the service Variable (.1 sec – 30 sec)

Expected time to exchange Variable (.1 sec – 30 sec)

4.3 Use Model

The sequence diagram below describes the service level interactions between the Outage Coordinator systems and the OMS. Channel level security and authentication are abstracted from this diagram (They will be covered in another document; B2B Security Specifications).

4.3.1 Submit New Outage

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


4.3.2 Submit Change to Existing Outage

4.4 Operational Details

4.4.1 Submit Resource Outage

The service has one operation with three message types.

Operation Message

Types

Message WSDL XSD

submitResourceOu

tage

Input submitResourceOu

tage

submitResourceOutage_v1.ws

dl/

submitResourceOutage_v1_D

ocAttach.wsdl/

submitResourceOutage_v1.xsd

Output submitResourceOu

tageResponse

OutageStandardOutput_v1.xsd

Fault faultReturnType StandardOutput.xsd

4.4.2 Submit Resource Outage Change Request

Operation Message

Types

Message WSDL XSD

sd Submit Outage

Outage Coordinator

OMS

SubmitGenerationOutage()

SubmitGenerationOutageResponse()

sd Submit Outage Change Request

Outage Coordinator

OMS

submitOutageChangeRequest()

submitGenerationOutageChangeRequestResponse()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


submitResourceO

utageChangeRequ

est

Input submitResourceO

utageChangeRequ

est

submitResourceOutageChang

eRequest_v1.wsdl/

submitResourceOutageChang

eRequest_v1_DocAttach.wsd

l

submitResourceOutageChange

Request_v1.xsd

Output submitResourceO

utageChangeRequ

estResponse



4.5 WSDL

4.5.1 submitResourceOutage_v1.wsdl / submitResourceOutage_v1_DocAttach.wsdl

4.5.2 submitResourceOutageChangeRequest_v1.wsdl / submitResourceOutageChangeRequest_v1_DocAttach.wsdl

4.6 Submit Resource Outage {Change Request}

4.6.1 Element Table


Format/ Length

Req’d

Message Header

TimeDate The dateTime, in UTC, when the payload is published

dateTime Yes

Source The source of the data String Yes

Version Subversion of the XSD:

Initial version will be v20141001

String Yes

MessagePayload.RegsiteredResourceOutage Yes

mRID ID for the Outage, Not required for new outage, required when submitting a change request.

String No

Description Participant’s description of the Outage/Change Request

String Yes

Comment Participant’s comment for the Outage/Change Request

String No

affectsRASSPS Participant indicates if this outage affects a RAS or SPS. Yes/No

String No

discoveryDateTime DateTime when the outage was discovered. dateTime No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

emergencyReturnTime Time to restore the outage if needed by the ISO. Integer No

emergencyReturnTimeType

Type of emergency return time. DAYS, HOURS, MINUTES

String Yes

mktOrgOutageID Reference ID assigned to the outage by the participant.

String Yes

outageCoordinationLongTermPlanning

This indicates the outage is part of your quarterly outage plan and allows the outage request to remain scheduled until it is evaluated approximately one month before its start date. See CAISO Operating Procedure T-113 for more information on quarterly outage plans. Yes/No

String No

RIMSProjectCommisionDate

Commission date of the the related RIMS project dateTime No

RIMSProjectCompletion Completion date of the related RIMS project dateTime No

RIMSProjectID RIMS id of the related RIMS project String No

RIMSProjectPhase RIMS phase that this outage will complete String No

Actual Period Actual start and end times of the outage, in UTC dateTime No

Estimated Period Planned start and end time of the outage, in UTC. dateTime Yes

OutageCause.code Participant list of cause code for their reference String No

isOffPeakOpportunityOutage

Participant indicates if the submission if for an off peak opportunity outage. Yes/No

String Yes

isShortNoticeOpportunityOutage

Participant indicates if the submission if for a short notice opportunity outage. Yes/No

String Yes

Work Kind of work codes. String Yes

MessagePayload.RegsiteredResourceOutage.MktOrganisation Yes

mRID Participant short name String Yes

MessagePayload.RegsiteredResourceOutage.MktOrganisation.MarketPerson No

firstName First name of the contact at the participant. String Yes

lastName Last name of the contact at the participant. String Yes

landlinePhone Phone number of the contact at the participant. Complex Yes

MessagePayload.RegsiteredResourceOutage.OutageChangeRequest No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

action Type of change request. If present indicates that his is a change request to an existing outage. UPDATE or CANCEL

String Yes

actionReason Reason for change String No

actionSubType Type of action subtype String No

MessagePayload.RegsiteredResourceOutage.RegisteredGenerator(Choice1)

mRID The resource id for the RegisteredGenerator. mrid minLen=1

maxLen=32

No

name An alternate name from the Participant name minLen=1

maxLen=40

No

RegisteredGenerator.LogicalConfiguration No

RegisteredGenerator.LogicalConfiguration.Configuration Yes

mRID The resource id for an MSG RegisteredGenerator’s Configuration.

mrid minLen=1

maxLen=32

No

name An alternate name from the Participant. name minLen=1

maxLen=40

No

RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource Yes

RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.Availability

No

dateTimePoint The time of this availability point in UTC. dateTime Yes

outOfService Unit has avail 0 starting at this time Yes/No No

returnToNetDependableCapacity

Indicates no derate at this time Float No

Pmaxvalue Indicates Pmax value of Unit Float No

RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.PMinimum

Yes

activePeriod.start Start date and time during which this restriction is applied

dateTime Yes

restrictedValue The new pmin value for this interval. Float Yes

RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.RampRateSegment

Yes

restrictedValue The new Ramp Rate for this segment Float Yes

segmentNumber The number of this segment Integer Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

segmentValue The MW value that identifies the right hand side of the segment.

Float Yes

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource Yes

timeToStartUp The time the resource needs to start after the outage has completed.

Float No

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.ASAvailability No

availableValue The new MW value for this interval. Float Yes

MarketProduct.marketProductType

Type of AS that is restricted. Enumeration

Yes

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.Availability No


outOfService Unit has avail 0 starting at this time. Yes/No No

returnToNetdependablecapacity

Indicates no derate starting at this time. Yes/No No

PmaxValue.vlaue Indicates Pmax value Float Yes

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.Availability.OutagedRegister

edResource.RegisteredResource.RegisteredResourceOutage No

RegisteredResource.RegisteredResourceOutage Yes


String Yes

RegisteredGenerator.OutagedRegisteredResource.LoadMaximum(Choice1)

activePeriod.start Start date and time of this interval dateTime Yes

restrictedValue The new MW value for this point. Float Yes




RegisteredGenerator.OutagedRegisteredResource.LoadMinimum(Choice2)


restrictedValue The new MW value for this interval. Float Yes

RegisteredGenerator.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d


restrictedValue The new maximum energy limit (WH) for this interval.

Float Yes

RegisteredGenerator.OutagedRegisteredResource.MinimumEnergyLimit (Choice4)


restrictedValue The new minimum energy limit (WH) for this interval.

Float Yes

RegisteredGenerator.OutagedRegisteredResource.PMinimum(Choice5)

activePeriod.start The time of this pmin rerate point in UTC dateTime Yes

restrictedValue The new minimum output of this resource/configuration for this interval

Float Yes

RegisteredGenerator.OutagedRegisteredResource.UseLimit(Choice6)


restrictedValue The new use Limit for the resource in this interval. Float Yes

RegisteredGenerator.OutagedRegisteredResource.RampRateSegment (Choice7)

restrictedValue The new ramp rate (MW/min) for this segment in this interval.

Float Yes

segmentNumber The identifier for this segment Integer Yes

segmentValue The right hand side (MW) of this segment. Float Yes

MessagePayload.RegisteredResourceOutage.RegisteredIntertie(Choice2)

mRID The resource id for the RegisteredIntertie. mrid minLen=1

maxLen=32

Yes

name An alternate name from the Participant name minLen=1

maxLen=40

Yes

RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource Yes


Float No

RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.ASAvailability No


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d



Yes

RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.Availability No






RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.Availability.OutagedRegistered

Resource.RegisteredResource.RegisteredResourceOutage No



String Yes

RegisteredIntertie.OutagedRegisteredResource.LoadMaximum(Choice1)






RegisteredIntertie.OutagedRegisteredResource.LoadMinimum(Choice2)



RegisteredIntertie.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)



Float Yes

RegisteredIntertie.OutagedRegisteredResource.MinimumEnergyLimit (Choice4)



Float Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

RegisteredIntertie.OutagedRegisteredResource.PMinimum(Choice5)



Float Yes

RegisteredIntertie.OutagedRegisteredResource.UseLimit(Choice6)



RegisteredIntertie.OutagedRegisteredResource.RampRateSegment (Choice7)


Float Yes



For detailed list of elements under OutageRegisterdResource click on link here.

MessagePayload.RegisteredResourceOutage.RegisteredLoad(Choice3)

mRID The resource id for the RegisteredLoad. mrid minLen=1

maxLen=32

Yes

Name An alternate name from the Participant name minLen=1

maxLen=40

Yes

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource Yes


Float No

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.ASAvailability No




Yes

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.Availability No





cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d


RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.Availability.OutagedRegisteredRe

source.RegisteredResource.RegisteredResourceOutage No



String Yes

RegisteredLoad.OutagedRegisteredResource.LoadMaximum(Choice1)






RegisteredLoad.OutagedRegisteredResource.LoadMinimum(Choice2)



RegisteredLoad.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)



Float Yes

RegisteredLoad.OutagedRegisteredResource.MinimumEnergyLimit (Choice4)



Float Yes

RegisteredLoad.OutagedRegisteredResource.PMinimum(Choice5)



Float Yes

RegisteredLoad.OutagedRegisteredResource.UseLimit(Choice6)


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d


RegisteredLoad.OutagedRegisteredResource.RampRateSegment (Choice7)


Float Yes



4.6.2 Schema (ResourceOutageData_v1.xsd)

4.6.3 Example XML File (SubmitResourceOutageData_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <m:ResourceOutageData xmlns:m="http://www.caiso.com/soa/ResourceOutageData_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/ResourceOutageData_v1.xsd# ResourceOutageData_v1.xsd "> <m:MessageHeader> <m:TimeDate>2001-12-31T12:00:00</m:TimeDate> <m:Source>CompanyA</m:Source> <m:Version>v20141001</m:Version> </m:MessageHeader> <m:MessagePayload> <m:RegisteredResourceOutage> <m:description>New Generator (MSG) Outage</m:description> <m:comment>Example</m:comment> <m:affectsRASSPS>YES</m:affectsRASSPS> <m:discoveryDateTime>2014-01-17T17:00:00Z</m:discoveryDateTime> <m:emergencyReturnTime>1</m:emergencyReturnTime> <m:emergencyReturnTimeType>HOURS</m:emergencyReturnTimeType> <m:mktOrgOutageID>9690</m:mktOrgOutageID> <m:outageCoordinationLongTermPlanning>NO</m:outageCoordinationLongTermPlanning> <m:estimatedPeriod> <m:end>2014-01-17T17:00:00Z</m:end> <m:start>2014-01-17T13:00:00Z</m:start> </m:estimatedPeriod> <m:MktOrganisation> <m:mRID>SCID1</m:mRID> <m:MarketPerson> <m:firstName>John</m:firstName>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:lastName>Smith</m:lastName> <m:landlinePhone> <m:areaCode>916</m:areaCode> <m:extension>555</m:extension> <m:localNumber>1234</m:localNumber> </m:landlinePhone> </m:MarketPerson> </m:MktOrganisation> <m:OutageCause> <m:code>9690</m:code> </m:OutageCause> <m:Work> <m:kind>PLANT_MAINTENANCE</m:kind> </m:Work> <m:isOffPeakOpportunityOutage>NO</m:isOffPeakOpportunityOutage> <m:isShortNoticeOpportunityOutage>NO</m:isShortNoticeOpportunityOutage> <m:RegisteredGenerator> <m:mRID>ResourceA</m:mRID> <m:name>Resource Alpha</m:name> <m:LogicalConfiguration> <m:Configuration> <m:mRID>ResA1x1</m:mRID> <m:name>Resource Alpha 1x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>80</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>100</m:value> </m:PmaxValue> </m:Availability> </m:OutagedRegisteredResource> </m:Configuration> <m:Configuration> <m:mRID>ResA2x1</m:mRID> <m:name>Resource Alpha 2x1</m:name> <m:OutagedRegisteredResource>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>160</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:PmaxValue> </m:Availability> <m:PMinimum> <m:activePeriod> <m:start>2014-01-17T13:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>81</m:value> </m:restrictedValue> </m:PMinimum> <m:PMinimum> <m:activePeriod> <m:start>2014-01-17T17:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:restrictedValue> </m:PMinimum> </m:OutagedRegisteredResource> </m:Configuration> </m:LogicalConfiguration> <m:OutagedRegisteredResource> <m:ASAvailability> <m:availableValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>0</m:value> </m:availableValue> <m:MarketProduct> <m:marketProductType>SR</m:marketProductType>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


</m:MarketProduct> </m:ASAvailability> </m:OutagedRegisteredResource> </m:RegisteredGenerator> </m:RegisteredResourceOutage> </m:MessagePayload> </m:ResourceOutageData>

4.6.4 Example XML File (SubmitResourceOutageChangeRequest_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <m:ResourceOutageData xmlns:m="http://www.caiso.com/soa/ResourceOutageData_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/ResourceOutageData_v1.xsd# ResourceOutageData_v1.xsd "> <m:MessageHeader> <m:TimeDate>2014-01-04T09:00:00Z</m:TimeDate> <m:Source>CompanyA</m:Source> <m:Version>v20141001</m:Version> </m:MessageHeader> <m:MessagePayload> <m:RegisteredResourceOutage> <m:mRID>123456789</m:mRID> <m:description>New generator (MSG) Outage</m:description> <m:comment>Example</m:comment> <m:affectsRASSPS>YES</m:affectsRASSPS> <m:discoveryDateTime>2014-01-04T09:00:00Z</m:discoveryDateTime> <m:emergencyReturnTime>1</m:emergencyReturnTime> <m:emergencyReturnTimeType>HOURS</m:emergencyReturnTimeType> <m:mktOrgOutageID>9690</m:mktOrgOutageID> <m:outageCoordinationLongTermPlanning>NO</m:outageCoordinationLongTermPlanning> <m:estimatedPeriod> <m:end>2014-01-17T18:00:00Z</m:end> <m:start>2014-01-17T13:00:00Z</m:start> </m:estimatedPeriod> <m:MktOrganisation> <m:mRID>SCID1</m:mRID> <m:MarketPerson> <m:firstName>John</m:firstName> <m:lastName>Smith</m:lastName> <m:landlinePhone> <m:areaCode>916</m:areaCode> <m:extension>555</m:extension>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:localNumber>1234</m:localNumber> </m:landlinePhone> </m:MarketPerson> </m:MktOrganisation> <m:OutageCause> <m:code>9690</m:code> </m:OutageCause> <m:OutageChangeRequest> <m:action>UPDATE</m:action> <m:actionReason>WORK_RESCHEDULED_TO_LATER_DATE_SC</m:actionReason> </m:OutageChangeRequest> <m:Work> <m:kind>PLANT_MAINTENANCE</m:kind> </m:Work> <m:isOffPeakOpportunityOutage>NO</m:isOffPeakOpportunityOutage> <m:isShortNoticeOpportunityOutage>NO</m:isShortNoticeOpportunityOutage> <m:RegisteredGenerator> <m:mRID>ResourceA</m:mRID> <m:name>Resource Alpha</m:name> <m:LogicalConfiguration> <m:Configuration> <m:mRID>ResA1x1</m:mRID> <m:name>Resource Alpha 1x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:OutagedRegisteredResource> <m:RegisteredResource> <m:RegisteredResourceOutage> <m:mRID>Outage1234</m:mRID> </m:RegisteredResourceOutage> </m:RegisteredResource> </m:OutagedRegisteredResource> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>100</m:value> </m:PmaxValue> </m:Availability> </m:OutagedRegisteredResource> </m:Configuration> </m:LogicalConfiguration> <m:OutagedRegisteredResource> <m:timeToStartUp>COLD</m:timeToStartUp> <m:ASAvailability> <m:availableValue>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>0</m:value> </m:availableValue> <m:MarketProduct> <m:marketProductType>SR</m:marketProductType> </m:MarketProduct> </m:ASAvailability> </m:OutagedRegisteredResource> </m:RegisteredGenerator> </m:RegisteredResourceOutage> </m:MessagePayload> </m:ResourceOutageData>

4.7 Submit Resource Outage {Change Request} Response

4.7.1 Element Table


Format/ Length

Req’d

Message Header No


dateTime Yes




String Yes

MessagePayload.EventLog Yes

MessagePayload.EventLog.Event Yes

result Event result. string Yes

id Event identifier. string Yes

description Event description. string No

creationDateTime Event creation time. dateTime No

MessagePayload.EventLog.Service Yes

id Service identifier. string Yes

name Name of a service. string Yes

MessagePayload.EventLog.Outage No

mrid ID assigned to the outage by the ISO String No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

mktOrgOutageID Reference ID assigned to the outage by the external User

String Yes

MessagePayload.EventLog.Outage.OutageChangeRequest No

mrid ID assigned to the outage change request by the ISO

String Yes

MessagePayload.EventLog.Outage.OutageGroup No

mRID ID assigned to the outage Group by the ISO String Yes

MessagePayload.EventLog.Outage.OutageValidation Yes

submitStatus Indicates whether the outage was accepted or rejected: ACCEPTED, REJECTED

String Yes

MessagePayload.EventLog.Outage.OutageValidation.OutageResult Yes

mrID ID assigned to the result by the ISO String Yes

type Type of result: ERROR, INFO, WARNING String Yes

description Description of result returned String Yes

status Status of the result: ACKNOWLEDGED. UNACKNOWLEDGED. This is applicable only to warnings.

String No

4.7.2 Schema (OutageStandardOutput_v1.xsd)

4.7.3 Example XML File (ResourceOutageStandardOutput.xml)

4.7.3.1 Example XML File for Submit Resource Outage Response

<?xml version="1.0" encoding="UTF-8"?> <OutageStandardOutput xmlns="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd# OutageStandardOutput_v1.xsd "> <MessageHeader> <TimeDate>2014-01-03T11:00:00Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <EventLog> <Event>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<id>1</id> <result>Success</result> </Event> <Outage> <mRID>123456789</mRID> <mktOrgOutageID>MarketOutageId-1234</mktOrgOutageID> <OutageValidation> <submitStatus>ACCEPTED</submitStatus> <OutageResult> <mRID>1</mRID> <description>Validated</description> <status>ACKNOWLEDGED</status> <type>INFO</type> </OutageResult> </OutageValidation> </Outage> <Service> <id>12345</id> <name>submitResourceOutage_v1</name> </Service> </EventLog> </MessagePayload> </OutageStandardOutput>

4.7.3.2 Example XML File for Submit Resource Outage Change Request Response

<?xml version="1.0" encoding="UTF-8"?> <m:ResourceOutageData xmlns:m="http://www.caiso.com/soa/ResourceOutageData_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/ResourceOutageData_v1.xsd# ResourceOutageData_v1.xsd "> <m:MessageHeader> <m:TimeDate>2014-01-04T09:00:00Z</m:TimeDate> <m:Source>CompanyA</m:Source> <m:Version>v20141001</m:Version> </m:MessageHeader> <m:MessagePayload> <m:RegisteredResourceOutage> <m:mRID>123456789</m:mRID> <m:description>New generator (MSG) Outage</m:description> <m:comment>Example</m:comment> <m:affectsRASSPS>YES</m:affectsRASSPS> <m:discoveryDateTime>2014-01-04T09:00:00Z</m:discoveryDateTime>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:emergencyReturnTime>1</m:emergencyReturnTime> <m:emergencyReturnTimeType>HOURS</m:emergencyReturnTimeType> <m:mktOrgOutageID>9690</m:mktOrgOutageID> <m:outageCoordinationLongTermPlanning>NO</m:outageCoordinationLongTermPlanning> <m:estimatedPeriod> <m:end>2014-01-17T18:00:00Z</m:end> <m:start>2014-01-17T13:00:00Z</m:start> </m:estimatedPeriod> <m:MktOrganisation> <m:mRID>SCID1</m:mRID> <m:MarketPerson> <m:firstName>John</m:firstName> <m:lastName>Smith</m:lastName> <m:landlinePhone> <m:areaCode>916</m:areaCode> <m:extension>555</m:extension> <m:localNumber>1234</m:localNumber> </m:landlinePhone> </m:MarketPerson> </m:MktOrganisation> <m:OutageCause> <m:code>9690</m:code> </m:OutageCause> <m:OutageChangeRequest> <m:action>UPDATE</m:action> <m:actionReason>WORK_RESCHEDULED_TO_LATER_DATE_SC</m:actionReason> </m:OutageChangeRequest> <m:Work> <m:kind>PLANT_MAINTENANCE</m:kind> </m:Work> <m:isOffPeakOpportunityOutage>NO</m:isOffPeakOpportunityOutage> <m:isShortNoticeOpportunityOutage>NO</m:isShortNoticeOpportunityOutage> <m:transmissionInduced>YES</m:transmissionInduced> <m:RegisteredGenerator> <m:mRID>ResourceA</m:mRID> <m:name>Resource Alpha</m:name> <m:LogicalConfiguration> <m:Configuration> <m:mRID>ResA1x1</m:mRID> <m:name>Resource Alpha 1x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:OutagedRegisteredResource> <m:RegisteredResource> <m:RegisteredResourceOutage> <m:mRID>Outage1234</m:mRID> </m:RegisteredResourceOutage> </m:RegisteredResource> </m:OutagedRegisteredResource> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>100</m:value> </m:PmaxValue> </m:Availability> </m:OutagedRegisteredResource> </m:Configuration> </m:LogicalConfiguration> <m:OutagedRegisteredResource> <m:timeToStartUp>COLD</m:timeToStartUp> <m:ASAvailability> <m:availableValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>0</m:value> </m:availableValue> <m:MarketProduct> <m:marketProductType>SR</m:marketProductType> </m:MarketProduct> </m:ASAvailability> </m:OutagedRegisteredResource> </m:RegisteredGenerator> </m:RegisteredResourceOutage> </m:MessagePayload> </m:ResourceOutageData>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


5. Retrieve Outage/Change Requests Business Scenario

5.1 Overview

Outage Coordinators can retrieve resource outages or outage change requests for affiliated generators.








30 minutes

Business impact if is unavailable Outage Coordinators can call the ISO for status on near-term outages and Change Requests.


Expected time to exchange Variable

5.3 Use Model


5.3.1 Retrieve Generation Outages

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


5.3.2 Retrieve Resource Outage Change Requests


Each service has one operation with three message types.

5.4.1 Retrieve Resource Outage

Operation Message

Types

Message WSDL XSD

retrieveResource

Outage

Input retrieveResource

Outage

retrieveResourceOutage_v1.

wsdl/

retrieveResourceOutage_v1_

DocAttach.wsdl

requestResourceOutage_v1.x

sd

Output retrieveResource

OutageResponse

ResourceOutageResults_v1.x

sd


5.4.2 Retrieve Resource Outage Change Request

Operation Message

Types

Message WSDL XSD

sd retriev eGenerationOutage

Outage Coordinator

OMS

retrieveGenerationOutage()

retrieveGenerationOutageResponse()

sd retriev eGenerationOutageChangeRequests

Outage Coordinator

OMS

retrieveGenerationOutageChangeRequests()

retrieveGenerationOutageResponseChangeRequests()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


retrieveResource

OutageChangeRe

quests

Input retrieveResourceO

utageChangeReque

sts

retrieveResourceOutageChan

geRequest_v1.wsdl/

retrieveResourceOutageChan

geRequest_v1_DocAttach.ws

dl

requestResourceOutage_v1.x

sd

Output retrieveResourceO

utageChangeReque

stResponse

ResourceOutageResults_v1.x

sd


5.5 WSDL

5.5.1 retrieveResourceOutage_v1.wsdl / retrieveResourceOutage_v1_DocAttach.wsdl

5.5.2 retrieveResourceOutageChangeRequest_v1.wsdl / retrieveResourceOutageChangeRequest_v1_DocAttach.wsdl

5.6 Retrieve Resource Outage {Change Request}

Request Criteria Input Parameters Results Outage WebOMS outage id or

Participant’s outage id The outage specified

Outage Range Range start and end date and Outage Status (optional)

All outages for all resources that the requester has access to for the date range specified optionally filtered by outage status if specified

Participant MktOrganization mrid and Range start and end date and Outage Status(optional)

All outages for all resources associated with the specified MktOrganization mrid that the requester has access to for the date range specified optionally filtered by outage status if specified

Resource RegisteredGenerator mrid and Range start and end date and Outage Status(optional)

All outages for the resource(s) specified and for the date range specified optionally filtered by outage status if specified

Outage Change Request Outage Change Request mrid The outage change request specified

5.6.1 Element Table

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Message Header No

TimeDate The dateTime, in UTC, when the payload is published dateTime Yes




String Yes

MessagePayload.Outage No

mRID The Primary identifier the ISO has given to an outage String No

mktOrgOutageId Reference ID assigned to the Outage by the external user

String No

MessagePayload.OutageChangeRequest No

mRID The Primary identifier the ISO has given to an outage change request

String Yes

MessagePayload.Participant No

rangePeriod Start and end date of the period being requested dateTime No

MessagePayload.Participant.MktOrganization Yes

mrID Participant Short Name of the requestor or affiliate String Yes

MessagePayload.Participant.Outage No

outageStatus Request all outages or change requests in this status String No

MessagePayload.Resource No


MessagePayload.Resource.RegisteredGenerator(Choice1)

mrID The resource id for the RegisteredGenerator. String Yes

MessagePayload.Resource.RegisteredIntertie(Choice2)


MessagePayload.Resource.RegisteredLoad(Choice3)


MessagePayload.Resource.Outage No

Status Request all outages or change requests in this status String No

MessagePayload.OutageRange No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

rangePeriodType Type of range period of outages being requested where:

ACTUAL represents duration of outage (this is the default if no rangePeriodType is specified)

CREATE represents creation date of outage

UPDATE represents last updated date of outage

String No


MessagePayload.OutageRange.Outage No


5.6.2 Schema (RequestResourceOutage_v1.xsd)

5.6.3 Example XML File (RequestResourceOutage_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <RequestResourceOutage xmlns="http://www.caiso.com/soa/RequestResourceOutage_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/RequestResourceOutage_v1.xsd# RequestResourceOutage_v1.xsd "> <MessageHeader> <TimeDate>2014-01-03T11:00:00Z</TimeDate> <Source>CompanyA</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <Resource> <Outage> <outageStatus>APPROVED</outageStatus> </Outage> <rangePeriod> <end>2001-12-31T12:00:00</end> <start>2001-12-31T12:00:00</start> </rangePeriod> <RegisteredGenerator> <mRID>ResourceA</mRID> </RegisteredGenerator> </Resource> </MessagePayload> </RequestResourceOutage>

5.6.4 Example XML file (RequestResourceOutageChangeRequest.xml)

<?xml version="1.0" encoding="UTF-8"?>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<RequestResourceOutage xmlns="http://www.caiso.com/soa/RequestResourceOutage_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/RequestResourceOutage_v1.xsd# RequestResourceOutage_v1.xsd "> <MessageHeader> <TimeDate>2014-01-03T11:00:00Z</TimeDate> <Source>CompanyA</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <Outage> <mRID>123456789</mRID> </Outage> <OutageChangeRequest> <mRID>912345677</mRID> </OutageChangeRequest> </MessagePayload> </RequestResourceOutage>

5.7 Retrieve Resource Outage {Change Request} Response

5.7.1 Element Table


Format/ Length

Req’d

Message Header


dateTime Yes




String Yes

MessagePayload.RegisteredResourceOutage Yes


String Yes


String Yes


String No

createDateTime Time this outage/change request was created dateTime Yes

createdBy The person that created the outage/change request

String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

lastModifiedDateTime Time this outage/change request was last modified

dateTime Yes

lastUpdatedBy The person that last updated the the outage/change request

Yes


String No



emergencyReturnTimeType Type of emergency return time. DAYS, HOURS, MINUTES

String Yes

isFinalApprovalReq The ISO determines if final approval is required before the outage can start

String Yes


String No


This indicates the outage is part of your quarterly outage plan and allows the outage request to remain scheduled until it is evaluated approximately one month before its start date. See CAISO Operating Procedure T-113 for more information on quarterly outage plans. Yes/No

String No

OutageStatus The current status of the outage String Yes

OutageStatusReason The reason for moving the outage to this status String No


Commission date of the the related RIMS project

dateTime No




versionID Version of this Outage String Yes

actualPeriod Actual start and end time of the outage, in UTC. dateTime No

Estimated Period Planned start and end time of the outage, in UTC.

dateTime Yes

OutageCause.code Participant list of cause code for their reference String No

isOffPeakOpportunityOutage

Participant indicates if the submission if for an off peak opportunity outage. Yes/No

String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

isShortNoticeOpportunityOutage

Participant indicates if the submission if for a short notice opportunity outage. Yes/No

String Yes

isSCPExempt Indicates whether or not the outage is exempt from SCP penalties. Yes./No

String Yes

Work Nature of work codes. String(Enumeration)

Yes

RADesignation Identifies this resource as an RA resource during the period of the outage.

String Yes

RAReplacementDecision.id Decision made on whether or not RA Replacement required: Yes/No

String No

isInvalid Indicates whether or not the outage is invalid due to MF major changes. Yes./No

String No

isInconsistent Indicates whether or not the outage is inconsistent due to MF minor changes. Yes./No

String No

MessagePayload.RegisteredResourceOutage.OutageGroup No

MRID The primary identifier of the Group String Yes

Description The description of the group String Yes

createdDateTime Time the group was created dateTime Yes

CreatedBy The person that created the group String Yes

lastModifiedDateTime Time the group was last modified dateTime Yes

LastModifiedBy The person that last updated the group String Yes

MessagePayload.RegisteredResourceOutage.MktOrganisation Yes


MessagePayload.RegisteredResourceOutage.MktOrganisation.MarketPerson No




MessagePayload.RegisteredResourceOutage.OutageChangeRequest No

mrID ID assigned to the outage change request by the ISO

String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Action Type of change request. If present indicates that his is a change request to an existing outage. UPDATE or CANCEL

String Yes

actionReason Reason for changes. String No

Status Status of the outage change request: PENDING, ACCEPTED, DENIED

String Yes

Status Reason Reason for status. Required when the outage change request is denied

String No

MessagePayload.RegisteredResourceOutage.Outage.OutageValidation.OutageResult No


Type Type of result: ERROR, INFO, WARNING String Yes

Description Description of result returned String Yes

Status Status of the result: ACKNOWLEDGED. UNACKNOWLEDGED. This is applicable only to warnings.

String No

MessagePayload.RegisteredResourceOutage.RegisteredGenerator(Choice1)

mRID The resource id for the RegisteredGenerator. mrid minLen=1

maxLen=32

Yes


maxLen=40

Yes

RegisteredResourceOutage.RegisteredGenerator.LogicalConfiguration No

RegisteredResourceOutage.RegisteredGenerator.LogicalConfiguration.Configuration Yes


mrid minLen=1

maxLen=32

No

Name An alternate name from the Participant. name minLen=1

maxLen=40

No

RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource Yes

LogicalConfiguration.Configuration.OutagedRegisteredResource.Availability No


outOfService Unit has avail 0 starting at this time Yes/No No

returnToNetDependableCapacity

Indicates no derate at this time Float No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Pmaxvalue Indicates Pmax value of Unit Float No

LogicalConfiguration.Configuration.OutagedRegisteredResource.PMinimum Yes

activePeriod.start Start date and time during which this restriction is applied

dateTime Yes

restrictedValue The new pmin value for this interval. Float Yes

LogicalConfiguration.Configuration.OutagedRegisteredResource.RampRateSegment Yes

restrictedValue The new Ramp Rate for this segment Float Yes

SegmentNumber The number of this segment Integer Yes

segmentValue The MW value that identifies the right hand side of the segment.

Float Yes

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource Yes


Float No

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.ASAvailability No




Yes

RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.Availability No






RegisteredGenerator.OutagedRegisteredResource.LoadMaximum(Choice1)






RegisteredGenerator.OutagedRegisteredResource.LoadMinimum(Choice2)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d



RegisteredGenerator.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)



Float Yes

RegisteredGenerator.OutagedRegisteredResource.MinimumEergyLimit (Choice4)



Float Yes

RegisteredGenerator.OutagedRegisteredResource.PMinimum(Choice5)



Float Yes

RegisteredGenerator.OutagedRegisteredResource.PMaxCurtailment (Choice6)

activePeriod.start The time of this PMax curtailment point in UTC dateTime Yes

restrictedValue The new PMax curtailment value of this resource/configuration for this interval

Float Yes

RegisteredGenerator.OutagedRegisteredResource.UseLimit(Choice7)



RegisteredGenerator.OutagedRegisteredResource.RampRateSegment (Choice8)


Float Yes



MessagePayload.RegisteredResourceOutage.RegisteredIntertie(Choice2)

mRID The resource id for the RegisteredIntertie. mrid minLen=1

maxLen=32

Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d


maxLen=40

Yes

RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource Yes


Float No

RegisteredResourceOutage. RegisteredIntertie.OutagedRegisteredResource.ASAvailability No




Yes

RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.Availability No






RegisteredIntertie.OutagedRegisteredResource.LoadMaximum(Choice1)






RegisteredIntertie.OutagedRegisteredResource.LoadMinimum(Choice2)



RegisteredIntertie.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)



Float Yes

RegisteredIntertie.OutagedRegisteredResource.MinimumEergyLimit (Choice4)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d



Float Yes

RegisteredIntertie.OutagedRegisteredResource.PMinimum(Choice5)



Float Yes

RegisteredIntertie.OutagedRegisteredResource.PMaxCurtailment (Choice6)



Float Yes

RegisteredIntertie.OutagedRegisteredResource.UseLimit(Choice7)



RegisteredIntertie.OutagedRegisteredResource.RampRateSegment (Choice8)


Float Yes



MessagePayload.RegisteredResourceOutage.RegisteredLoad(Choice3)

mRID The resource id for the RegisteredLoad. mrid minLen=1

maxLen=32

Yes


maxLen=40

Yes

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource Yes


Float No

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.ASAvailability No


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d



Yes

RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.Availability No






RegisteredLoad.OutagedRegisteredResource.LoadMaximum(Choice1)






RegisteredLoad.OutagedRegisteredResource.LoadMinimum(Choice2)



RegisteredLoad.OutagedRegisteredResource.MaximumEnergyLimit (Choice3)



Float Yes

RegisteredLoad.OutagedRegisteredResource.MinimumEergyLimit (Choice4)



Float Yes

RegisteredLoad.OutagedRegisteredResource.PMinimum(Choice5)



Float Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

RegisteredLoad.OutagedRegisteredResource.PMaxCurtailment (Choice6)



Float Yes

RegisteredLoad.OutagedRegisteredResource.UseLimit(Choice7)



RegisteredLoad.OutagedRegisteredResource.RampRateSegment (Choice8)


Float Yes



5.7.2 Schema (ResourceOutageResults_v1.xsd)

5.7.3 Example XML File (ResourceOutageResults_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <m:ResourceOutageResults xmlns:m="http://www.caiso.com/soa/ResourceOutageResults_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/ResourceOutageResults_v1.xsd# ResourceOutageResults_v1.xsd "> <m:MessageHeader> <m:TimeDate>2001-12-31T12:00:00</m:TimeDate> <m:Source>CompanyA</m:Source> <m:Version>v20160301</m:Version> </m:MessageHeader> <m:MessagePayload> <m:RegisteredResourceOutage> <m:mRID>123456789</m:mRID> <m:description>New Generator (MSG) Outage</m:description> <m:comment>Example</m:comment> <m:createdBy>John Smith</m:createdBy> <m:createdDateTime>2014-01-03T11:00:04Z</m:createdDateTime> <m:lastModifiedDateTime>2014-01-03T11:00:04Z</m:lastModifiedDateTime> <m:lastUpdatedBy>John Smith</m:lastUpdatedBy> <m:affectsRASSPS>YES</m:affectsRASSPS>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:discoveryDateTime>2014-01-03T11:00:00Z</m:discoveryDateTime> <m:emergencyReturnTime>1</m:emergencyReturnTime> <m:emergencyReturnTimeType>HOURS</m:emergencyReturnTimeType> <m:isFinalApprovalReq>YES</m:isFinalApprovalReq> <m:mktOrgOutageID>9690</m:mktOrgOutageID> <m:outageCoordinationLongTermPlanning>NO</m:outageCoordinationLongTermPlanning> <m:outageStatus>RECEIVED</m:outageStatus> <m:outageStatusReason>AUTO</m:outageStatusReason> <m:outageType>PLANNED</m:outageType> <m:versionID>1</m:versionID> <m:estimatedPeriod> <m:end>2014-01-17T17:00:00Z</m:end> <m:start>2014-01-17T13:00:00Z</m:start> </m:estimatedPeriod> <m:MktOrganisation> <m:mRID>SCID1</m:mRID> <m:MarketPerson> <m:firstName>John</m:firstName> <m:lastName>Smith</m:lastName> <m:landlinePhone> <m:areaCode>916</m:areaCode> <m:extension>555</m:extension> <m:localNumber>1234</m:localNumber> </m:landlinePhone> </m:MarketPerson> </m:MktOrganisation> <m:OutageCause> <m:code>9690</m:code> </m:OutageCause> <m:OutageChangeRequest> <m:mRID>912345677</m:mRID> <m:action>UPDATE</m:action> <m:actionReason>CANCELLED_BY_CREW_PTO</m:actionReason> <m:status>REJECTED</m:status> </m:OutageChangeRequest> <m:OutageChangeRequest> <m:mRID>912345678</m:mRID> <m:action>UPDATE</m:action> <m:actionReason>WORK_RESCHEDULED_TO_LATER_DATE_SC</m:actionReason> <m:status>ACCEPTED</m:status> </m:OutageChangeRequest> <m:OutageValidation> <m:OutageResult> <m:mRID>1</m:mRID> <m:description>Validated</m:description> <m:status>ACKNOWLEDGED</m:status> <m:type>INFO</m:type> </m:OutageResult> </m:OutageValidation>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:Work> <m:kind>PLANT_MAINTENANCE</m:kind> </m:Work> <m:isInconsistent>NO</m:isInconsistent> <m:isInvalid>YES</m:isInvalid> <m:isOffPeakOpportunityOutage>NO</m:isOffPeakOpportunityOutage> <m:isSCPExempt>NO</m:isSCPExempt> <m:isShortNoticeOpportunityOutage>NO</m:isShortNoticeOpportunityOutage> <m:RegisteredGenerator> <m:mRID>ResourceA</m:mRID> <m:name>Resource Alpha</m:name> <m:LogicalConfiguration> <m:Configuration> <m:mRID>ResA1x1</m:mRID> <m:name>Resource Alpha 1x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>80</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>100</m:value> </m:PmaxValue> </m:Availability> </m:OutagedRegisteredResource> </m:Configuration> <m:Configuration> <m:mRID>ResA2x1</m:mRID> <m:name>Resource Alpha 2x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>160</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:PmaxValue> </m:Availability> <m:PMinimum> <m:activePeriod> <m:start>2014-01-17T13:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>81</m:value> </m:restrictedValue> </m:PMinimum> <m:PMinimum> <m:activePeriod> <m:start>2014-01-17T17:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:restrictedValue> </m:PMinimum> </m:OutagedRegisteredResource> </m:Configuration> </m:LogicalConfiguration> <m:OutagedRegisteredResource> <m:ASAvailability> <m:availableValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>0</m:value> </m:availableValue> <m:MarketProduct> <m:marketProductType>SR</m:marketProductType> </m:MarketProduct> </m:ASAvailability> </m:OutagedRegisteredResource> </m:RegisteredGenerator> </m:RegisteredResourceOutage> </m:MessagePayload> </m:ResourceOutageResults>

5.7.4 Example XML file (ResourceOutageChangeRequestResults_v1.xml)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<?xml version="1.0" encoding="UTF-8"?> <m:ResourceOutageResults xmlns:m="http://www.caiso.com/soa/ResourceOutageResults_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/ResourceOutageResults_v1.xsd# ResourceOutageResults_v1.xsd "> <m:MessageHeader> <m:TimeDate>2001-12-31T12:00:00</m:TimeDate> <m:Source>CompanyA</m:Source> <m:Version>v20160301</m:Version> </m:MessageHeader> <m:MessagePayload> <m:RegisteredResourceOutage> <m:mRID>123456789</m:mRID> <m:description>New Generator (MSG) Outage</m:description> <m:comment>Example</m:comment> <m:createdBy>John Smith</m:createdBy> <m:createdDateTime>2014-01-03T11:00:04Z</m:createdDateTime> <m:lastModifiedDateTime>2014-01-03T11:00:04Z</m:lastModifiedDateTime> <m:lastUpdatedBy>John Smith</m:lastUpdatedBy> <m:affectsRASSPS>YES</m:affectsRASSPS> <m:discoveryDateTime>2014-01-03T11:00:00Z</m:discoveryDateTime> <m:emergencyReturnTime>1</m:emergencyReturnTime> <m:emergencyReturnTimeType>HOURS</m:emergencyReturnTimeType> <m:isFinalApprovalReq>YES</m:isFinalApprovalReq> <m:mktOrgOutageID>9690</m:mktOrgOutageID> <m:outageCoordinationLongTermPlanning>NO</m:outageCoordinationLongTermPlanning> <m:outageStatus>RECEIVED</m:outageStatus> <m:outageStatusReason>AUTO</m:outageStatusReason> <m:outageType>PLANNED</m:outageType> <m:versionID>1</m:versionID> <m:estimatedPeriod> <m:end>2014-01-17T17:00:00Z</m:end> <m:start>2014-01-17T13:00:00Z</m:start> </m:estimatedPeriod> <m:MktOrganisation> <m:mRID>SCID1</m:mRID> <m:MarketPerson> <m:firstName>John</m:firstName> <m:lastName>Smith</m:lastName> <m:landlinePhone> <m:areaCode>916</m:areaCode> <m:extension>555</m:extension> <m:localNumber>1234</m:localNumber> </m:landlinePhone> </m:MarketPerson> </m:MktOrganisation>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:OutageCause> <m:code>9690</m:code> </m:OutageCause> <m:OutageChangeRequest> <m:mRID>912345677</m:mRID> <m:action>UPDATE</m:action> <m:actionReason>WORK_RESCHEDULED_TO_LATER_DATE_SC</m:actionReason> <m:status>ACCEPTED</m:status> </m:OutageChangeRequest> <m:OutageValidation> <m:OutageResult> <m:mRID>1</m:mRID> <m:description>Validated</m:description> <m:status>ACKNOWLEDGED</m:status> <m:type>INFO</m:type> </m:OutageResult> </m:OutageValidation> <m:Work> <m:kind>PLANT_MAINTENANCE</m:kind> </m:Work>

<m:isInconsistent>NO</m:isInconsistent> <m:isInvalid>YES</m:isInvalid>

<m:isOffPeakOpportunityOutage>NO</m:isOffPeakOpportunityOutage> <m:isSCPExempt>NO</m:isSCPExempt> <m:isShortNoticeOpportunityOutage>NO</m:isShortNoticeOpportunityOutage> <m:RegisteredGenerator> <m:mRID>ResourceA</m:mRID> <m:name>Resource Alpha</m:name> <m:LogicalConfiguration> <m:Configuration> <m:mRID>ResA1x1</m:mRID> <m:name>Resource Alpha 1x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>80</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>100</m:value> </m:PmaxValue> </m:Availability> </m:OutagedRegisteredResource> </m:Configuration> <m:Configuration> <m:mRID>ResA2x1</m:mRID> <m:name>Resource Alpha 2x1</m:name> <m:OutagedRegisteredResource> <m:Availability> <m:dateTimePoint>2014-01-17T13:00:00Z</m:dateTimePoint> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>160</m:value> </m:PmaxValue> </m:Availability> <m:Availability> <m:dateTimePoint>2014-01-17T17:00:00Z</m:dateTimePoint> <m:returnToNetDependableCapacity>YES</m:returnToNetDependableCapacity> <m:PmaxValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:PmaxValue> </m:Availability> <m:PMinimum> <m:activePeriod> <m:start>2014-01-17T13:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>81</m:value> </m:restrictedValue> </m:PMinimum> <m:PMinimum> <m:activePeriod>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<m:start>2014-01-17T17:00:00Z</m:start> </m:activePeriod> <m:restrictedValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>200</m:value> </m:restrictedValue> </m:PMinimum> </m:OutagedRegisteredResource> </m:Configuration> </m:LogicalConfiguration> <m:OutagedRegisteredResource> <m:ASAvailability> <m:availableValue> <m:multiplier>M</m:multiplier> <m:unit>W</m:unit> <m:value>0</m:value> </m:availableValue> <m:MarketProduct> <m:marketProductType>SR</m:marketProductType> </m:MarketProduct> </m:ASAvailability> </m:OutagedRegisteredResource> </m:RegisteredGenerator> </m:RegisteredResourceOutage> </m:MessagePayload> </m:ResourceOutageResults>

5.8 Fault Return

For Fault return see section Fault Return

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


6. Submit Transmission Outage {Change Requests} Business Scenario

6.1 Overview

Outage coordinators can submit transmission outages or changes to previously submitted outages (Outage Change Requests) for affiliated equipment.








30 minutes

Business impact if is unavailable Outage Coordinators can call the ISO directly with critical near-term outages.


Expected time to exchange Variable (.1 sec – 30 sec)

6.3 Use Model


6.3.1 Submit New Transmission Outage

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


6.3.2 Submit Change to Existing Transmission Outage


6.4.1 Submit Transmission Outage

The service has one operation with three message types.

Operation Message

Types

Message WSDL XSD

SubmitTransmissi

onOutage

Input submitTransmission

Outage

submitTransmissionOutage

_v2.wsdl/

submitTransmissionOutage

_v2_DocAttach.wsdl

TransmissionOutageData_v2.x

sd

Output submitTransmission

OutageResponse



6.4.2 Submit Transmission Outage Change Request

Operation Message

Types

Message WSDL XSD

sd Submit Transmission Outage

Outage Coordinator

OMS

SubmitTransmissionOutage()

SubmitTransmissionOutageResponse()

sd SubmitTransmissionOutageChangeRequest

Outage Coordinator

OMS

SubmitTransmissionOutageChangeRequest()

SubmitTransmissionOutageChangeRequestResponse()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


SubmitTransmissi

onOutageChange

Request

Input submitTransmissi

onOutageChange

Request

submitTransmissionOutageC

hangeRequest_v2.wsdl/

submitTransmissionOutageC

hangeRequest_v2_DocAttach

.wsdl

TransmissionOutageData_v2.x

sd

Output submitTransmissi

onOutageChange

RequestResponse



6.5 WSDL

6.5.1 submitTransmissionOutage_v2.wsdl / submitTransmissionOutage_v2_DocAttach.wsdl

6.5.2 SubmitTransmissionOutageChangeRequest_v2.wsdl/ SubmitTransmissionOutageChangeRequest_v2_DocAttach.wsdl

6.6 Submit Transmission Outage {Change Request}

Note: Outage cause codes are mandatory for forced transmission outages. At least one primary and one secondary cause code enumeration must be provided upon outage submission. The cause codes may be modified upon submission of an outage change request. The list of valid primary cause codes are: Aircraft (P), Animal Contact (P), Circuit Breakers/Circuit

Switches Trouble (P), Contamination (P), System Disturbance (P), Fire (P), Generation Maintenance/Trouble

(P), Late Notification (P), Line Equipment Trouble (P), Lightning (P), Natural Disasters (P), Operation Error

(P), Other (P), Protection (P), Scheduled Outage (P) Other Substation Equipment Trouble (P), Utility Contact

(P), Unknown (P), Vegetation (P), Vehicles (P), Weather (P)

Primary Cause Code Name Primary Cause Code Enumeration

Aircraft (P) AIRCRAFT_P

Animal Contact (P) ANIMAL_CONTACT_P

Circuit Breakers/Circuit Switches

Trouble (P)

CIRCUIT_BREAKERS_OR_CIRCUIT_SWITCHES_TROUBLE_P

Contamination (P) CONTAMINATION_P

System Disturbance (P) SYSTEM_DISTURBANCE_P

Fire (P) FIRE_P

Generation Maintenance/Trouble (P) GENERATION_MAINTENANCE_OR_TROUBLE_P

Late Notification (P) LATE_NOTIFICATION_P

Line Equipment Trouble (P) LINE_EQUIPMENT_TROUBLE_P

Lightning (P) LIGHTNING_P

Natural Disasters (P) NATURAL_DISASTERS_P

Operation Error (P) OPERATION_ERROR_P

Other (P) OTHER_P

Protection (P) PROTECTION_P

Scheduled Outage (P) SCHEDULED_OUTAGE_P

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Other Substation Equipment Trouble

(P)

OTHER_SUBSTATION_EQUIPMENT_TROUBLE_P

Utility Contact (P) UTILITY_CONTACT_P

Unknown (P) UNKNOWN_P

Vegetation (P) VEGETATION_P

Vehicles (P) VEHICLES_P

Weather (P) WEATHER_P

The list of valid secondary cause codes are: Arrestors (S), Station Auxiliary Equipment (S), Battery

Systems (S),Bushings (S), COMM Facilities Not 100% Dedicated to Control (S), Conductor, Shield Wire, and

Splices (S), Direct Current Transmission Components (S), Disconnects (S), Encroachments/Unauthorized

Attachments (S), Guys and Anchors (S), Hardware, Fittings and Accessories (S), Insulators (S), Line

Switches (S), None (S) , Work Procedure/Human Error (S), Reactive Devices (S), Regulator (S), Control and

Relay System (S), Structures/Foundations (S), Underground Transmission Components (S), Circuit

Breakers/Circuit Switches (S), Other (S)

Secondary Cause Code Name Secondary Cause Code Enumeration Arrestors (S) ARRESTORS_S

Station Auxiliary Equipment (S) STATION_AUXILIARY_EQUIPMENT_S

Battery Systems (S) BATTERY_SYSTEMS_S

Bushings (S) BUSHINGS_S

COMM Facilities Not 100%

Dedicated to Control (S) COMM_FACILITIES_NOT_100_PERCENT_DEDICATED_TO_CONTR

OL_S

Conductor, Shield Wire, and

Splices (S) CONDUCTOR_SHIELD_WIRE_AND_SPLICES_S

Direct Current Transmission

Components (S) DIRECT_CURRENT_TRANSMISSION_COMPONENTS_S

Disconnects (S) DISCONNECTS_S

Encroachments/Unauthorized

Attachments (S) ENCROACHMENTS_OR_UNAUTHORIZED_ATTACHMENTS_S

Guys and Anchors (S) GUYS_AND_ANCHORS_S

Hardware, Fittings and

Accessories (S) HARDWARE_FITTINGS_AND_ACCESSORIES_S

Insulators (S) INSULATORS_S

Line Switches (S) LINE_SWITCHES_S

None (S) NONE_S

Work Procedure/Human Error

(S) WORK_PROCEDURE_OR_HUMAN_ERROR_S

Reactive Devices (S) REACTIVE_DEVICES_S

Regulator (S) REGULATOR_S

Control and Relay System (S), CONTROL_AND_RELAY_SYSTEM_S

Structures/Foundations (S), STRUCTURES_OR_FOUNDATIONS_S

Underground Transmission

Components (S), UNDERGROUND_TRANSMISSION_EQUIPMENT_S

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Circuit Breakers/Circuit Switches

(S), CIRCUIT_BREAKERS_OR_CIRCUIT_SWITCHES_S

Other (S) OTHER_S

6.6.1 Element Table


Format/ Length

Req’d

Message Header


dateTime Yes




String Yes

MessagePayload.TransmissionOutage


String No


String Yes


String No


String No





String Yes


String Yes


Indicates Outage is part of your Quarterly Outage Yes/No No



RIMSProjectCommissionDate

RIMS project commission date dateTime No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

RIMSProjectCompletion RIMS project completion Yes/No No

RIMSProjectID RIMS project ID. String No

RIMSProjectPhase RIMS project phase. String No

OutageCause.code Reason code for Outage String No

Work.kind Kind of work String Yes

trumpFlag Indicates Outage trumps existing conflicting Outages

Yes/No No

congestionRevenueRightsDesignation

Indicates Outage affects the CRR auction Yes/No String No.

isNewEquipmentEnergized

Participant indicates that new equipment will be energized when the outage is complete. Yes/No

String No.

MessagePayload.TransmissionOutage.OperatingParticipant Yes


MessagePayload.TransmissionOutage.OperatingParticipant.Person No

firstName First name of the contact at the participant. String No

lastName Last name of the contact at the participant. String No

landlinePhone Phone number of the contact at the participant. Complex No

MessagePayload.TransmissionOutage.OutageChangeRequest No

action Type of change request. If present indicates that this is a change request to an existing outage. UPDATE or CANCEL

String Yes

actionReason Reason for changes. String No

actionSubType For Update, define type of Update IN_OK, IN_SERVICE , OUT, OUT_OK

String No

MessagePayload.TransmissionOutage.Equipments Yes

mRID The ISO RDFID for the Equipment. mrid minLen=1

maxLen=40

No

Names.name The Participant ID from Transmission Register (TR) for the equipment. Can be used instead of the ISO RDFID. Set the name type to PARTICIPANTID.

String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Names.NameType Type of this name, PARTICIPANTID, PARTICIPANTNAME

String Yes

MessagePayload.TransmissionOutage.Equipments.AdjustedOperationalRating No

Active Period Interval during which Equipment has this restricted value. Must be the same or a subset of the outage range.

dateTime Yes

normalRestrictedValue New normal rating for this period : Unit of measure, value and multiplier

FloatQuantity

No

isRecurring Repeats the section of the day defined by start and end

each day for the duration of the outage. Yes/No String No

emergencyRestrictedValue

New Emergency rating for this period : Unit of measure, value and multiplier

FloatQuantity

No

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment Yes

switchModelingComplete

Indicates that the switch modeling is not complete yet. Allows Out Of Service outages to be submitted before the full switching plan is available. Analysis is delayed until switch model is complete. Yes/No

String No

useFacilityOutageDefinition

For this equipment Out Of Service use the ISO generated list of switches and positions. Yes/No

String No

MessagePayload.TransmissionOutage.Equipments.VoltageLevel No

BaseVoltage The base Voltage used for all equipment within voltage level

Voltage Complex No

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment.Switch No

mRID RDFID of Switch. ISO’s unique identifier. mrid minLen=1

maxLen=40

No

Names.name The Participant ID from Transmission Register (TR) for the switch. Can be used instead of the ISO RDFID. Set the name type to PARTICIPANTID.

String Yes


String Yes

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment.Switch.SwitchingOperations Yes

newState New status of the switch for the newStatePeriod. Open/Close.

SwitchState Complex Type

Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

newStatePeriod Start/End period for which the new state (open or close) is active

dateTime Yes

6.6.2 Schema (TransmissionOutageData_v2.xsd)

6.6.3 Example XML File (SubmitTransmissionOutageData_v2.xml)

<?xml version="1.0" encoding="UTF-8"?>  <TransmissionOutageData xsi:schemaLocation="http://www.caiso.com/soa/TransmissionOutageData_v2.xsd# TransmissionOutageData_v1.xsd" xmlns="http://www.caiso.com/soa/TransmissionOutageData_v2.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <TransmissionOutage> <description>New Transmission Outage</description> <comment>Sample</comment> <affectsRASSPS>NO</affectsRASSPS> <discoveryDateTime>2001-12-17T09:30:47Z</discoveryDateTime> <emergencyReturnTime>1</emergencyReturnTime> <emergencyReturnTimeType>HOURS</emergencyReturnTimeType> <mktOrgOutageID>ref_id_1000</mktOrgOutageID> <RIMSProjectCommissionDate>2001-12-17T09:30:47Z</RIMSProjectCommissionDate> <RIMSProjectCompletion>NO</RIMSProjectCompletion> <RIMSProjectID>rims_project_id_1000</RIMSProjectID> <RIMSProjectPhase>Planning</RIMSProjectPhase> <actualPeriod> <end>2001-12-17T09:30:47Z</end> <start>2001-12-17T09:30:47Z</start> </actualPeriod> <Equipments> <mRID>Unique Equipment Name</mRID> <Names> <name>Participant Equipment A name</name> <NameType> <name>name</name> </NameType> </Names> <AdjustedOperationalRating>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<activePeriod> <end>2001-12-17T09:30:47Z</end> <start>2001-12-17T12:30:47Z</start> </activePeriod> <normalRestrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>80</value> </normalRestrictedValue> <isRecurring>NO</isRecurring> <emergencyRestrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>40</value> </emergencyRestrictedValue> </AdjustedOperationalRating> <OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete> <useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <SwitchingOperations> <newState>close</newState> <newStatePeriod> <end>2001-12-31T12:00:00</end> <start>2001-12-31T12:00:00</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> <VoltageLevel> <BaseVoltage> <nominalVoltage> <multiplier>k</multiplier> <unit>V</unit> <value>0.0</value> </nominalVoltage> </BaseVoltage> </VoltageLevel> </Equipments> <estimatedPeriod> <end>2001-12-17T09:30:47Z</end> <start>2001-12-17T09:30:47Z</start> </estimatedPeriod> <OperatingParticipant> <mRID>PTO1</mRID> <Person> <firstName>John</firstName> <lastName>Smith</lastName> <landlinePhone> <areaCode>916</areaCode>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<extension>555</extension> <localNumber>1234</localNumber> </landlinePhone> </Person> </OperatingParticipant> <Work> <kind>EQUIPMENT_DERATE</kind> </Work> <isNewEquipmentEnergized>NO</isNewEquipmentEnergized> </TransmissionOutage> </MessagePayload> </TransmissionOutageData>

6.6.4 Example XML File (SubmitTransmissionOutageChangeRequest_v2.xml)

<?xml version="1.0" encoding="UTF-8"?>  <TransmissionOutageData xsi:schemaLocation="http://www.caiso.com/soa/TransmissionOutageData_v2.xsd# TransmissionOutageData_v1.xsd" xmlns="http://www.caiso.com/soa/TransmissionOutageData_v2.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <TransmissionOutage> <mRID>123456789</mRID> <description>New Transmission Outage</description> <comment>Sample</comment> <affectsRASSPS>NO</affectsRASSPS> <discoveryDateTime>2014-01-20T13:00:00Z</discoveryDateTime> <emergencyReturnTime>1</emergencyReturnTime> <emergencyReturnTimeType>HOURS</emergencyReturnTimeType> <mktOrgOutageID>ref_id_1000</mktOrgOutageID> <RIMSProjectCommissionDate>2001-12-17T09:30:47Z</RIMSProjectCommissionDate> <RIMSProjectCompletion>NO</RIMSProjectCompletion> <RIMSProjectID>rims_project_id_1000</RIMSProjectID> <RIMSProjectPhase>Planning</RIMSProjectPhase> <actualPeriod> <start>2014-01-23T13:30:00Z</start> </actualPeriod> <Equipments> <mRID>Unique Equipment Name</mRID> <Names> <name>Participant Equipment A name</name>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<NameType> <name>name</name> </NameType> </Names> <AdjustedOperationalRating> <activePeriod> <end>2014-01-31T13:30:00Z</end> <start>2014-01-23T13:00:00Z</start> </activePeriod> <normalRestrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>60</value> </normalRestrictedValue> <isRecurring>NO</isRecurring> <emergencyRestrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>20</value> </emergencyRestrictedValue> </AdjustedOperationalRating> <OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete> <useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <SwitchingOperations> <newState>close</newState> <newStatePeriod> <end>2001-12-31T12:00:00</end> <start>2001-12-31T12:00:00</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> <VoltageLevel> <BaseVoltage> <nominalVoltage> <multiplier>k</multiplier> <unit>V</unit> <value>0.0</value> </nominalVoltage> </BaseVoltage> </VoltageLevel> </Equipments> <estimatedPeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:00:00Z</start> </estimatedPeriod> <OperatingParticipant> <mRID>PTO1</mRID>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<Person> <firstName>John</firstName> <lastName>Smith</lastName> <landlinePhone> <areaCode>916</areaCode> <extension>555</extension> <localNumber>1234</localNumber> </landlinePhone> </Person> </OperatingParticipant> <OutageChangeRequest> <action>UPDATE</action> </OutageChangeRequest> <Work> <kind>EQUIPMENT_DERATE</kind> </Work> <isNewEquipmentEnergized>NO</isNewEquipmentEnergized> </TransmissionOutage> </MessagePayload> </TransmissionOutageData>

6.7 Submit TransmissionOutage {Change Request} Response

6.7.1 Element Table


Format/ Length

Req’d

Message Header No


dateTime Yes




String Yes

MessagePayload.EventLog Yes

MessagePayload.EventLog.Event Yes

result Event result. string Yes

id Event identifier. string Yes

description Event description. string No

creationDateTime Event creation time. dateTime No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

MessagePayload.EventLog.Service Yes

id Service identifier. string Yes

name Name of a service. string Yes

MessagePayload.EventLog.Outage No

mrid ID assigned to the outage by the ISO String No

mktOrgOutageID Reference ID assigned to the outage by the external User

String Yes

MessagePayload.EventLog.Outage.OutageChangeRequest No

mrid ID assigned to the outage change request by the ISO

String Yes

MessagePayload.EventLog.Outage.OutageGroup No

mRID ID assigned to the outage Group by the ISO String Yes

MessagePayload.EventLog.Outage.OutageValidation Yes

submitStatus Indicates whether the outage was accepted or rejected: ACCEPTED, REJECTED

String Yes

MessagePayload.EventLog.Outage.OutageValidation.OutageResult Yes


type Type of result: ERROR, INFO, WARNING String Yes



String No

6.7.2 Schema (OutageStandardOutput_v1.xsd)

6.7.3 Example XML File (TransmissionOutageStandardOutput_v1.xml)

6.7.3.1 Example XML File for Submit Transmission Outage Response

<?xml version="1.0" encoding="UTF-8"?>  <OutageStandardOutput

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


xsi:schemaLocation="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd# OutageStandardOutput_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>OMS</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <EventLog> <Event> <id>1000</id> <result>Success</result> </Event> <Outage> <mRID>123456789</mRID> <mktOrgOutageID>ref_id_1000</mktOrgOutageID> <OutageValidation> <submitStatus>ACCEPTED</submitStatus> <OutageResult> <mRID>1</mRID> <description>Validated</description> <type>INFO</type> </OutageResult> </OutageValidation> </Outage> <Service> <id>12345</id> <name>submitTransmissionOutage_v1</name> </Service> </EventLog> </MessagePayload> </OutageStandardOutput>

6.7.3.2 Example XML File for Submit Transmission Outage Change Request Response

<?xml version="1.0" encoding="UTF-8"?>  <OutageStandardOutput xsi:schemaLocation="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd# OutageStandardOutput_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>OMS</Source> <Version>v20160301</Version> </MessageHeader>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<MessagePayload> <EventLog> <Event> <id>1</id> <result>Success</result> </Event> <Outage> <mRID>123456789</mRID> <mktOrgOutageID>ref_id_1000</mktOrgOutageID> <OutageChangeRequest> <mRID>987654321</mRID> </OutageChangeRequest> <OutageValidation> <submitStatus>ACCEPTED</submitStatus> <OutageResult> <mRID>1</mRID> <description>Validated</description> <type>INFO</type> </OutageResult> </OutageValidation> </Outage> <Service> <id>12345</id> <name>submitTransmissionOutageChangeRequest_v1</name> </Service> </EventLog> </MessagePayload> </OutageStandardOutput>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7. Retrieve Transmission Outage/Change Requests

7.1 Overview

Outage Coordinators can retrieve transmission outages or outage change requests for affiliated generators.








30 minutes

Business impact if is unavailable Outage Coordinators can call the ISO for status on near-term outages and Change Requests.



7.3 Use Model


7.3.1 Retrieve Transmission Outages

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7.3.2 Retrieve Transmission Outage Change Requests



7.4.1 Retrieve Transmission Outage

Operation Message

Types

Message WSDL XSD

retrieveTransmissi

onOutage

Input retrieveTransmissi

onOutage

retrieveTransmissionOutage_

v2.wsdl/

retrieveTransmissionOutage_

v2_DocAttach.wsdl

requestTransmissionOutage_

v1.xsd

Output retrieveTransmsis

sionOutageRespo

nse

TransmissionOutageResults_

v2.xsd


7.4.2 Retrieve Transmission Outage Change Request

sd retriev eTransmissionOutage

Outage Coordinator

OMS

retrieveTransmissionOutage()

retrieveTransmissionOutageResponse()

sd retriev eTransmissionOutageChangeRequest

Outage Coordinator

OMS

retrieveTransmissionOutageChangeRequest()

retrieveTransmissionOutageChangeRequestResponse()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Operation Message

Types

Message WSDL XSD

retrieveTransmissi

onOutageChange

Request

Input retrieveTransmissi

onOutageChangeR

equest

retrieveTransmissionOutage

ChangeRequest_v2.wsdl/

retrieveTransmissionOutage

ChangeRequest_v2_DocAtta

ch.wsdl

requestTransmissionOutage_

v1.xsd

Output retrieveTransmissi

onOutageChangeR

equestResponse

TransmissionOutageResults_

v2.xsd


7.5 WSDL

7.5.1 retrieveTransmissionOutage_v2.wsdl / retrieveTransmissionOutage_v2_DocAttach.wsdl

7.5.2 retrieveTransmissionOutageChangeRequest_v2.wsdl / retrieveTransmissionOutageChangeRequest_v2_DocAttach.wsdl

7.6 Retrieve Transmission Outage {Change Request}

Request Criteria Input Parameters Results

Outage WebOMS outage id or Participant’s outage id

The outage specified

Outage Range Range start and end date and Outage Status (optional)

All outages for all resources that the requester has access to for the date range specified optionally filtered by outage status if specified

Participant MktOrganization mrid and Range start and end date and Outage Status(optional)

All outages for all resources associated with the specified MktOrganization mrid that the requester has access to for the date range specified optionally filtered by outage status if specified

Equipment Resource (Equipment mrid or Equipment Names.name and Equipment Names.NameType.name = PARTICIPANTID) and Range start and end date and Outage Status(optional)

All outages for the equipment specified and for the date range specified optionally filtered by outage status if specified

Outage Change Request Outage Change Request mrid The outage change request specified

7.6.1 Element Table

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

Message Header No





String Yes

MessagePayload.Outage No

mRID The Primary identifier the ISO has given to an outage String No

mktOrgOutageID Reference ID assigned to the outage by the external user

String No

MessagePayload.OutageChangeRequest No

mRID The Primary identifier the ISO has given to an outage change request

String No

MessagePayload.Participant No


MessagePayload.Participant.MktOrganization Yes

mrID Participant Short Name of the requestor String No

MessagePayload.Participant.Outage No


MessagePayload.Participant.rangePeriod Yes

rangePeriod Start and end date of the period being requested String Yes

MessagePayload.EquipmentResource


MessagePayload.EquipmentResource.Equipment Yes

mRID Master resource identifier issues by Model Authority String No

name Equipment Name, it may not be unique String No

Names All Names of this equipment Name Complex Type

No

MessagePayload.EquipmentResource.Outage No


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

MessagePayload.OutageRange No

rangePeriodType Type of range period of outages being requested where:

ACTUAL represents duration of outage (this is the default if no rangePeriodType is specified)

CREATE represents creation date of outage

UPDATE represents last updated date of outage

String No

rangePeriod Start and end date of the period being requested dateTime Yes

MessagePayload.OutageRange.Outage


7.6.2 Schema (RequestTransmissionOutage_v1.xsd)

7.6.3 Example XML File (RequestTransmissionOutage_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <RequestTransmissionOutage xsi:schemaLocation="http://www.caiso.com/soa/RequestTransmissionOutage_v1.xsd# RequestTransmissionOutage_v1.xsd" xmlns="http://www.caiso.com/soa/RequestTransmissionOutage_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <EquipmentResource> <Equipment> <mRID>1234</mRID> <name>ISONameLineB</name> </Equipment> <Outage> <outageStatus>APPROVED</outageStatus> </Outage> <rangePeriod> <end>2014-02-01T00:00:00Z</end> <start>2014-01-01T00:00:00Z</start> </rangePeriod> </EquipmentResource> </MessagePayload> </RequestTransmissionOutage>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7.6.4 Example XML file (RequestTransmissionOutageChangeRequest_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <RequestTransmissionOutage xsi:schemaLocation="http://www.caiso.com/soa/RequestTransmissionOutage_v1.xsd# RequestTransmissionOutage_v1.xsd" xmlns="http://www.caiso.com/soa/RequestTransmissionOutage_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>String</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <EquipmentResource> <Equipment> <mRID>1234</mRID> <name>ISONameLineB</name> </Equipment> <rangePeriod> <end>2014-02-01T00:00:00Z</end> <start>2014-01-01T00:00:00Z</start> </rangePeriod> </EquipmentResource> </MessagePayload> </RequestTransmissionOutage>

7.7 Retrieve Transmission Outage {Change Request} Response

7.7.1 Element Table


Format/ Length

Req’d

Message Header No


dateTime Yes




String Yes

MessagePayload.TransmissionOutage Yes


String No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d


String Yes


String No

createDateTime Time this outage/change request was created dateTime Yes

createdBy The person that created the outage/change request

String Yes

lastModifiedDateTime Time this outage/change request was last modified dateTime Yes

lastUpdatedBy The person that last updated the the outage/change request

dateTime Yes


String No





String Yes

isFinalApprovalReq Flag to indicate if final approval is required. Yes/No String No


String No


Indicates the outage is part of your quarterly outage plan

Yes/No No

OutageStatus The current status of the outage String Yes

OutageStatusReason The reason for moving the outage to this status String No

OutageType The type of outage: PLANNED, FORCED OutageKind

Yes


Commission date of the the related RIMS project dateTime No




versionID Version of this Outage String Yes

congestionRevenueRightsDesignation

Indicates that an Outage affects the Congestion Revenue Rights (CRR) auction.

Yes/No No

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

isNewEquipmentEnergized

Participant indicates that new equipment will be energized when the outage is complete. Yes/No

String No



Work.kind Kind of work String Yes

trumpFlag Indicates Outage trumps existing conflicting Outages

Yes/No No

MessagePayload.TransmissionOutage.OutageGroup No

MRID The primary identifier of the Group String Yes

Description The description of the group String Yes

createdDateTime Time the group was created dateTime Yes

CreatedBy The person that created the group String Yes

lastModifiedDateTime Time the group was last modified dateTime Yes

LastModifiedBy The person that last updated the group String Yes

MessagePayload.TransmissionOutage.OperatingParticipant Yes


MessagePayload.TransmissionOutage.OperatingParticipant.Person No




MessagePayload.TransmissionOutage.OutageChangeRequest No

mrID ID assigned to the outage change request by the ISO

String Yes

action Type of change request. UPDATE or CANCEL String Yes

actionReason Reason for Change String No

actionSubType Forupdate, define the type of Update String No

status Status of the outage change request: PENDING, ACCEPTED, DENIED

String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

statusReason Reason for status. Required when the outage change request is denied

String No

MessagePayload.TransmissionOutage.Equipments Yes

mRID The RDF id for the Equipment. mrid minLen=1

maxLen=40

Yes

name ISO name of Equipment name minLen=1

maxLen=80

Yes

Names.name ISO names of Equipment. Max number of names :2. When the equipment can be matched to a TR registration contains the

TR ID (nameType=PARTICIPANTID) and the

TR Name (nameType=PARTICIPANTNAME)

String No

Names.NameType Type of this name. PARTICIPANTID, PARTICIPANTNAME

String No

PSR Type Type of power system resource

ACLINESEGMENT, BREAKER, BUSBARSECTION, CONFORMLOAD, DCLINESEGMENT, DISCONNECT, ENERGYCONSUMER, LINE, NONCONFORMLOAD, POWERTRANSFORMER, STATICVARCOMPENSATOR, SUBSTATION, SWITCH

Enumeration

Yes

MessagePayload.TransmissionOutage.Equipments.AdjustedOperationalRating No

Active Period Interval during which Equipment has this restricted value

dateTime Yes

normalRestrictedValue New normal rating for this period : Unit of measure, value and multiplier

FloatQuantity

No

isRecurring Repeats the section of the day defined by start and end

each day for the duration of the outage. Yes/No String No

emergencyRestrictedValue

New Emergency rating for this period : Unit of measure, value and multiplier

FloatQuantity

No

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

switchModelingComplete

Indicates that the switch modeling is not complete yet. Allows Out Of Service outages to be submitted before the full switching plan is available. Analysis is delayed until switch model is complete. Yes/No

String No

useFacilityOutageDefinition

For this equipment Out Of Service use the ISO generated list of switches and positions. Yes/No

String No

MessagePayload.TransmissionOutage.Equipments.VoltageLevel No

BaseVoltage The base Voltage used for all equipment within voltage level

Voltage Complex No

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment.Switch(Required=No)

mRID ISO RDFID of the Switch mrid minLen=1

maxLen=40

Yes

name ISO name of Equipment name minLen=1

maxLen=80

Yes

Names.name ISO names of Equipment. Max number of names :2 When the switch can be matched to a TR registration contains the

TR ID (nameType=PARTICIPANTID) and the

TR Name (nameType=PARTICIPANTNAME)

String No


String No

MessagePayload.TransmissionOutage.Equipments.OutagedEquipment.Switch.SwitchingOperations Yes

newState New status of the switch for the newStatePeriod. Open/Close

SwitchState Complex Type

Yes

newStatePeriod Start/End period for which the new state (open or close) is active

dateTime Yes

7.7.2 Schema (TransmissionOutageResults_v2.xsd)

7.7.3 Example XML File (TransmissionOutageResults_v2.xml)

<?xml version="1.0" encoding="UTF-8"?>  <TransmissionOutageResults xsi:schemaLocation="http://www.caiso.com/soa/TransmissionOutageResults_v2.xsd# TransmissionOutageResults_v1.xsd"

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


xmlns="http://www.caiso.com/soa/TransmissionOutageResults_v2.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-01-27T13:30:00Z</TimeDate> <Source>OMS</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <TransmissionOutage> <mRID>123456789</mRID> <description>Line work to install new equipment.</description> <comment>Out for Maintenance</comment> <createdBy>John Smith</createdBy> <createdDateTime>2014-01-20T16:30:00Z</createdDateTime> <lastModifiedDateTime>2014-01-23T13:30:00Z</lastModifiedDateTime> <lastUpdatedBy>John Smith</lastUpdatedBy> <affectsRASSPS>NO</affectsRASSPS> <discoveryDateTime>2014-01-20T16:15:00Z</discoveryDateTime> <emergencyReturnTime>2</emergencyReturnTime> <emergencyReturnTimeType>HOURS</emergencyReturnTimeType> <isFinalApprovalReq>YES</isFinalApprovalReq> <mktOrgOutageID>P123456789</mktOrgOutageID> <outageStatus>OUT_OK</outageStatus> <outageStatusReason>Outage Started</outageStatusReason> <outageType>FORCED</outageType> <RIMSProjectCommissionDate>2014-01-31T13:30:00Z</RIMSProjectCommissionDate> <RIMSProjectCompletion>YES</RIMSProjectCompletion> <RIMSProjectID>RIMS001</RIMSProjectID> <RIMSProjectPhase>Phase 3</RIMSProjectPhase> <versionID>2</versionID> <actualPeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </actualPeriod> <Equipments> <mRID>Conductor_1234</mRID> <name>ISONameLineA_seg1</name> <Names> <name>ParticipantNameLineA</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <PSRType> <type>ACLINESEGMENT</type> </PSRType> <OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <mRID>Switch_1234</mRID> <name>ISONameSwitch1</name> <Names> <name>ParticipantNameSwitch1</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> <Switch> <mRID>Switch_2345</mRID> <name>ISONameSwitch2</name> <Names> <name>ParticipantNameSwitch2</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> </Equipments> <Equipments> <mRID>Conductor_1235</mRID> <name>ISONameLineA_seg2</name> <Names> <name>ParticipantNameLineA</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <PSRType> <type>ACLINESEGMENT</type> </PSRType>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete> <useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <mRID>Switch_3234</mRID> <name>ISONameSwitch3</name> <Names> <name>ParticipantNameSwitch3</name> <NameType> <name>PARTICIPANTNAME</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> <Switch> <mRID>Switch_4345</mRID> <name>ISONameSwitch4</name> <Names> <name>ParticipantNameSwitch4</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> </Equipments> <estimatedPeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:00:00Z</start> </estimatedPeriod> <OperatingParticipant> <mRID>PTCP</mRID> <Person> <firstName>Joanne</firstName> <lastName>Jones</lastName> <landlinePhone>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<areaCode>916</areaCode> <localNumber>5551234</localNumber> </landlinePhone> </Person> </OperatingParticipant> <OutageGroup> <mRID>Group1</mRID> <description>Group for trumped outages</description> <createdDateTime>2014-01-20T16:30:00Z</createdDateTime> <lastModifiedDateTime>2014-01-20T16:30:00Z</lastModifiedDateTime> <createdBy>ISO OC1</createdBy> <lastModifiedBy>ISO OC1</lastModifiedBy> </OutageGroup> <Work> <kind>OUT_OF_SERVICE</kind> </Work> <isNewEquipmentEnergized>YES</isNewEquipmentEnergized> </TransmissionOutage> </MessagePayload> </TransmissionOutageResults>

7.7.4 Example XML file (TransmissionOutageResultsChangeRequests_v2.xml)

<?xml version="1.0" encoding="UTF-8"?>  <TransmissionOutageResults xsi:schemaLocation="http://www.caiso.com/soa/TransmissionOutageResults_v2.xsd# TransmissionOutageResults_v1.xsd" xmlns="http://www.caiso.com/soa/TransmissionOutageResults_v2.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>String</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <TransmissionOutage> <mRID>123456789</mRID> <description>Line work to install new equipment.</description> <comment>Out for Maintenance</comment> <createdBy>John Smith</createdBy> <createdDateTime>2014-01-20T16:30:00Z</createdDateTime> <lastModifiedDateTime>2014-01-23T13:30:00Z</lastModifiedDateTime> <lastUpdatedBy>John Smith</lastUpdatedBy> <affectsRASSPS>NO</affectsRASSPS> <discoveryDateTime>2014-01-20T16:15:00Z</discoveryDateTime>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<emergencyReturnTime>2</emergencyReturnTime> <emergencyReturnTimeType>HOURS</emergencyReturnTimeType> <isFinalApprovalReq>YES</isFinalApprovalReq> <mktOrgOutageID>P123456789</mktOrgOutageID> <outageStatus>OUT_OK</outageStatus> <outageStatusReason>Outage Started</outageStatusReason> <outageType>FORCED</outageType> <RIMSProjectCommissionDate>2014-01-31T13:30:00Z</RIMSProjectCommissionDate> <RIMSProjectCompletion>YES</RIMSProjectCompletion> <RIMSProjectID>RIMS001</RIMSProjectID> <RIMSProjectPhase>Phase 3</RIMSProjectPhase> <versionID>2</versionID> <actualPeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </actualPeriod> <Equipments> <mRID>Conductor_1234</mRID> <name>ISONameLineA_seg1</name> <Names> <name>ParticipantNameLineA</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <PSRType> <type>ACLINESEGMENT</type> </PSRType> <OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete> <useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <mRID>Switch_1234</mRID> <name>ISONameSwitch1</name> <Names> <name>ParticipantNameSwitch1</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<Switch> <mRID>Switch_1234</mRID> <name>ISONameSwitch1</name> <Names> <name>ParticipantNameSwitch1</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> </Equipments> <Equipments> <mRID>Conductor_1235</mRID> <name>ISONameLineA_seg2</name> <Names> <name>ParticipantNameLineA</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <PSRType> <type>ACLINESEGMENT</type> </PSRType> <OutagedEquipment> <switchModelingComplete>NO</switchModelingComplete> <useFacilityOutageDefinition>NO</useFacilityOutageDefinition> <Switch> <mRID>Switch_3234</mRID> <name>ISONameSwitch3</name> <Names> <name>ParticipantNameSwitch3</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


</SwitchingOperations> </Switch> <Switch> <mRID>Switch_4345</mRID> <name>ISONameSwitch4</name> <Names> <name>ParticipantNameSwitch4</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> <SwitchingOperations> <newState>open</newState> <newStatePeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:30:00Z</start> </newStatePeriod> </SwitchingOperations> </Switch> </OutagedEquipment> </Equipments> <estimatedPeriod> <end>2014-01-31T13:00:00Z</end> <start>2014-01-23T13:00:00Z</start> </estimatedPeriod> <OperatingParticipant> <mRID>PTCP</mRID> <Person> <firstName>Joanne</firstName> <lastName>Jones</lastName> <landlinePhone> <areaCode>916</areaCode> <localNumber>5551234</localNumber> </landlinePhone> </Person> </OperatingParticipant> <OutageChangeRequest> <mRID>912345678</mRID> <action>UPDATE</action> <status>ACCEPTED</status> <statusReason>APPROVED</statusReason> </OutageChangeRequest> <OutageGroup> <mRID>Group1</mRID> <description>Group for trumped outages</description> <createdDateTime>2014-01-20T16:30:00Z</createdDateTime> <lastModifiedDateTime>2014-01-20T16:30:00Z</lastModifiedDateTime> <createdBy>ISO OC1</createdBy> <lastModifiedBy>ISO OC1</lastModifiedBy>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


</OutageGroup> <Work> <kind>OUT_OF_SERVICE</kind> </Work> <isNewEquipmentEnergized>YES</isNewEquipmentEnergized> </TransmissionOutage> </MessagePayload> </TransmissionOutageResults>

7.8 Fault Return


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


8. Retrieve Availability

8.1 Overview

Outage Coordinators can retrieve the availability profile of a generating resource.








30 minutes

Business impact if is unavailable The availability profile will be viewable in the OMS user interface.



8.3 Use Model


8.3.1 Retrieve Availability

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10




8.4.1 Retrieve Availability

Operation Message

Types

Message WSDL XSD

retrieveAvailability Input retrieveAvailability retrieveAvailability_v1.

wsdl/

retrieveAvailability_v1

_DocAttach.wsdl

requestAvailability_v1.xsd

Output retrieveAvailability

Response

AvailabilityResults_v1.xsd


8.5 WSDL

8.5.1 retrieveAvailability_v1.wsdl / retrieveAvailability_v1_DocAttach.wsdl

8.6 Retrieve Availability

Request Criteria Input Parameters Results Date Range Range start and end date and

Effective Date (optional) Availability points for all resources that the requester has access to for the date range specified with optional availability effective date

Participant MktOrganization mrid and Range start and end date and and Effective Date (optional)

Availability points for all resources associated with the specified MktOrganization mrid that the requester has access to for the date range specified with optional availability effective date

sd retriev e Av ailability

Participant

OMS

retrieveAvailabil ity()

retrieveAvailabil ityResponse()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Resource RegisteredGenerator mrid and Range start and end date and and Effective Date (optional)

Availability points for the resource(s) specified and for the date range specified with optional availability effective date

8.6.1 Element Table


Format/ Length

Req’d

Message Header





String Yes

MessagePayload.Resource Yes

effectiveDateTime Provides an optional method for viewing data as of a specific time

dateTime No

rangePeriod Start and end date of the period being requested dateTime Yes

Choice of RegisteredGenerator or RegisteredIntertie or RegisteredLoad

mrid Unique Identifier of the resource being requested String Yes

8.6.2 Schema (RequestAvailability_v1.xsd)

8.6.3 Example XML File (RequestAvailability_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <RequestAvailability xsi:schemaLocation="http://www.caiso.com/soa/RequestAvailability_v1.xsd# RequestAvailability_v1.xsd" xmlns="http://www.caiso.com/soa/RequestAvailability_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-04-01T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <Resource> <effectiveDateTime>2014-03-15T09:00:00Z</effectiveDateTime> <rangePeriod>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<end>2014-04-01T00:00:00Z</end> <start>2014-03-01T00:00:00Z</start> </rangePeriod> <RegisteredGenerator> <mRID>ResourceA</mRID> </RegisteredGenerator> </Resource> <Resource> <rangePeriod> <end>2014-04-01T00:00:00Z</end> <start>2014-03-01T00:00:00Z</start> </rangePeriod> <RegisteredGenerator> <mRID>ResourceA</mRID> </RegisteredGenerator> </Resource> </MessagePayload> </RequestAvailability>

8.7 Request Availability Response

8.7.1 Element Table


Format/ Length

Req’d

Message Header No


dateTime Yes




String Yes

MessagePayload.RegisteredGenerator No

mRID The resource id for the RegisteredGenerator. String No

Name An alternate name from the Participant String No

MessagePayload.RegisteredGenerator.LogicalConfiguration No

MessagePayload.RegisteredGenerator.LogicalConfiguration.Configuration Yes


String No

Name An alternate name from the Participant. String No

MessagePayload.RegisteredGenerator.Logicalconfiguration.Configuration.OutagedRegisteredResource(

Required=Yes)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

MessagePayload.RegisteredGenerator.Logicalconfiguration.Configuration.OutagedRegisteredResource

.Availability Yes



MessagePayload.RegisteredGenerator.OutagedRegisteredResource Yes

MessagePayload.RegisteredGenerator.OutagedRegisteredResource.Availability Yes

8.7.2 Schema (AvailabilityResults_v1.xsd)

8.7.3 Example XML File (AvailabilityResults_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <AvailabilityResults xmlns="http://www.caiso.com/soa/AvailabilityResults_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.caiso.com/soa/AvailabilityResults_v1.xsd# AvailabilityResults_v1.xsd "> <MessageHeader> <TimeDate>2014-04-01T09:31:00Z</TimeDate> <Source>String</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <RegisteredGenerator> <mRID>ResourceA</mRID> <name>Resource Alpha</name> <LogicalConfiguration> <Configuration> <mRID>ResA1x1</mRID> <name>Resource Alpha 1x1</name> <OutagedRegisteredResource> <Availability> <dateTimePoint>2014-01-17T13:00:00Z</dateTimePoint> <OutagedRegisteredResource> <RegisteredResource> <RegisteredResourceOutage> <mRID>12345</mRID> <PMaxCurtailment> <activePeriod> <start>2014-01-17T10:00:00Z</start> </activePeriod> <restrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>50</value>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


</restrictedValue> </PMaxCurtailment> </RegisteredResourceOutage> </RegisteredResource> </OutagedRegisteredResource> <PmaxValue> <multiplier>M</multiplier> <unit>W</unit> <value>100</value> </PmaxValue> </Availability> </OutagedRegisteredResource> </Configuration> </LogicalConfiguration> <OutagedRegisteredResource> <Availability> <dateTimePoint>2001-12-31T12:00:00</dateTimePoint> <OutagedRegisteredResource> <RegisteredResource> <RegisteredResourceOutage> <mRID>12345</mRID> <PMaxCurtailment> <activePeriod> <start>2001-12-31T12:00:00</start> </activePeriod> <restrictedValue> <multiplier>M</multiplier> <unit>W</unit> <value>30</value> </restrictedValue> </PMaxCurtailment> </RegisteredResourceOutage> </RegisteredResource> </OutagedRegisteredResource> <PmaxValue> <multiplier>M</multiplier> <unit>W</unit> <value>100</value> </PmaxValue> </Availability> </OutagedRegisteredResource> </RegisteredGenerator> </MessagePayload> </AvailabilityResults>

8.8 Fault Return


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


9. Retrieve Facility Outage Definition

9.1 Overview

Outage Coordinators can retrieve the pre-agreed switch positions for out of service equipment.








30 minutes

Business impact if is unavailable The Outage coordinator will not be able to access the pre-canned facility outage definition. The definitions are constant across network model updates.



9.3 Use Model


9.3.1 Retrieve Facility Outage Definition

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10





Operation Message

Types

Message WSDL XSD

retrieveFacilityouta

geDefinition

Input retrieveFacilityOutag

eDefinition

retrieveFacilityoutage

Definition_v1.wsdl/

retrieveFacilityoutage

Definition_v1_DocAtt

ach.wsdl

requestFacilityoutageDefinition_

v1.xsd

Output retrieveFacilityOutag

eDefinitionResponse

FacilityOutageDefinitionResults

_v1.xsd


9.5 WSDL

9.5.1 retrieveFacilityOutageDefinition_v1.wsdl / retrieveFacilityOutageDefinition_v1_DocAttach.wsdl

9.6 Retrieve Facility Outage Definition

Request Criteria Input Parameters Results

Participant MktOrganization mrid

The facility outage definitions for all equipment associated with the specified MktOrganization mrid that the requester has access

Equipment Equipment mrid or (Equipment Names.name and Equipment Names.NameType.name = PARTICIPANTID)

The facility outage definition for the equipment specified

sd retriev e Facility Outage Definition

Outage Coordinator

OMS

retrieveFacilityOutageDefinition()

retrieveFacilityOutageDefinitionResponse()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


9.6.1 Element Table


Format/ Length

Req’d

Message Header No





String Yes

MessagePayload.Facility.Equipment No

mRID The resource id for the Equipment. String No

Names.name ISO Name for the equipment. ISO or Participant name is required.

String No

Names.NameType.name

Name of the name type.

PARTICIPANTID

Enumeration

No

MessagePayload.Participant.MktOrganisation No

mRID Market Oragnisation ID String No

9.6.2 Schema (requestFacilityOutageDefinition_v1.xsd)

9.6.3 Example XML File (RequestFacilityOutageDefinition_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <RequestFacilityOutageDefinition xsi:schemaLocation="http://www.caiso.com/soa/RequestFacilityOutageDefinition_v1.xsd# RequestFacilityOutageDefinition_v1.xsd" xmlns="http://www.caiso.com/soa/RequestFacilityOutageDefinition_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-01-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <Participant> <MktOrganisation> <mRID>PCG2</mRID> </MktOrganisation> </Participant>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<Facility> <Equipment> <mRID>12345</mRID> <Names> <name>LINE-A</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> </Equipment> <Equipment> <mRID>54321</mRID> <Names> <name>LINE-B</name> <NameType> <name>PARTICIPANTID</name> </NameType> </Names> </Equipment> </Facility> </MessagePayload> </RequestFacilityOutageDefinition>

9.7 Request Facility Outage Response

9.7.1 Element Table


Format/

Length

Req’d

Message Header No


dateTime Yes




String Yes

MessagePayload.Contingency Yes

mRID Contingency Identifier String Yes

definitionEndDateTime End date/time of this definition DateTime No

definitionStartDateTime Start date/time of this definition DateTime No

MessagePayload.Contingency.ContingencyElement Yes

switchStatus Status of associated Switching Element String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/

Length

Req’d

MessagePayload.Contingency.ContingencyElement.Equipment Yes

mRID The resource id for the Equipment. String Yes

name ISO Name for the equipment. ISO or Participant name is required.

String Yes

Names All Names of this identified Object Name(Complex Type)

No

MessagePayload.Contingency.Equipment No



String Yes


No

PSRType Custom classification for this power system String Yes

MessagePayload.Contingency.EquipmentContainer No



String Yes


No

PSRType Custom classification for this power system

ACLINESEGMENT, BUSBARSECTION, CONFORMLOAD, DCLINESEGMENT, ENERGYCONSUMER, NONCONFORMLOAD, POWERTRANSFORMER, SERIESCOMPENSATOR, SHUNTCOMPENSATOR, STATICVARCOMPENSATOR

Enumeration

Yes

9.7.2 Schema (FacilityOutageDefinitionResults_v1.xsd)

9.7.3 Example XML File (FacilityOutageDefinitionResults_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <FacilityOutageDefinitionResults xmlns="http://www.caiso.com/soa/FacilityOutageDefinitionResults_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


xsi:schemaLocation="http://www.caiso.com/soa/FacilityOutageDefinitionResults_v1.xsd# FacilityOutageDefinitionResults_v1.xsd "> <MessageHeader> <TimeDate>2014-01-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <Contingency> <mRID>ContingnecyId: 1234</mRID> <definitionEndDateTime>2014-12-31T12:00:00</definitionEndDateTime> <definitionStartDateTime>2015-12-31T12:00:00</definitionStartDateTime> <ContingencyElement> <switchStatus>Closed</switchStatus> <Equipment> <mRID>12345</mRID> <name>LineA</name> <Names> <name>AlternativeName for LineA</name> <NameType> <name>name</name> </NameType> </Names> </Equipment> </ContingencyElement> <Equipment> <mRID>54321</mRID> <name>LineB</name> <Names> <name>Alternative Name for Line-B</name> <NameType> <name>name</name> </NameType> </Names> <PSRType> <type>ACLINESEGMENT</type> </PSRType> </Equipment> </Contingency> </MessagePayload> </FacilityOutageDefinitionResults>

9.8 Fault Return


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


10. Withdraw Outage Change Request

10.1 Overview

Outage Coordinators can withdraw a previously submitted but not yet approved change request for generator and transmission outage.








30 minutes

Business impact if is unavailable The Outage coordinator can use the user interface or call the ISO directly to withdraw the change request.



10.3 Use Model



cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10





Operation Message

Types

Message WSDL XSD

withdrawOutageCh

angeRequest

Input withdrawOutageChan

geRequest

withdrawOutageChan

geRequest_v1.wsdl

withdrawOutageChangeRequest

_v1.xsd

Output withdrawOutageChan

geRequestResponse



10.5 WSDL

10.5.1 withdrawOutageChangeRequest_v1.wsdl

10.6 Withdraw Outage ChangeRequest

10.6.1 Element Table


Format/ Length

Req’d

Message Header





String Yes

MessagePayload.OutageChangeRequest Yes

sd Withdraw Outage Change Request

Outage Coordinator

OMS

withdrawOutageChangeRequest()

withdrawOutagechagneRequestStandardOutput()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

mRID ISO identifier for the change request. String Yes

10.6.2 Schema (WithdrawOutageChangeRequest_v1.xsd)

10.6.3 Example XML File (WithdrawOutageChangeRequest_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <WithdrawOutageChangeRequest xsi:schemaLocation="http://www.caiso.com/soa/WithdrawOutageChangeRequest_v1.xsd# WithdrawOutageChangeRequest_v1.xsd" xmlns="http://www.caiso.com/soa/WithdrawOutageChangeRequest_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <OutageChangeRequest> <mRID>912345677</mRID> </OutageChangeRequest> <OutageChangeRequest> <mRID>912345679</mRID> </OutageChangeRequest> </MessagePayload>

</WithdrawOutageChangeRequest>

10.7 Withdraw Outage Change Request Standard Output


See OutageStandardOutput

10.7.2 Schema (StandardOutput_v1.xsd)

10.7.3 Example XML File (WithdrawOutageChangeRequestStandardOutput_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <OutageStandardOutput xsi:schemaLocation="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd# OutageStandardOutput_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-01-03T11:00:00Z</TimeDate>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <EventLog> <Event> <id>1</id> <result>Success</result> </Event> <Outage> <mRID>123456789</mRID> <mktOrgOutageID>MarketOutageId-1234</mktOrgOutageID> <OutageValidation> <submitStatus>ACCEPTED</submitStatus> <OutageResult> <mRID>1</mRID> <description>Validated</description> <status>ACKNOWLEDGED</status> <type>INFO</type> </OutageResult> </OutageValidation> </Outage> <Service> <id>12345</id> <name>withdrawOutagechangeRequest_v1</name> </Service> </EventLog> </MessagePayload> </OutageStandardOutput>

10.8 Fault Return


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


11. Acknowledge Outage Warning

11.1 Overview

Outage Coordinators must acknowledge review of warnings associated with outages. For example, when a transmission outage trumps a previously submitted outage.








30 minutes

Business impact if is unavailable No impact, not time critical.



11.3 Use Model


11.3.1 Acknowledge Outage Warning

sd Acknowledge Outage Warning

Outage Coordinator

OMS

AcknowledgeOutageWarning()

AcknowledgeOutageWarningStandardOutput()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10





Operation Message

Types

Message WSDL XSD

AcknowledgeOu

tageWarning

Input AcknowledgeOutageW

arning

acknowledgeOutageW

arning_v1.wsdl

AcknowledgeOutageWarning_v

1.xsd

Output AcknowledgeOutageW

arningStandardOutput



11.5 WSDL

AcknowledgeOutageWarning_v1.wsdl

11.6 Acknowledge Outage Warning



Format/ Length

Req’d

Message Header No





String Yes

MessagePayload.OutageResult Yes

mRID ISO identifier for the outage warning. String Yes

11.6.2 Schema (AcknowledgeOutageWarning_v1.xsd)

11.6.3 Example XML File (AcknowledgeOutageWarning_v1.xml)

<?xml version="1.0" encoding="UTF-8"?>  <AcknowledgeOutageWarning xsi:schemaLocation="http://www.caiso.com/soa/AcknowledgeOutageWarning_v1.xsd# AcknowledgeOutageWarning_v1.xsd" xmlns="http://www.caiso.com/soa/AcknowledgeOutageWarning_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<MessageHeader> <TimeDate>2001-12-17T09:30:47Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <OutageResult> <mRID>Outage_Result_Id_1</mRID> </OutageResult> <OutageResult> <mRID>Outage_Result_Id_2</mRID> </OutageResult> </MessagePayload> </AcknowledgeOutageWarning>

11.7 Acknowledge Outage Warning Standard Output


See OutageStandardOutput


11.7.3 Example XML File (AcknowledgeOutageWarningStandardOutput_v1.xml)

<?xml version="1.0" encoding="UTF-8"?> <OutageStandardOutput xsi:schemaLocation="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd# OutageStandardOutput_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStandardOutput_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-01-03T11:00:00Z</TimeDate> <Source>CompanyA</Source> <Version>v20141001</Version> </MessageHeader> <MessagePayload> <EventLog> <Event> <id>1</id> <result>Success</result> </Event> <Outage> <mRID>123456789</mRID> <mktOrgOutageID>MarketOutageId-1234</mktOrgOutageID> <OutageValidation> <submitStatus>ACCEPTED</submitStatus> <OutageResult> <mRID>1</mRID> <description>Validated</description>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<status>ACKNOWLEDGED</status> <type>INFO</type> </OutageResult> </OutageValidation> </Outage> <Service> <id>12345</id> <name>acknowledgeOutageWarning_v1</name> </Service> </EventLog> </MessagePayload> </OutageStandardOutput> For Fault return see section Fault Return

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


12. Outage Status Update

12.1 Overview

Outage Coordinators, after registering their endpoint, can receive a message when an outage status changes.








30 minutes

Business impact if is unavailable Messages will be sent as soon as service is restored.



12.3 Use Model

The sequence diagram below describes the service level interactions between the ISO Outage Management System (OMS) and the Outage Coordinator systems. These messages are sent from the OMS so the security model is different than the regular B2B services. These messages use one way authentication between the OMS hosting service and the participant’s servers.

12.3.1 Acknowledge Outage Warning

sd Outage Status Update

OMS

Outage Coordinator

OutageStatusUpdate()

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10




12.4.1 Outage Status Update

Operation Message

Types

Message WSDL XSD

OutageStatusUp

date

Input OutageStatusUpdate OutageStatusUpdate_v

1.wsdl

OutageStatusUpdate _v1.xsd

Output OutageStatusUpdateRe

sponse

StandardOutput.xsd


12.5 WSDL

12.5.1 OutageStatusUpdate_v1.wsdl

12.6 Outage Status Update

Element Table


Format/ Length

Req’d

Message Header No



Version Subversion of the XSD: Initial version will be v20141001

String Yes

MessagePayload.Outage Yes

mRID ISO identifier for the outage. String Yes

isFinalApprovalReq Notification of Final Approval Required Yes/No Yes

mktOrgOutageID The participant’s identifier for the outage String No

outageStatus The new status of the outage String Yes

outageStatusReason The reason for the change in status String No

MessagePayload.Outage.OutageChangeRequest No

mRID Identifier for the change request String Yes

Action Original action for the change request String Yes

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10



Format/ Length

Req’d

ActionReason Reason For change OutageChangeRequestActionReason ( Enumeration fo string values)

No

ActionSubType For update, define the type of update. OutageChangeRequestActionSubType ( Enumeration fo string values)

No

Status Status of the change request String Yes

MessagePayload.Outage.OutageGroup No

mRID Identifier for a group the outage belongs to String Yes

MessagePayload.Outage.OutageValidation No

MessagePayload.Outage.OutageValidation.OutageResult Yes

mRID ID assigned to the result by the ISO String Yes



String Yes

Type Type of result: ERROR, INFO, WARNING String Yes

MessagePayload.Outage.MarketOrganization No

mRID ID assigned to the generator participant by the ISO String Yes

MessagePayload.Outage.OperatingParticipant No

mRID ID assigned to the transmission participant by the ISO String Yes

12.6.1 Schema (OutageStatusUpdate_v1.xsd)

12.6.2 Example XML File (OutageStatusUpdate_v1.xml) for a Generation Outage

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<?xml version="1.0" encoding="UTF-8"?>  <OutageStatusUpdate xsi:schemaLocation="http://www.caiso.com/soa/OutageStatusUpdate_v1.xsd# OutageStatusUpdate_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStatusUpdate_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-02-17T09:30:47Z</TimeDate> <Source>OMS</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <Outage> <mRID>123456789</mRID> <isFinalApprovalReq>NO</isFinalApprovalReq> <mktOrgOutageID>P123456789</mktOrgOutageID> <outageStatus>CANCELLED</outageStatus> <outageStatusReason>Cancelled by Participant</outageStatusReason> <MarketOrganization> <mRID>XYZ1</mRID> </MarketOrganization> <OutageChangeRequest> <mRID>987654321</mRID> <action>CANCEL</action> <status>ACCEPTED</status> </OutageChangeRequest> </Outage> </MessagePayload> </OutageStatusUpdate>

12.6.3 Example XML File (OutageStatusUpdate_v1.xml) for a Transmission Outage

<?xml version="1.0" encoding="UTF-8"?>  <OutageStatusUpdate xsi:schemaLocation="http://www.caiso.com/soa/OutageStatusUpdate_v1.xsd# OutageStatusUpdate_v1.xsd" xmlns="http://www.caiso.com/soa/OutageStatusUpdate_v1.xsd#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <MessageHeader> <TimeDate>2014-02-17T09:30:47Z</TimeDate> <Source>OMS</Source> <Version>v20160301</Version> </MessageHeader> <MessagePayload> <Outage> <mRID>123456789</mRID> <isFinalApprovalReq>NO</isFinalApprovalReq> <mktOrgOutageID>P123456789</mktOrgOutageID> <outageStatus>CANCELLED</outageStatus>

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


<outageStatusReason>Cancelled by Participant</outageStatusReason> <OperatingParticipant> <mRID>ABC1</mRID> </OperatingParticipant> <OutageChangeRequest> <mRID>987654321</mRID> <action>CANCEL</action> <status>ACCEPTED</status> </OutageChangeRequest> </Outage> </MessagePayload> </OutageStatusUpdate>

12.7 Standard Output


See StandardOutput


12.7.3 Example XML File

The ISO would look for any successful response code.

12.8 Fault Return


cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


13. Appendix

13.1 Communication Equipment

Participant Communications Equipment Participant ID

Communications Equipment Participant Name

SCE ICCP_Data_Links_SCE ICCP Data Links SCE Communication_Circuits_SCE Communication Circuits SCE EMS_SCE EMS SCE Dispatch_Center_SCE Dispatch Center SCE Control_Systems_SCE Control Systems SCE Metering_SCE Metering SCE Microwave_System_SCE Microwave System SCE SCADA_SCE SCADA SCE RAS_Equipment_SCE RAS Equipment SCE RTU_SCE RTU SCE Intertie_Protection_Schemes_SCE Intertie Protection Schemes SCE Intertie_Metering_SCE Intertie Metering SCE Interruptible_Load_SCE Interruptible Load SCE SONET_System_SCE SONET System SCE Four_Corners_Transfer_Trip_SCE Four Corners Transfer Trip SCE Internet_Intranet_Equipment_SCE Internet/Intranet Equipment SCE Fiber_Optic_Cables_SCE Fiber Optic Cable(s) SCE Phone_Circuits_Equipment_SCE Phone/Circuits Equipment SCE

PGAE ICCP_Data_Links_PGAE ICCP Data Links PGAE Communication_Circuits_PGAE Communication Circuits PGAE EMS_PGAE EMS PGAE Dispatch_Center_PGAE Dispatch Center PGAE Control_Systems_PGAE Control Systems PGAE Metering_PGAE Metering PGAE Microwave_System_PGAE Microwave System PGAE SCADA_PGAE SCADA PGAE RAS_Equipment_PGAE RAS Equipment PGAE RTU_PGAE RTU PGAE Intertie_Protection_Schemes_PGAE Intertie Protection Schemes PGAE Intertie_Metering_PGAE Intertie Metering PGAE Interruptible_Load_PGAE Interruptible Load PGAE SONET_System_PGAE SONET System PGAE Four_Corners_Transfer_Trip_PGAE Four Corners Transfer Trip PGAE Internet_Intranet_Equipment_PGAE Internet/Intranet Equipment PGAE Fiber_Optic_Cables_PGAE Fiber Optic Cable(s) PGAE Phone_Circuits_Equipment_PGAE Phone/Circuits Equipment PGAE

SDGE ICCP_Data_Links_SDGE ICCP Data Links SDGE Communication_Circuits_SDGE Communication Circuits SDGE EMS_SDGE EMS SDGE Dispatch_Center_SDGE Dispatch Center SDGE

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


Control_Systems_SDGE Control Systems SDGE Metering_SDGE Metering SDGE Microwave_System_SDGE Microwave System SDGE SCADA_SDGE SCADA SDGE RAS_Equipment_SDGE RAS Equipment SDGE RTU_SDGE RTU SDGE Intertie_Protection_Schemes_SDGE Intertie Protection Schemes SDGE Intertie_Metering_SDGE Intertie Metering SDGE Interruptible_Load_SDGE Interruptible Load SDGE SONET_System_SDGE SONET System SDGE Four_Corners_Transfer_Trip_SDGE Four Corners Transfer Trip SDGE Internet_Intranet_Equipment_SDGE Internet/Intranet Equipment SDGE Fiber_Optic_Cables_SDGE Fiber Optic Cable(s) SDGE Phone_Circuits_Equipment_SDGE Phone/Circuits Equipment SDGE

VEA Fiber_Optic_Cables_VEA Fiber Optic Cable(s) VEA Phone_Circuits_Equipment_VEA Phone/Circuits Equipment VEA EMS_VEA EMS VEA Dispatch_Center_VEA Dispatch Center VEA Control_Systems_VEA Control Systems VEA Metering_VEA Metering VEA Microwave_System_VEA Microwave System VEA SCADA_VEA SCADA VEA RAS_Equipment_VEA RAS Equipment VEA RTU_VEA RTU VEA Intertie_Protection_Schemes_VEA Intertie Protection Schemes VEA Intertie_Metering_VEA Intertie Metering VEA Interruptible_Load_VEA Interruptible Load VEA SONET_System_VEA SONET System VEA Four_Corners_Transfer_Trip_VEA Four Corners Transfer Trip VEA Internet_Intranet_Equipment_VEA Internet/Intranet Equipment VEA Fiber_Optic_Cables_VEA Fiber Optic Cable(s) VEA Phone_Circuits_Equipment_VEA Phone/Circuits Equipment VEA

13.2 WebOMS Error Codes

13.2.1 Transmission Error Codes

Code Message

1000 Defined Participant is not valid for the current user.

1002 Submitted Outage Class is not valid for the submitted Participant.

1004 Outage Start Time is too far in the past.

1005 Submitted outage request requires Emergency Return Time to be defined.

1006 Request submitted with Nature of Work that does not allow overlapping outages (Participant Outage ID :).

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


1007 Submitted outage request exceeds the duration limit for the selected Nature of Work.

1008 Submitted outage request references an invalid Nature of Work for the submitting user.

2005 Discovery Date/Time must be between 1900 and 3000.

2007 Nature of Work is a required attribute of the outage request submission.

2008 Description is a required attribute of the outage request submission.

2009 Participant Outage ID is a required attribute of the outage request submission.

2022 Outage request duration is not valid for the duration of the planned outage period based on the Equipment/Participant relationship.

2023 Only manually entered equipment can be used with the COMMUNICATIONS Nature of Work.

2025 Estimated Start Time should be less than Estimated End Time.

2026 Actual Start Time should be less than Actual End Time.

2027 Nature of Work is not valid to submit Transmission Outage.

2028 At least one piece of equipment must be defined for a valid outage definition.

2029 Modelling must be entered when using Nature of Work OUT_OF_SERVICE.

2031 Outage ID %d already has a pending request, a new request cannot be submitted.

2037 Emergency Return Time is invalid, duration defined is longer than outage duration

2038 Normal Rating Change value must be defined if Emergency Rating Change value is defined

2039 Emergency Rating Change value must be defined if Normal Rating Change value is defined

2040 Equipment Normal Rating Change must be less than or equal to the Emergency Rating Change value

2041 Equipment Normal Rating can not be negative

2042 Equipment Emergency Rating can not be negative

2044 Switch modelling start date/time is inconsistent with the outage start date/time range.

2045 Switch modelling end date/time is inconsistent with the outage end date/time range.

2047 Switch modelling overlaps with another switch modelling with different modelling state and can not be submitted.

2048 Confirmed By user can not be the same as the Modeled By user.

2049 Equipment Rating Change start date/time is inconsistent with the outage start date/time range.

2050 Equipment Rating Change end date/time is inconsistent with the outage end date/time range.

2051 Outage on shared equipment conflicts with an existing outage submitted by another participant. Contact CAISO to resolve outage conflicts.

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


2052 Confirmed By user can not be set if the Modelled By User is not set.

2053 Requested outage has overlapping equipment with one or more outages with pending requests - Outage IDs - (Participant Outage ID :) -

2054 Requested outage request has overlapping equipment with one or more outages with pending requests - Outage IDs - (Participant Outage ID :) -

2083 Referenced Equipment ID is not unique.

2085 Outage Date/Times cannot be changed within the same request that changes an outage state to {0}.

2090 Emergency Return Time must be non-negative.

2091 Discovery Date/Time is not editable.

2092 Switch modelling contains invalid switch.

2093 Referenced Switch Name is not unique.

2094 Switch modelling contains invalid switch

2095 Invalid outage code was submitted.

2096 At least one Primary outage code must be submitted for a Forced outage.

2097 At least one Secondary outage code must be submitted for a Forced outage.

2098 Selected Nature of Work requires at least one Equipment Rating Change to be defined

2100 At least one equipment has pending ownership change during the planned outage period.

2101 Switch Modeling is not allowed when Nature of Work is

2102 Switch Modeling must be entered when Nature of Work is

2103 Switch Modeling must include CLOSED status when Nature of Work is OUT_OF_SERVICE_WITH_SPECIAL_SETUP.

2104 Equipment of type COMMUNICATIONS can only be on an outage with a Nature of work of COMMUNICATIONS.

2105 Outages with a Nature of Work of COMMUNICATIONS can only have equipment of type COMMUNICATIONS.

2106 Equipment of type PATH_LIMITS can only be on an outage with a Nature of work of PATH_LIMITATIONS.

2107 Equipment submitted with outage is not valid for Nature of Work of PATH_LIMITATIONS.

2108 Outage request duration is not valid for the duration of the planned outage period based on the Switch/Participant relationship.

3061 Actual Start Date/Time can only be submitted when transitioning to OUT State.

3062 Actual Start Time cannot be before the Planned Start Time, when the Planned Start Time is in the future.

3063 Actual End Date/Time can only be submitted when transitioning to IN_SERVICE_EDITABLE State.

3064 Equipment Rating Change start time should be less than end time.

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


3065 Equipment Rating Change section has overlapping time range.

3068 Normal and Emergency Ratings are required in Equipment Rating Changes.

3069 Equipment Rating change data must be defined for all equipments for EQUIPMENT_DERATE Nature of Work.

3070 Equipment must be added in Equipment Grid for all selected Rating change data for EQUIPMENT_DERATE Nature of Work.

3071 Outage must have 1 piece of Equipment besides Equipment Rating change data.

3072 Equipment that has Rating Change data can not also have Switch Modelling defined for the equipment

13.2.2 Generation Error Codes

Code Message

7001 Unknown resource for participant

7002 Participant not allowed to submit resource outage

7008 User does not have privilege to modify outage for participant

7021 Outage request to CANCEL or DISAPPROVE outage cannot change estimated start/end times

7022 Outage request overlaps with pending request on another outage (Participant Outage ID: ) on the same resource

7023 Invalid outage change request without action (UPDATE or CANCEL)

7024 Invalid outage change request without outage ID

7025 Outage ID on outage change request does not exist

7027 Invalid outage request without resource mRID or name

7028 Participant does not own resource at start time of outage

7029 Participant does not own resource at end time of outage

7030 Resource has ownership has gap for participant during the outage

7031 Outage on change request already contains a request in pending state

7032 Outage on change request is in final state and cannot be changed

7033 Estimated end date/time of outage must be later than estimated start date/time of outage

7034 WARNING: Actual start time cannot be submitted via the API for this state transition

7035 Invalid resource - not found

7036 Invalid resource - resource is decommissioned prior to end date/time of outage

7038 Resource in outage change request is different from resource in outage

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7039 Multiple resources with same name - please provide outage request with resource mRID

7040 Resource availability in outage request contains multiple identical breakpoints

7041 Resource MSG configuration availability in outage request contains multiple identical breakpoints

7042 Invalid generating unit availability information for MSG resource

7043 Invalid MSG configuration information for aggregate resource

7044 Missing generating unit availability information for aggregate resource

7045 Missing resource availability information when generating unit availability information provided

7046 Missing MSG configuration availability information for MSG resource

7047 Missing resource availability information when MSG configuration availability information provided

7048 MSG configuration information with no MSG configuration mRID or name

7049 Unknown MSG configuration mRID

7050 Unknown MSG configuration name

7051 MSG configuration not defined at end date/time of outage

7053 Outage start time is too far in the past

7054 Outage emergency return time not provided

7055 Invalid emergency return time beyond outage end date/time

7056 Invalid Nature of Work for outage class

7057 Outage duration exceeds duration limit for Nature of Work

7058 Invalid Nature of Work for user

7059 Invalid Nature of Work for non-Use Limit resource

7060 Invalid flowgate IFM/RTM percentage - must be greater than 0% and less than 100%.

7061 Invalid outage with ramp rate re-rate change extends beyond one calendar day

7062 Invalid outage with ramp rate re-rate. Start time of outage must be current calendar day when created prior to 10pm, or current/next calendar day when created at or after 10pm

7063 Invalid outage with OC Long-Term Planning and/or Off-Peak Opportunity Outage and/or Short-Notice Opportunity Outage flag. Only one of the flags can be set for an outage.

7064 Invalid Short-Notice Opportunity Outage outside of defined threshold

7065 Discovery Date/Time is not editable.

7066 Outage cannot be submitted for unclassified (UNCL) resource type

7067 Participant Outage ID required for outage submitted via web services

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7069 Invalid outage action for new outage

7070 Short-Notice Opportunity flag cannot be changed in outage change request

7071 PMinimum re-rate not allowed for resource type

7072 PMinimum re-rate profile outside of outage time

7073 Availability change not allowed for resource type

7074 Load Max de-rate not allowed for resource type

7075 Load Max de-rate profile outside of outage time

7076 Load Min re-rate not allowed for resource type

7077 Load Min re-rate profile outside of outage time

7078 Ramp rate change not allowed for resource type

7079 AS availability change not allowed for resource type

7080 Min Energy limit change not allowed for resource type

7081 Min Energy limit re-rate profile outside of outage time

7082 Max Energy limit change not allowed for resource type

7083 Max Energy limit de-rate profile outside of outage time

7084 Invalid AS availability

7085 Invalid non-zero AS availability value for market product for non-spinning reserve ancillary service

7086 Invalid non-zero AS availability value for market product for spinning reserve ancillary service

7087 Invalid non-zero AS availability value for market product for Regulation Up ancillary service

7088 Invalid non-zero AS availability value for market product for Regulation Down ancillary service

7089 Invalid AS availability - Regulation Up (RU) and Regulation Down (RD) must be provided in pairs

7090 Same AS availability provided multiple times in outage

7091 Multiple resource PMinimum re-rate for the same breakpoint

7092 Multiple MSG configuration PMinimum re-rate for the same breakpoint

7093 Multiple resource Load Max de-rate for the same breakpoint

7094 Multiple resource Load Min re-rate for the same breakpoint

7095 Multiple resource Max Energy de-rate for the same breakpoint

7096 Multiple resource Min Energy re-rate for the same breakpoint

7097 Multiple resource Use Limit for the same breakpoint

7098 Multiple resource ramp rate values for the same segment

7099 Multiple MSG configuration ramp rate values for the same segment

7100 Resource PMinimum re-rate less than minimum operating MW

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7101 MSG configuration PMinimum re-rate less than minimum operating MW

7102 Resource Load Max provided but resource does not have capacity of type LOAD

7103 Resource Load Min provided but resource does not have capacity of type LOAD

7104 Resource Energy Max provided but resource does not have capacity of type CEN

7105 Resource Energy Min provided but resource does not have capacity of type CEN

7106 Out-of-Service resource availability flag set with non-zero MW

7107 Out-of-Service and Return to Net Dependable Capacity flag for resource set for the same breakpoint

7108 Invalid resource availability reassignment in new outage request

7109 Invalid resource availability outage reassignment for non-vacated period

7110 Reassigned Resource availability outage does not exist

7111 Resource availability reassignment to outage on different resource

7112 Reassigned outage in resource availability does not overlap with vacated period

7113 Reassigned outage in resource availability is in final state

7114 Out-of-Service MSG configuration availability flag set with non-zero MW

7115 Out-of-Service and Return to Net Dependable Capacity flag for MSG configuration set for the same breakpoint

7117 User does not have privilege to create outage for participant

7118 InterTie resource is not a RA-designated resource for the entire duration of outage

7119 Invalid discovery date/time

7120 Invalid RIMS project commission date/time

7121 Invalid estimated start date/time

7122 Out-of-Service generating unit availability flag set with non-zero MW

7123 Out-of-Service and Return to Net Dependable Capacity flags set generating unit for the same breakpoint

7124 Invalid estimated end date/time

7125 Invalid state transition with estimated start date/time in the past

7127 Invalid change in resource future MaxLoad value for outage state

7128 Invalid Short-Notice Opportunity Outage duration exceeds duration limit

7129 Short-Notice Opportunity Outage duration cannot be extended

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7130 Resource load max de-rate not defined at beginning of outage

7135 MSG resource and configurations must reassign availability to the same outage for the same breakpoint

7136 Aggregate resource and generating units must reassign availability to the same outage for the same breakpoint

7137 Outage request payload is identical to last submitted outage request

7138 Invalid Short-Notice Opportunity flag for Forced Immediate outage

7139 A/S availability derate with overlapping outage (Participant Outage ID :) not allowed

7140 Invalid resource partial curtailment reassignment for vacated period exceeds outage curtailment

7141 Invalid MSG configuration partial curtailment reassignment for vacated period exceeds outage curtailment

7142 Invalid generating unit partial curtailment reassignment for vacated period exceeds outage curtailment

7143 Invalid resource negative Load Max

7144 Invalid resource negative Load Min

7145 Invalid resource negative Energy Max

7146 Invalid resource negative Energy Min

7147 Invalid resource negative PMnimum

7148 Invalid MSG configuration negative PMinimum

7149 Invalid negative resource availability

7150 Invalid negative generating unit availability

7151 Invalid negative MSG configuration availability

7152 Invalid Use Limit profile for non-Use Limit resource

7153 Invalid negative Use Limit MWh

7154 Invalid Use Limit profile outage of outage time

7155 Ramp rate change with overlapping outage (Participant Outage ID :) not allowed

7156 Invalid availability Return to Net Dependable Capacity flag set for resource availability for vacated period with multiple overlaps

7157 Invalid availability Return to Net Dependable Capacity flag set for MSG configuration availability for vacated period with multiple overlaps

7158 Invalid availability Return to Net Dependable Capacity flag set for generating unit availability for vacated period with multiple overlaps

7159 Invalid PMinimum re-rate with overlap outage (Participant Outage ID :)

7160 Invalid Load Max de-rate with overlap outage (Participant Outage ID :)

7161 Invalid Load Min de-rate with overlap outage (Participant Outage ID :)

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7162 Invalid Energy Max de-rate with overlap outage (Participant Outage ID :)

7163 Invalid Energy Min re-rate with overlap outage (Participant Outage ID :)

7164 Invalid overlapping outage (Participant Outage ID :) for Nature of Work

7165 Invalid overlapping outage (Participant Outage ID :) for NGR resource

7166 Invalid outage request Max Load < Min Load

7167 Invalid outage request Max Load > resource Max Capacity

7168 Invalid outage request Max Load < Min Load set on another outage

7169 Invalid outage request Max Load < Min Capacity

7170 Invalid outage request Min Load < Min Capacity

7171 Invalid outage request Min Load > Max Load set on another outage

7172 Invalid outage request Min Load > Max Capacity

7173 Invalid outage request Max Energy < Min Energy

7174 Invalid outage request Max Energy > Max Capacity

7175 Invalid outage request Max Energy < Min Energy set on another outage

7176 Invalid outage request Max Energy < Min Capacity

7177 Invalid outage request Min Energy < Min Capacity

7178 Invalid outage request Min Energy > Max Energy set on another outage

7179 Invalid outage request Min Energy > Max Capacity

7180 Resource availability for vacated time period not provided

7182 MSG configuration availability for vacated time period not provided

7184 Generating unit availability for vacated time period not provided

7186 Outage request availability < PMinimum

7187 Outage request availability > Max operating MW

7188 Outage request availability < PMinimum set on another outage

7189 Outage request availability < Min operating MW

7190 Outage request PMinimum < Min operating MW

7191 Outage request PMinimum > availability set on another outage

7192 Outage request PMinimum > Max operating MW

7193 Outage request availability < PMinimum for MSG configuration

7194 Outage request availability > Max operating MW for MSG configuration

7195 Outage request availability < PMinimum for MSG configuration set on another outage

7196 Outage request availability < Min operating MW for MSG configuration

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7197 Outage request PMinimum < Min operating MW for MSG configuration

7198 Outage request availability > Max operating MW for generating unit

7202 WARNING - Outaged resource is required market generation in another outage

7205 Outage description not provided

7206 Multiple resources in outage request not allowed

7207 Unknown resource and/or generating unit

7208 Generating unit not associated with outage resource

7209 Invalid AS availability for generating unit

7210 Invalid MSG configuration information for generating unit

7211 Invalid Max Load information for generating unit

7212 Invalid Min Load information for generating unit

7213 Invalid Use Limit information for generating unit

7214 Invalid Max Energy information for generating unit

7215 Invalid Min Energy information for generating unit

7216 Invalid P-Minimum information for generating unit

7217 Invalid Ramp Rate information for generating unit

7218 Multiple resources of different type (Generator, InterTie, Load) in request

7219 Invalid resource for participant

7220 Unknown market participant

7221 Unknown resource

7222 Market participant not provided

7226 Nature of Work not provided

7228 Resource load min re-rate not defined at beginning of outage

7230 Resource energy max de-rate not defined at beginning of outage

7232 Resource energy min re-rate not defined at beginning of outage

7234 Resource use limit not defined at beginning of outage

7236 Resource configuration Pmin re-rate not defined at beginning of outage

7238 Resource Pmin re-rate not defined at beginning of outage

7240 Resource availability not defined at beginning of outage

7242 Resource configuration availability not defined at beginning of outage

7244 Aggregate generating unit not defined at beginning of outage

7246 Configuration ramp rate change not allowed for resource type

7247 Invalid change in resource past MaxLoad value for outage state

7248 Invalid change in generating unit future availability value for outage state

7249 Emergency Return Time must be non-negative.

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7250 Invalid resource ramp rate re-rate less than minimum limit

7251 Invalid resource ramp rate re-rate greater than maximum limit

7252 Invalid resource ramp rate re-rate without OP ramp rate

7253 Invalid configuration ramp rate re-rate less than minimum limit

7254 Invalid configuration ramp rate re-rate greater than maximum limit

7255 Invalid configuration ramp rate re-rate without OP ramp rate

7256 AS Availability not provided for Nature of Work that requires AS availability

7257 Invalid AS Availability provided for Nature of Work

7258 PMax derate not provided for Nature of Work that requires PMax derate

7259 Invalid PMax derate provided for Nature of Work

7260 PMin rerate not provided for Nature of Work that requires PMin rerate

7261 Invalid PMin rerate provided for Nature of Work

7262 Load Max derate not provided for Nature of Work that requires Load Max derate

7263 Invalid Load Max derate provided for Nature of Work

7264 Load Min rerate not provided for Nature of Work that requires Load Min rerate

7265 Invalid Load Min rerate provided for Nature of Work

7266 Energy Max derate not provided for Nature of Work that requires Energy Max derate

7267 Invalid Energy Max derate provided for Nature of Work

7268 Energy Min rerate not provided for Nature of Work that requires Energy Min rerate

7269 Invalid Energy Min rerate provided for Nature of Work

7270 Use Limit not provided for Nature of Work that requires Use Limit

7271 Invalid Use Limit provided for Nature of Work

7272 Ramp Rate not provided for Nature of Work that requires Ramp Rate

7273 Invalid Ramp Rate provided for Nature of Work

7274 WARNING - Required generation is an outaged resource

7275 Invalid Load Max time point outside of outage planned start/end time

7276 Invalid Load Min time point outside of outage planned start/end time

7277 Invalid Energy Max time point outside of outage planned start/end time

7278 Invalid Energy Min time point outside of outage planned start/end time

7279 Invalid resource PMin time point outside of outage planned start/end time

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7280 Invalid resource availability time point outside of outage times and outage vacated times

7281 Invalid generating unit availability time point outside of outage times and outage vacated times

7282 Invalid MSG configuration PMin time point outside of outage planned start/end time

7283 Invalid MSG configuration availability time point outside of outage times and outage vacated times

7284 Invalid Use Limit time point outside of outage planned start/end time

7285 Invalid change in resource past MinLoad value for outage state

7286 Invalid change in resource future MinLoad value for outage state

7287 Invalid change in resource past MaxEnergy value for outage state

7288 Invalid change in resource future MaxEnergy value for outage state

7289 Invalid change in resource past MinEnergy value for outage state

7290 Invalid change in resource future MinEnergy value for outage state

7291 Invalid change in resource past availability value for outage state

7292 Invalid change in future resource availability value for outage state

7293 Invalid change in resource past PMin value for outage state

7294 Invalid change in resource future PMin value for outage state

7295 Invalid change in MSG configuration past availability value for outage state

7296 Invalid change in MSG configuration future availability value for outage state

7297 Invalid change in MSG configuration past PMin value for outage state

7298 Invalid change in MSG configuration future PMin value for outage state

7299 Invalid change in generating unit past availability value for outage state

7301 WARNING: Actual end time cannot be submitted via the API for this state transition

7302 Actual start date/time not provided

7303 Invalid actual start date/time in payload

7304 Actual Start Date/Time cannot be in the future

7305 Actual end date/time not provided

7306 Invalid actual end date/time in payload

7307 Actual End Date/Time cannot be in the future

7308 Actual end date/time must be later than start date/time

7309 Invalid outage - time range cannot cross over multiple definitions of the same resource

7310 Invalid request with invalid overlapping outages

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


7311 Submitted outage request cannot end after the time the outage invalid time

7312 Resource availability is greater than maximum availability

7313 Reassigned availability is greater than maximum availability for reassigned outage

7314 Availability is greater than maximum availability for configuration

7315 Reassigned availability is greater than maximum availability for reassigned outage for configuration

7316 Availability is greater than maximum availability for generating unit

7317 Reassigned availability is greater than maximum availability for reassigned outage for generating unit

7801 Unknown resource for RA between Start Date and End Date (UTC) with category type.

7801 Unknown configuration (mRID) for Generator resource for RA between Start Date and End Date (UTC) with category type.

7803 Invalid incremental payload flag. Only full updates are supported.

7804 Overlap Resource/Configuraqtion for RA (mRID) Category type.

7804 User is prohibited from re-scheduling the Planned Start Date/Time.

7805 User is prohibited from re-scheduling the Planned End Date/Time.

7806 User is prohibited from re-scheduling Planned Start Date/Time to be in the past.

7807 User is prohibited from re-scheduling Planned End Date/Time to be in the past.

7808 MSG Configuration Availability submitted with NDC flag set and value not equal to configuration maximum.

7809 Nature of Work can not be changed for existing outages.

7810

This outage currently spans a resource model breakpoint where the model changes do not allow outages to span the transition. The outage must be shortened in the UI to be in sync with the updated resource model.

13.2.3 Warning Codes

Code Message

4000 Resource has overlapping definitions

4001 Resource has gaps in definitions

4021 Resource has gaps in limit definitions

4007 Aggregate resource has gaps in limit definitions

cczxxz


ISO Public


Technology

Template

Version: 1.4

Document

Version: 1.91.10


4008 MSG resource has gaps in limit definitions

4002 Resource has duplicate Max Operating MW for the same time period

4003 Resource has duplicate Min Operating MW for the same time period

4004 Resource has duplicate generating unit Max Operating Value for the same time period

4005 Resource has duplicate MSG configuration Max Operating MW for the same time period

4006 Resource has duplicate MSG configuration Min Operating MW for the same time period

4009 Resource has Max Operating MW < Min Operating MW

4010 MSG Resource has Max Operating MW < Min Operating MW

4011 Resource has Max Capacity MW < Min Capacity MW

4012 Resource with "LOAD" capacity type has Max Capacity MW < Min Capacity MW. Max Capacity and Min Capacity are swapped by webOMS