QSE Qualification and Testing Guide

QSE Qualification Testing QSE Qualification Testing

Qualified Scheduling Entities (QSE) Nodal Qualification Testing Guide

Version 2.2December 2010

PROTOCOL DISCLAIMERThis Guide describes ERCOT processes and is not intended to be a substitute for the ERCOT Nodal Protocols (available at http://www.ercot.com/mktrules/nprotocols/), as amended from time to time. If any conflict exists between this document and the ERCOT Nodal Protocols, the ERCOT Nodal Protocols shall control in all respects.

1. OVERVIEW OF QSE TESTING------------------------------------------------------------6

1.1. Introduction------------------------------------------------------------------------------------------------------------6

1.2. Guiding Principles of QSE Qualification Testing--------------------------------------------------------------6

1.3. ERCOT’s Wide Area Network (WAN)----------------------------------------------------------------------------7

1.4. Testing Timeline------------------------------------------------------------------------------------------------------8

1.5. Test Communications & Results Reporting-------------------------------------------------------------------8

1.6. Document Overview-------------------------------------------------------------------------------------------------8

1.7. Document Update Policy-------------------------------------------------------------------------------------------8

2. DOCUMENTATION PREREQUISITES FOR QUALIFICATION TESTING---------9

2.1. Documentation to be Supplied to ERCOT----------------------------------------------------------------------9

3. COMMUNICATIONS POINT TO POINT CONNECTIVITY TEST--------------------9

3.1. Introduction------------------------------------------------------------------------------------------------------------9

3.2. Requirements and Prerequisites-------------------------------------------------------------------------------10

3.3. References------------------------------------------------------------------------------------------------------------10

3.4. Test Schedule and Expected Duration------------------------------------------------------------------------10

3.5. Test Plans for Qualification--------------------------------------------------------------------------------------10

3.6. Communications Test Results-----------------------------------------------------------------------------------11

4. MULTI-PROTOCOL LABEL SWITCHING (MPLS) INSTALLATION TESTING-11

4.1. Introduction----------------------------------------------------------------------------------------------------------11

4.3. References------------------------------------------------------------------------------------------------------------13

4.5. Test Plan for Qualification----------------------------------------------------------------------------------------13

QSE Qualification Testing QSE Qualification Testing4.6. MPLS Test Results--------------------------------------------------------------------------------------------------14

5. INTER-CONTROL CENTER COMMUNICATIONS PROTOCOL (ICCP) TECHNICAL QUALIFICATION TESTING----------------------------------------------------14

5.1. Introduction----------------------------------------------------------------------------------------------------------14

5.3. References------------------------------------------------------------------------------------------------------------15

5.6. ICCP Technical Test Results--------------------------------------------------------------------------------------19

6. RESOURCE SPECIFIC ICCP TESTING REQUIREMENTS---------------------------19

6.1. Introduction----------------------------------------------------------------------------------------------------------19

6.3. References------------------------------------------------------------------------------------------------------------20

6.5. Resource Unit Point-By-Point Test-----------------------------------------------------------------------------20

6.6. Resource Specific ICCP Test Results---------------------------------------------------------------------------20

7. MARKET OPERATIONS WEB / MARKET MANAGER USER INTERFACE TRANSACTION TESTING----------------------------------------------------------------------20

7.1. Introduction----------------------------------------------------------------------------------------------------------20

7.3. References------------------------------------------------------------------------------------------------------------21

7.4. Testing Schedule and Expected Duration--------------------------------------------------------------------21

7.6. Web / Market Manager User Interface Transaction Test Script---------------------------------------23

8. MARKET OPERATIONS XML TRANSACTION TESTING--------------------------23

8.1. Introduction----------------------------------------------------------------------------------------------------------23

QSE Qualification Testing QSE Qualification Testing8.2. Requirements and Prerequisites-------------------------------------------------------------------------------24

8.3. References------------------------------------------------------------------------------------------------------------24

8.4. Testing Schedule and Expected Duration--------------------------------------------------------------------24

8.6. XML / MOS Transaction Test Script----------------------------------------------------------------------------26

9. ANCILLARY SERVICES QUALIFICATION TESTING--------------------------------27

9.1. Introduction----------------------------------------------------------------------------------------------------------27

9.3. References------------------------------------------------------------------------------------------------------------28

9.6. A/S Test Results-----------------------------------------------------------------------------------------------------30

REVISION HISTORYDATE AUTHOR VERSION COMMENTS03/01/01 R. Connell 1.0 Consolidated existing plans into one document03/05/01 R. Connell 1.0 Incorporated comments from Steve Grendel03/07/01 R. Connell 1.0 Revised with feedback from individual testing

authorities03/08/01 V. Gates 1.0 Revised formatting, sections 1 – 503/09/01 R. Connell 1.1 Revised content from qualification owners and

inserted timeline. Sent to QSEs for comment.03/14/01 J. Teixeira 1.2 Incorporated QSE comments and testing authority

updates based on comments. Sent to Web Site.05/01/08 J. Webb 2.0 Major version update that addresses QSE

qualification for the Texas Nodal Market.08/26/08 L. Bier 2.1 Continue nodal revisions. Update sections 3 & 4

with M. Stewart’s comments. Update sections 7 & 8 with S. Middleton’s comments. Update sections 4 & 5 with S. White’s comments. Updated by P. Coon

12/1/10 P. Coon 2.2 General updates

1. Overview of QSE Testing

The manager of Wholesale Client Services maintains the Overview section of this ERCOT document.

1.1. Introduction

This document guides people in organizations seeking to become Qualified Scheduling Entities (QSEs) through ERCOT’s qualification process, which is started after registering with ERCOT. Qualification testing ensures that a QSE can correctly communicate with ERCOT’s systems, and must be successfully completed in order to participate in ERCOT wholesale electric markets. Note that qualification tests do not affect the live electric market and will not result in binding transactions. A summary of the registration and qualification processes is given below:

Complete Market Participant Registration with QSE role

Complete Standard Form Market Participant agreement

Complete Service filings

Install the ERCOT Wide Area Network (WAN) configuration as applicable

Complete the QSE qualification testing, which includes:

o Communications Point to Point Testing

o Multi-Protocol Label Switching (MPLS) WAN Connectivity Testing

o Inter-control Center Communications Protocol (ICCP) Technical Qualification

o Resource Specific ICCP Qualification

o Market Operations/Market Manager User Interface Transaction Testing as applicable

o Market Operations XML Transaction Testing (required for QSE’s representing Resources)

o Ancillary Services Qualification as applicable

1.2. Guiding Principles of QSE Qualification Testing

The qualification process meets the requirements stated in the ERCOT protocols and have been designed according to these guiding principles:

Qualification activities should demonstrate that the entity is capable of performing the functions of a QSE.

Qualification activities should demonstrate that the entity is capable of complying with the requirements of all ERCOT Protocols and guidelines

Qualification activities should demonstrate a working functional interface with all required ERCOT systems as defined in the ERCOT Protocols.

ERCOT’s Wholesale Client Services Department will be the sole point of contact for QSE qualification scheduling, tracking and reporting.

Qualification activities should utilize the actual production systems installed at the QSE control centers which the QSE will use to perform the functions of a QSE unless otherwise approved by ERCOT.

Qualification activities should not compromise the future security and reliability of the ERCOT interconnect.

Upon successful qualification of a QSE, no additional testing activities should be necessary prior to commencement of service.

Qualification activities should utilize production data wherever possible.

Qualification activities should demonstrate that all data exchanges associated with each represented resource function as necessary for commencement of service.

Addition of resources to a QSE’s portfolio after initial qualification shall require additional qualification activities as necessary prior to commencement of service of those specific resources.

1.3. ERCOT’s Wide Area Network (WAN)

The qualification tests described in this document verify the QSE’s ability to communicate with ERCOT’s WAN. Figure 1 provides a simplified illustration of the ERCOT network topology.

Figure 1 Network Topology Overview

A high degree of redundancy is designed into this network. Circuit or equipment failures occurring within the MPLS or Digital Access Control System (DACS) networks will cause automatic rerouting of critical operational data.

1.4. Testing Timeline

The anticipated durations of each test are provided in the test description sections. As with any test, if all the data and processes are working smoothly, the test should proceed in a timely fashion. If, however, the systems and processes to support a test are not functioning properly or there are reliability issues that need to be addressed by ERCOT, the test make take longer than anticipated or need to be rescheduled. ERCOT will make every attempt to keep tests running on schedule.

Any requests for retesting must be made to ERCOT and will be scheduled as appropriate. Test failures will be rescheduled by ERCOT and will result in repeating the failed test.

1.5. Test Communications & Results Reporting

ERCOT client services and qualification testing personnel will maintain close communications during the qualification test process to coordinate test scheduling and provide test results.

ERCOT has created a test results form for each qualification test. The forms will be used to document the process and completion of each test event.

1.6. Document Overview

This document contains the following sections:Section 2 Documentation Prerequisites for Qualification TestingSection 3 Communications Point to Point TestingSection 4 Wide Area Network Installation and TestingSection 5 ICCP Technical Testing RequirementsSection 6 Resource Specific ICCP Testing Section 7 Market Operations Web/ Market Manager User Interface Transaction

TestingSection 8 Market Operations XML Transaction TestingSection 9 Ancillary Services Testing

1.7. Document Update Policy

ERCOT is responsible for keeping this document current. Periodic document revisions are posted to the ERCOT web site, Registration and Qualification.

The document revision number is in the form Version x.y, where x is the major version number and y is the minor version number. The minor version number changes whenever there is any update to the document. The major version number changes only when there is a significant content change.

2. Documentation Prerequisites for Qualification Testing

The manager of Wholesale Client Services maintains this section of the document.

2.1. Documentation to be supplied to ERCOT

Before starting qualification testing, The QSE applicant must register for the Market Participant role(s) which are to be performed. The ERCOT website’s registration section provides the forms for QSE role [http://www.ercot.com/services/rq/qse/]. Forms must be signed and dated by a company representative with the knowledge and authority to certify its accuracy and authenticity.

For Entities setting up a secure Wide-Area Network connection with ERCOT the following lists the various items requested on the WAN application.

Attachment WAN Application Information SummaryA: WAN Agreement

Standard form agreement for establishing and maintenance of WAN connection with ERCOT ISO.

B: General Information

Completion of site survey information for each Market Participant location that will be connecting to the ERCOT private network (data capacity requirement and location(s) of installation).Requests for optional connection to ERCOT private network.Contact information for establishing and maintaining WAN connection.

C: WAN Service Contacts

WAN Service Contacts during business hours and for emergency.

D: WAN Installation Options

WAN Installation Options required for pricing estimate.

E: WAN Invoicing Information

Billing information for invoicing WAN charges.

F and G: Site Diagrams

Diagrams of typical equipment and connections

3. Communications Point to Point Connectivity Test

The manager of Network & Deskside Services maintains the Communications Point to Point Connectivity Test section, of this ERCOT document.

3.1. Introduction

The objective of the Communications Point to Point Connectivity Test is to verify voice connectivity between QSE’s site and ERCOT. Successful completion of this Communications Point to Point Connectivity Test and/or the MPLS Installation and Connectivity Test (depending

if the QSE plans to communicate voice, data, or both) is required for the remaining tests to begin. The test plan in the section below is the guiding document for this test.

3.2. Requirements and Prerequisites

QSE must have successfully completed the MPLS Installation and Connectivity Test prior to performing this test.

To establish point to point connectivity, coordinate with the ERCOT representative to:

a) Establish the status of QSE’s channel bank installation,

b) Designate QSE’s contact person

