ISO Interface Specification
|
|
- Cora Hodge
- 6 years ago
- Views:
Transcription
1 ISO Interface Specification Outage Management System Date Created: 12/27/2013 Doc ID: GNFDMDEHU6BB Page 1 of 112
2 Template 1.4 Location of <Add um path or URL here> Revision History Date Version Description Author 12/27/ creation Sean Crimmins 01/08/ Initial document with Generation Sean Crimmins submit/retrieve 1/27/ Updated with Transmission Sean Crimmins submit/retrieve 2/7/ Added common services and facility Sean Crimmins outage definition 2/7/ Added outage status update Sean Crimmins 4/7/ Updated WSDLs and sample XSDs to Sunil Nallagangu reflect latest XSD modifications 4/15/ Updated spec to accommodate Sunil Nallagangu changes in ResourceOutageResults_v1.xsd 5/29/ Updated spec to accommodate latest Sunil Nallagangu changes in XSDs 7/21/ Added SOAP Header and MTOM Sunil Nallagangu attachment Info 08/01/ Updated spec to reflect latest XSDs Sunil Nallagangu 08/28/ Updated spec to reflect latest XSDs Sunil Nallagangu 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: Relaxed Resource(Generator/Intertie/Load) name from 32 to 40 chars. 10/10/ Updated retrieve resource outage, retrieve transmission outage, retrieve availability and retrieve facility outage definition sections to include tables that describe how the different request Yinka Ajede Doc ID: GNFDMDEHU6BB Page 2 of 112
3 Template 1.4 Date Version Description Author criteria can be used. 11/10/ TransmissionOutageResults (B2B) - Adding enumerations (CONFORMLOAD, NONCONFORMLOAD and STATICVARCOMPENSATOR) to equipment type. FacilityOutageDefinitionResults (B2B) - Adding only STATICVARCOMPENSATOR enumeration to equipment type (already has ConformLoad and nconformload in the enumerations) Sunil Nallagangu 11/11/ Added list of primary and secondary cause codes that are required for forced transmission outages 11/11/ RequestFacilityOutageDefinition updated to enable search by Participant market organisation 11/17/2014 Added enumerations to be used for primary and secondary codes that are required for forced transmission outages Yinka Ajede Sunil Nallagangu 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. 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.) Doc ID: GNFDMDEHU6BB Page 3 of 112
4 Template 1.4 Table of Contents 1. INTRODUCTION PURPOSE CONTACT INFORMATION RELATED DOCUMENTS RELEASE NOTES API TRANSITION SUPPORT MTOM ATTACHMENTS...10 DATE TIME DATA TYPE ELEMENTS SOAP HEADER ELEMENTS & MTOM ATTACHMENTS IDENTITY OF MESSAGE PRODUCER Identity Timestamp Message Freshness MTOM ATTACHMENTS STANDARD XSDS STANDARD ATTACHMENT INFORMATION Element table Schema (StandardAttachmentInfor.xsd) Example XML File (StandardAttachmentInfor.xml) FAULT RETURN Element Table Schema (StandardOutput.xsd) Example XML File (StandardOutput.xml) SUBMIT RESOURCE OUTAGE {CHANGE REQUESTS} BUSINESS SCENARIO OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Submit New Outage Submit Change to Existing Outage OPERATIONAL DETAILS Submit Resource Outage Submit Resource Outage Change Request WSDL submitresourceoutage_v1.wsdl / submitresourceoutage_v1_docattach.wsdl submitresourceoutagechangerequest_v1.wsdl / submitresourceoutagechangerequest_v1_docattach.wsdl SUBMIT RESOURCE OUTAGE {CHANGE REQUEST} Element Table Schema (ResourceOutageData_v1.xsd) Example XML File (SubmitResourceOutageData_v1.xml) Example XML File (SubmitResourceOutageChangeRequest_v1.xml) SUBMIT RESOURCE OUTAGE {CHANGE REQUEST} RESPONSE Element Table Schema (OutageStandardOutput_v1.xsd)...33 Doc ID: GNFDMDEHU6BB Page 4 of 112
5 Template Example XML File (ResourceOutageStandardOutput.xml) RETRIEVE OUTAGE/CHANGE REQUESTS BUSINESS SCENARIO OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Retrieve Generation Outages Retrieve Resource Outage Change Requests OPERATIONAL DETAILS Retrieve Resource Outage Retrieve Resource Outage Change Request WSDL retrieveresourceoutage_v1.wsdl / retrieveresourceoutage_v1_docattach.wsdl retrieveresourceoutagechangerequest_v1.wsdl / retrieveresourceoutagechangerequest_v1_docattach.wsdl RETRIEVE RESOURCE OUTAGE {CHANGE REQUEST} Element Table Schema (RequestResourceOutage_v1.xsd) Example XML File (RequestResourceOutage_v1.xml) Example XML file (RequestResourceOutageChangeRequest.xml) RETRIEVE RESOURCE OUTAGE {CHANGE REQUEST} RESPONSE Element Table Schema (ResourceOutageResults_v1.xsd) Example XML File (ResourceOutageResults_v1.xml) Example XML file (ResourceOutageChangeRequestResults_v1.xml) FAULT RETURN SUBMIT TRANSMISSION OUTAGE {CHANGE REQUESTS} BUSINESS SCENARIO OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Submit New Transmission Outage Submit Change to Existing Transmission Outage OPERATIONAL DETAILS Submit Transmission Outage Submit Transmission Outage Change Request WSDL SubmitTransmissionOutage_v1.wsdl / SubmitTransmissionOutage_v1_DocAttach.wsdl SubmitTransmissionOutageChangeRequest_v1.wsdl/ SubmitTransmissionOutageChangeRequest_v1_DocAttach.wsdl SUBMIT TRANSMISSION OUTAGE {CHANGE REQUEST} Element Table Schema (TransmissionOutageData_v1.xsd) Example XML File (SubmitTransmissionOutageData_v1.xml) Example XML File (SubmitTransmissionOutageChangeRequest_v1.xml) SUBMIT TRANSMISSIONOUTAGE {CHANGE REQUEST} RESPONSE Element Table Schema (OutageStandardOutput_v1.xsd) Example XML File (TransmissionOutageStandardOutput_v1.xml) RETRIEVE TRANSMISSION OUTAGE/CHANGE REQUESTS...72 Doc ID: GNFDMDEHU6BB Page 5 of 112
6 Template OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Retrieve Transmission Outages Retrieve Transmission Outage Change Requests OPERATIONAL DETAILS Retrieve Transmission Outage Retrieve Transmission Outage Change Request WSDL retrievetransmissionoutage_v1.wsdl / retrievetransmissionoutage_v1_docattach.wsdl retrievetransmissionoutagechangerequest_v1.wsdl / retrievetransmissionoutagechangerequest_v1_docattach.wsdl RETRIEVE TRANSMISSION OUTAGE {CHANGE REQUEST} Element Table Schema (RequestTransmissionOutage_v1.xsd) Example XML File (RequestTransmissionOutage_v1.xml) Example XML file (RequestTransmissionOutageChangeRequest_v1.xml) RETRIEVE TRANSMISSION OUTAGE {CHANGE REQUEST} RESPONSE Element Table Schema (TransmissionOutageResults_v1.xsd) Example XML File (TransmissionOutageResults_v1.xml) Example XML file (TransmissionOutageResultsChangeRequests_v1.xml) FAULT RETURN RETRIEVE AVAILABILITY OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Retrieve Availability OPERATIONAL DETAILS Retrieve Availability WSDL retrieveavailability_v1.wsdl / retrieveavailability_v1_docattach.wsdl RETRIEVE AVAILABILITY Element Table Schema (RequestAvailability_v1.xsd) Example XML File (RequestAvailability_v1.xml) REQUEST AVAILABILITY RESPONSE Element Table Schema (AvailabilityResults_v1.xsd) Example XML File (AvailabilityResults_v1.xml) FAULT RETURN RETRIEVE FACILITY OUTAGE DEFINITION OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Retrieve Facility Outage Definition OPERATIONAL DETAILS Retrieve Facility Outage Definition WSDL...96 Doc ID: GNFDMDEHU6BB Page 6 of 112
7 Template retrievefacilityoutagedefinition_v1.wsdl / retrievefacilityoutagedefinition_v1_docattach.wsdl RETRIEVE FACILITY OUTAGE DEFINITION Element Table Schema (requestfacilityoutagedefinition_v1.xsd) Example XML File (requestfacilityoutagedefinition_v1.xml) REQUEST FACILITY OUTAGE RESPONSE Element Table Schema (FacilityOutageDefinitionResults_v1.xsd) Example XML File (FacilityOutageDefinitionResults_v1.xml) FAULT RETURN WITHDRAW OUTAGE CHANGE REQUEST OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Retrieve Facility Outage Definition OPERATIONAL DETAILS Retrieve Facility Outage Definition WSDL withdrawoutagechangerequest_v1.wsdl / withdrawoutagechangerequest_v1_docattach.wsdl WITHDRAW OUTAGE CHANGEREQUEST Element Table Schema (WithdrawOutageChangeRequest_v1.xsd) Example XML File (WithdrawOutageChangeRequest_v1.xml) WITHDRAW OUTAGE CHANGE REQUEST STANDARD OUTPUT Element Table Schema (StandardOutput_v1.xsd) Example XML File (WithdrawOutageChangeRequestStandardOutput_v1.xml) FAULT RETURN ACKNOWLEDGE OUTAGE WARNING OVERVIEW SERVICE LEVEL AGREEMENT USE MODEL Acknowledge Outage Warning OPERATIONAL DETAILS Retrieve Facility Outage Definition WSDL AcknowledgeOutageWarning_v1.wsdl / AcknowledgeOutageWarning_v1_DocAttach.wsdl ACKNOWLEDGE OUTAGE WARNING Element Table Schema (AcknowledgeOutageWarning_v1.xsd) Example XML File (AcknowledgeOutageWarning_v1.xml) ACKNOWLEDGE OUTAGE WARNING STANDARD OUTPUT Element Table Schema (StandardOutput_v1.xsd) Example XML File (AcknowledgeOutageWarningStandardOutput_v1.xml) OUTAGE STATUS UPDATE OVERVIEW SERVICE LEVEL AGREEMENT Doc ID: GNFDMDEHU6BB Page 7 of 112
8 Template USE MODEL Acknowledge Outage Warning OPERATIONAL DETAILS Outage Status Update WSDL OutageStatusUpdate_v1.wsdl / OutageStatusUpdate_v1_DocAttach.wsdl OUTAGE STATUS UPDATE Element Table Schema (OutageStatusUpdate_v1.xsd) Example XML File (OutageStatusUpdate_v1.xml) OUTAGE STATUS UPDATE Element Table Schema (StandardOutput_v1.xsd) Example XML File FAULT RETURN Doc ID: GNFDMDEHU6BB Page 8 of 112
9 Template 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 to siug@caiso.com 1.3 Related s 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. 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 Figure 1 ISO MARKET Web Services Interface Specification Set The ISO MARKET Web Services Interface Specification Set is available online at the locations indicated below. Doc.. Name Location Doc ID: GNFDMDEHU6BB Page 9 of 112
10 Template 1.4 Doc.. Name Location ISO MARKET B2B Security Specification Client Public/Private Key Instructions ISO MARKET Interface Specification for Bidding Services (you must have access to the Market Participant Portal) ClientPublic_PrivateKeyGuidelines.pdf icationaccess/default.aspx ISO MARKET Interface Specification for Inter-SC Trade Services ISO MARKET Interface Specification for Market Results Services ISO Interface Specification for Outage Management Services icationaccess/default.aspx icationaccess/default.aspx seplanning/default.aspx 7 ISO Acceptable Use Guidelines cesacceptableuseguidelinesapr9_2013.pdf 1.4 Release tes 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. Attachments will still be zipped and Base64 encoded. The previous style of rpc literal will not be supported. Doc ID: GNFDMDEHU6BB Page 10 of 112
11 Template 1.4 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 te: 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> t07: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=" <ns1:caisousernametoken> <ns1:username>lnp Tester40</ns1:Username> <nce>3433lfff23</nce> <Created> T16:30:45.0 PDT</Created> </ns1:caisousernametoken> </ns1:caisowsheader> Identity Doc ID: GNFDMDEHU6BB Page 11 of 112
12 Template 1.4 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 Timestamp The Security Timestamp is encapsulated via the <created> element in the <CAISOUsernameToken> and indicates when the token was created Message Freshness This specification uses a nce as a measure to thwart replay attacks. The nce 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: <ns1:attachmenthash xmlns:ns1=" <hashvalue>erptrfx6a288dmby+jg61jpbfay=</hashvalue> </ns1:attachmenthash> 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: <att:attachmentinfor> <att:attachmentdata1>cid: </att:attachmentdata1> </att:attachmentinfor> Here is a complete example of SOAP message. Doc ID: GNFDMDEHU6BB Page 12 of 112
13 Template 1.4 <soapenv:envelope xmlns:soapenv=" xmlns:stan=" xmlns:att=" <soapenv:header> <ns1:caisowsheader xmlns:ns1=" 30/CAISOWSHeader.xsd"> <ns1:caisousernametoken> <ns1:username>lnp Tester40</ns1:Username> <nce>3433lfff23</nce> <Created> T16:30:45.0 PDT</Created> </ns1:caisousernametoken> </ns1:caisowsheader> <ns1:attachmenthash xmlns:ns1=" <hashvalue>erptrfx6a288dmby+jg61jpbfay=</hashvalue> </ns1:attachmenthash> <!-- this is optional --> <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: " xmlns:inc=" </att:attachmentdata1> </att:attachmentinfor> </soapenv:body> </soapenv:envelope> Doc ID: GNFDMDEHU6BB Page 13 of 112
14 Template 1.4 In above example content-id cid: refers to actual attachment data in binary format that follows above SOAP message. Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: < > Content-Disposition: attachment; name="2e132f b-55b9f7a08fbf.uue" H4sIAAAAAAAAAL1W30/jOBB+7v4VVe+5dcICCyhkhQq3VwnaqgmLeFqZZNr6SOyc7bTw3+84P9o 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 Element table Doc ID: GNFDMDEHU6BB Page 14 of 112
15 Template 1.4 Element Data Description Type Req d id Globally unique identifier. string name Attachment filename. string description Description of attachment. string version Version ID of attachment file string sequencenumber Sequence number if there are multiple attachments. string type Attachments file type, zip string size Size of attachment file. string source Source of attachment file. string tool Tool used to generate attachment. string creationtime Time attachment file was created. datetime compressflag Indicates whether or not attachment has been compressed (YES or NO). string compressmethod Compress method used (if attachment file compressed). string AttributeList.Sequence Attribute list sequence number. string AttributeList.Name Name of an attribute string AttributeList.Value Value of an attribute string Schema (StandardAttachmentInfor.xsd) Each service bundle will contain the same StandardAttachmentInfor.xsd Example XML File (StandardAttachmentInfor.xml) <?xml version="1.0" encoding="utf-8"?> <!-- Sample XML file generated by XMLSpy v2006 U ( --> <standardattachmentinfor xmlns=" 13/StandardAttachmentInfor.xsd" xmlns:xsi=" xsi:schemalocation=" 13/StandardAttachmentInfor.xsd"> <Attachment> <id> </id> <name>out1</name> <description>outage_attachement</description> <version>1.1</version> <sequencenumber>12</sequencenumber> Doc ID: GNFDMDEHU6BB Page 15 of 112
16 Template 1.4 <type>zip</type> <size>180</size> <source>gwed</source> <tool>gzip</tool> <creationtime> t09: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 Element Table Element Data Description Type/ OutputDataType.EventLog Format/ Req d id Event log identifier. string name Event log name. string description Event log description. string type Event log type. string creationtime Event log creation time. date collectiontype Event log collection type. string collectionquantity Event log collection quantity. string Event.result Event result. string Event.id Event identifier. string Event.name Event name. string Event.description Event description. string Event.creationTime Event creation time. datetime Event.severity Event severity. string Event.priority Event priority. string Doc ID: GNFDMDEHU6BB Page 16 of 112
17 Template 1.4 Element Data Description Type/ Event.sequence Number Event sequence number. string Format/ Req d Event.eventType Event type. string Service.id Service identifier. string Service.name Service name. string Service.description Service description. string Service.comments Service comments. string Schema (StandardOutput.xsd) Each service bundle will have the same StandardOutput.xsd file Example XML File (StandardOutput.xml) <?xml version="1.0" encoding="utf-8"?> <!--Sample XML file generated by XMLSpy v2013 rel. 2 sp2 ( <m:outputdatatype xsi:schemalocation=" StandardOutput.xsd" xmlns:m=" xmlns:xsi=" <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> t11: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> t11: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> </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> </m:service> </m:eventlog> </m:outputdatatype> Doc ID: GNFDMDEHU6BB Page 17 of 112
18 Template 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) Expected frequency (average and maximum) Longest time the service can be unavailable before business is impacted Business impact if is unavailable Variable (1KB to 1MB+) On demand (50/day 200/day). 30 minutes 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) Submit New Outage sd Submit Outage OMS Outage Coordinator SubmitGenerationOutage() SubmitGenerationOutageResponse() Doc ID: GNFDMDEHU6BB Page 18 of 112
19 Template Submit Change to Existing Outage sd Submit Outage Change Request OMS Outage Coordinator submitoutagechangerequest() submitgenerationoutagechangerequestresponse() 4.4 Operational Details Submit Resource Outage The service has one operation with three message types. Operation submitresourceou tage Message Types Message WSDL XSD Input submitresourceou submitresourceoutage_v1.ws submitresourceoutage_v1.xsd Output tage submitresourceou dl/ submitresourceoutage_v1_d OutageStandardOutput_v1.xsd tageresponse ocattach.wsdl/ Fault faultreturntype StandardOutput.xsd Submit Resource Outage Change Request Operation submitresourceo utagechangerequ est Message Types Input Output Message WSDL XSD submitresourceo utagechangerequ est submitresourceo utagechangerequ estresponse submitresourceoutagechang erequest_v1.wsdl/ submitresourceoutagechang erequest_v1_docattach.wsd l submitresourceoutagechange Request_v1.xsd OutageStandardOutput_v1.xsd Fault faultreturntype StandardOutput.xsd 4.5 WSDL submitresourceoutage_v1.wsdl / submitresourceoutage_v1_docattach.wsdl submitresourceoutagechangerequest_v1.wsdl / submitresourceoutagechangerequest_v1_docattach.wsdl Doc ID: GNFDMDEHU6BB Page 19 of 112
20 Template 1.4 Location: Submit Resource Outage {Change Request} Element Table Element Data Description Type/ Message Header Format/ Req d TimeDate The datetime, in UTC, when the payload is published datetime Source The source of the data Version Subversion of the XSD: Initial version will be v MessagePayload.RegsiteredResourceOutage mrid ID for the Outage, t required for new outage, required when submitting a change request. Description Participant s description of the Outage/Change Request Comment Participant s comment for the Outage/Change Request affectsrassps Participant indicates if this outage affects a RAS or SPS. / discoverydatetime DateTime when the outage was discovered. datetime emergencyreturntime Time to restore the outage if needed by the ISO. Integer emergencyreturntimet ype Type of emergency return time. DAYS, HOURS, MINUTES mktorgoutageid Reference ID assigned to the outage by the participant. outagecoordinationlong TermPlanning 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. / RIMSProjectCommision Date Commission date of the the related RIMS project datetime RIMSProjectCompletion Completion date of the related RIMS project datetime Doc ID: GNFDMDEHU6BB Page 20 of 112
21 Template 1.4 Element Data Description Type/ Format/ Req d RIMSProjectID RIMS id of the related RIMS project RIMSProjectPhase RIMS phase that this outage will complete Actual Period Actual start and end times of the outage, in UTC datetime Estimated Period Planned start and end time of the outage, in UTC. datetime OutageCause.code Participant list of cause code for their reference isoffpeakopportunityou tage isshortticeopportunit youtage Participant indicates if the submission if for an off peak opportunity outage. / Participant indicates if the submission if for a short notice opportunity outage. / Work Kind of work codes. MessagePayload.RegsiteredResourceOutage.MktOrganisation mrid Participant short name MessagePayload.RegsiteredResourceOutage.MktOrganisation.MarketPerson firstname First name of the contact at the participant. lastname Last name of the contact at the participant. landlinephone Phone number of the contact at the participant. Complex MessagePayload.RegsiteredResourceOutage.OutageChangeRequest action Type of change request. If present indicates that his is a change request to an existing outage. UPDATE or CANCEL actionreason Reason for change actionsubtype Type of action subtype MessagePayload.RegsiteredResourceOutage.RegisteredGenerator(Choice1) mrid The resource id for the RegisteredGenerator. mrid minlen=1 maxlen=32 name An alternate name from the Participant name minlen=1 maxlen=40 RegisteredGenerator.LogicalConfiguration RegisteredGenerator.LogicalConfiguration.Configuration mrid The resource id for an MSG RegisteredGenerator s Configuration. mrid minlen=1 maxlen=32 Doc ID: GNFDMDEHU6BB Page 21 of 112
22 Template 1.4 Element Data Description Type/ Format/ name An alternate name from the Participant. name minlen=1 maxlen=40 Req d RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.Availability datetimepoint The time of this availability point in UTC. datetime outofservice Unit has avail 0 starting at this time / returntonetdependable Capacity Indicates no derate at this time Float Pmaxvalue Indicates Pmax value of Unit Float RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.PMinimum activeperiod.start Start date and time during which this restriction is applied datetime restrictedvalue The new pmin value for this interval. Float RegisteredGenerator.LogicalConfiguration.Configuration.OutagedRegisteredResource.RampRateSegment restrictedvalue The new Ramp Rate for this segment Float segmentnumber The number of this segment Integer segmentvalue The MW value that identifies the right hand side of the segment. Float RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource timetostartup The time the resource needs to start after the outage has completed. Float RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.ASAvailability availablevalue The new MW value for this interval. Float MarketProduct.marketPr oducttype Type of AS that is restricted. Enumera tion RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.Availability datetimepoint The time of this availability point in UTC. datetime outofservice Unit has avail 0 starting at this time. / returntonetdependablec apacity Indicates no derate starting at this time. / PmaxValue.vlaue Indicates Pmax value Float Doc ID: GNFDMDEHU6BB Page 22 of 112
23 Template 1.4 Element Data Description Type/ Format/ Req d RegisteredResourceOutage.RegisteredGenerator.OutagedRegisteredResource.Availability.OutagedRegister edresource.registeredresource.registeredresourceoutage RegisteredResource.RegisteredResourceOutage mrid ID for the Outage, t required for new outage, required when submitting a change request. RegisteredGenerator.OutagedRegisteredResource.LoadMaximum(Choice1) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this point. Float outofservice Unit has avail 0 starting at this time. / returntonetdependablec apacity Indicates no derate starting at this time. / RegisteredGenerator.OutagedRegisteredResource.LoadMinimum(Choice2) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this interval. Float RegisteredGenerator.OutagedRegisteredResource.MaximumEnergyLimit (Choice3) activeperiod.start Start date and time of this interval datetime restrictedvalue The new maximum energy limit (WH) for this interval. Float RegisteredGenerator.OutagedRegisteredResource.MinimumEnergyLimit (Choice4) activeperiod.start Start date and time of this interval datetime restrictedvalue The new minimum energy limit (WH) for this interval. RegisteredGenerator.OutagedRegisteredResource.PMinimum(Choice5) activeperiod.start The time of this pmin rerate point in UTC datetime restrictedvalue The new minimum output of this resource/configuration for this interval RegisteredGenerator.OutagedRegisteredResource.UseLimit(Choice6) activeperiod.start Start date and time of this interval datetime restrictedvalue The new use Limit for the resource in this interval. Float Float Float RegisteredGenerator.OutagedRegisteredResource.RampRateSegment (Choice7) Doc ID: GNFDMDEHU6BB Page 23 of 112
24 Template 1.4 Element Data Description Type/ restrictedvalue The new ramp rate (MW/min) for this segment in this interval. Float Format/ segmentnumber The identifier for this segment Integer segmentvalue The right hand side (MW) of this segment. Float MessagePayload.RegisteredResourceOutage.RegisteredIntertie(Choice2) Req d mrid The resource id for the RegisteredIntertie. mrid minlen=1 maxlen=32 name An alternate name from the Participant name minlen=1 maxlen=40 RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource timetostartup The time the resource needs to start after the outage has completed. Float RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.ASAvailability availablevalue The new MW value for this interval. Float MarketProduct.marketPr oducttype Type of AS that is restricted. Enumera tion RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.Availability datetimepoint The time of this availability point in UTC. datetime outofservice Unit has avail 0 starting at this time. / returntonetdependablec apacity Indicates no derate starting at this time. / PmaxValue.vlaue Indicates Pmax value Float RegisteredResourceOutage.RegisteredIntertie.OutagedRegisteredResource.Availability.OutagedRegistered Resource.RegisteredResource.RegisteredResourceOutage RegisteredResource.RegisteredResourceOutage mrid ID for the Outage, t required for new outage, required when submitting a change request. RegisteredIntertie.OutagedRegisteredResource.LoadMaximum(Choice1) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this point. Float outofservice Unit has avail 0 starting at this time. / Doc ID: GNFDMDEHU6BB Page 24 of 112
25 Template 1.4 Element Data Description Type/ returntonetdependablec apacity Format/ Indicates no derate starting at this time. / RegisteredIntertie.OutagedRegisteredResource.LoadMinimum(Choice2) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this interval. Float RegisteredIntertie.OutagedRegisteredResource.MaximumEnergyLimit (Choice3) activeperiod.start Start date and time of this interval datetime restrictedvalue The new maximum energy limit (WH) for this interval. RegisteredIntertie.OutagedRegisteredResource.MinimumEnergyLimit (Choice4) activeperiod.start Start date and time of this interval datetime restrictedvalue The new minimum energy limit (WH) for this interval. RegisteredIntertie.OutagedRegisteredResource.PMinimum(Choice5) activeperiod.start The time of this pmin rerate point in UTC datetime restrictedvalue The new minimum output of this resource/configuration for this interval RegisteredIntertie.OutagedRegisteredResource.UseLimit(Choice6) activeperiod.start Start date and time of this interval datetime restrictedvalue The new use Limit for the resource in this interval. Float RegisteredIntertie.OutagedRegisteredResource.RampRateSegment (Choice7) restrictedvalue The new ramp rate (MW/min) for this segment in this interval. segmentnumber The identifier for this segment Integer segmentvalue The right hand side (MW) of this segment. Float For detailed list of elements under OutageRegisterdResource click on link here. MessagePayload.RegisteredResourceOutage.RegisteredLoad(Choice3) Float Float Float Float Req d mrid The resource id for the RegisteredLoad. mrid minlen=1 maxlen=32 Name An alternate name from the Participant name minlen=1 maxlen=40 Doc ID: GNFDMDEHU6BB Page 25 of 112
26 Template 1.4 Element Data Description Type/ RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource Format/ Req d timetostartup The time the resource needs to start after the outage has completed. Float RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.ASAvailability availablevalue The new MW value for this interval. Float MarketProduct.marketPr oducttype Type of AS that is restricted. Enumera tion RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.Availability datetimepoint The time of this availability point in UTC. datetime outofservice Unit has avail 0 starting at this time. / returntonetdependablec apacity Indicates no derate starting at this time. / PmaxValue.vlaue Indicates Pmax value Float RegisteredResourceOutage.RegisteredLoad.OutagedRegisteredResource.Availability.OutagedRegisteredRe source.registeredresource.registeredresourceoutage RegisteredResource.RegisteredResourceOutage mrid ID for the Outage, t required for new outage, required when submitting a change request. RegisteredLoad.OutagedRegisteredResource.LoadMaximum(Choice1) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this point. Float outofservice Unit has avail 0 starting at this time. / returntonetdependablec apacity Indicates no derate starting at this time. / RegisteredLoad.OutagedRegisteredResource.LoadMinimum(Choice2) activeperiod.start Start date and time of this interval datetime restrictedvalue The new MW value for this interval. Float RegisteredLoad.OutagedRegisteredResource.MaximumEnergyLimit (Choice3) activeperiod.start Start date and time of this interval datetime restrictedvalue The new maximum energy limit (WH) for this interval. Float Doc ID: GNFDMDEHU6BB Page 26 of 112
27 Template 1.4 Element Data Description Type/ RegisteredLoad.OutagedRegisteredResource.MinimumEnergyLimit (Choice4) Format/ Req d activeperiod.start Start date and time of this interval datetime restrictedvalue The new minimum energy limit (WH) for this interval. RegisteredLoad.OutagedRegisteredResource.PMinimum(Choice5) activeperiod.start The time of this pmin rerate point in UTC datetime restrictedvalue The new minimum output of this resource/configuration for this interval RegisteredLoad.OutagedRegisteredResource.UseLimit(Choice6) activeperiod.start Start date and time of this interval datetime restrictedvalue The new use Limit for the resource in this interval. Float RegisteredLoad.OutagedRegisteredResource.RampRateSegment (Choice7) restrictedvalue The new ramp rate (MW/min) for this segment in this interval. segmentnumber The identifier for this segment Integer segmentvalue The right hand side (MW) of this segment. Float Float Float Float Schema (ResourceOutageData_v1.xsd) Location: Example XML File (SubmitResourceOutageData_v1.xml) <?xml version="1.0" encoding="utf-8"?> <m:resourceoutagedata xmlns:m=" xmlns:xsi=" xsi:schemalocation=" ResourceOutageData_v1.xsd "> <m:messageheader> <m:timedate> t12:00:00</m:timedate> <m:source>companya</m:source> <m:version>v </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> Doc ID: GNFDMDEHU6BB Page 27 of 112
28 Template 1.4 <m:discoverydatetime> t17: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> t17:00:00z</m:end> <m:start> t13: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:work> <m:kind>plant_maintenance</m:kind> </m:work> <m:isoffpeakopportunityoutage>no</m:isoffpeakopportunityoutage> <m:isshortticeopportunityoutage>no</m:isshortticeopportunityoutage> <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> t13: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> t17:00:00z</m:datetimepoint> Doc ID: GNFDMDEHU6BB Page 28 of 112
29 Template 1.4 <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> t13: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> t17: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> t13: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> t17: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> Doc ID: GNFDMDEHU6BB Page 29 of 112
30 Template 1.4 </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:resourceoutagedata> Example XML File (SubmitResourceOutageChangeRequest_v1.xml) <?xml version="1.0" encoding="utf-8"?> <m:resourceoutagedata xmlns:m=" xmlns:xsi=" xsi:schemalocation=" ResourceOutageData_v1.xsd "> <m:messageheader> <m:timedate> t09:00:00z</m:timedate> <m:source>companya</m:source> <m:version>v </m:version> </m:messageheader> <m:messagepayload> <m:registeredresourceoutage> <m:mrid> </m:mrid> <m:description>new generator (MSG) Outage</m:description> <m:comment>example</m:comment> <m:affectsrassps>yes</m:affectsrassps> <m:discoverydatetime> t09: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> t18:00:00z</m:end> <m:start> t13:00:00z</m:start> Doc ID: GNFDMDEHU6BB Page 30 of 112
31 Template 1.4 </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:isshortticeopportunityoutage>no</m:isshortticeopportunityoutage> <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> t13: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> Doc ID: GNFDMDEHU6BB Page 31 of 112
32 Template 1.4 </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> 4.7 Submit Resource Outage {Change Request} Response Element Table Element Data Description Type/ Message Header Format/ Req d TimeDate The datetime, in UTC, when the payload is published datetime Source The source of the data Version Subversion of the XSD: Initial version will be v MessagePayload.EventLog MessagePayload.EventLog.Event result Event result. string id Event identifier. string description Event description. string creationdatetime Event creation time. datetime MessagePayload.EventLog.Service Doc ID: GNFDMDEHU6BB Page 32 of 112
33 Template 1.4 Element Data Description Type/ Format/ Req d id Service identifier. string name Name of a service. string MessagePayload.EventLog.Outage mrid ID assigned to the outage by the ISO mktorgoutageid Reference ID assigned to the outage by the external User MessagePayload.EventLog.Outage.OutageChangeRequest mrid ID assigned to the outage change request by the ISO MessagePayload.EventLog.Outage.OutageGroup mrid ID assigned to the outage Group by the ISO MessagePayload.EventLog.Outage.OutageValidation submitstatus Indicates whether the outage was accepted or rejected: ACCEPTED, REJECTED MessagePayload.EventLog.Outage.OutageValidation.OutageResult mrid ID assigned to the result by the ISO type Type of result: ERROR, INFO, WARNING description Description of result returned status Status of the result: ACKNOWLEDGED. UNACKNOWLEDGED. This is applicable only to warnings Schema (OutageStandardOutput_v1.xsd) Location: Example XML File (ResourceOutageStandardOutput.xml) Example XML File for Submit Resource Outage Response <?xml version="1.0" encoding="utf-8"?> <OutageStandardOutput xmlns=" xmlns:xsi=" xsi:schemalocation=" OutageStandardOutput_v1.xsd "> <MessageHeader> Doc ID: GNFDMDEHU6BB Page 33 of 112
34 Template 1.4 <TimeDate> T11:00:00Z</TimeDate> <Source>CompanyA</Source> <Version>v </Version> </MessageHeader> <MessagePayload> <EventLog> <Event> <id>1</id> <result>success</result> </Event> <Outage> <mrid> </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> Example XML File for Submit Resource Outage Change Request Response <?xml version="1.0" encoding="utf-8"?> <m:resourceoutagedata xmlns:m=" xmlns:xsi=" xsi:schemalocation=" ResourceOutageData_v1.xsd "> <m:messageheader> <m:timedate> t09:00:00z</m:timedate> <m:source>companya</m:source> <m:version>v </m:version> </m:messageheader> <m:messagepayload> <m:registeredresourceoutage> <m:mrid> </m:mrid> <m:description>new generator (MSG) Outage</m:description> Doc ID: GNFDMDEHU6BB Page 34 of 112
ISO Interface Specification
ISO Interface Specification Outage Management System Date Created: 9/29/201511/30/2015 Doc ID: GNFDMDEHU6BB-46-46 Page 1 of 135 Location of Revision History Date Version Description
More informationTechnical Interface Specification For Master File Data Exchange Services v
Technical Interface Specification For Master File Data Exchange Services v20111001 Version: 2.7 Revision History Date Version Description 05/29/09 1.13 Project First Released Version. 12/15/09 2.1 Project
More informationTechnical Interface Specification For Master File Data Exchange Services v
DRAFT Technical Interface Specification For Master File Data Exchange Services v20121001 Version: 2.12 Revision History Date Version Description 05/29/09 1.13 Project First Released Version. 12/15/09 2.1
More informationTechnical Interface Specification For Master File Data Exchange Services
Draft Technical Interface Specification For Master File Data Exchange Services Version: 3.3 Revision History Date Version Description 05/29/09 1.13 Project First Released Version. 12/15/09 2.1 Project
More informationTechnical Interface Specification For Master File Data Exchange Services
Draft Technical Interface Specification For Master File Data Exchange Services Version: 4.1.3 Revision History Date Version Description 05/29/09 1.13 Project First Released Version. 12/15/09 2.1 Project
More informationMRI-Settlements (MRI-S) For RC Interface Specification
Doc ID: GNFDMDEHU6BB-46-46 Page of 5 MRI-Settlements (MRI-S) For RC Interface Specification Date Created: //208 RCSI ISO Interface Specification Date Created: //208 Location of Revision History Date Version
More informationDRS Replacement. ISO Interface Specification. Date Created: 11/9/2015. Document Version: 1.0. Owner: CAISO/ITPD
ISO Interface Specification DRS Replacement Date Created: 11/9/2015 Owner: CAISO/ITPD Doc ID: GNFDMDEHU6BB-46-46 Page 1 of 32 Location of http://www.caiso.com/s/externalbusinessrequirementsspecificationv10demandresponsesystem
More informationMRI-Settlements. ISO Interface Specification. Date Created: 10/18/2017. Document Version: 2.0. Owner: Lam, Rick. Copyright 2012 California ISO
ISO Interface Specification MRI-Settlements Date Created: 10/18/2017 Deleted: OMAR Online Replacement Doc ID: GNFDMDEHU6BB-46-46 Page 1 of 66 Location of Revision History Date Version Description Author
More informationOMAR Online Replacement
Doc ID: GNFDMDEHU6BB-46-46 Page 1 of 64 ISO Interface OMAR Online Replacement [ Location of Revision History Date Version Description Author 12/8/2015 1.0 Initial Version CAISO 03/10/2016 1.1 Revised element
More informationCustomer Market Results Interface (CMRI) For RC Interface Specification. Version: 1.0.0
Customer Market Results Interface (CMRI) For RC Interface Specification Version: 1.0.0 November 1, 2018 Revision History Date Version Description 11/01/2018 1.0.0 Initial document release Page 2 of 10
More informationPISOA Interface Specification. Fall 2017 Release
PISOA Interface Specification Fall 2017 Release Version: 1.0 July 21, 2017 Revision History Date Version Description 07/21/2017 1.0 Initial document release related to the PISO Interfaces. RequestVERMeasurements
More informationAutomated Load Forecast System (ALFS) For RC Interface Specification
Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load
More informationAutomated Load Forecast System (ALFS) Interface Specification. Fall 2017 Release
Automated Load Forecast System (ALFS) Interface Specification Fall 2017 Release Version: 1.1 March 27, 2017 Revision History Date Version Description 03/01/2017 1.0 Initial document release related to
More informationDemand Response Registration System
ISO Interface Demand Response Registration System Owner: CAISO California ISO INTERNAL USE. For use by all authorized California ISO personnel. Do not release or disclose outside the California ISO. Doc
More informationSIBR Interface Specification for Bidding Services
SIBR Interface Specification for Bidding Services (Business Rules v 8.x(Fall 2015) or later) Version: 12.1 April 23, 2015 Revision History Date Version By Description 4/23/2015 12.1 WT URL name changes
More informationBase Schedule Aggregation Portal (BSAP) Interface Specification for BSAP Services
Base Schedule Aggregation Portal (BSAP) Interface Specification for BSAP Services (Business Rules v 9.x(Fall 2018) or later) Version: 1.4 December 5, 2018 Revision History Date Version By Description 1.4
More informationSIBR Interface Specification for Bidding Services
SIBR Interface Specification for Bidding Services (Business Rules v 8.x(Fall 2014) or later) Version: 11.5 Oct 8, 2014 Revision History Date Version By Description 11/5/2014 11.6 WT 10/8/2014 11.5 WT Minor
More informationSLIC Web Service API Guide
SLIC Web Service API Guide Version: 5.0.6 February 19, 2014 Revision History Date Version Description Author 2002 1.0 October 2003 2.0 February 2007 3.0 Initial release of this document Revised to include
More informationSLIC Web Service API Guide
SLIC Web Service API Guide Version: 4.4.1 September 28, 2012 Revision History Date Version Description Author 2002 1.0 October 2003 2.0 February 2007 3.0 Initial release of this document Revised to include
More informationIndustry Training Register. Guide to integration for ITOs
Industry Training Register Guide to integration for ITOs Version 5.0 Objective id A823307 Published 15 January 2013 Page 2 of 29 ITR guide to integration for ITOs Contents 1 INTRODUCTION... 4 1.1 About
More informationCustomer Market Results Interface (CMRI) Interface Specification Fall 2016 Release
Customer Market Results Interface (CMRI) Interface Specification Fall 2016 Release : 3.5.0 February 3, 2016 Revision History Date Description 10/23/2013 2.0 Initial document release related to the Spring
More informationOutage Management System Customer Partnership Group. November 2017
Outage Management System Customer Partnership Group November 2017 Customer Partnership Group Scope and Objective Created in response to customer s request to have more involvement in the planning, design
More informationTechnical User Group Agenda
Technical User Group Agenda May 2nd, 2017 Web Conference Information URL: https://www.connectmeeting.att.com Meeting Number: 8665282256 Access Code: 6085978 10:00 a.m. 11:00 a.m. (Pacific Time) Conference
More informationCustomer Market Results Interface (CMRI) Interface Specification Fall 2018Independent 2019 Release
Customer Market Results Interface (CMRI) Interface Specification Fall 2018Independent 2019 Release : 3.8.12 September 6Feburary 6, 20182019 Revision History Date Description 10/23/2013 2.0 Initial document
More informationOutage Scheduler User's Guide
GUIDE 10 Outage Scheduler User's Guide September 2016 Version: 3.0 Revision Date: 09/13/2016 This document was prepared by: Scheduling, Energy Market Operations New York Independent System Operator 10
More informationEnergy Storage and Distributed Energy Resources Phase 2 Implementation
Energy Storage and Distributed Energy Resources Phase 2 Implementation Customer Partnership Group January 29, 2018 1:00 p.m. 2:00 p.m. (Pacific Standard Time) Public Agenda Item Project Schedule Update
More informationHMA-T G-POD Web Service Acceptance Test Report
HMA-T G-POD Web Service Acceptance Test Report Terradue Srl page ii of iv Short Title HMA-T G-POD Web Service Acceptance Test Report Prepared by Terradue Srl Approved by Fabrice Brito Reference T2-ESA-GPOD-TP-09-003
More informationMarket Results Interface- Settlements (MRI-S) Meter Data Submission User Guide
Market Results Interface- Settlements (MRI-S) Meter Data Submission User Guide Version 1.9 11/28/18 Document Production Doc ID: FGD5EMQPXRTV-204-24121 Page 1 of 48 REVISION HISTORY VERSION NO. (Must match
More informationPartner Web Services. GetOrderStatus Version 1 Service Manual
Partner Web Services GetOrderStatus Version 1 Service Manual Contents 1 Introduction... 4 1.1 Overview... 4 1.2 Supporting Resources... 4 2 Service Overview... 4 3 Service Endpoints... 5 4 Request/Response
More informationIEC Overview CIM University UCAIug Summit Austin, TX. 18 November 2011
IEC 61968-100 Overview CIM University UCAIug Summit Austin, TX 18 November 2011 Agenda Introduction A look at the purpose, scope and key terms and definitions. Use Cases and Messaging Patterns What are
More informationInforce Transactions TECHNICAL REFERENCE. DTCCSOLUTIONS September Copyright 2011 Depository Trust Clearing Corporation. All Rights Reserved.
TECHNICAL REFERENCE Inforce Transactions Page 1 Table of Contents 1 Overview... 3 2 Roles and Responsibilities... 3 2.1 Participants... 3 2.2 DTCC Server... 4 3 Communication Protocols... 5 3.1 SOAP Messages...
More informationMarket Results Interface- Settlements (MRI-S) Meter Data Submission User Guide
Market Results Interface- Settlements (MRI-S) Meter Data Submission User Guide Version Document Copyright 2017 California Doc ID: FGD5EMQPXRTV-168-95026 Page 1 of 45 REVISION HISTORY VERSION NO. (Must
More informationHMA-T G-POD Web Service Acceptance Test Report
HMA-T G-POD Web Service Acceptance Test Report Terradue Srl page ii of iv Short Title HMA-T G-POD Web Service Acceptance Test Report Prepared by Terradue Srl Approved by Fabrice Brito Reference T2-ESA-GPOD-TP-09-003
More informationSecurities Lending Reporting Web Service
Securities Lending Reporting Web Service External Interface Specification Broker Trades Message Specification November 2009 (November 2007) ASX Market Information 2009 ASX Limited ABN 98 008 624 691 Table
More informationEnterprise PeopleTools 8.50 PeopleBook: Reporting Web Services
Enterprise PeopleTools 8.50 PeopleBook: Reporting Web Services September 2009 Enterprise PeopleTools 8.50 PeopleBook: Reporting Web Services SKU pt850pbr0 Copyright 1988, 2009, Oracle and/or its affiliates.
More informationThe Surplus Line Association of Oregon Oregon Surplus Line Automation Suite Bulk Data Submission Guide
The Surplus Line Association of Oregon Oregon Surplus Line Automation Suite Bulk Data Submission Guide 1901 Commonwealth Ln Tallahassee, FL 32303 Phone: 850.383.1011 Fax: 850.383-1015 www.infinity-software.com
More informationETR & ACER REMIT: NG Market Interface Specification
ETR & ACER REMIT: NG Market Interface Specification ETR-ACER REMIT NG-Market v5.12 Page 1 of 100 Contents 1 Purpose... 3 2 Glossary... 3 3 Requirement... 3 3.1 Unavailability of Consumption Units... 4
More informationSOAP API. The correct URL has been hidden. Please contact your account manager for the full URL information.
SMS Help Guides TNZ Group Limited sales@tnz.co.nz +64 9 9293000 +64 9 522 8839 SOAP API SOAP is a simple way of sending SMS/TXT messages via the internet. It is a great solution for integration into existing
More informationSOAP Specification. 3 major parts. SOAP envelope specification. Data encoding rules. RPC conventions
SOAP, UDDI and WSDL SOAP SOAP Specification 3 major parts SOAP envelope specification Defines rules for encapsulating data Method name to invoke Method parameters Return values How to encode error messages
More informationLab 3: Simple Integration Use Case
Exercise 1 : Create the web service...2 Exercise 2 : Deploy the web service...4 Exercise 3 : Test the service...8 1/16 In this exercise, you will learn how to activate a Maximo inbound web service. This
More informationUsing BMC SRM OOB Web Services
Using BMC SRM OOB Web Services The BMC Service Request Management application is shipped with a number of OOB Web Services that can be used to Create, Query and Modify requests (see Figure 1. at end of
More informationBEAAquaLogic Enterprise Repository. Automation for Web Services Guide
BEAAquaLogic Enterprise Repository Automation for Web Services Guide Version 3.0. RP1 Revised: February, 2008 Table of Contents Overview System Settings Properties for Managing WSDL- and UDDI-Related
More informationEPA Moderated Transaction System (EMTS) Flow Configuration Document. Version: 1.0 January 19, 2010
EPA Moderated Transaction System () Flow Configuration Document Version: 1.0 January 19, 2010 Prepared by: Perrin Quarles Associates, Inc. 652 Peter Jefferson Parkway, Suite 300 Charlottesville, VA 22911
More informationDEVELOPER GUIDE PART B CONNECTOR REQUIREMENTS
DEVELOPER GUIDE PART B CONNECTOR REQUIREMENTS Warning: This is a redacted version of the SIDES Developer Guide and is NOT the latest version. For development, log into the Members Site and obtain the latest
More informationFax Broadcast Web Services
Fax Broadcast Web Services Table of Contents WEB SERVICES PRIMER... 1 WEB SERVICES... 1 WEB METHODS... 1 SOAP ENCAPSULATION... 1 DOCUMENT/LITERAL FORMAT... 1 URL ENCODING... 1 SECURE POSTING... 1 FAX BROADCAST
More informationMODIS Interface Specification
MODIS MODIS (Issue 4) Page 1 of 85 Contents 1 Purpose... 3 2 Glossary... 3 3 Requirement... 3 3.1 Unavailability of Consumption Units... 4 B0710: Planned Unavailability of Consumption Units (A7.1a)...
More informationWorking Group Charter: Basic Profile 1.2 and 2.0
Working Group Charter: Basic Profile 1.2 and 2.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 Web Services Basic
More information_ Dear Secretary Bose: The attached. Folsom, CA
California Independent System Operator June 29, 2012 The Honorable Kimberly D. Bose Secretary Federal Energy Regulatory Commission 888 First Street, NE Washington, DC 20426 Re: California Independent System
More informationWorking Group Charter: Web Services Basic Profile
Working Group Charter: Web Services Basic Profile Web Services Basic Profile (wsbasic) Creation Date: 2002.03.05 Revision Date: 2008.09.09 Document Editors: WS-I Secretary (secretary@ws-i.org) This Working
More informationIEC Implementation Profiles for IEC 61968
IEC 61968-100 Implementation Profiles for IEC 61968 Overview CIM University UCAIug Summit New Orleans, LA 22 October 2012 Agenda Introduction A look at the purpose, scope and key terms and definitions.
More informationCONSTRUCTION OF INSTAT/XML DOCUMENT AND DESCRIPTION OF ITS STRUCTURAL ELEMENTS (with effect from 24 March 2017)
1 CONSTRUCTION OF INSTAT/XML DOCUMENT AND DESCRIPTION OF ITS STRUCTURAL ELEMENTS (with effect from 24 March 2017) 1. The description of the data structure of INSTAT/XML document (further description) is
More informationQuality Notes QNO Role Guide March 2018
Quality Notes QNO Role Guide March 2018 Copyright 2018 Exostar, LLC All rights reserved. 1 Contents Introduction... 3 About the QN Originator (QNO) Role... 3 Search... 3 Using Search to Locate Quality
More informationDaman isupplier Portal User Guide. Procurement
Procurement Table of Content 1. Introduction... 4 Benefits associated with using isupplier include:... 4 2. System Requirements... 4 2.1 Recommended Operating System:... 4 2.2 Browser Requirements:...
More informationEIM Entity Readiness Criteria May 6, 2015
EIM Entity Readiness Criteria May 6, 2015 FERC Directive Regarding Readiness Criteria We therefore direct CAISO to submit a compliance filing within 60 days of issuance of this order, to revise the EIM
More informationSIX Trade Repository AG
January 2018 Client Table of contents 1.0 Introduction 4 1.1 Purpose 4 1.2 Acronyms 4 1.3 Version table 4 2.0 Overview of systems and workflows 4 3.0 Input connectivity options 6 3.1 FTS-Gateway 6 3.1.1
More informationCalifornia Independent System Operator Corporation Fifth Replacement Electronic Tariff
Table of Contents Appendix M... 2 Dynamic Scheduling Protocol (DSP)... 2 1. DYNAMIC SCHEDULES OF IMPORTS TO THE CAISO BALANCING AUTHORITY AREA... 2 1.2 Contractual Relationships... 2 1.3 Communications,
More informationThe ESP Handbook. Chapter 6 The Direct Access Service Request Completing the DASR
The ESP Handbook Chapter 6 The Direct Access Service Request Completing the DASR Version 6.0 August 1, 2013 6.1. An Introduction to the Direct Access Service Request The Direct Access Service Request (DASR)
More information1. Responsibilities. Settlement Quality Meter Data (SQMD) Plan Submission & Approval Process (External) Operating Procedure
Table of Contents Purpose... 1 1. Responsibilities... 2 2. Scope/Applicability... 3 2.1 Background... 3 2.2 Scope / Applicability... 3 3. Detail... 4 3.1 SQMD Plan Imposed by the CAISO Tariff... 4 3.1.1
More informationEnterprise Integration Using IEC
Enterprise Integration Using IEC 61968-100 Scott Neumann, UISOL Margaret Goodrich, SISCO Michael Johnson, Elster CIMug Meeting Introduction The purpose of this presentation is to describe enterprise integration
More informationViator Supplier API Technical Specification
Viator Supplier API Technical Specification 1.0.8 Copyright 1997, 2016 Viator, Inc. All rights reserved. Viator is a registered trademark of Viator, Inc. 1.0.8 Table of Contents Revision... v 1. Introduction...
More informationDEVELOPER GUIDE PART C DEVELOPMENT STEPS
DEVELOPER GUIDE PART C DEVELOPMENT STEPS Warning: This is a redacted version of the SIDES Developer Guide and is NOT the latest version. For development, log into the Members Site and obtain the latest
More informationWeb Services Overview
Web Services Overview Using Eclipse WTP Greg Hester Pacific Hi-Tech, Inc. greg.hester.pacifichitech.com 1 September 17, 2008 Agenda Web Services Concepts How Web Services are used Web Services tools in
More informationC exam. IBM C IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile. Version: 1.
C9510-319.exam Number: C9510-319 Passing Score: 800 Time Limit: 120 min File Version: 1.0 IBM C9510-319 IBM WebSphere Application Server Developer Tools V8.5 with Liberty Profile Version: 1.0 Exam A QUESTION
More informationREMIT Reporting Service
REMIT Reporting Service User Guide Version:1.1 31 March 2015 Deleted: 19 Contents 1. Introduction... 4 2. REMIT Reporting Services Agreement... 5 2.1 Subscription to Services-Registry of Subscribed Users
More informationData Compliance Guidelines Version 1.2
Version 1.2 January 2007 (This page is intentionally blank) Published By: STAR Organization 2007 i Table of Contents 1. Introduction... 1 2. General Data Compliance Criteria... 2 2.1 Implementation Versions...
More informationCA SiteMinder Web Services Security
CA SiteMinder Web Services Security Policy Configuration Guide 12.52 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation
More informationThe contents of this publication the specifications of this application are subject to change without notice.
V.1.0. Publication Notice The contents of this publication the specifications of this application are subject to change without notice. GFI Software reserves the right to make changes without notice to
More informationRelease Notes. OASIS Fall 2015 Application Release Version 1.0
Release Notes OASIS Fall 2015 Application Release 6.8.0 Version 1.0 September 17, 2015 REVISION HISTORY VERSION NO. DATE DESCRIPTION 1.0 09/17/2015 Initial version Page 2 of 12 Release Identification Application/System
More informationSouthwest Power Pool Portal Market Participant General User s Guide
Southwest Power Pool Portal Market Participant General User s Guide 1. Overview... 4 1.1 User Roles... 4 1.1.1 Market Participant Level Roles... 4 1.1.2. Asset Owner Level Roles... 4 1.1.3. Market Operations
More informationCity/Zip Lookup Web Service Implementation Guide Version 1.00
City/Zip Lookup Web Service Implementation Guide Version 1.00 Revised: 10/04/2016 SECTION 1 - NARRATIVE... 1 SECTION 2 - INPUT PARAMETERS... 2 SECTION 3 - OUTPUT PARAMETERS... 3 SECTION 4 - SOAP XML EXAMPLES...
More informationImplementation Guide. afrr capacity market. Version: 0.8
Implementation Guide afrr capacity market Business process: afrr capacity market Version: 0.8 Status: Draft Date: 28.06.2018 1 Revision History Version Release Date Changed by Comments 0.8 Draft A 28.06.2018
More informationBulk Statistics. Feature Summary and Revision History. This chapter provides configuration information for:
This chapter provides configuration information for: Feature Summary and Revision History, page 1 Configuring Communication with the Collection Server, page 2 Viewing Collected Data, page 6 Collecting
More informationXML. Rail Events and Intermodal Ramp Activity
XML Rail Events and Intermodal Ramp Activity Message Implementation Guide Version 1.0.0 Change history Version Date Comments 1.0.0 10-Aug-2016 Initial version Contact our ecommerce team: Hamburg Süd Customer
More informationFNM Expansion Training Webinar
FNM Expansion Training Webinar Cynthia Hinman Lead Client Trainer August 11, 2014 The information contained in these materials is provided for general information only and does not constitute legal or
More informationMODIS Screens User Guide for ETR and ACER REMIT. Market Operation Data Interface System Market Participant Screens General Screens
MODIS Screens User Guide for ETR and ACER REMIT Market Operation Data Interface System Market Participant Screens General Screens MODIS User Guide Screens V0 18 Page 1 of 33 Contents 1 Purpose... 3 2 MODIS
More informationIntroduction to IEC Landis+Gyr May 27, 2015
Introduction to IEC61968-100 IEC61968-100 Implementation Profiles 2 IEC61968-100.... The Basics (1) IEC61968-100 reflects best practices and integration experiences and has been in effective use since
More informationMarket Participant User Guide ISO Reliability Requirements Application (IRR UI)
Market Participant User Guide ISO Reliability Requirements Application (IRR UI) Version 1 Last Revised: November 21, 2011 ISO Public 1 of 84 Table of Contents 1. Introduction... 5 1.1 Resource Adequacy
More informationWeb Service Elements. Element Specifications for Cisco Unified CVP VXML Server and Cisco Unified Call Studio Release 10.0(1) 1
Along with Action and Decision elements, another way to perform backend interactions and obtain real-time data is via the Web Service element. This element leverages industry standards, such as the Web
More informationXML. Truck Events and Transportation Carrier Shipment Status Message
XML Truck Events and Transportation Carrier Shipment Status Message Message Implementation Guide Version 1.0.0 Change history Version Date Comments 1.0.0 15-Aug-2016 Initial version Contact our ecommerce
More informationSpatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE)
Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Model Builder User Guide Version 1.3 (24 April 2018) Prepared For: US Army Corps of Engineers 2018 Revision History Model
More informationSchema Change Request ASWG Change Management Process Draft Version 0.2
Schema Change Request Document ID CR#6 Change Type Enhancement Title Date 7 October, 2003 Prepared By Anne Waller PRIORITY Notes Page 1 of 15 Document Control Version Date Author Summary of Change 0.1
More informationXchangeCore Quick Start Guide to the Incident Management Service And Incident Work Products
XchangeCore Quick Start Guide to the Incident Management Service And Incident Work Products The XchangeCore Community www.xchangecore.com Revision Number Date Description Revisions R05C00 6/16/2014 Initial
More informationSAP Disclosure Management Document Version: 10.0 SP SAP Taxonomy Designer
SAP Disclosure Management Document Version: 10.0 SP08-2014-03-13 Table of Contents 1 What is the Taxonomy Designer?.... 4 1.1 Taxonomy Designer Features....4 2 Using the Taxonomy Designer Interface...5
More informationACORD Web Services Profile: 2.0 vs. 1.0
ACORD Web Services Profile: 2.0 vs. 1.0 Kevin Schipani, Serge Cayron ACORD ACORD 2009 Agenda Introduction ti to AWSP 2.0 Members views - Requirements and Use Cases Conclusion Background AWSP 1 for initial
More informationipass API Guide Version 1.4 October
ipass API Guide Version 1.4 October Overview 4 Getting an ipass API...4 Base s...4 EndPoints...4 Encoding...5 Authentication...5 User Object...5 Create...8 Update...8 Suspend...9 Activate...9 Delete...9
More informationGetting started with OWASP WebGoat 4.0 and SOAPUI.
Getting started with OWASP WebGoat 4.0 and SOAPUI. Hacking web services, an introduction. Version 1.0 by Philippe Bogaerts mailto:philippe.bogaerts@radarhack.com http://www.radarhack.com 1. Introduction
More informationWe appreciate your feedback
Publishing date: 02/07/2014 Document title: We appreciate your feedback Please click on the icon to take a 5 online survey and provide your feedback about this document REMIT ELECTRICITY NOMINATIONS REPORTING
More informationAttestation Service for Intel Software Guard Extensions (Intel SGX): API Documentation. Revision: 3.0
Attestation Service for Intel Software Guard Extensions (Intel SGX): API Documentation Revision: 3.0 1 1 Abbreviations... 4 2 Attestation Service for Intel SGX... 5 Supported environments... 5 Authentication...
More informationdciphering Computing Amazon Seller Central Soap/XML Services as of Jan/2009
Introduction: If you have had opportunity to review the documentation for Amazon s Web Services API for Seller Central you may have been impressed with all the documentation available and thought it would
More informationCopyright 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13
1 Roadmap Dave Bain PeopleSoft Product Management 2 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any
More informationBatch Submission Manual
Batch Submission Manual Last Modified: August 14, 2012 Batch Submission Manual 8/14/2012 Page 1 of 17 TABLE OF CONTENTS 1. Purpose... 3 2. Introduction... 4 2.1 The XML Batch Submission Method... 4 2.2
More informationService Design Description for the xxx Service <xyz Technology>
ENAV20-9.24 Service Design Description for the xxx Service Contents 1 Introduction... 4 1.1 Purpose of the Document... 4 1.2 Intended Readership... 5 1.3 Inputs from Other Projects...
More informationINTERNET TRANSACTION SERVICES CORE
11.19.2015 INTERNET TRANSACTION SERVICES CORE User Guide Version 1.0.2 CAQH CORE Operating Rules Connectivity Specification v2.2.0 Contents Contents 1 Introduction... 3 2 Specifications... 4 2.1 CORE Connectivity
More informationIntroduction to the Prime Fulfillment API
CHAPTER 1 The Cisco Prime Fulfillment application program interface (API) allows you to use operations support system (OSS) client programs to connect to the Prime Fulfillment system. The Prime Fulfillment
More informationAlternate Data Submission Users Guide
Alternate Data Submission Users Guide AHRQ Common Formats for Event Reporting Community Pharmacy Version 1.0 Change Log Version Author Date Revision 1.0 PSOPPC 12/2016 Initial Version 1.1 PSOPPC 04/2018
More informationCancer Waiting Times. Getting Started with Beta Testing. Beta Testing period: 01 February May Copyright 2018 NHS Digital
Getting Started with Beta Testing Beta Testing period: 01 February 2018 03 May 2018 Copyright 2018 NHS Digital Document management Revision History Version Date Summary of Changes 0.1 23/03/2018 Initial
More informationNational Identity Exchange Federation. Web Services System- to- System Profile. Version 1.1
National Identity Exchange Federation Web Services System- to- System Profile Version 1.1 July 24, 2015 Table of Contents TABLE OF CONTENTS I 1. TARGET AUDIENCE AND PURPOSE 1 2. NIEF IDENTITY TRUST FRAMEWORK
More informationScheduling Infrastructure Business Rules (SIBR) User Interface (UI) Update
Scheduling Infrastructure Business Rules (SIBR) User Interface (UI) Update Heidi Carder Senior Client Trainer, Training & Readiness February 21, 2018 The information contained in these materials is provided
More informationPartner Web Services. GetMyPrice Service Manual
Partner Web Services GetMyPrice Service Manual Contents 1 Introduction... 5 1.1 Overview... 5 1.2 Supporting Resources... 5 2 Service Overview... 5 2.1 Benefits of GetMyPrice Service... 6 3 Service Endpoints...
More informationSCA11H CLOUD SERVER INTERFACE SPECIFICATION
1 (12) SCA11H CLOUD SERVER INTERFACE SPECIFICATION SCA11H Doc. No. 1325 Rev. 4 2 (12) Table of Contents 1 Introduction...3 2 Service information...3 3 Writing Data...4 3.1 Header...4 3.2 Message body...4
More information