Integration Update 1 External Interfaces & Integration Aug Stephen Kerr

Integration Update 2 Agenda Updates to External Interface Specification New Services Sandbox & EDS deployment Integration Development Feedback

Integration Update 3 Updates to External Interface Specification Revision 1.02 was posted on July 20 th for review & updated to v 1.03 on August 9 th. The changes in version 1.03 are –Reflected restriction on use of 24:00 described by section 1.6 into sections and –Extended description of notifications to describe use of port 443 and signing requirements in section 5.3 –BidSet ‘get’ and ‘cancel’ operations must be for the same trade date –Corrected operatingMode tag in description –Removed tradeId as a key for all types of trades, as this is not supported by MMS –Corrected Figure 13 to not use BidSet for cancel –Clarified the use of ‘short name’ as the QSE ID as opposed to DUNS number for use on header/Source –Corrected CRR –Modify get SystemStatus to return version information –Clarified that only one BidSet can be provided on a submission in section 3.2. –Order of element types in BidSet modified to be consistent with MMS needs –Added externalId to BidSet examples. –Clarified EnergyTrade to specify 15 minute intervals. –Added multiHourBlock indicator to ASOffer –Added externalId to XML examples –Added crrAccountHolderId to section PTP Obligation Bid –Removed expirationTime for ASTrade –Modified examples to use PENDING state –Corrected examples of namespace usage –Inserted new Appendix F to provide representative SOAP examples –Extended description of Error structure in section 3.4 –Clarified that QSE should be identified using the ‘short name’ in the Message/Source, as well as buyer and seller for trades –Revised outage structure, still in draft form In addition, we will provide successful XML examples in future packages

Integration Update 4 Updates to External Interface Specification Comments we deliberately did not address: –There is no way to query notifications We have not planned for this functionality and will need a change request –DC Tie trade needs a buyer and seller To be consistent with MMS functionality –Why was delete output schedule removed from three part offer but delete three part offer remains in the output schedule To be consistent with MMS functionality

Integration Update 5 New services being built The services we are building for end Aug release as loopback services are listed There will be no back-end functionality associated with these services in the Sandbox The back-end systems have not implemented these services yet and are subject to change The Market Information types will be simulated but we have not yet decided what the response will be –Simple document or XML response The services will be deployed to the EDS environment on the transition plan schedule –The highest priorities are to support EDS3 –The lowest priorities relate to future back-end functionality New Market Transaction Services –Self Arranged Ancillary Services –Ancillary Services Offer –Ancillary Services Trade –DAM Energy Bid –DAM Energy Only Offer –Congestion Revenue Rights Offer –PTP Obligation Bid –Self Schedule New Market Information Services –Proxy Curves (highest) –Startup and Shutdown Instructions –Total Regulation –Load Ratio Share –Unit Availability (highest) –Forecasted Load (lowest) –Real-Time System Load (highest) –Market LMPs and SPPs (highest) –Mitigated Curves (highest) New Notifications –Outage Notifications (lowest) –Notices and Alerts (highest) –CRR Awards New Outage Scheduling Services –Outage Creation (lowest)

Integration Update 6 Sandbox & EDS deployment Following services are available –Three Part Offer –Incremental/Decremental Offers –Current Operating Plan –Output Schedule –Bid Set Acceptance –Bid Set Errors –Get mRID –System Status –Notifications Defects are being posted here: – Back-end integration with MMS entered test in early August for early EDS3 –Three Part Offer –Incremental/ Decremental Offers –Current Operating Plan –Output Schedule

Integration Update 7 Interface Development Feedback EMS MMS design documents –Few comments received and it is all being addressed –Comment that the design documents did not address the key questions being asked of the EMS MMS interface.