Top Banner
Retail Market: User Interaction & Data Delivery in Nodal
84

Retail Market: User Interaction & Data Delivery in Nodal

Jan 24, 2016

Download

Documents

Nessa

Retail Market: User Interaction & Data Delivery in Nodal. Legal Disclaimers and Admonitions. Protocol Disclaimer - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Retail Market: User Interaction & Data Delivery in Nodal

Retail Market: User Interaction & Data Delivery in Nodal

Page 2: Retail Market: User Interaction & Data Delivery in Nodal

Slide 2

Legal Disclaimers and Admonitions

Protocol Disclaimer

This presentation provides a general overview of the Texas

Nodal Market Implementation and is not intended to be a

substitute for the ERCOT Nodal Protocols, as amended from

time to time. If any conflict exists between this presentation

and the ERCOT Nodal Protocols, the ERCOT Nodal Protocols

shall control in all respects.

For more information, please visit:

http://nodal.ercot.com/protocols/index.html

Page 3: Retail Market: User Interaction & Data Delivery in Nodal

Slide 3

Legal Disclaimers and Admonitions

Antitrust Admonition

ERCOT strictly prohibits market participants and their

employees who are participating in ERCOT activities from

using their participation in ERCOT activities as a forum for

engaging in practices or communications that violate antitrust

laws. The ERCOT Board has approved guidelines for

Members of ERCOT Committees, subcommittees and working

groups to be reviewed and followed by each market participant

attending ERCOT meetings. For details, please review the

guidelines in the attachments tab of this presentation.

Page 4: Retail Market: User Interaction & Data Delivery in Nodal

Slide 4

Target Audience

This course is intended for the ERCOT Retail Market and is directed towards those Retail Market Participants (MPs) currently using Texas Market Link (TML) and will be utilizing the Market Information System (MIS).

This informational presentation provides MPs with a basic understanding of the layout of the MIS and the differences between today’s TML and tomorrow’s MIS. In addition, detailed information in regards to retail data postings on TML and MIS will be covered at the extract and report level.

MIS and extract and report questions between now and go-live should be submitted to [email protected] or addressed on the Friday Market Trials Market Call scheduled on the ERCOT calendar.

MIS and extract and report questions after Nodal go-live should be directed to your Retail Account Manager. ERCOT Market Information List (EMIL) and extract specification questions should be submitted to [email protected].

Page 5: Retail Market: User Interaction & Data Delivery in Nodal

Market Information System

Page 6: Retail Market: User Interaction & Data Delivery in Nodal

Slide 6

Market Information System Objectives

Upon completion of this section, you will be able to:

• Understand overview and layout of MIS including:

– What is MIS?

– Access and Security

– Data and Information Classification

– Market Information System Design

Page 7: Retail Market: User Interaction & Data Delivery in Nodal

Slide 7

What is MIS?

Main Entry: Market Information SystemAcronym: MISFunction: ERCOT Portal User InterfaceCurrently Scheduled Live Date: 10/12/20101 : a centralized Portal for access to information, data and applications.2 : link farm - https://mis.ercot.com/pps/tibco/mis/ accesses the MIS in the Market Trials environment3: Texas Market Link (TML) replacement

• Using a production digital certificate, Market Participants (MPs) may access the MIS

during our current Market Trials activities. This environment does not currently contain all

postings that will be available at Nodal go-live. The data currently available is considered

Market Trials test data.

• MIS contains links to all external deliverables for information specifically required by Nodal

Protocols and Other Binding Documents. Per Nodal Protocol 12.2(4), ERCOT may not

use the MIS to post information beyond that specifically required in these protocols.

• Texas Market Link (TML) will stay active to support Retail and Zonal settlements postings.

The decommission effort will be managed through the ERCOT project process.

Page 8: Retail Market: User Interaction & Data Delivery in Nodal

Slide 8

Access and Security

• MIS is securely authenticated by the use of the digital certificate, which is

assigned based on entity types and DUNS configuration. If an entity serves as

more than one entity type, they would need a digital certificate for each.

• The MP User Security Administrator (USA) is responsible for assigning

employee digital certificates and roles.

• Below are the Nodal digital certificate roles that will be used for MIS access:

• LSE_EXTRACTS

• TDSP_EXTRACTS

• MP_VIEW_SWITCH

• MP_CREATE_SWITCH

• MARKETRAK

• In the event an MIS session times out, the user must open a new browser and

re-authenticate with their digital certificate.

Page 9: Retail Market: User Interaction & Data Delivery in Nodal

