100 likes | 109 Views
Texas Nodal Independent Market Monitoring and Data Collection For Protocol Section 17 Business Requirements Document Sylvia Shiroyama – October 24, 2006. Sources of Requirements to EDW. Requirements Through Project Teams . Requirements Due to Changing Source for Existing Reports/Extracts.
E N D
Texas NodalIndependent Market Monitoring and Data CollectionFor Protocol Section 17Business Requirements DocumentSylvia Shiroyama – October 24, 2006 http://nodal.ercot.com 1
Sources of Requirements to EDW • Requirements Through Project Teams • Requirements Due to Changing Source for Existing Reports/Extracts EDW • Independent Market Monitor Protocol 17 • Compliance Protocol 8 http://nodal.ercot.com 2
Document Contents • Introduction • Scope • Document Conventions • Assumptions and Dependencies • Definitions • Structure • Functional Requirements • Supplemental Requirements • Functional Requirements • Requirements from Nodal Protocols • Requirements from other Binding Documents http://nodal.ercot.com 3
Requirements Specification • Supplementary Requirements • Performance Requirements • Legal and Regulatory Requirements • System and Communication Requirements • Back up and Recovery Requirements • Availability and Redundancy Requirements • Maintainability Requirements • Training and Documentation Requirements • Usability Requirements • Protocol Coverage • Sub-Process Coverage http://nodal.ercot.com 4
Scope The market monitoring data collection is designed to assist the PUCT and WEMM to: (a) Protect Market Participants and Customers from the exercise of market power and from market manipulations; (b) Ensure that there is effective and persistent competition for events that are not mitigated; (c) Ensure that the market design and implementation are efficient; (d) Guard against inefficiencies in the market and market manipulations; (e) Ensure a justifiable and reasonable price impact; and (f) Ensure that data posted on the MIS Public Area fulfills the objective of transparency of market information consistent with Section 1.3, Confidentiality. http://nodal.ercot.com 5
Assumptions and Dependencies • A1) Auditor will provide recommendations to address potential areas for improvement. (Reference to FR5, FR6, FR7) • A2) Auditor will be auditing the data repository of required data and processes associated with that data repository. (Reference to FR5, FR6, FR7) • A3) The Data Archive as stated in the protocols is any data system which retains on-line operational data for 4 years and data in these systems will be maintained for an additional 3 years. (Reference to FR3, FR8) • A4) The Data Warehouse as stated in the protocols is any data system which retains on-line operational data for 4 years. (Reference to FR3, FR5, FR8) • D1) Data and process owners will identify the appropriate source system of record for all required and included data to be collected into the EDW. (Reference to FR3, FR8) • D2) The business owners of each source system are responsible for data validation prior to replication in the EDW. (Reference to FR3) • D3) The presentation functions of the MIS Public Area will be provided by the Nodal MIS project. (Reference to FR9) http://nodal.ercot.com 6
Definitions and Acronyms http://nodal.ercot.com 7
Functional Requirements • FR1 - Market Monitoring Data Collection • FR2 - Market Data Collection and Use • FR3 – Data Collection and Retention • FR4 – Data Catalog • FR5 – Accuracy of Data Collection • FR6 – Accuracy of Data Submission • FR7 – Annual Data Accuracy Audit • FR8 – Data Retention • FR9 – Provision of Data to Individual Market Participants • FR10 – Regulatory Reports • FR11 – Evaluation of ERCOT Operations and Market Performance • FR12 – Response to PUCT Data Requests – Substantive Rule 25.362(e)(1)(C) http://nodal.ercot.com 8
Supplementary Requirements • Data Requirement Specification • Data Collection Timing Specification • Data Access Specification • Data Access Security • Data Access Performance Requirement http://nodal.ercot.com 9
Protocol Coverage http://nodal.ercot.com 10