c) Set the testing date and time to test the OPX and Hotline circuits to ERCOT’s Taylor site

3.3. References

Please refer to the following documentation for specific details on the WAN and Point to Point Communications requirements:

“ERCOT Operating Guide, Section 7, Telemetry and Communications”, a document found on the www.ercot.com web site

The Market Rules web page of the ERCOT website Nodal Protocols

3.4. Test Schedule and Expected Duration

Once the MPLS test is completed, ERCOT will work with the QSE to schedule and perform the point-to-point communications test (see requirements and prerequisites section above). The test should be completed in less than 1 hour.

3.5. Test Plans for Qualification

Following the successful installation of the WAN, the test for point-to-point communications should proceed with designated QSE contact person.

3.5.1. Perform Connectivity Test

At the date and time of the scheduled test, ERCOT will send 0dbm (zero decibels at the monitoring level) at 1004HZ on the off-premises extension (OPX) and Hotline circuits. If this signal is not received, the problem is worked until resolved. If necessary, another test date will be scheduled.

This test requires sending ERCOT 0dbm at 1004HZ to ERCOT on the OPX and Hotline circuit. If ERCOT does not receive the signal, the problem is worked until resolved. If necessary, another test date will be scheduled.

Call ERCOT on the OPX to check for voice quality. ERCOT will call back on the OPX and Hotline to check for voice quality.

3.6. Communications Test Results

The Communications point-to-point test will be tracked by ERCOT and results communicated to Market Participant and ERCOT Wholesale Client Services for documentation.

SAMPLE TEST FORMQSE Name: QSE Representative:

ERCOT Representative:

Start Date:

End Date:

Communications TestPassed (Yes/No) Comments

ERCOT Initials

Requirements and Prerequisites met