Slide 9

Data and Information Classification Types

• Public

• Public data is available on the MIS with corresponding links on

ERCOT.com. This data is considered ‘Public’ on TML today.

• Secure

• Secure data is data accessible to all MPs possessing a valid Digital

Certificate. This data classification does not exist on TML today.

• Certified

• Certified data is DUNS number specific data. This is data

considered ‘Private’ on TML today.

Page 10: Retail Market: User Interaction & Data Delivery in Nodal

Slide 10

Market Information System Design

• MIS has been designed to more closely match the layout of

ERCOT.com where functional areas and items are grouped together.

• Main and sub pages of the MIS are referred to as LANDING PAGES.

• Landing pages contain grouped content within PORTLETS. Certified

portlets are configured based on entity type. Therefore, one landing

page, will likely look different for each entity type.

• Portlets are broken down by data classification type:

• Public

• Secure

• Certified

Page 11: Retail Market: User Interaction & Data Delivery in Nodal

Slide 11

Market Information System Homepage

Page 12: Retail Market: User Interaction & Data Delivery in Nodal

Slide 12

Market Information System Design

• Dashboards

• Near real-time data feeds available on MIS secure area.

• Search

• Market Participants will have the ability to search on the MIS.

• View By Protocol (VBP)

• Listing of all MIS postings ordered by protocol section.

• Access to data based on role assignment by the company’s USA.

Page 13: Retail Market: User Interaction & Data Delivery in Nodal

Slide 13

View By Protocol

Page 14: Retail Market: User Interaction & Data Delivery in Nodal

Data Delivery

Today’s TML Functionality

vs.

Tomorrow’s MIS Functionality

Page 15: Retail Market: User Interaction & Data Delivery in Nodal

Slide 15

Data Delivery Objectives

Upon completion, you will be able to:

• Recognize and understand differences in functionality

between TML and MIS for:

– Report Explorer vs. Reports and Extracts Index, Landing

Pages

– Public Extracts and Reports

• Retail Applications

Page 16: Retail Market: User Interaction & Data Delivery in Nodal

Slide 16

Report Explorer

TML Today:• One location, one Market Participant folder per DUNS number.

• Alphabetical list of sub-folders for extracts/reports.

• As of Nodal go-live, TML will only display Retail and Zonal settlements data

postings.

Page 17: Retail Market: User Interaction & Data Delivery in Nodal

Slide 17

Reports and Extracts Index

MIS Tomorrow:

• Reports and Extracts Index

• Dynamic alphabetical listing of reports available to the Market Participant based on

availability of data. Access to data based on role assignment by the company’s

USA.

• As of Nodal go-live, MIS will only display Retail and Nodal data postings.

Page 18: Retail Market: User Interaction & Data Delivery in Nodal

Slide 18

Landing Pages

MIS Tomorrow:

• Multiple ‘Landing Pages’ and ‘Portlets’ broken down by data

classification type: • Public

• Secure

• Certified

Page 19: Retail Market: User Interaction & Data Delivery in Nodal

Slide 19

Public Extracts and Reports

TML Today:

• One Sub-folder ‘Public’• Alphabetical listing

• Accessible from ERCOT.com

MIS Tomorrow:

• Multiple ‘Public’ portlets on various Landing Pages grouped

by functional areas:• Alphabetical listing within portlet

• Accessible from ERCOT.com

Page 20: Retail Market: User Interaction & Data Delivery in Nodal

Slide 20

Retail Applications

TML Today:

• Available under Archive and Market Activities Tabs based on Roles

– Portal Resources◦ MarkeTrak

– Customer Switching◦ Create Enrollment, Create Move In, Create Move Out

– Continuous Service Agreements◦ Establish CSA, Delete CSA

– Query ESIID Transaction◦ Find ESIID, Find Transaction

– Schedule an Extract◦ Data Request – Schedule, Schedule/Unschedule an Extract

Page 21: Retail Market: User Interaction & Data Delivery in Nodal

Slide 21

Retail Applications

MIS Tomorrow:

• Available under the Applications Page based on digital certificate roles:– MarkeTrak

– Create Enrollment

– Create Move In

– Create Move Out

– Establish CSA

– Delete CSA

– Find ESIID

– Find Transaction

– Market Data Transparency

– Extract Subscriber

NOTES:

• The Retail applications will look like TML when clicked on in MIS until TML is

decommissioned.

• Market Data Transparency (MDT) application will be a redirect back to TML until TML is

