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

1 Machine to Machine Interface Update

Machine-to-Machine Interface Update

January 10, 2007

Daryl Shing


December 31st Deliverables

• DRAFT Machine-to-Machine Interface StrategyOutlines 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 SpecificationsSample Machine-to-Machines Interface Specifications covering a subset of Market Transactions, Market Information and Notifications.

• Nodal Sandbox RoadmapDescribes the goal and strategy for the Nodal Sandbox environment.


Machine-to-Machine Interface List

Potential Source System Operation Count

CRR 22

EMS 12

MMS 70

NMMS 6

OS 6

EDW/CS 16

Total 132


Next Steps

• Nodal Sandbox

– Jan 31st 2007 - Interoperability Starts ‘Whoami’ service will be made available to the Market.

– Monthly – Additions to the Sandbox capabilities.

– September 1st 2007 - Interoperability Ends

• Machine-to-Machine Interfaces

– Jan 31st 2007 - Definition of Interfaces for Bidding and Notifications.

– Feb 28th 2007 - Definition of Interfaces for Awards and Obligations and a partial set of Interfaces for Market Information Requests.

– March 31st 2007 Final StrategyFinal List of InterfacesComplete Set of Interface Specifications


Feedback

• 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.


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.


Initial Integration Analysis Artifact - CMM Interfaces (Logical)


Initial Integration Analysis Artifact - S&B Interfaces (Logical)


Registration Interfaces Preliminary View (working on more detailed Interfaces view)


Artifact - 1 System Interface Matrix

• Captures information like Data Elements, Element Attributes, Frequency, Volumetrics, Business Events etc.


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

7/11/2006 7/12/2006 7/13/2006 7/14/2006 7/15/2006 7/16/2006 7/17/2006 7/18/2006 7/19/2006 7/20/2006 7/21/2006

7/11/2006 7/12/2006 7/13/2006 7/14/2006 7/15/2006 7/16/2006 7/17/2006 7/18/2006 7/19/2006 7/20/2006 7/21/2006

7/11/2006 7/12/2006 7/13/2006 7/14/2006 7/15/2006 7/16/2006 7/17/2006 7/18/2006 7/19/2006 7/20/2006 7/21/2006

7/11/2006 7/12/2006 7/13/2006 7/14/2006 7/15/2006 7/16/2006 7/17/2006 7/18/2006 7/19/2006 7/20/2006 7/21/2006

7/10/2006Start CMM Process - 2 AM

7/10/2006Initial Exposure Calculation - 7 AM

7/10/2006Exposure Updated for RTM – 1:30 PM

7/10/2006Collateral Postings by 3 PM

7/10/2006ACL published by 5 PM

CMM

CRR

DAM

RTM

7/11/2006 7/12/2006 7/13/2006 7/14/2006 7/15/2006 7/16/2006 7/17/2006 7/18/2006 7/19/2006 7/20/2006 7/21/2006

Settlement

7/11/2006CRR Bidding Window Opens - Midnight

7/11/2006DAM Bidding Closes 10 AM for operating day 7/12/06

7/11/2006DAM Bidding starts 6 AM for operating day 7/12/06

7/22/2006RTM Initial Statement for operating day 7/12/06

7/11/06Day Ahead

7/12/06Operating Day

7/11/06Day Ahead


7/11/06Day Ahead


7/11/06Day Ahead


7/19/2006DAM Payment due for operating day 7/12/06

7/20/2006CRR Auction Invoices complete for operating day 7/12/06

7/13/2006Certified SPP available for OPD 7/12/06 @ 1600

7/11/2006CRR trading cut-off for operating day 7/12/06 7/13/2006

Certified SPP available for operating day 7/12/06 @ 2200

7/14/2006CRR Bidding Window Closes

7/15/2006DAM for operating day 7/12/06 Invoicing Complete

7/19/2006Optimization Complete

7/11/06 – 7/14/06CRR Bidding Window

7/11/06 – 7/19/06CRR Optimization

Unified Schedule - One Month of Operating Days

10/25/2006 Page 5 of 5


Questions

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

Documents

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