Perform Connectivity Test

Communications Test Results

Forwarded to Client Services. Faxed to QSE Representative

Is retest scheduled? (Yes/No/N/A) Comments: Initials:

4. Multi-Protocol Label Switching (MPLS) Installation Testing

The manager of Network & Deskside Services maintains the MPLS section of this ERCOT document.

4.1. Introduction

The objective of the MPLS test is to verify network connectivity to ERCOT following installation of the communications hardware. Successful completion of the MPLS installation test is required prior to the eXtensible Markup Language (XML) and Inter-control Center Communications Protocol (ICCP) qualification tests. The MPLS Installation Test Plan in the section below is the guiding document for this testing.

If the QSE will be representing generation resources, it is required to communicate with ERCOT via the MPLS. ERCOT will identify specific Transmission Service Providers (TSPs) and other QSEs MPs (i.e. representing load acting as a resource) that are required to connect to the MPLS.

ERCOT will implement a Transmission Control Protocol/Internet Protocol (TCP/IP) based MPLS that supports the transfer of data between ERCOT and Market Participants. ERCOT staff or its contractors will design, install, monitor and manage the ERCOT Private Wide Area Net (WAN). ERCOT will pay for all costs associated with each WAN connection and pass those actual costs through the ERCOT accounting process to all Market Participants that connect to the MPLS.

The QSE is to designate a contact person to coordinate the installation and test activities, and make the installation site ready and install the channel bank where required. Figure 2 illustrates the necessary equipment installed at QSE’s site that provides connectivity between QSE’s network and ERCOT. Several connection architectures are possible; the illustration represents one of the simplest.

Figure 2 Participant Site Connections

The WAN connection design supports a robust Local Area Network (LAN) architecture. The ERCOT-provided equipment connections provide redundant paths to ERCOT through the MPLS network, and an additional backup path through the Point to Point network.

During the equipment installation phase, ERCOT will work to ensure that connections to ERCOT meet requirements for reliability and performance. As changes occur that affect the data path or LAN technologies, ERCOT will adjust the equipment suite as needed.

To establish the WAN, do the following:

Request WAN connection from designated ERCOT account manager who will give provide the WAN application form. ERCOT will take the information from completed form, create a cost estimate for WAN connectivity, and provide the ERCOT WAN Agreement legal form for the QSE to sign. ERCOT will not initiate installation until receipt of approval from WAN applicant.

Coordinate with ERCOT and the WAN Management Provider to schedule access to install the equipment.

Concurrent with these efforts, make the site ready and install a channel bank where necessary. Consult with ERCOT for technical requirements for this telecommunications equipment as necessary.

Give the WAN Management Provider access to the equipment site. The WAN Management Provider will notify ERCOT when installation is complete.

If there are problems with the installation, the MP, ERCOT and the WAN Management Provider will coordinate the resolution.

4.3. References

Please refer to the following documentation for specific details on the MPLS requirements:

The Market Rules web page of the ERCOT website Nodal Protocols “ERCOT Nodal ICCP Communications Handbook”, a document found on the nodal

ERCOT website.

The schedule for hardware installation can be established after the WAN Management Provider has been contacted (see the step list in the requirements and prerequisites section above). Once hardware installation is complete, the test should be completed in less than 1 hour.

4.5. Test Plan for Qualification

Following confirmation of successful installation of the MPLS, the test for connectivity should proceed with QSE’s designated contact person.

4.5.1. “Ping” Test

First the QSE must complete the connection of QSE’s firewall/router to the network. Then verify that a message can be received and echoed back from ERCOT by pinging the ERCOT IP address from a computer behind the firewall/router. To obtain the IP address to ping, refer to the network diagram for installation that ERCOT will provide. If the connection is successful, the machine should respond with the amount of time it takes to echo the file; report this to the ERCOT test coordinator.

4.5.2. File Transfer Test

An account will be set up for the QSE on the ERCOT machine TCHFTP, which is exposed to the MPLS network and the Internet. The account information will be emailed to QSE’s designated contact. Currently the IP address is 192.168.172.24 (the updated address will be given if it changes).

To verify that files can be transferred correctly, create a text file containing company’s name and the current date, then send this file via File Transfer Protocol (FTP) to QSE’s account on the ERCOT machine. If the connection is successful, the FTP commands will complete without error. Call the ERCOT test coordinator to report that the file was sent; ERCOT test coordinator will verify that the file was received correctly.

4.6. MPLS Test Results

The MPLS installation testing will be tracked by ERCOT and results communicated to Market Participant and ERCOT Wholesale Client Services for documentation.

SAMPLE TEST FORMQSE Name: QSE Representative:

ERCOT Representative:

Start Date:

End Date:

MPLSPassed (Yes/No) Comments

ERCOT Initials

Ping Test

File Transfer Test

MPLS Test Results

Forwarded to client services. Faxed to QSE Representative

Is retest scheduled? (Yes/No/N/A) Comments: Initials:

5. Inter-control Center Communications Protocol (ICCP) Technical Qualification Testing

The EMMS Production Support ICCP Supervisor maintains the ICCP Technical Qualification Test section of this ERCOT document.

5.1. Introduction

The objective of the test is to verify basic Inter-control Center Communications Protocol (ICCP) interoperability, as well as system reliability. The tests are worded to assume that the QSE has a fully operational system. However, it is possible to perform most of the tests if the ICCP node is fully functional without an attached Supervisory Control and Data Acquisition (SCADA) system or an Environmental Management System (EMS).

The test procedure descriptions make use of the terms client and server to denote the ICCP role of interest within each step of a test. Realizing that both the QSE’s and ERCOT’s ICCP nodes are acting in both roles, the terms are further qualified by indicating whether the reference is to the Participant client, the Participant server, the ERCOT client or the ERCOT server.

The test plan in the section below is the guiding document for this test. The procedures have been written generically because each of the QSE’s products will have a different user interface. The Procedure section of each test states what the system must do, but does not state how it is done. Similarly, Expected Results indicates what should happen during the test, but does not specify how operations and actions should be verified. The QSE’s testing staff must understand

how the QSE’s system operates in order to perform these tests and obtain results. Consult with the ERCOT test representative any questions.

Must have successfully completed the MPLS Connection Test (section 3, above).

ICCP products must conform to IEC 870-6 Tase.2 Version 1996-08, also known as ICCP Inter-Control Center Communications Protocol Version 6.1.

Domain names must be set up according to the convention specified in the ERCOT Nodal ICCP Handbook.

If the QSE has an existing set of Basic Data Transfer Objects that includes a status point in a Report By Exception (RBE) data set and an analog point in a Periodic data set. If so, exchange the data set names with ERCOT. Alternatively, the QSE may do the following:

Assign the object name pppp_TEST_STATUS_001 to the status object, where pppp is the identifier.

Assign the object name pppp_TEST_ANALOG_01 to the analog object. Report the names used to the ERCOT test coordinator, who will provide the object names

ERCT_TEST_STATUS_xxx and ERCT_TEST_ANALOG_xx to the equivalent objects on the ERCOT system.

Regardless of how object names are derived, all status objects shall be given the data type Data_StateQ, and all analog objects shall be given the data type Data_RealQ according to the TASE.2 standard.

To support testing Report by Exception, the QSE must configure a status object referenced by a unique data set. This status object can be one already defined in the QSE’s system, or can be specified as pppp_TEST_STATUS_RBE.

5.3. References

Please refer to the following documentation for specific details on ICCP:

ERCOT website. IEC 870-6 Tase.2 Version 1996-08 , a document that may be found on or ordered from

the internet

The test has been organized so that the QSE will engage in testing both client and server roles with ERCOT. No more than 1 day should be required to complete all tests if testing goes smoothly. This time estimate assumes that the QSE has successfully established basic TCP/IP connectivity with ERCOT per section 3, and are configured accordance with the requirements of this document (see requirements and prerequisites section).

The following sections detail the test plans.

5.5.1. Association Test: System Startup

To verify that associations are established in the proper way when ICCP is started, first start ICCP. For a Dual-use Association, wait until the ERCOT system establishes the association. For Single-use Associations, ensure that the QSE’s client establishes a client association. Wait for ERCOT to establish the Participant server association. If the connection is successful, the QSE’s system will show all started associations as active. Report this result to the ERCOT test coordinator, who will verify that the ERCOT side associations are active.

5.5.2. Association Test: System Fail-over

To verify that associations are re-established in the event of a fail-over on QSE’s system, cause a fail-over from QSE’s active system to standby system. For a Dual-use Association, wait until the ERCOT system establishes the association. For Single-use Associations, ensure that QSE’s system establishes Participant client association. Wait for ERCOT to establish the Participant server association. If the connection is successful, QSE’s system will show all started associations as active. Report this result to the ERCOT test coordinator, who will verify that the ERCOT side associations are active.

To verify that associations are re-established in the event of a fail-over on ERCOT’s system, restart QSE’s system to the normal operating state and communicate with the ERCOT test coordinator that he may fail over from ERCOT’s active system to the standby system. For a Dual-use Association, wait until the ERCOT system establishes the association. For Single-use Associations, ensure that QSE’s system establishes Participant client association. Wait for ERCOT to establish the Participant server association. If the connection is successful, QSE’s system will show all started associations as active. Report this result to the ERCOT test coordinator, who will verify that the ERCOT side associations are active.

5.5.3. Association Test: Participant Association Conclusion

To verify that an association can be properly closed, conclude the association(s) from QSE’s running system. QSE’s system should indicate that the association is no longer active. Report this result to the ERCOT test coordinator, who will verify that QSE’s system closed the association.

5.5.4. Association Test: ERCOT Association Conclusion

To verify that QSE’s system recognizes an association closed by ERCOT, ensure QSE’s system is in association with ERCOT’s (per System Startup Test) and contact the ERCOT test coordinator, who will conclude ERCOT’s association(s) with QSE’s system. QSE’s system should indicate that the association is no longer active. Report this result to the ERCOT test coordinator.

5.5.5. Data Set Processing Test: Participant Creates Data Set

To verify that data sets are established correctly, create a Data Set in the ERCOT server that refers to the predefined status object (See the Requirements and Prerequisites section). Create a

Data Set in the ERCOT server that refers to the predefined analog object. Contact the ERCOT test coordinator to verify that two Data Sets exist in the ERCOT server that contains the same list of Data Value object name and Data Value object that the QSE sent.

5.5.6. Data Set Processing Test: ERCOT Creates Data Set

To verify that the QSE can receive ERCOT Data Sets, ensure QSE’s system is in association with ERCOT’s (per System Startup Test) and contact the ERCOT test coordinator, who will create a Data Set in QSE’s server that refers to the predefined status object. He will create a Data Set in the Participant server that refers to the predefined analog object. Call the ERCOT test coordinator and verify that the two Data Sets exist and contain the same Data Value object name and the correct Data Value object.

5.5.7. Data Transfer Test: ERCOT to Participant Basic Data Transfer

To verify that QSE’s client process can correctly process a Periodic Transfer, start a Data Set Transfer Set in the ERCOT server defining the periodic transfer rate of the Data Set referencing a status value. Then start a Data Set Transfer Set in the ERCOT server defining the periodic transfer rate of the Data Set referencing an analog value. Contact the ERCOT test coordinator, who will change the values of the objects in the Data Sets. Verify that the new values appear on QSE’s client within the periodic transfer rate time window, and that QSE has received two Information Reports for each of the new values that ERCOT sent.

5.5.8. Data Transfer Test: Participant to ERCOT Basic Data Transfer

To verify that QSE’s server process can correctly process a Periodic Transfer, contact the ERCOT test coordinator, who will start a Data Set Transfer Set in QSE’s server defining the periodic transfer rate of the Data Set referencing a status value. Then he will start a Data Set Transfer Set in QSE’s server defining the periodic transfer rate of the Data Set referencing an analog value. Change both the values (status and analog) of the objects included in the Data Sets. Contact the ERCOT test coordinator, who will verify that the new values appear on the ERCOT client within the periodic transfer rate time window, and that he has received two Information Reports for each of the values that QSE changed.

5.5.9. Data Transfer Test: ERCOT to Participant Data Quality Test

To verify that QSE’s client correctly interprets quality codes sent to it by the ERCOT server, choose an analog value included in the data being sent in the Data Transfer Test: ERCOT to Participant Basic Data Transfer (above). Ensure that the quality codes associated with the chosen value are:

Validity = VALID CurrentSource = TELEMETERED NormalValue = NORMAL

Contact the ERCOT test coordinator, who will manually enter a new value to the chosen data object.

Verify to the ERCOT test coordinator that the quality codes received from the ERCOT server change to the following values:

Validity = HELD CurrentSource = TELEMETERED NormalValue = NORMAL

Confirm that the value appears on a display with display attributes indicating that the value was manually entered.

5.5.10. Data Transfer Test: Participant to ERCOT Data Quality Test

To verify that QSE’s server provides correctly set quality codes to the ERCOT client, choose an analog value included in the data being sent in the Data Transfer Test: Participant to ERCOT Basic Data Transfer (above). Ensure that the quality codes associated with the chosen value are:

Validity = VALID CurrentSource = TELEMETERED NormalValue = NORMAL

On QSE’s server, manually enter a new value to the chosen data object. Contact the ERCOT test coordinator, who will verify that the quality codes he receives change to the following values:

Validity = HELD CurrentSource = TELEMETERED NormalValue = NORMAL

5.5.11. Data Transfer Test: Report By Exception- Integrity Interval

To verify that QSE’s server correctly processes the Integrity Interval specified in a Transfer Set configured for RBE, contact the ERCOT test coordinator, who will ensure that the ERCOT client starts a Data Set Transfer Set configured for RBE in QSE’s server. The Transfer Set must reference the Data Set containing pppp_TEST_STATUS_RBE (see requirements and prerequisites section above).

Contact the ERCOT test coordinator, who will ensure that after the integrity time window passes, the ERCOT client shows that it has received a new value for pppp_TEST_STATUS_RBE, and the ERCOT server receives a new copy of pppp_TEST_STATUS_RBE.

5.5.12. Data Transfer Test: Report By Exception- Value Change

To verify that QSE’s server correctly processes a change of value in a Transfer Set configured for RBE, continue to use the Transfer Set started in Data Transfer Test: Report by Exception- Integrity Interval test above. On QSE’s server, change the value of pppp_TEST_STATUS_RBE after one of the integrity intervals has passed. Contact the ERCOT test coordinator, who will ensure that after an integrity interval has passed, the changed value appears in the ERCOT client.

5.5.13. Reliability Test: One-Hour Transfer Test

To verify that QSE’s client and server processes can reliability exchange data with the ERCOT system for at least one hour, continue to use the Transfer Sets started in the Data Transfer Tests

above. Run these test for one hour. Afterwards, contact the ERCOT test coordinator and confirm that data exchanges have taken place within the specified timing windows for the entire hour.

5.5.14. Reliability Test: Communication Interruption Test

To verify that QSE’s client and server processes can correctly detect and report a failure of communication, continue to run the Transfer Sets started in the Data Transfer Tests; Basic Data Transfers, but disconnect the communication port to QSE’s ICCP node. Contact the ERCOT test coordinator and confirm that both the ERCOT and Participant systems report loss of communication.

5.6. ICCP Technical Test Results

The results of these tests will be tracked and communicated to Market Participant and ERCOT Wholesale Client Services for documentation.

ICCP Technical Test qualifies the following capability:Association Test: System Startup Association Test: System Fail over

Association Test: Participant Association Association Test: ERCOT Association Conclusion

Data Set Processing Test: Participant Creates Data Set

Data Set Processing Test: ERCOT Creates Data Set

Data Transfer Test: ERCOT to Participant Basic Data Transfer

Data Transfer Test: Participant to ERCOT Basic Data Transfer

Data Transfer Test: ERCOT to Participant Quality Test

Data Transfer Test: Participant to ERCOT Quality Test

Data Transfer Test: Report by Exception – Integrity Interval

Data Transfer Test: Report by Exception – Value Change

Reliability Test: Communication Interruption Test

6. Resource Specific ICCP Testing Requirements

The EMMS Production Support ICCP Supervisor maintains the ICCP Technical Qualification Test section, of this ERCOT document.

6.1. Introduction

The objective of the test suite is to verify that the data received by ERCOT matches what is stored on QSE’s system. The test plan in the section below is the guiding document for this test.

QSE provides the unit names and phone numbers to the ERCOT test coordinator.

QSE’s system must be configured in accordance with the requirements of this document.

6.3. References

ERCOT website.

The test has been organized so that the QSE tests each resource unit with ERCOT point-by-point. Approximately 50-100 points can be verified per hour.

6.5. Resource Unit Point-By-Point Test

The following section is the general test plan for resource testing. Contact the ERCOT test coordinator to compare each required point for each unit on ERCOT’s system with corresponding point at QSE’s plant.

6.6. Resource Specific ICCP Test Results

The results of these tests will be tracked and communicated to Market Participant and ERCOT Wholesale Client Services for documentation. Test qualifies initial ICCP Resource Unit Point by Point list.

7. Market Operations Web / Market Manager User Interface Transaction Testing

The Market Operations Web / Market Manager User Interface Testing portion of this ERCOT document is maintained by the Market Operations staff.

7.1. Introduction

The objective of the test suite is to verify that QSE can successfully transmit market data through ERCOT’s market manager user interface, which is based on standard web technologies. The Market Manager is a Web interface which may be used by market participants with no resources. The terms market system and MMS may be used interchangeably. Note that Market Manager is an application within the Market Information System. The Market Information System (MIS) is the primary interface for all ERCOT Market Participants and hosts a number of applications (e.g. Market Manager). The test plan in the section below is the guiding document for this test.

QSE’s system must be configured in accordance with the requirements of the MMS UI User Manual (see references).

QSE must log into the market manager test system using a test digital certificate and submit a sample transaction, such as an Energy Only Offer or Energy Trade. The test coordinator will provide the test digital certificate.

QSE should review the MMS UI User Manual (see references) and to be familiarized with any known issues with interface before using it.

QSE should attend the participant training as available, which will facilitate becoming familiarized with the ERCOT web-based systems and business rules.

7.3. References

Market Manager User Guide , a document found on the www.ercot.com web site provides a guide to the entry of data to the market system and retrieval of date from the market system.

The Market Rules web page of the ERCOT website Nodal Protocols, sections 3.9, 4.4, 6.4

7.4. Testing Schedule and Expected Duration

ERCOT will work with the QSE to schedule and perform the test. Note that not all tests may be required; the test coordinator will convey which ones are required.

Assuming that QSE’s system is configured correctly and that the QSE has successfully logged into the market manager test system (see requirements and prerequisites section), no more than 2 hours should be required to complete all tests. If testing problems cause the schedule to be exceeded, the test operator may schedule another test date.

At the date and time scheduled for the test, the test operator will call and verify that the QSE is ready to proceed. He will remain on the phone through the following tests, verifying that each of QSE’s test inputs have been received by the ERCOT system.

7.5.1. DAM Energy-Only Offer Tests

Successfully create a DAM Energy-Only Offer and transmit it. Edit the DAM Energy-Only Offer and successfully save the changes. Query the system for the DAM Energy-Only Offer and view the data.

7.5.2. DAM Energy Bid Tests

Successfully create a DAM Energy Bid and transmit it. Edit the DAM Energy Bid and successfully save the changes. Query the system for the DAM Energy Bid and view the data. Successfully cancel the DAM Energy Bid.

7.5.3. Energy Trade Tests

Successfully create an Energy Trade and transmit it. Edit the Energy Trade Bid and successfully save the changes. Query the system for the Energy Trade and view the data. Successfully cancel the Energy Trade.

7.5.4. Self-schedule Tests

Successfully create a Self-schedule and transmit it. Edit the Self-schedule and successfully save the changes. Query the system for the Self-schedule and view the data. Successfully cancel the Self-schedule.