decommissioned .

Page 22: Retail Market: User Interaction & Data Delivery in Nodal

Slide 22

Retail Applications

Page 23: Retail Market: User Interaction & Data Delivery in Nodal

Slide 23

Extract Scheduler vs Extract Subscriber

TML Today:

• Schedule an Extract

• Schedule/Unschedule an Extract

• Role based function allowing MPs the ability to schedule COMS private extracts

• Ability to schedule and unschedule

MIS Tomorrow:

• Extract Subscriber

• Role based function allowing MPs the ability to schedule COMS certified extracts

• Choice of output format (i.e. csv, xml, etc.)

• Ability to schedule and unschedule

• Note: All currently scheduled MP extracts for the Zonal and Retail markets from TML

Extract Scheduler will be stay scheduled with the go-live of Extract Subscriber

Page 24: Retail Market: User Interaction & Data Delivery in Nodal

Slide 24

Extract Subscriber

Page 25: Retail Market: User Interaction & Data Delivery in Nodal

Points of Entry

Downloading Content from ERCOT

Delivery Options and How They Are Used

Page 26: Retail Market: User Interaction & Data Delivery in Nodal

Slide 26

Point of Entry Objectives

Upon completion, you will be able to:

• Identify list and function of the available points of entry for

viewing and downloading data from ERCOT:

– TML

– MIS

– Retail API

– External Web Services

– ERCOT.com

Page 27: Retail Market: User Interaction & Data Delivery in Nodal

Slide 27

Texas Market Link

TML Today:

• End User - Person to GUI

• MP can view and download data

• Not Protocol Driven

• Mostly CSV postings

• ERCOT Market Information List (EMIL) will contain Last Run

Dates for retiring extracts and reports.

• TML decommissioning will occur through the ERCOT project

process. Project is currently included on the 2011 Project Priority

List (PPL).

Page 28: Retail Market: User Interaction & Data Delivery in Nodal

Slide 28

Market Information System

MIS Tomorrow:

• End User - Person to GUI

• MP can view and download data

• Protocol and Other Binding Documents postings only

• Mostly zip files containing XML and CSV files

• ERCOT Market Information List (EMIL) will contain list of

available postings

• Replaces the TML after decommission efforts

Page 29: Retail Market: User Interaction & Data Delivery in Nodal

Slide 29

Retail API

Retail API Today and Tomorrow:

• End User – Machine to Machine Interface

• MP can retrieve data based on Report Type ID and date

• Type: any valid report type ID (either type name or type id) or ‘All’

• Date: any valid date (YYYYMMDD) or ‘All’

• Utilized for both TML and MIS postings

Page 30: Retail Market: User Interaction & Data Delivery in Nodal

Slide 30

External Web Services

EWS Tomorrow:

• End User – Machine to Machine Interface

• EWS functions:• Market Transactions

• Submit/Query/Update/Cancel Bids, Offers, Trades and Schedules

• Market Information

• Get Awards, Forecasted/System/Total Load, LMPs, SPPs, MCPCs, etc

• Get Reports

• Get Notifications

• Using ‘Get Report’, MP can retrieve data based on Report Type ID and date

• Type: any valid report type id

• Date: StartTime and EndTime optional elements

• Utilized for both TML and MIS postings

• EIP – External Interface Specifications posted at:

http://nodal.ercot.com/readiness/sandbox/index.html

Page 31: Retail Market: User Interaction & Data Delivery in Nodal

Slide 31

ERCOT.com

ERCOT.com Today:

• All user access to public data.

• Supports zonal postings, stakeholder services and ERCOT corporate

communications publications.

• Information not limited by protocols.

ERCOT.com Tomorrow:

• All user access to public data.

• Supports nodal postings, stakeholder services and ERCOT corporate

communications publications.

• Information not limited by protocols.

• Zonal grid information and market information pages will be re-designed

to include Nodal public postings.

Page 32: Retail Market: User Interaction & Data Delivery in Nodal

Supporting Documentation

Page 33: Retail Market: User Interaction & Data Delivery in Nodal

Slide 33

ERCOT Market Information List

EMIL

• Contains information on all required external deliverables as required by Nodal

Protocol 12.2(4).

ERCOT.com Today:

• Replaces the Extract and Report Information Matrix posted at

http://www.ercot.com/services/mdt/

Nodal.ERCOT.com Today:

• Available under Key Documents at

http://nodal.ercot.com/readiness/reports/index.html

ERCOT.com and MIS Tomorrow:

• Will be available under Key Documents at http://www.ercot.com/services/mdt/

• Available on the Services Landing Page in the Supporting Information Portlet

Page 34: Retail Market: User Interaction & Data Delivery in Nodal

Slide 34

ERCOT Market Information List (EMIL)

EMIL can be used for a variety of reasons including:

• Sorting and Filtering as needed

• Viewing new Nodal required deliverables

• Details on Protocol section or Market Guide requirements

for each published item

• Finding EMIL Index # to locate relevant specifications in

appropriate documentation

• Acquiring Report Type ID for the ‘Get Report’ Web Services

• Currently adding information for Nodal go-live

extracts/reports including first post date and Zonal

extracts/reports last post date and replacement information

Page 35: Retail Market: User Interaction & Data Delivery in Nodal

Slide 35

EMIL

Page 36: Retail Market: User Interaction & Data Delivery in Nodal

Slide 36

EMIL

Page 37: Retail Market: User Interaction & Data Delivery in Nodal

Slide 37

EMIL

Page 38: Retail Market: User Interaction & Data Delivery in Nodal

Slide 38

EMIL

Information is categorized:• Nodal• Zonal/Nodal – No Change, • Zonal/Nodal – Modify• Retail and Zonal – Will Retire

Page 39: Retail Market: User Interaction & Data Delivery in Nodal

Slide 39

EMIL

EMIL Contains:• Index # and corresponding Report ID

• Product Name

• Generating Frequency

• Protocol Reference(s)

• Location or method of distribution (MIS, API, etc.)

• Security Classification

Page 40: Retail Market: User Interaction & Data Delivery in Nodal

Slide 40

EMIL

EMIL Tab• Items located on the EMIL tab in the EMIL list are required

protocol or market guide postings.

Page 41: Retail Market: User Interaction & Data Delivery in Nodal

Slide 41

EMIL

Non MIS Postings Tab

• Non-protocol-driven information posted to http://ERCOT.com

• Same overview information

• Information contained here includes all legal and media

references, all market rules postings and any reports not

required by Protocols

Page 42: Retail Market: User Interaction & Data Delivery in Nodal

Slide 42

EMIL

Applications Web Services Tab• Includes all Retail Web Services, Market Data Transparency Web

Services and all Nodal Web Services in support of nodal and as

required by the Protocols

• Utilize ‘Get Report’ feature to retrieve documents with an assigned

Report ID

• All other Web Services are submission, change, cancel or query

functions.

Page 43: Retail Market: User Interaction & Data Delivery in Nodal

Slide 43

EMIL

Alerts & Notices Tab• Includes all Alerts & Notifications as required by the protocols and

posted to the MIS and/or the MMS and OS User Interfaces.

• The items outlined in the EIP Specifications are delivered automatically

via the Nodal Web Services to the Market Participant ‘computer to

computer’.

• There are additional Notifications that are created and published via the

MIS and post to either the MIS UI and/or ERCOT.com.

Page 44: Retail Market: User Interaction & Data Delivery in Nodal

Slide 44

DDLs and XSDs

ERCOT.com and TML Today:

• Available under DDLs or XSDs at http://www.ercot.com/services/mdt/

• Available on TML under the Public Folder, Sub-Folder Extract Data Definitions

Nodal.ERCOT.com Today:

• Drafts available on the Readiness Center at

http://nodal.ercot.com/readiness/reports/index.html

ERCOT.com and MIS Tomorrow:

• Available under DDLs or XSDs at http://www.ercot.com/services/mdt/

• Available on the Services Landing Page in the Supporting Information Portlet

Page 45: Retail Market: User Interaction & Data Delivery in Nodal

Slide 45

DDLs and XSDs

Data Definition Language (DDL)

XML Schema Definitions (XSD)

• Provides necessary information that allows users to load ERCOT data into their own environments

• Contains metadata information, including:

◦ Data type of each field

◦ Brief description of the data that is to be loaded into each column

◦ Any table or character/precision constraints or alterations

Page 46: Retail Market: User Interaction & Data Delivery in Nodal

Slide 46

Example – Settlements DDL

DDL provides structure for CSV file

Page 47: Retail Market: User Interaction & Data Delivery in Nodal

Slide 47

Example – Settlements DDL

DDL table/column definitions

Page 48: Retail Market: User Interaction & Data Delivery in Nodal

Slide 48

Example – Settlements XSD

XSD files provide format & tag info for your

XML files

(DDL files provide structure for CSV file)

