1. Machine to Machine Interface Update 1 Machine-to-Machine Interface Update January 10, 2007 Daryl Shing

2. Machine to Machine Interface Update 2 December 31st Deliverables DRAFT Machine-to-Machine Interface Strategy Outlines the key components of our approach to delivering the Nodal Machine-to-Machine Interfaces. DRAFT Machine-to-Machine Interface List The list of interface operations we expect to support in Nodal. DRAFT Machine-to-Machine Interface Specifications Sample Machine-to-Machines Interface Specifications covering a subset of Market Transactions, Market Information and Notifications. Nodal Sandbox Roadmap Describes the goal and strategy for the Nodal Sandbox environment.

3. Machine to Machine Interface Update 3 Machine-to-Machine Interface List Potential Source SystemOperation Count CRR22 EMS12 MMS70 NMMS6 OS6 EDW/CS16 Total132

4. Machine to Machine Interface Update 4 Next Steps Nodal Sandbox –Jan 31 st 2007 - Interoperability Starts ‘Whoami’ service will be made available to the Market. –Monthly – Additions to the Sandbox capabilities. –September 1 st 2007 - Interoperability Ends Machine-to-Machine Interfaces –Jan 31 st 2007 - Definition of Interfaces for Bidding and Notifications. –Feb 28 th 2007 - Definition of Interfaces for Awards and Obligations and a partial set of Interfaces for Market Information Requests. –March 31 st 2007 Final Strategy Final List of Interfaces Complete Set of Interface Specifications

5. Machine to Machine Interface Update 5 Feedback –Missing Operations? –Concerns with the overall Strategy? –Missing information in the Sample Specifications? –Comments on the proposed Nodal Sandbox? Updated documents will be provided monthly to coincided with each new Sandbox release. Disclaimer: Please be aware that building code against these draft deliverables may result in re-work.

6. Machine to Machine Interface Update 6 Integration Analysis Process Overview Identify Integrations –Functional teams create CSDs. –SoSA captures at the Enterprise Level the integrations required to produce a complete solution. –IDA (Technical Architects, Business Architects), the Project Teams and the Integration Vendor work together to produce Artifacts shown in the next few pages. Produce Requirements, Use Cases and Design –Initial Integration artifacts will capture the following information Data Element Name, Element Attributes, Volumetrics, Data Frequency etc. Business Triggering Events that drive the movement of information –These artifacts will feed Integration Requirements Analysis and Use Cases activities performed by the Integration Vendor Identify gaps, integration characteristics, mismatches and transformations of data that is necessary between systems –Integrations Requirements and Use Cases feed design and implementation of the integration between the systems. –Feed the design back into SoSA.

7. Machine to Machine Interface Update 7 Initial Integration Analysis Artifact - CMM Interfaces (Logical)

8. Machine to Machine Interface Update 8 Initial Integration Analysis Artifact - S&B Interfaces (Logical)

9. Machine to Machine Interface Update 9 Registration Interfaces Preliminary View (working on more detailed Interfaces view)

10. Machine to Machine Interface Update 10 Artifact - 1 System Interface Matrix Captures information like Data Elements, Element Attributes, Frequency, Volumetrics, Business Events etc.

11. Machine to Machine Interface Update 11 Artifact – Business Process Timelines In addition to identifying Interfaces and Interface specs, there are timing issues - basically Business Triggering Events which determine when a particular Business Process has to start –Systems “downstream” are dependent on systems “upstream” to finish before they can kick off their activities –ERCOT will identify and capture these Business Events and thresholds –Create Artifacts to capture this information Build views to Monitor these events from both an Operational and Business Perspective

12. Machine to Machine Interface Update 12 Questions