7.5.5. Capacity Trade Tests

Successfully create a Capacity Trade and transmit it. Edit the Capacity Trade and successfully save the changes. Query the system for the Capacity Trade and view the data. Successfully cancel the Capacity Trade.

7.5.6. DC Tie Schedule Tests

Successfully create a DC Tie schedule and transmit it. Edit the DC Tie schedule and successfully save the changes. Query the system for the DC Tie schedule and view the data. Successfully cancel the DC Tie schedule.

7.5.7. Ancillary Service Offer Tests

Successfully create an Ancillary Service Offer and transmit it. Edit the Ancillary Service Offer and successfully save the changes. Query the system for the Ancillary Service Offer and view the data. Successfully cancel the Ancillary Service Offer.

7.5.8. Ancillary Service Trade Tests

Successfully create an Ancillary Service Trade and transmit it. Edit the Ancillary Service Trade and successfully save the changes. Query the system for the Ancillary Service Trade and view the data. Successfully cancel the Ancillary Service Trade.

7.5.9. Self-arranged Ancillary Service Tests

If QSE will be representing a Load resource, successfully create a Self-arranged Ancillary Service and transmit it. Edit the Self-arranged Ancillary Service and successfully save the changes. Query the system for the Self-arranged Ancillary Service and view the data. Successfully cancel the Self-arranged Ancillary Service.

7.5.10. Point-To-Point (PTP) Obligation Bid Tests

Successfully create a Point-To-Point (PTP) Obligation Bid and transmit it. Edit the PTP Obligation Bid and successfully save the changes. Query the system for the PTP Obligation Bid and view the data. Successfully cancel the PTP Obligation Bid.

7.5.11. Congestion Revenue Right (CRR) Offer Tests

If QSE will be representing a NOIE Congestion Revenue Right Account Holder (CRR AH), successfully create a Congestion Revenue Right (CRR) Offer and transmit it. The CRR may be of any type (Flowgate, PTP option or obligation) EXCEPT one “with refund”. Edit the CRR Offer and successfully save the changes. Query the system for the CRR Offer and view the data. Successfully cancel the CRR Offer.

7.6. Web / Market Manager User Interface Transaction Test Script

The test is performed with the specified market functionality script listed below. Test results are tracked and reported to Market Participant and Wholesale Client Services for documentation.

List of Market Manager Entries for Test (ERCOT may require additional entries as necessary):

Requirements and Prerequisites met22

DAM Energy-Only Tests

DAM Energy Bid Tests

Energy Trade Tests

Self-schedule Tests

Capacity Trade Tests

DC Tie Schedule Tests

Ancillary Service Offer Tests

Ancillary Service Trade Tests

Self-arranged Ancillary Service Tests

Point-To-Point (PTP) Obligation Bid Tests

Congestion Revenue Right (CRR) Offer Tests

Overall Market Operations Web / Market Manager User Interface Transaction Testing Results

8. Market Operations XML Transaction Testing

The Market Operations XML Transaction Testing section of this ERCOT document is maintained by the Manager of EMMS Production.

8.1. Introduction

The objective of the Market Operations eXtensible Markup Language (XML) Transaction Testing is to verify that QSE’s system(s) can interact with the ERCOT market systems through ERCOT’s web services. If QSE has resources, QSE must use this interface (QSEs without resources may use it as well, or may use the market manager interface). This test ensures that QSE’s XML messages are correctly formatted and transmitted and that the QSE can interpretation the messages received back from the market system. The Programmatic Interface is the XML (web services) interface with the market servers. The terms Programmatic Interface, API, Market System, and Web Services may be used interchangeably. XML may also be used, but the term is not exclusively used for API.

The Test Plan in the section below is the guiding document for this testing.

QSE must create sample data for each test listed below before beginning testing. The data can be fabricated but should be realistic. QSE may submit data to ERCOT before testing begins to ensure that the XML is formatted correctly; this ensures that testing runs smoothly.

QSE must establish communications with the test system using a test digital certificate and submit a sample transaction, such as an Energy Only Offer, Current Operating Plan (COP), Three-Part Offer (TPO), or an Outage Schedule (OS).

To establish QSE’s system’s interaction with ERCOT nodal market systems, QSE must be familiar with web technologies, which includes understanding:

XML for data description, XSD / WSDL, and XML parsing and validation. Protocols HTTPS, and TCP/IP. Security and authentication technologies: encryption, use of digital certificates,

authentication, web services, and SSL (secure sockets layer). General network communication software methodology.

8.3. References

EIP External Interfaces Specification , a document found on the www.ercot.com web site that will guide the QSE’s staff in creating messages to be sent to the market system and interpreting the messages received from the market system.

The Market Rules web page of the ERCOT website Nodal Protocols, sections 3.9, 4.4, 6.4

EIP MIS External interfaces Specification , a document found on the www.ercot.com web site that will guide the QSE’s staff in integrating applications with the MIS portal.

8.4. Testing Schedule and Expected Duration

ERCOT will work with the QSE’s staff to schedule and perform the test. Note that the QSE may not be required to do all the tests; the test coordinator will convey ones are required.

Assuming that QSE’s system is configured correctly and that QSE’s test data is complete and correct (see requirements and prerequisites section), no more than 2 hours should be required to complete all tests. If testing problems cause the schedule to be exceeded, the test operator may schedule another test date.

At the date and time scheduled for the test, the test operator will call and verify that QSE staff is ready to proceed. He will remain on the phone through the following tests, verifying that each of QSE’s test inputs have been received by the ERCOT system.

8.5.1. Current Operating Plan (COP) Tests

Successfully create a COP and transmit it. Edit the COP and successfully save the changes. Query the system for the COP and view the data.

8.5.2. Three-Part Offer (TPO) Tests

If the QSE will not be depending on a Dynamically Scheduled Resource (DSR), successfully create a TPO and transmit it. Edit the TPO and successfully save the changes. Query the system for the TPO and view the data. Successfully cancel the TPO.

8.5.3. Increment/Decrement (INC/DEC) Tests

If the QSE is planning to use a DSR, successfully create an INC/DEC and transmit it. Edit the INC/DEC and successfully save the changes. Query the system for the INC/DEC and view the data. Successfully cancel the INC/DEC.

8.5.4. Outage Schedule (OS) Tests

Successfully create an OS and transmit it. Edit the OS and successfully save the changes. Query the system for the OS and view the data. Successfully cancel the OS.

8.5.5. DAM Energy-Only Offer Tests

Successfully create a DAM Energy-Only Offer and transmit it. Edit the DAM Energy-Only Offer and successfully save the changes. Query the system for the DAM Energy-Only Offer and view the data.