Page 49: Retail Market: User Interaction & Data Delivery in Nodal

Slide 49

Example – Settlements XSD

Page 50: Retail Market: User Interaction & Data Delivery in Nodal

Slide 50

User Guides

ERCOT.com Today:

• Zonal User Guides available at http://www.ercot.com/services/mdt/userguides/

Nodal.ERCOT.com Today:

• Draft Nodal User Guides available Key Documents at

http://nodal.ercot.com/readiness/reports/index.html

ERCOT.com and MIS Tomorrow:

• All active User Guides available at

http://www.ercot.com/services/mdt/userguides/

• Available on the Services Landing Page in the Supporting Information Portlet

Page 51: Retail Market: User Interaction & Data Delivery in Nodal

Slide 51

Extract and Report Specifications

Nodal.ERCOT.com Today:

• Specifications are available at

http://nodal.ercot.com/readiness/reports/sp/index.html

• Available for new or modified nodal extracts and reports

• Excludes ad-hoc manual postings

ERCOT.com Tomorrow:

• Specifications will be available under Key Documents at

http://www.ercot.com/services/mdt/

• Available for new or modified nodal extracts and reports

• Excludes ad-hoc manual postings

Page 52: Retail Market: User Interaction & Data Delivery in Nodal

Slide 52

Extract and Report Specifications

Page 53: Retail Market: User Interaction & Data Delivery in Nodal

Slide 53

Extract and Report Specifications

Page 54: Retail Market: User Interaction & Data Delivery in Nodal

Slide 54

Example – DAM MODE Specification

Page 55: Retail Market: User Interaction & Data Delivery in Nodal

Slide 55

Example – DAM MODE Specification

Page 56: Retail Market: User Interaction & Data Delivery in Nodal

Questions

Page 57: Retail Market: User Interaction & Data Delivery in Nodal

Extracts & Reports

Page 58: Retail Market: User Interaction & Data Delivery in Nodal

Slide 58

Objectives

Upon completion, you will be able to:

• Identify list of extracts and reports used in Retail Market:

– No change

– Modified

– Retiring & Replaced

• Understand data posting location

• Identify location of reference materials

Page 59: Retail Market: User Interaction & Data Delivery in Nodal

Slide 59

No Change

This list of extracts and reports will have no change to the

content and content format with the transition into

Nodal.

• Posting: TML, MIS. Public postings also available on www.ercot.com.

Page 60: Retail Market: User Interaction & Data Delivery in Nodal

Slide 60

Modified

This list of extracts and reports will have modifications to

the name, content and/or content format with the

transition into Nodal.

• Posting: TML, MIS. Public postings also available on www.ercot.com.

Page 61: Retail Market: User Interaction & Data Delivery in Nodal

Slide 61

Default Profile ESIID Report

• Posting: TML, MIS• Specification: COPG-197 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Zonal version will continue to post through the True-Up Settlement of all zonal operating days (<= 11/30/2010)

– Nodal version will post to same location at zonal version. This means you could have 2 postings per day.

– Nodal filename will be different than zonal file name

Page 62: Retail Market: User Interaction & Data Delivery in Nodal

Slide 62

ESIID Service History and Usage Extract

• Posting: TML, MIS• Specification: ZP12-245 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL:

http://nodal.ercot.com/readiness/reports/DDL/DDL/Draft%20ESIID%20Extract%20DDL%20v.09.txt

• Draft User Guide: Draft ESIID Service History & Usage Extract User Guide - http://nodal.ercot.com/readiness/reports/index.html

• Draft Join Documentation: ESIID Join Diagram v0.02 - http://nodal.ercot.com/readiness/reports/index.html

• Summary of changes:– Addition of tables SETTLEMENTPOINT, SETLPOINTTYPE, and

SETLPOINTHISTORY

Page 63: Retail Market: User Interaction & Data Delivery in Nodal

Slide 63

Load Estimation Counts Report

• Posting: TML, MIS• Specification: COPG-316 (public) & COPG-767 (certified) worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Zonal version will continue to post through the True-Up Settlement of all zonal operating days (<= 11/30/2010)

– Nodal version will post to same location at zonal version. This means you could have 2 postings per day.

– Nodal filename will be different than zonal file name– Nodal file will contain more than one operating day

Page 64: Retail Market: User Interaction & Data Delivery in Nodal

Slide 64

Missing Consumption Report

• Posting: TML, MIS• Specification: NP10-771 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– ESIID Record will be reported when there is no NIDR, IDR, AMS interval data loaded (based on the Profile Code) for sysdate – 38 days.