8.5.6. DAM Energy Bid Tests

Successfully create a DAM Energy Bid and transmit it. Edit the DAM Energy Bid and successfully save the changes. Query the system for the DAM Energy Bid and view the data. Successfully cancel the DAM Energy Bid.

8.5.7. Energy Trade Tests

Successfully create an Energy Trade and transmit it. Edit the Energy Trade Bid and successfully save the changes. Query the system for the Energy Trade and view the data. Successfully cancel the Energy Trade.

8.5.8. Self-schedule Tests

Successfully create a Self-schedule and transmit it. Edit the Self-schedule and successfully save the changes. Query the system for the Self-schedule and view the data. Successfully cancel the Self-schedule.

8.5.9. Capacity Trade Tests

Successfully create a Capacity Trade and transmit it. Edit the Capacity Trade and successfully save the changes. Query the system for the Capacity Trade and view the data. Successfully cancel the Capacity Trade.

8.5.10. DC Tie Schedule Tests

Successfully create a DC Tie schedule and transmit it. Edit the DC Tie schedule and successfully save the changes. Query the system for the DC Tie schedule and view the data. Successfully cancel the DC Tie schedule.

8.5.11. Ancillary Service Offer Tests

Successfully create an Ancillary Service Offer and transmit it. Edit the Ancillary Service Offer and successfully save the changes. Query the system for the Ancillary Service Offer and view the data. Successfully cancel the Ancillary Service Offer.

8.5.12. Ancillary Service Trade Tests

Successfully create an Ancillary Service Trade and transmit it. Edit the Ancillary Service Trade and successfully save the changes. Query the system for the Ancillary Service Trade and view the data. Successfully cancel the Ancillary Service Trade.

8.5.13. Self-arranged Ancillary Service Tests

If QSE will be representing a Load Resource, successfully create a Self-arranged Ancillary Service and transmit it. Edit the Self-arranged Ancillary Service and successfully save the changes. Query the system for the Self-arranged Ancillary Service and view the data. Successfully cancel the Self-arranged Ancillary Service.

8.5.14. Point-To-Point (PTP) Obligation Bid Tests

Successfully create a Point-To-Point (PTP) Obligation Bid and transmit it. Edit the PTP Obligation Bid and successfully save the changes. Query the system for the PTP Obligation Bid and view the data. Successfully cancel the PTP Obligation Bid.

8.5.15. Congestion Revenue Right (CRR) Offer Tests

If QSE will be representing a NOIE Congestion Revenue Right Account Holder (CRR AH), successfully create a Congestion Revenue Right (CRR) Offer and transmit it. The CRR may be of any type (Flowgate, PTP option or obligation) EXCEPT one “with refund”. Edit the CRR Offer and successfully save the changes. Query the system for the CRR Offer and view the data. Successfully cancel the CRR Offer.

8.6. XML / MOS Transaction Test Script

The test is performed with the specified market functionality script listed below. Test results are tracked and reported to Market Participant and Wholesale Client Services for documentation.

List of XML Messaging for Test (ERCOT may require additional entries as necessary):

COP Tests

TPO Tests

INC/DEC Tests

OS Tests

DAM Energy-Only Tests

DAM Energy Bid Tests

Energy Trade Tests

Self-schedule Tests

Capacity Trade Tests

DC Tie Schedule Tests

Ancillary Service Offer Tests26

Ancillary Service Trade Tests

Self-arranged Ancillary Service Tests

Point-To-Point (PTP) Obligation Bid Tests

Congestion Revenue Right (CRR) Offer Tests

Overall XML / MOS Transaction Testing Results

9. Ancillary Services Qualification Testing

The Ancillary Services section of this ERCOT document is maintained by Supervisor- Operations Planning.

9.1. Introduction

The objective of this test is to ensure that QSEs providing ancillary services meet the AS Qualification Criteria set forth in the ERCOT Protocols. If the Market Participant is going to provide ancillary service(s) as a QSE, related qualification criteria must be met, including:

QSE qualification criteria to represent Resources and applicable ancillary service dispatch instructions.

Resource-specific Regulation Service Testing Resource-specific Non-Spinning Reserve Service Testing (NSRS) Resource-specific Responsive Reserve Testing (RRS)

QSE is limited to one test per day, although multiple QSEs may be testing on that day. ERCOT operators will determine the testing order for the entities scheduled for that day.

The ERCOT Ancillary Services Qualification, Testing, and Monitoring Program, ERCOT Protocol 8.1.1.1 and Operating Guide Section 3.2.4 and 9.4, are the guiding documents for initial Ancillary Services testing between ERCOT and its Participants.

ERCOT limits provisional qualification to the following conditions:

QSE is qualifying for ancillary service with a Resource currently qualified for that service and is moving into the QSE’s Resource portfolio. Provisional qualification is issued for the Resource upon confirmation that the QSE has met the associated service’s QSE qualification criteria in accordance with Section 8.1.1.

QSE is already qualified for the ancillary service for which it wants to supply with a Resource that is being added to the QSE’s Resource portfolio for which is also is qualified for the same service(s).

The QSE must have successfully completed the Inter-control Center Communications Protocol (ICCP) Technical Qualification Testing before performing ancillary services tests.

The QSE must have successfully completed the Market Operations XML Transaction Test prior to performing ancillary services tests.

The QSE must submit all the required AS Testing Parameters and URL information identified in the “AS Qualification Test Template” by noon of the day before the scheduled test date. ERCOT’s test coordinator will provide the template and answer any questions the QSE staff may have.

9.3. References

ERCOT Operating Guide, Section 8, a document found on the www.ercot.com web site The Market Rules web page of the ERCOT website Nodal Protocols NERC Planning Standards “System Modeling Data Requirements, Generation Equipment IEEE standard 421.2, for automatic voltage regulator test methodology

ERCOT will work with QSE to schedule and perform applicable tests. Note that the QSE may not be required to do all the tests depending on the ancillary services the QSE will supply and associated Resources.

QSEs are limited to one test per day, since many of the tests require a continuous 8 hour test period. The expected test durations for all tests are given below.

Non-spinning Reserve Testing: 8 continuous hours Regulation Service Testing: 1 hour Responsive Reserve Testing: 8 continuous hours

In order to participate in Ancillary Services the QSE must have completed prior qualification of ICCP and API data paths, voice communications, and provided required telemetry in accordance with Protocol Section 6.5.5.2, Operational Data Requirements,

When a test starts, ERCOT operators will initiate and test start via the system interface and voice communications. As each test progresses, the operations department of either party may terminate the test for security reasons and reschedule another test date. As each test completes its predefined time duration, ERCOT’s operators will initiate a test stop message via the system interface and voice communications.

9.5.1. Quick Start Service