– Dropping the Last Received column, which is blank today.– Header will include:

◦ ID

◦ MREDUNS

◦ METERTYPE

Page 65: Retail Market: User Interaction & Data Delivery in Nodal

Slide 65

Provide All ESIID Extract Records (web service)

• Posting: TML, MIS• Specification: COMS-438 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft XSD: Draft Market Data Transparency XSD will be posted at

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft Market Data Transparency User Guide

http://nodal.ercot.com/readiness/reports/index.html• Summary of changes:

– Addition of tables SETTLEMENTPOINT, SETLPOINTTYPE, and SETLPOINTHISTORY

Page 66: Retail Market: User Interaction & Data Delivery in Nodal

Slide 66

Public Reference Data Extract

• Posting: TML, MIS

• Specification: ZP12-465 worksheet - http://nodal.ercot.com/readiness/reports/sp/index.html

• Draft DDL: DRAFT PRDE DDL v0.14 - http://nodal.ercot.com/readiness/reports/DDL/index.html

• Draft XSD: DRAFT PRDE XSD v0.14 - http://nodal.ercot.com/readiness/reports/XSD/index.html

• Draft User Guide: Draft PRDE User Guide - http://nodal.ercot.com/readiness/reports/index.html

• Summary of changes:

– Available in CSV and XML

– Addition of tables to support the following extracts:

Page 67: Retail Market: User Interaction & Data Delivery in Nodal

Slide 67

TDSP Distribution Loss Factors Actual

• Posting: TML, MIS, http://www.ercot.com/mktinfo/data_agg/• Specification: NP13-9 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Name change: Actual TDSP Distribution Loss Factors Report– Removed multiple header rows– Added the Recorder, TDSP Code, DUNS number, Loss Code, and

LSTIME columns

RECORDER TDSPNAME TDSPCODE DUNSNUMBER LOSSCODE STARTTIME STOPTIME LSTIME 0:15 0:30 …LACTERCOT 9/27/2009 9/27/2009 23:59 2/19/2010 9:08 31564 30955ACTDISTLOSSFACT_999_D TEST TDSP 999 123456789 D 9/27/2009 9/27/2009 23:59 2/19/2010 9:08 0.035699869 0.035801713ACTDISTLOSSFACT_999_E TEST TDSP 999 123456789 E 9/27/2009 9/27/2009 23:59 2/19/2010 9:08 0.011443222 0.011285544

Page 68: Retail Market: User Interaction & Data Delivery in Nodal

Slide 68

TDSP Distribution Loss Factors Forecasted

• Posting: TML, MIS, http://www.ercot.com/mktinfo/data_agg/• Specification: NP13-262 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Name change: Forecasted TDSP Distribution Loss Factors Report– Removed multiple header rows– Added the Recorder, TDSP Code, DUNS number, Loss Code, and

LSTIME columns– Added a separate header row for the LFORERCOT data record that

is reported for 24 hourly intervals

RECORDER TDSPNAME TDSPCODE DUNSNUMBER LOSSCODE STARTTIME STOPTIME LSTIME 1:00 2:00 3:00 …LFORERCOT 9/30/2009 9/30/2009 23:59 2/19/2010 9:08 29392 27754 26661RECORDER TDSPNAME TDSPCODE DUNSNUMBER LOSSCODE STARTTIME STOPTIME LSTIME 0:15 0:30 0:45 ….DISTLOSSFACT_999_D TEST TDSP 999 123456789 D 9/30/2009 9/30/2009 23:59 2/19/2010 9:08 0.036136216 0.036136216 0.036136216DISTLOSSFACT_999_E TEST TDSP 999 123456789 E 9/30/2009 9/30/2009 23:59 2/19/2010 9:08 0.010886721 0.010886721 0.010886721

Page 69: Retail Market: User Interaction & Data Delivery in Nodal

Slide 69

TDSP Transmission Loss Factors Actual

• Posting: TML, MIS, http://www.ercot.com/mktinfo/data_agg/• Specification: NP13-14 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Name change: Actual TDSP Transmission Loss Factors Report– Removed multiple header rows– Added the Recorder and LSTIME columns

RECORDER STARTTIME STOPTIME LSTIME 0:15 0:30 …LACTERCOT 9/27/2009 9/27/2009 23:59 2/19/2010 9:08 31564 30955ACTLOSSFACT 9/27/2009 9/27/2009 23:59 2/19/2010 9:08 0.023970884 0.024053287

Page 70: Retail Market: User Interaction & Data Delivery in Nodal

Slide 70

TDSP Transmission Loss Factors Forecasted

• Posting: TML, MIS, http://www.ercot.com/mktinfo/data_agg/• Specification: NP13-262 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Summary of changes:

– Name change: Forecasted TDSP Transmission Loss Factors Report– Added the Recorder and LSTIME columns– Added a separate header row for the LFORERCOT data record that

is reported for 24 hourly intervals

RECORDER STARTTIME STOPTIME LSTIME 1:00 2:00 3:00 4:00 …LFORERCOT 9/30/2009 9/30/2009 23:59 2/19/2010 9:08 29392 27754 26661 26146RECORDER STARTTIME STOPTIME LSTIME 0:15 0:30 0:45 1:00 …FORTLOSSFACT 9/30/2009 9/30/2009 23:59 2/19/2010 9:08 0.024264773 0.024264773 0.024264773 0.024264773

Page 71: Retail Market: User Interaction & Data Delivery in Nodal

Slide 71

Retiring & Replaced

This list of extracts and reports will be retiring with the

transition into Nodal and have a corresponding

extract/report or new posting for the data.

• Posting: MIS

Data Aggregation Daily Postings (UFE Reports)/Unaccounted For EnergyLoad Estimation Volumes – CertifiedLoad Estimation Volumes – PublicLoad ExtractProvide Public Data Extract (web service)WS and NWS IDR Proxy Dates

Page 72: Retail Market: User Interaction & Data Delivery in Nodal

Slide 72

Data Aggregation Daily Postings (UFE Reports)/Unaccounted For Energy

Data Aggregation Daily Postings (UFE Reports)/Unaccounted For Energy

retires with the last settlement of the last Zonal operating day (11/30/2010 to be posted ~06/2011)– Posting: TML, http://www.ercot.com/mktinfo/data_agg/

Real Time Market Market Operating Day Extract (RTM MODE) will include load data for Nodal operating days (12/1/2010 first operating day)– Posting: MIS

Page 73: Retail Market: User Interaction & Data Delivery in Nodal

Slide 73

Data Aggregation Daily Postings (UFE Reports)/Unaccounted For Energy - continued

Information on RTM MODE:• Specification: NP12-749 worksheets -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL: DRAFT Settlements DDL v0.14 -

http://nodal.ercot.com/readiness/reports/DDL/index.html• Draft XSD: DRAFT Settlements XSD v0.14 -

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft Settlements User Guide -

http://nodal.ercot.com/readiness/reports/index.html• Draft Join Documentation: Draft Settlement DDL Join Document -

http://nodal.ercot.com/readiness/reports/index.html• Highlights:

– Data is posted by approved operating day– Includes all secure data for the operating day

Page 74: Retail Market: User Interaction & Data Delivery in Nodal

Slide 74

Load Estimation Volumes - Certified

Load Estimation Volumes Certified retires with the last settlement of the last Zonal operating day (11/30/2010 to be posted ~06/2011)– Posting: TML

Real Time Market Consolidated Operating Day Extract (RTM CODE) will include load data for Nodal operating days (12/1/2010 first operating day)– Posting: MIS

Page 75: Retail Market: User Interaction & Data Delivery in Nodal

Slide 75

Load Estimation Volumes - Certified - continued

Information on RTM CODE:• Specification: NP12-747 worksheets -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL: DRAFT Settlements DDL v0.14 -

http://nodal.ercot.com/readiness/reports/DDL/index.html• Draft XSD: DRAFT Settlements XSD v0.14 -

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft Settlements User Guide -

http://nodal.ercot.com/readiness/reports/index.html• Draft Join Documentation: Draft Settlement DDL Join Document -

http://nodal.ercot.com/readiness/reports/index.html• Highlights:

– Data is posted by approved operating day– Includes all certified data for the specific market participant– Must be scheduled using Extract Subscriber

Page 76: Retail Market: User Interaction & Data Delivery in Nodal

Slide 76

Load Estimation Volumes - Public

Load Estimation Volumes Public retires with the last settlement of the last Zonal operating day (11/30/2010 to be posted ~06/2011)– Posting: TML, http://www.ercot.com/mktinfo/data_agg/

Real Time Market Market Operating Day Extract (RTM MODE) will include load data for Nodal operating days (12/1/2010 first operating day)– Posting: MIS

Page 77: Retail Market: User Interaction & Data Delivery in Nodal