In accordance with Protocol Section 8.1.1.2, for purposes of qualifying Quick Start Generation Resources (QSGRs), ERCOT shall issue a unit-specific VDI for the MW amount that the QSE is requesting to qualify its QSGR to provide. The QSE shall telemeter an ONTEST Resource Status. The QSGR will only be qualified to provide an amount not to exceed the observed output at the end of a ten minute test period.

Before the test is scheduled to begin, the ERCOT test operator will verify that the QSGR under test has COP Resource Status of ON and COP LSL and HSL values to the expected sustainable LSL and HSL for the QSGR for the test period. For test the QSE will telemeter a QSGR Resource Status of ON and an LSL of zero prior to receiving qualifying test deployment

instruction from ERCOT. The status of the breaker shall be open and the output of the QSGR shall be zero. SCADA will be verified to insure that the Resource is Off-Line with 0 MW and an open breaker status for the appropriate interval. Also, during this time the Resource limits being used by the Resource Limit Calculator (RLC) will be verified to be appropriate for the test.

During scheduled test period with no advance notice, ERCOT will send a Dispatch Instruction with a base-point to the Generation Resources requesting qualification. QSE receives the base-point, update resources’ statuses and wait for a base-point to be calculated during the next SCED cycle. QSE’s system must send an electronic acknowledgment that is time stamped at least 5 minutes before the start of the interval.

The breaker must be closed before the start of the interval, and not earlier than 5 minutes before the start of the interval. The Resource’s generation output must be equal to or greater than the amount that that QSE wishes to have the Resource qualified to provide by 10 minutes after the start of the interval.

9.5.2. Non-Spinning Reserve Testing

QSE must confirm capability to receive API/XML Non-Spinning Reserve deployment from ERCOT and reflect the Ancillary Service Schedule change to the Resource in test within 5 minutes for on-line Resource and within 20 minutes for an off-line Resource. The off-line Generation Resource or Load Resource must confirm capability to synchronize and ramp (or unload) to test A/S schedule within 30 minutes in accordance with 8.1.1.4.3, Non-Spinning Reserve Service Energy Deployment Criteria.

ERCOT will send QSE the Non Spinning messages via the messaging system. Acknowledge this to start the test.

At some time during the test window, without prior knowledge of QSE, ERCOT will send a message via the ERCOT messaging system directing release to SCED of an amount of Non-Spinning reserve to Energy through the change in the Ancillary Service Schedule for the specific Resource being qualified. The messaging system will have instructions that indicate the corresponding time intervals. Upon receiving this message, the QSE must acknowledge the dispatch, start non-spinning resources (if off-line), and ramp to the power level directed by ERCOT test SCED Base Points. For the 60-minute duration of the test, the Resource’s output shall be measured.

9.5.3. Regulation Service

QSE must confirm capability to receive Regulation Service deployments over ICCP, confirm QSE control system is capable of directing regulation deployments to designated Resources, and capable of switching control to constant frequency. The Resource in test must deliver full amount of regulating capacity offered within five minutes in accordance with 8.1.1.4.1, Regulation Service and Generation Resource/Controllable Load.

For the 60-minute duration of the test, when market and reliability conditions allow, the ERCOT Control Area Operator will send QSE a random sequence of raise, hold, and lower control signals, effectively representing a typical Regulation Up or Regulation Down deployment. Each signal will remain unchanged for at least two minutes.

During the test, a ten-minute period is used to test the Resource’s ability to achieve the entire amount of Reg-Up requested for qualification during the period. A ten-minute period is used to test QSE’s ability to achieve the entire amount of Reg-Down requested for qualification during the period.

9.5.4. Responsive Reserve Service Testing (by QSE)

QSE must confirm capability to receive Responsive Reserve deployment and change Ancillary Service Schedule within 15 seconds. Qualifying Resource must confirm governor in service and capability of ramping to RRS deployment within ten minutes of notice in accordance with 8.1.1.4.2, Responsive Reserve Service Deployment Criteria.

At specific time during the test window, without prior knowledge of QSE, ERCOT will send a signal via the Responsive Reserve deployment system requesting deployment of an amount of RRS to Energy equal to the amount for which QSE is requesting qualification. Upon receiving this message, QSE must change Ancillary Service Schedule to release RRS to SCED in the amount specified and acknowledges receipt of the order. ERCOT will issue test SCED Base Points corresponding to ramp to RRS amount.

9.6. A/S Test Results

The results of the Ancillary Services tests are tracked and reported to Market Participant and Wholesale Client Services for documentation.

QSE Qualification and Testing Guide

Documents

Qualification Testing of Solar Photovoitaic Powered ...pdf.usaid.gov/pdf_docs/PNAAV341.pdf · NASA CR 168181 q --o -7 Qualification Testing of Solar Photovoitaic Powered Refrigerator

QSE (Q-Star) Series Electromagnetic Meter Owner’s Manual... · qse grounding lug qse gro undi qse grounding lug qse gro undi l a connect wire to ring terminal. tighten ring terminal

cosumar QSE

Iopf Paper Qualification Testing 04 Final1

Design Qualification Test Report QSE/QTE QSE-080-01-L-D-A

Photovoltaic Module Qualification Plus Testing · · 2013-12-26Photovoltaic Module Qualification Plus Testing Sarah Kurtz, ... 4.1.2 UV Exposure for Backsheets ... warrantied performance

AHRI 220 Reverberation Room Qualification and Testing Procedures

IP601 International Proficiency Qualification Thorough ... · IP601 International Proficiency Qualification Thorough Examination and Testing of Local Exhaust Ventilation Systems Qualification

Manuel QSE

DEVELOPMENT, TESTING AND QUALIFICATION OF INNOVATIVE …

Accelerated Stress Testing, Qualification Testing, HAST ... · Accelerated Stress Testing, Qualification Testing, HAST, Field Experience – what do they all mean? (Presentation),

IABG - Product Qualification - Analysis. Testing ... · PDF fileIABG Product qualification Analysis, testing and qualification. Ventilator on the multi-axis vibration test stand.

Sound Quality & Jury Testing · 2019-02-08 · The sound quality process Sound recording Objective qualification: Sound quality metrics Subjective qualification: Jury Testing Audio

QSE Quality Systems Engineering QSE Pipe Fixture

Qualification, Manufacturing, and Reliability Testing Methodologies

Flight Qualification Testing of the Thales LPT9510 Pulse

qualification testing for PCB.pdf

Reliability Testing and Product Qualification Mark A. Burns

Screening and Qualification Testing of Chip Tantalum

Développement d’une méthodologie d’audit QSE …€¦ · Mastère spécialisé : QSE Samy PIERRE - Développement d’une méthodologie d’audit QSE intégalement à distance