Slide 77

Load Estimation Volumes - Public - continued

Information on RTM MODE:• Specification: NP12-749 worksheets -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL: DRAFT Settlements DDL v0.14 -

http://nodal.ercot.com/readiness/reports/DDL/index.html• Draft XSD: DRAFT Settlements XSD v0.14 -

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft Settlements User Guide -

http://nodal.ercot.com/readiness/reports/index.html• Draft Join Documentation: Draft Settlement DDL Join Document -

http://nodal.ercot.com/readiness/reports/index.html• Highlights:

– Data is posted by approved operating day– Includes all secure data for the operating day

Page 78: Retail Market: User Interaction & Data Delivery in Nodal

Slide 78

Load Extract

Load Extract retires with the last settlement of the last Zonal operating day (11/30/2010 to be posted ~06/2011)– Posting: TML

Real Time Market Consolidated Operating Day Extract (RTM CODE) & Real Time Market Market Operating Day Extract (RTM MODE) will include load data for Nodal operating days (12/1/2010 first operating day)– Posting: MIS

Page 79: Retail Market: User Interaction & Data Delivery in Nodal

Slide 79

Load Extract - continued

Information on RTM CODE & RTM MODE:• Specification: NP12-747 & NP 12-749 worksheets -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL: DRAFT Settlements DDL v0.14 -

http://nodal.ercot.com/readiness/reports/DDL/index.html• Draft XSD: DRAFT Settlements XSD v0.14 -

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft Settlements User Guide -

http://nodal.ercot.com/readiness/reports/index.html• Draft Join Documentation: Draft Settlement DDL Join Document -

http://nodal.ercot.com/readiness/reports/index.html• Highlights:

– Data is posted by approved operating day– MODE – includes all secure data for the operating day– CODE – includes all certified data for the specific market participant– CODE – must be scheduled using Extract Subscriber

Page 80: Retail Market: User Interaction & Data Delivery in Nodal

Slide 80

Provide Public Data Extract (web service)

Provide Public Data Extract (web service) retires at Nodal go-live 12/1/2010– Posting: TML

• Draft XSD: Draft Market Data Transparency XSD will be posted at http://nodal.ercot.com/readiness/reports/XSD/index.html

• Draft User Guide: Draft Market Data Transparency User Guide http://nodal.ercot.com/readiness/reports/index.html

Public Reference Data Extract will be posted on a daily basis including a full data set as of the previous day– Posting: MIS, TML

Page 81: Retail Market: User Interaction & Data Delivery in Nodal

Slide 81

WS and NWS Proxy Dates

WS and NWS Proxy Dates retires with the last initial zonal settlement (11/30/2010 operating day to be posted 12/7/2010)– Posting: TML

Public Reference Data Extract will be posted on a daily basis including a full data set as of the previous day– Posting: MIS, TML

Page 82: Retail Market: User Interaction & Data Delivery in Nodal

Slide 82

WS and NWS Proxy Dates - continued

Information on PRDE:• Specification: ZP12-465 worksheet -

http://nodal.ercot.com/readiness/reports/sp/index.html• Draft DDL: DRAFT PRDE DDL v0.14 -

http://nodal.ercot.com/readiness/reports/DDL/index.html• Draft XSD: DRAFT PRDE XSD v0.14 -

http://nodal.ercot.com/readiness/reports/XSD/index.html• Draft User Guide: Draft PRDE User Guide -

http://nodal.ercot.com/readiness/reports/index.html• Highlights:

– Latest full data set published on a daily basis

Page 83: Retail Market: User Interaction & Data Delivery in Nodal

Slide 83

Other Changes

Upcoming change to download file name from TML and Retail API scheduled for Sunday, 8/8/2010

• 30 day market notice sent with the new download format on 7/12/2010• Purpose is to ensure consistency between TML, Retail API, MIS, EWS for

file downloads• No change to the display file naming convention. Format will remain:

ext.(mm-dd-yyyy hh24:mi:ss).extract_name.extenstion

ext/rpt/msc may be used in the first component of the file name.

• New download file naming convention:ext.000RPTID.000000000000DUNS.yyyymmdd.hh24miss.Extract_Name.extension

ext/rpt/msc may be used in the first component of the file name.– This naming convention will also be used when downloading data from MIS, EWS –

Get Report, and extract postings available on www.ercot.com– ext/rpt/cdr may be used in the first component of the file name

Page 84: Retail Market: User Interaction & Data Delivery in Nodal

Questions??