Sample Acceptance Test Procedure(s

)

The California ISO makes no warranty with regard to this guide, including but not limited to the accuracy or completeness of the guide, responsibility for any damage or loss to systems or software caused by the use of the guide or assurances that the user of the guide will not require additional third party engineering services

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

TABLE OF CONTENTS 1. 2. PURPOSE -------------------------------------------------------------------------------------------- 3 INTRODUCTION ------------------------------------------------------------------------------------ 4
2.1 Ground Rules ------------------------------------------------------------------------------------------------------------- 5 2.2 General Test Instructions ---------------------------------------------------------------------------------------------- 5 2.3 Test Sequence------------------------------------------------------------------------------------------------------------- 6 2.4 Test Results---------------------------------------------------------------------------------------------------------------- 6 2.5 Test Procedures ---------------------------------------------------------------------------------------------------------- 7 2.6 Test Schedule ------------------------------------------------------------------------------------------------------------- 8

3

APPENDICES---------------------------------------------------------------------------------------- 9
APPENDIX A ------------------------------------------------------------------------------------------------------------------10 – OUTLINE OF TEST CASES -------------------------------------------------------------------------------------------10 Appendix B – -------------------------------------------------------------------------------------------------------------------13 Test Procedures --------------------------------------------------------------------------------------------------------------13 Appendix C ---------------------------------------------------------------------------------------------------------------------55 TEST Punch List ------------------------------------------------------------------------------------------------------------55 Appendix D ---------------------------------------------------------------------------------------------------------------------56 - Discrepancy Report Form ------------------------------------------------------------------------------------------------56

4

CERTIFICATION PROCESS--------------------------------------------------------------------58

The California ISO makes no warranty with regard to this guide, including but not limited to the accuracy or completeness of the guide, responsibility for any damage or loss to systems or software caused by the use of the guide or assurances that the user of the guide will not require additional third party engineering services

Page 2 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

1.

PURPOSE

The purpose of this document is to provide you with examples of the test procedures performed for the acceptance of the Hathaway Field RIG (Field RIG unit equivalents acceptable to the ISO may require steps and/or processes related to testing different from those presented herein).

It is the responsibility of each owner to perform testing of their RIG installations to ensure the functionality required by the ISO’s technical standards. The owner and vendor should agree on specific test procedures and resources necessary. The ISO will assist the owner or representative by demonstrating test procedures, inspecting and certifying the installation and participating in the final point to point checks.

It is important to understand that this document is being provided to you for use as a guide, and has been developed based on the testing and experience acquired to date. Some additions and or modification to existing tests may be necessary to accommodate your site. . The California ISO makes no warranty with regard to this guide, including but not limited to the accuracy or completeness of the guide, responsibility for any damage or loss to systems or software caused by the use of the guide or assurances that the user of the guide will not require additional third party engineering services.

Page 3 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

2.

INTRODUCTION The first is a

There are three types of acceptance tests defined in this write up.

Manufacturing Test or Factory Acceptance Test (FAT). . The purpose of the FAT is generally to demonstrate the functionality of the equipment, not necessarily specific to the site. Examples of the type of testing conducted during the FAT can be found on the ISO GCP Web Page (http://www.caiso.com/thegrid/operations/gcp), Procedures section.

The second type of test is the Site Acceptance Test (SAT). The SAT has been defined to demonstrate the site specific functionality of the RIG (i.e. checks to ensure connectivity to plant systems and communications, data base checks from RIG to Hathaway work station etc. ). SAT testing is generally performed on site. The third type of test is the System Integration Test (SIT). The SIT is a complete “end to end” test from the ISO EMS system to the plant control systems and individual units. This is performed after the ISO representatives have certified the correct installation of the RIG and is coordinated with the ISO resources in Folsom.

Certain procedures of the SAT and SIT will require coordination with the ISO and Hathaway. Some of these tests can be run independently, and some need to be run in specific order. It is suggested that the generator owner or representative coordinate with the ISO Project Engineer and the manufacturer representative in advance to schedule the necessary resources.

Page 4 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

2.1

GROUND RULES

In order to run a successful test, it is necessary to establish the methods and general procedures which will be followed throughout the test. It is important that these rules and procedures be agreed to, and followed, by all parties during the test. Clear definition of each parties roles and responsibilities and communicating changes in procedures are crucial to ensure problems and issues are resolved quickly. 2.2 GENERAL TEST INSTRUCTIONS Hathaway, plant personnel, and engineering personnel should each appoint an individual or individuals to be involved in all matters related to testing (“Test Representative”). The level of involvement of Test Representatives from these groups is dependent upon the testing being performed and should be defined in advance.

These Test Representatives are solely responsible for representing their respective companies during the test. The mutual agreement of these Test Representatives is necessary for approving the tests, any departure from the procedure, and any documentation of errors or omissions.

An outline of the test examples can be located in Appendix A. The actual testing requires execution of test procedures, examples of which can be located in Appendix B. These procedures are designed to state the test steps in an efficient, modular manner and allow for completion of the test objectives in a timely manner. repetition of test instructions has been avoided whenever possible. Unnecessary

Page 5 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

2.3

TEST SEQUENCE

Test Representatives may add or delete items from the test, redirect the test, skip sections, or review sections at any time during the test providing such changes are agreed to and do not result in safety issues or equipment damage. The requirement to provide a fully functional RIG (or equivalent equipment acceptable to ISO) should be the standard to guide all testing.

The tests are designed to run in the sequence given in this example document except where noted. The proper sequencing of tests is necessary because of set up procedures that may have occurred in previous tests. However, it is recognized that circumstances often require that the sequence be interrupted. Such an interruption or re-scheduling should not require that all Test Representatives agree.

Successful testing involves the active participation, teamwork and understanding of test procedures by all parties and Test Representatives. Primarily Hathaway

personnel or ISO personnel will help execute the tests in order to expedite them. This will provide the customer with the opportunity to observe and question the test results. Upon successful completion of each section, the Test Representatives will sign off that section as complete and accepted.

2.4 TEST RESULTS Evidence of execution of test procedures and documentation of test results will be done using the test log form incorporated with the test procedure in Appendix C. Test representatives will document conduct of each test procedure on separate log sheets. Logs should contain entries documenting conduct of the various test steps with a listing of exceptions, discrepancies, abnormal events, or general remarks. When required, actual test results and parameter values may be recorded. Each representative should sign off for completion of each test procedure. Additional documentation may be Page 6 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

attached to the test logs as required to record test results. attachments.

Test logs will list all

There may be cases where the test results are not satisfactory. Appendix D contains a Discrepancy Report (DR) form where all such results should be recorded. Discrepancy Reports should also be used to document any outstanding issues arising from the tests.

All discrepancies should be classified daily by the Testing Representatives into one of the following example categories: • • FIX BEFORE OPERATIONAL FIX BEFORE FINAL ACCEPTANCE At

Whenever possible, discrepancy correction should occur during the testing.

completion of the test, the responsible parties will review all remaining discrepancies against these categories for correction. The resulting punchlist will be tracked until all discrepancies are resolved. 2.5 TEST PROCEDURES

It is suggested that brief status meetings among Testing Representatives be held daily throughout the duration of the testing. These meetings can be broken down as follows:

An orientation meeting be held prior to the start of the test period, each day. This meeting should be used to introduce all participants involved in the testing, and review the test plan, schedule and procedures. The expectations should be set forth so all parties are aware of what is to be accomplished by the end of the test period.

A review meeting should be held at the conclusion of the test period, each day. The purpose of this meeting will be to review the findings of the tests performed that day, discuss any unsatisfactory test results, determine the proper course of action to obtain satisfactory results and review and prioritize the testing/discrepancies for the next day. Page 7 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

Reasonable efforts should be taken to resolve and retest discrepancies before continuing on to subsequent tests. 2.6 TEST SCHEDULE

It is recommended that a test schedule and resource list be developed for each test. These documents should outline the testing that is to be performed, the dates, and all resources necessary to conduct each test.

Page 8 of 58

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft

3

APPENDICES

Appendix A – Outline of Test Cases Appendix B - Test Procedures Appendix C – Test Punch List Appendix D – Discrepancy Report

Page 9 of 58

Appendix A

APPENDIX A – OUTLINE OF TEST CASES This is a list of all the recommended tests. Some of these tests may not be necessary for every Class of RIG, as functionality varies. This outline has been developed to help facilitate the testing process and direct you to the appropriate test procedures. Test No. 1 2 3 When Performed SAT SAT SAT Test Description System Inspection (Inventory, Documentation Review, and Visual Inspection) Startup, Shutdown, and Restart Cabinet Sensors and Alarms Parties Involved Plant Hathaway Plant Hathaway Plant Hathaway ISO Plant Hathaway Plant Hathaway Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO
10

4 5 6

SAT SAT SAT

GPS Clock. UPS and Power Supplies Review of Protocol Conversions

6.1

SAT

Protocol Conversions– Conitel 2020

6.2

SAT

Protocol Conversions – CDC-T1

6.3

SAT

Protocol Conversions – PG&E

6.4

SAT

Protocol Conversions – DNP 3.0 Master

6.5

SAT

Protocol Conversions – C2100H

6.6

SAT

Protocol Conversions – Modbus

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway Page 11 of 58

6.7

SAT

Protocol Conversions – Modbus IOC to Protocol Engine

7

SAT

ISO Meter Communications to MDAS

8

SAT

Meter Audit Trail

9

SAT

Unit Authority Switch / Control Authorizations

10

SAT

ISO EMS Interface

11

SAT

System Status and Alarming

12

SAT

VoIP communications.

13

SAT

System Failure and Recovery

14 15

SAT SIT

Security System (card swap) Integration Testing (Development)

15.1

SIT

Trending

15.2

SIT

Pulse Control

15.3

SIT

V-Notch

15.4

SIT

Unit Maximum – Minimum Limits

15.5

SIT

Unit Stop Verification

15.6

SIT

Unit AGC Test

Sample Test Procedures

Date Revision No.

1/19/2000 2.1 Draft ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant Hathaway ISO Plant ISO

15.7

SIT

IOC to Plant Communications Link

15.8

SIT

Master IOC to Field IOC Communication Link

15.9

SIT

RTG to Master IOC Communication Link

16

SIT

Integration Testing (Production)

16.1

SIT

Trending

16.2

SIT

Raise/Lower Stability

16.3

SIT

AGC, ACE and Schedule Tracking

17

Certification

Page 12 of 58

Appendix B

APPENDIX B – Test Procedures

13

Appendix B

UNAVAILABLE AND EXCEPTIONS All items or features that are a part of this system, but for one reason or another are not available at the time of the tests are listed below. Items may not be available for a test for a variety of reasons including items not completed at the time of the test or unavailability of special test equipment. In advance of the tests, Hathaway will provide a list of equipment, test sections, and steps for the tests that are so affected. This does not preclude the inclusion of such items during the test, if possible. For example, the following items are unavailable for test: Item or Feature 1. ICCP “client” 2. ICCP “server” Reason / Disposition Under Development Under Development

The preceding exceptions and/or unavailable items are noted and agreed to.

_______________________________ Plant Test Supervisor

_______________________________ HATHAWAY Test Supervisor

_______________________________ ISO Test Supervisor

14

Appendix B

Test No: Vendor: Test:

1 HATHAWAY SYSTEM INSPECTION - The system will be inspected for completeness and quality. All equipment pieces and their quantities will be verified by referring to the System Configuration Drawings. The Hathaway Test Supervisor will provide these documents. The system test configuration is verified by a walk-through inspection. Perform testing as follows: (1) perform a physical inventory of the equipment and documentation against the original order (and any changes) to determine what is present and what is missing. Any discrepancies will be added to the punchlist for resolution. (2) review the physical configuration and system layout of the equipment against (a) the drawings/documentation provided, and (b) all sets of review comments previously submitted on the drawings and documentation. Any discrepancies in either the equipment or the documentation will be noted and added to the punchlist for resolution. (3) perform a visual inspection of the equipment for good workmanship and appearance. Any discrepancies will be noted and added to the punchlist for resolution.
Punch

Procedure:

Initial

Date

SYSTEM INSPECTION Comments:

15

Appendix B

Test No: Vendor: Test: Procedure:

2 HATHAWAY STARTUP, SHUTDOWN, AND RESTARTS System start-up and initialization is an automatic process requiring no user intervention beyond applying power to the individual components. This portion of the test covers the proper startup and shutdown procedures for the RIG system. Restarts are also demonstrated.

Procedure: 1) Apply power to the Field RIG cabinet. RIG communication and security tasks automatically start executing and its status is indicated on the System Status display. 2) Turn off the Field RIG. 3) Repeat the power-up and initialization sequence, described above, and restore the system to full operation on network. 4) Repeat step 2 so Field RIG boots in standalone mode. At the completion of this test, all system equipment should be powered up and demonstrated as connected and visible to the ISO Development EMS.
Initial Date Punch

STARTUP, SHUTDOWN, RESTARTS Comments:

Page 16 of 58

Appendix B

Test No: Vendor: Test:

3 HATHAWAY CABINET SENSORS AND ALARMS

This test requires the use of the ISO Development EMS system. Scheduling of this testing with ISO Operations Systems personnel should be obtained before the test is executed. Procedure: 1) Open the front door of Field RIG Cabinet. Confirm that an alarm is generated at the ISO Development EMS. 2) Close the front door of the Field RIG Cabinet. Confirm that the alarm condition is cleared at the ISO Development EMS. 3) Repeat steps 1 and 2 for the back door of the Field RIG by opening the back door. 4) Repeat steps 1 and 2 for the water intrusion sensor by lifting the water float. 5) Repeat steps 1 and 2 for the cabinet over temperature alarm by raising the temperature of the sensor. 6) Disconnect the Plant Communications from the Protocol Engine. Confirm that a Communications alarm is generated at the ISO workstations and that the ISO Development EMS system is notified of a Field RIG Alarm. 7) Reconnect the Plant Communications. Confirm that the alarm condition is cleared without intervention at the ISO workstation and the ISO EMS Development System and that all data points are updated, in the memory of the IOC, within their specified scan rates. 8) Disconnect the UPS’ serial communications channel from the IOC. Confirm that a UPS communications failure alarm is generated at the workstations and that the ISO EMS Development system is notified of a Field RIG Alarm. 9) Reconnect the UPS’ serial communications channel. Confirm that the alarm condition is cleared at the ISO workstation and the ISO EMS Development System.
Initial Date Punch

CABINET SENSORS AND ALARMS Comments:

Page 17 of 58

Appendix B

Test No: Vendor: Test: Procedure:

4 HATHAWAY GPS CLOCK

1) Disconnect the Field RIG from the network first to avoid any network time updates. 2) Change the CMOS time in the Field RIG to something other than the current date and time. In order to reset the CMOS time, reboot the computer, rapidly hit the delete key, select date/time, and enter desired values and then escape. 3) Reboot the Field RIG and after vxWorks initializes, check the date and time via both the date function and the GPSShow functions. The correct time will show in both as long as the GPS card receives a “good quality” time. 4) Test time drift of local IOC clock by discontinuing the system time broadcast over a 24 hour period and disconnecting the GPS antenna so that “quality good” status is lost. Verify IOC time after the 24 hours against a second time source. (High accurate source provided by Hathaway). Note drift prior to test and at end of test. Start _______________ 24 Hour ________________

5) With the GPS antenna still disconnected, change the CMOS time to 30 hours before the current time. 6) Boot the Field RIG and ensure that the time is as set in the proceeding step. 7) Connect the Field RIG to the network and confirm that the Field RIG time is corrected via the network time function.
Initial Date Punch

GPS CLOCK Comments:

Page 18 of 58

Appendix B

Test No: Vendor: Test:

5 HATHAWAY UPS - This test demonstrates that the Field RIG is communicating with its UPS unit and that alarming checking is taking place on the status data gathered via the serial communications link. This testing is further intended to demonstrate the ability of the UPS to power the Field RIG, without disruption, through a series of simulated failures.

Procedure: 1) Remove source power to the UPS and verify that it successfully, non-disruptively maintains operation of the RIG as well as generating the expected alarms to the RIG. 2) Allow the UPS to run the RIG until it generates battery warning and shutdown alarms and through to complete failure of the UPS. Note the time of operation and the alarms generated. 3) Reconnect to source power and verify that the UPS can charge and power the RIG concurrently. Notice alarm status indication of the UPS. 4) Once fully re-charged, test the UPS by disconnecting its battery. Verify the alarm status. Reconnect the battery. Verify the alarm status. 5) Repeat test and confirm cycle time on the battery. 6) Bypass UPS to Raw Power only, check systems, and return to full UPS. Acceptance: The UPS should properly operate the RIG for the minimum time span of 30 minutes and should generate the manufacturer-specified alarm conditions for the fault conditions inflicted.
Initial Date Punch

UPS Comments:

Page 19 of 58

Appendix B

Test No: Vendor: Test: Procedure:

6 HATHAWAY Review of Protocol Conversions

Hathaway will provide the protocol conversion spreadsheets used to design and implement the various protocol conversions. Plant personnel will review this material in order to ensure that the conversions have been designed in a way to successfully execute the conversions.

Page 20 of 58

Appendix B

Test No: Vendor: Test: Procedure:

6.1 HATHAWAY Protocol Conversions – Conitel 2020

Configure the Protocol Engine with the Conitel 2020 prom set (one port set to “master” and one port set to “Field”). Analog Input Tests 1) Apply a signal to the first analog input of the plant control equipment. Confirm that the input can be read at the workstation, the Master and ISO Development EMS. Test input at 0, mid-range and full scale. Using the plant control equipment, generate a message type with a value and status that represents an over-range on the input. Confirm alarm reporting and value conversions to the ISO Development EMS. 2) Repeat for analog inputs 2-8 using the mid-range value. Digital Input Tests 3) Apply a signal to the first digit input. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Cycle point closed, open, closed, and open and confirms that changes are sent in real time to the workstation, the Master and the ISO Development EMS. 4) Repeat for digital inputs. Test each bit in one full word and across multiple words. Test Multi-state Change Detect, if applicable. Accumulator Tests 5) Apply a signal to the Form C accumulator. Command the system to freeze and read the accumulators. Confirm that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control equipment and the ISO Development EMS (and the Master), through the Master and Field RIGs. 6) Apply a signal to the Form A accumulators. Command the system to freeze and read the accumulators. Confirm that that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control equipment and the ISO Development EMS (and the Master), through the Master and Field RIGs.

Page 21 of 58

Appendix B

Direct Control Output Tests 7) Via the ISO Development EMS, and then via the Master, set the first control output. Confirm that the output reaches the plant control equipment. Setup multiple control outputs and confirm. Test standard output pulses. 8) Repeat for control outputs 2-4. AGC Control Pulse Width Output Tests 9) Via the ISO Development EMS, and then via the Master, set the first pulse width output. Confirm that the output reaches the plant control equipment. Vary the pulse width output and confirm that the output varies accordingly. 10) Repeat for pulse width output 2. 11) Via the ISO Development EMS, and then via the Master, set the first pulse train output. Confirm that the output reaches the plant control equipment. Vary the pulse train output and confirm that the output varies accordingly. Analog Setpoint Output Tests 12) Via the ISO Development EMS, and then via the Master, set the first analog output. Confirm that the output reaches the plant control equipment. Test output at 0, midrange, full scale. 13) Repeat for analog outputs 2-8. General: Verify the proper operation of all relevant protocol message and command types for the given protocol.
Initial Date Punch

PROTOCOL CONVERSIONS – Conitel 2020 Comments:

Page 22 of 58

Appendix B

Test No: Vendor: Test: Procedure:

6.2 HATHAWAY PROTOCOL CONVERSIONS – CDC-TYPE1

Configure the Protocol Engine with the CDC-T1 prom set (one port set to “master” and one port set to “field”). Analog Input Tests 1) Apply a signal to the first analog input of the plant control system equipment. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Test input at 0, mid-range and full scale. Using the test plant control equipment, generate a message type with a value and status that represents an over-range on the input. Confirm alarm reporting and value conversions to the ISO Development EMS. 2) Repeat for analog inputs 2-8 using the mid-range value. Digital Input Tests 3) Apply a signal to the first digit input. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Cycle point closed, open, closed, and open and confirms that changes are sent in real time to the workstation, the Master and the ISO Development EMS. 4) Repeat for digital inputs. Test each bit in one full word and across multiple words. Test Multi-state Change Detect, if applicable. Accumulator Tests 5) Apply a signal to the Form C accumulator. Command the system to freeze and read the accumulators. Confirm that the workstation, the Master and the plant control system equipment can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control equipment and the ISO Development EMS (and the Master), through the Master and Field RIGs. 6) Apply a signal to the Form A accumulators. Command the system to freeze and read the accumulators. Confirm that that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS(and the Master), through the Master and Field RIGs.

Page 23 of 58

Appendix B

Direct Control Output Tests 7) Via the ISO Development EMS, and then via the Master, set the first control output. Confirm that the output reaches the plant control system equipment. Setup multiple control outputs and confirm. Test standard output pulses. 8) Repeat for control outputs 2-4. AGC Control Pulse Width Output Tests 9) Via the ISO Development EMS, and then via the Master, set the first pulse width output. Confirm that the output reaches the plant control system equipment. Vary the pulse width output and confirm that the output varies accordingly. 10) Repeat for pulse width output 2. 11) Via the ISO Development EMS, and then via the Master, set the first pulse train output. Confirm that the output reaches the plant control system equipment. Vary the pulse train output and confirm that the output varies accordingly. Analog Setpoint Output Tests 12) Via the ISO Development EMS and then via the Master, set the first analog output. Confirm that the output reaches the plant control system equipment. Test output at 0, mid-range, full scale. 13) Repeat for analog outputs 2-8. General: Verify the proper operation of all relevant protocol message and command types for the given protocol.
Initial Date Punch

PROTOCOL CONVERSIONS – CDC-T1 Comments:

Page 24 of 58

Appendix B

Test No: Vendor: Test: Procedure:

6.3 HATHAWAY PROTOCOL CONVERSIONS – PG&E

Configure the Protocol Engine with the PG&E prom set (one port set to “master” and one port set to “field”). Analog Input Tests 1) Apply a signal to the first analog input of the plant control system equipment. Confirm that the input can be read at the workstation, the Master and the ABB. Test input at 0, mid-range and full scale. Using the plant control system equipment, generate a message type with a value and status that represents an over-range on the input. Confirm alarm reporting and value conversions to the ISO Development EMS simulator. 2) Repeat for analog inputs 2-8 using the mid-range value. Digital Input Tests 3) Apply a signal to the first digit input. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Cycle point closed, open, closed, and open and confirms that changes are sent in real time to the workstation, the Master and the ISO Development EMS. 4) Repeat for digital inputs 2-4. Accumulator Tests 5) Apply a signal to the Form C accumulator. Command the system to freeze and read the accumulators. Confirm that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS (and the Master), through the Master and Field RIGs. 6) Apply a signal to the Form A accumulators. Command the system to freeze and read the accumulators. Confirm that that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS (and the Master), through the Master and Field RIGs. Page 25 of 58

Appendix B

Direct Control Output Tests 7) Via the ISO Development EMS, and then via the Master, set the first control output. Confirm that the output reaches the plant control system equipment. Setup multiple control outputs and confirm. Test standard output pulses. 8) Repeat for control outputs 2-4. AGC Control Pulse Width Output Tests 9) Via the ISO Development EMS, and then via the Master, set the first pulse width output. Confirm that the output reaches the plant control system equipment. Vary the pulse width output and confirm that the output varies accordingly. 10) Repeat for pulse width output 2. 11) Via the ISO Development EMS System, and then via the Master, set the first pulse train output. Confirm that the output reaches the plant control system equipment. Vary the pulse train output and confirm that the output varies accordingly. Analog Setpoint Output Tests 12) Via the ISO Development EMS System, and then via the Master, set the first analog output. Confirm that the output reaches the plant control system equipment. Test output at 0, mid-range, full scale. 13) Repeat for analog outputs 2-8. General: 14) Verify the proper operation of all relevant protocol message and command types for the given protocol.
Initial Date Punch

PROTOCOL CONVERSIONS – PG&E Comments:

Page 26 of 58

Appendix B

Test No: Vendor: Test:

6.4 HATHAWAY PROTOCOL CONVERSIONS – DNP 3.0 (MASTER)

Procedure: Analog Input Test 1) Apply a signal to the first analog input. Confirm that the input can be read at both the workstation and the ISO Development EMS. 2) Repeat for analog inputs 2-41. Digital Input Test 3) Apply a signal to the first digit input. Confirm that the input can be read at both the workstation and the ISO Development EMS. 4) Repeat for digital inputs 2-12. Accumulator Tests 5) Apply a signal to the Form C accumulators. Command the system to freeze and read the accumulators. Confirm that both the workstation and the ISO Development EMS can read the accumulator.

Page 27 of 58

Appendix B

Direct Control Output Tests 6) Via the ISO Development EMS, set the raise/lower output. Confirm that the output reaches the plant control system equipment. 7) Repeat for raise/lower outputs 2-8. AGC Control Analog Setpoint Output 8) Via the ISO Development EMS, set the first analog output. Confirm that the output reaches the plant control system equipment. 9) Repeat for analog outputs 2-8. Test cold start and all other appropriate and relevant function codes
Initial Date Punch

PROTOCOL CONVERSIONS – DNP 3.0 (Master) Comments:

Page 28 of 58

Appendix B

Test No: Vendor: Test:

6.5 HATHAWAY PROTOCOL CONVERSIONS – C2100H PROTOCOL

Procedure: Configure the Protocol Engine with the C2100H prom set (one port set to C2100H “master” ,one port set to CDC-T1 “master” and one port set to CDC-T1 “field”). Analog Input Tests 1) Apply a signal to the first analog input of the plant control equipment. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Test input at 0, mid-range and full scale. Using the plant control system equipment, generate a message type with a value and status that represents an over-range on the input. Confirm alarm reporting and value conversions to the ISO Development EMS. 2) Repeat for analog inputs 2-8 using the mid-range value. Digital Input Tests 3) Apply a signal to the first digit input. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Cycle point closed, open, closed, and open and confirms that changes are sent in real time to the workstation, the Master and the ISO Development EMS. 4) Repeat for digital inputs. Test for each bit in one full word and across multiple words. Test multi-state change detect, if applicable. Accumulator Tests 5) Apply a signal to the Form C accumulator. Command the system to freeze and read the accumulators. Confirm that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS (and the Master), through the master and Field RIGs. 6) Apply a signal to the Form A accumulators. Command the system to freeze and read the accumulators. Confirm that that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS (and the Master), through the master and Field RIGs. Page 29 of 58

Appendix B

Direct Control Output Tests 7) Via the ISO Development EMS, and then via the Master, set the first control output. Confirm that the output reaches the plant control system equipment. Setup multiple control outputs and confirm. Test standard output pulses. 8) Repeat for control outputs 2-4. AGC Control Pulse Width Output Tests 9) Via the ISO Development EMS, and then via the Master, set the first pulse width output. Confirm that the output reaches the plant control system equipment. Vary the pulse width output and confirm that the output varies accordingly. 10) Repeat for pulse width outputs 2-4. Analog Setpoint Output Tests 11) Via the ISO Development EMS, and then via the Master, set the first analog output. Confirm that the output reaches the plant control system equipment. Test output at 0, mid-range, full scale. 12) Repeat for analog outputs 2-8. General: Verify the proper operation of all relevant protocol message and command types for the given protocol.
Initial Date Punch

PROTOCOL CONVERSIONS – C2100H Protocol

Comments:

Page 30 of 58

Appendix B

Test No: Vendor: Test:

6.6 HATHAWAY PROTOCOL CONVERSIONS– MODBUS

Procedure: 1) Connect a Modicon PLC to the IOC using a spare port. 2) Generate a minimal number of test database points in the IOC, to allow the Modbus driver to scan and poll the PLC. Modify the master RIG database to incorporate these points in the DNP3.0 “map”. 3) Apply signals to the various PLC inputs. Confirm that the input can be read at both the workstation and the ISO Development EMS. 4) Remove the temporary database points from the master and Field RIG databases.
Initial Date Punch

PROTOCOL CONVERSIONS – Modbus Comments:

Page 31 of 58

Appendix B

Test No: Vendor: Test: Procedure:

6.7 HATHAWAY PROTOCOL CONVERSIONS– MODBUS IOC TO PROTOCOL ENGINE

Using the existing database points for each plant control system equipment, which enable the Modbus driver to scan and poll the RTU with each Test Protocol. Use the master RIG database that incorporates these points in its DNP3.0 “map”. Configure the Protocol Engine with the prom set (one port set to C2100H “master” ,one port set to CDC-T1 “master” and one port set to CDC-T1 “field”). Analog Input Tests 1. Apply a signal to the first analog input of the plant control system equipment. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Test input at 0, mid-range and full scale. Using the plant control system equipment, generate a message type with a value and status that represents an over-range on the input. Confirm corresponding DNP3.0 message type and value conversions to the ISO Development EMS. 2. Repeat for analog inputs 2-8 using the mid-range value. Digital Input Tests 3. Apply a signal to the first digit input. Confirm that the input can be read at the workstation, the Master and the ISO Development EMS. Cycle point closed, open, closed, and open and confirm that changes are sent in real time to the workstation, the Master and the ISO Development EMS. 4. Repeat for digital inputs. Test for each bit in one full word and across multiple words. Test multi-state change detect. Accumulator Tests 5. Apply a signal to the Form C accumulator. Command the system to freeze and read the accumulators. Confirm that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant control system equipment and the ISO Development EMS (and the Master), through the master and Field RIGs. 6. Apply a signal to the Form A accumulators. Command the system to freeze and read the accumulators. Confirm that that the workstation, the Master and the ISO Development EMS can read the accumulator. Verify than special protocoldependent indications (such as accumulator roll-over) translate between the plant Page 32 of 58

Appendix B

control system equipment and the ISO Development EMS (and the Master), through the master and Field RIGs. Direct Control Output Tests 7. Via the ISO Development EMS, and then via the Master, set the first control output. Confirm that the output reaches the plant control system equipment. Setup multiple control outputs and confirm. Test standard output pulses. 8. Repeat for control outputs 2-4. AGC Control Pulse Width Output Tests 9. Via the ISO Development EMS, and then via the Master, set the first pulse width output. Confirm that the output reaches the plant control system equipment. Vary the pulse width output and confirm that the output varies accordingly. 10. Repeat for pulse width outputs 2-4. Analog Setpoint Output Tests 11. Via the ISO Development EMS, and then via the Master, set the first analog output. Confirm that the output reaches the plant control system equipment. Test output at 0, mid-range, full scale. 12. Repeat for analog outputs 2-8. 13. General: Verify the proper operation of all relevant protocol message and command types for the given protocol.
Initial Date Punch

PROTOCOL CONVERSIONS – Modbus IOC to Protocol Engine Comments:

Page 33 of 58

Appendix B

Test No: Vendor: Test:
530

7 HATHAWAY ISO METER COMMUNICATIONS - This test will verify the transmission of the ISO Meter data from the ISO Test meter to the MDAS system.

Procedure: 1) Using two MDAS units, one communicating via the Master RIG and one directly communicating over the network, communicate with a meter and ensure that identical information is provided to both MDAS. All standard MDAS functionality should be exercised.
530 364

2) Using the TCP/IP communications directly to the Cisco router (which acts as a terminal server for the test meter) the Field RIG will “poll” the test meter and retrieve the designated tables. A subset of these will then be mapped into database points in the Field RIG and be available for display via a test graphic display in the workstations. The data shown on the workstation displays shall match the data being read by the MDAS systems, prior to the scaling of these values (as is done in the MDAS system). A selected set of values will then be scaled in the Field RIG, using “calc” blocks, and the results viewed on the test graphic and compared to the MDAS values. 3) Repeat Step 1 with three meters accessed via the same Field RIG. Ensure that identical information is provided to both MDAS. Acceptance: The values of the meter data read in both tests must exactly match aside from excess (beyond “significant”) digits, in order to pass the testing. Conversion to floating-point values can generate “rounding” but this must not occur in the “raw” meter readings and must not effect the “significant” digits of the scaled values. The meter recorder data, in pulses must exactly match, in each of the channels for all intervals.
Initial Date Punch

ISO METER COMMUNICATIONS Comments:

Page 34 of 58

Appendix B

Test No: Vendor: Test:

8 HATHAWAY METER AUDIT TRAIL

Procedure: 1) From the ISO MDAS, via the Master RIG and Field RIG, perform the following functions: a) b) c) d) Set the meter’s password Change the meter’s password Read all the data in the meter Initialize the meter

2) Confirm Field RIG storage of 60 days worth of data. Confirm that said data can be accessed by other minMDAS and by ISO MDAS. 3) ISO/MDAS/MV-90 access to the meter through the Field RIG. To do a Read All Data in the meter at the same time have Field RIG try to read the meter. 4) Compare timing of meter interrogation via EC-Net and RIG to verify communications latency is not introduced that would degrade ISO MDAS pass through requirements.
Initial Date Punch

Meter Audit Trail Comments:

Page 35 of 58

Appendix B

Test No: Vendor: Test:

9 HATHAWAY UNIT AUTHORITY SWITCH / CONTROL AUTHORIZATIONS - This test demonstrates the control commands can only be received from one entity at any given time.

Procedure: Select the control entity (Owner, ISO, etc.) for the test generating unit. 1) Command the unit from the selected entity and ensure that the command executes the appropriate field device. 2) Attempt to command the unit from another entity. Ensure that the command does not execute and that an alarm message appears in the audit log. 3) Repeat Steps 2 and 3 for each available entity. 4) Select the control entity AUTO for the test generating unit. 5) Confirm which entity is in control of the unit based on the input commands coming from the plant owner. 6) Command the unit from the designated entity and ensure that the command executes. 7) Attempt to command the unit from another entity. Ensure that the command does not execute and that an alarm message appears in the audit log. 8) Have the plant owner transfer control to a different entity. 9) Ensure that commands can be executed by the designated entity and that no other entity can control the unit. 10) View the status of the UAS from the various control entities.
Initial Date Punch

UAS/CONTROL AUTHORIZATIONS Comments:

Page 36 of 58

Appendix B

Test No: Vendor: Test:

10 HATHAWAY EMS INTERFACE - The purpose of this testing is to demonstrate the realtime ability of the system to move data from the external plant control system equipment, into a Field RIG, across the TCP/IP network and deliver it as a value mapped to a DNP3.0 channel on the Master RIG which in turn will deliver it via that channel to the EMS systems. The second purpose of this testing is to demonstrate the real-time transfer of supervisory commands from the EMS systems, through the Master RIG and Field RIG, out to the external plant control system equipment connected to the Field RIG.

Procedure: 1) Using the plant interface connected to the Field RIG, assorted inputs shall be stimulated and the Field RIG shall detect these changes during its routine polling of that plant interface. 2) Using the workstations and the RIG diagnostic graphic display(s) the changes to the plant interface inputs shall be presented as such changes are made. 3) Using the EMS systems attached to the master RIG, the change in the inputs to the plant control system equipment shall be reflected in a matching change to the DNP block(s) which correspond to the plant control system equipment inputs. 4) Supervisory control commands shall be issued by using the EMS systems to send control messages to the Field RIG which will in turn send the appropriate command to the corresponding plant interface output. 5) Test plant interface down and data quality code flags populated to EMS for each plant interface and data type. 6) Disconnect the Field RIG from the network. Confirm that all data reported to the ISO Development EMS is flagged as bad quality. This demonstrates that bad data quality is reported for all points when the RIG is off line. 7) Reconnect the Field RIG to the network. Confirm that the data reported for the active plant interface configuration is reporting as data quality good. Ensure that all data for the other plant interface configurations are reported as bad quality. This demonstrates that the data quality flag is based on successful communications to the plant interface.

Page 37 of 58

Appendix B

Test No 10 (continued) Acceptance: The test shall be successful if the data and command transfers occur within the 4 second window, regardless of the other functions taking place during this testing.
Initial Date Punch

EMS INTERFACE Comments:

Page 38 of 58

Appendix B

Test No: Vendor: Test:

11 HATHAWAY SYSTEM STATUS AND ALARMING - The purpose of this testing is to demonstrate the displays, alarms and operator logs which will be provided with the system and included as part of the applications database and configuration for each RIG, as it is incorporated into the overall system. The goal of this testing will be to show how the system status and alarm displays will react to various types of faults, failures and alarm conditions.

The test will demonstrate the alarming functions of the Field RIG for the following conditions; Cabinet access, Cabinet over temperature, Cabinet water incursion, UPS failure modes, Communications loss to Protocol Engine, Loss of communications to Field RIG, GPS signal loss, Loss of communications port on Protocol Engine Procedure: In general, the testing will be conducted by simulation of the failures or conditions listed above and showing that the system successfully detects these and presents this in the form of alarm displays, alarm logs, audible annunciation and in status graphic displays. The supervision of the testing will take place at the system UNIX workstations.
Initial Date Punch

SYSTEM STATUS AND ALARMING Comments:

Page 39 of 58

Appendix B

Test No: Vendor: Test:

12 HATHAWAY VOIP COMMUNICATIONS TESTING - The purpose of this testing is to demonstrate the ability of the Field RIG VoIP equipment to function in parallel with the rest of the equipment and to demonstrate that the bandwidth usage for simultaneous voice communications does not degrade the real-time performance of data exchanges and supervisory control functions.

Procedure: 1) The “red” phone of the Field RIG shall be activated and a voice communication established to the Folsom control center to a corresponding telephone. 2) Voice communications will be maintained while the system is functioning. 3) The system status, I/O status and alarm displays for the Field RIG shall be activated on the workstations. 4) Alarms and value changes shall be “forced” on the Field RIG by manipulating the sensors of the Field RIG and the inputs of the plant control system equipment (RTU/DCS, etc) connected to the Field RIG. 5) Supervisory commands shall be issued to the Field RIG via the EMS system connected to the master RIG.
Initial Date Punch

VOIP COMMUNICATIONS Comments:

Page 40 of 58

Appendix B

Test No: Vendor: Test:

13 HATHAWAY SYSTEM FAILURE AND RECOVERY TESTING – This test verifies the failover from the primary circuit to the back-up circuit (with permanent router installed). This is based on a dual T1 plus ISDN configuration. This procedure may need to be modified depending on the configuration at the site.

Procedure: 1) Pull primary T-1 to verify correct connection and continued connectivity to router. a) CD light on corresponding T-1 interface on router will turn off and AL light goes on b) MCI performs ping test to router i) If router cannot be pinged MCI will open trouble ticket ii) If router can be pinged, hathaway will perform ping test and other tests to insure correct information response from the Router, the IOC and the Meter port 2) Pull secondary T-1 a) CD light on corresponding T-1 interface on router will turn off and AL light goes on b) MCI performs ping test to router i) CD light on corresponding T-1 interface on router will turn off and AL light goes on ii) Router will auto dial on ISDN line to reconnect to network (takes approximately two minutes for complete synchronization) c) MCI performs ping test to router i) If router cannot be pinged MCI will open trouble ticket ii) If router can be pinged, Hathaway will perform ping test and other tests to insure correct information response from the Router, the IOC, and Meter port
Initial Date Punch

SYSTEM FAILURE AND RECOVERY Comments:

Page 41 of 58

Appendix B

Test No: Vendor: Test: Procedure:

14 HATHAWAY SECURITY SYSTEM – Card Swap Remove the primary Field RIG IOC Security Card. Install the back-up Field RIG IOC Security Card. Ensure the Field RIG IOC is operating properly.
Punch

Initial

Date

SECURITY SYSTEM – Card Swap Comments:

Page 42 of 58

Appendix B

Test No: Vendor: Test:

15.1 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST - TRENDING

Procedure: 1. Check Unit Trending setup on ISO Development EMS to Trend setpoint output and Unit Net MW. 2. Check Unit Trending setup on RIG Workstation to Trend setpoint output and Unit new MW from the Field RIG. 3. Check Unit trending setup at Station to Trend setpoint output received from the Rig and Unit Net MW from the plant control system equipment. 4. When testing is complete make sure copies of all trends are routed to the EMS Engineer performing the tests for evaluation. 5. Monitor unit performance factors on EMS during testing on AGC.
Initial Date Punch

Development SIT – Trending Comments:

Page 43 of 58

Appendix B

Test No: Vendor: Test:

15.2 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – PULSE CONTROL

Procedure: 1. Establish unit at stable load point for testing. 2. Send unit a manual raise pulse based on default pulse duration. 3. Confirm pulse throughput on TIS4000 workstation monitoring the Field RIG. 4. Confirm pulse output from the Field RIG at correct raise point and duration. 5. Pulse unit on raise cycle with enough pulses to verify satisfactory response (10MW). 6. Send unit a manual lower pulse based on default pulse duration. 7. Confirm pulse output from the Field RIG at lower point duration. 8. Pulse unit on lower cycle with enough pulses to verify satisfactory response (10MW). 9. Setup unit on Development AGC.
Initial Date Punch

Development SIT – Pulse Control Comments:

Page 44 of 58

Appendix B

Test No: Vendor: Test:

15.3 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – V-NOTCH

Procedure: 1. Check and note current Unit Load. 2. Move unit to at least 20% below the upper operating limit. 3. Ramp unit up 10% and before reaching full 10% capacity up ramp and unit stability reverse ramp to down 10%. Check unit stability and response at desired setpoint per rate. 4. Ramp unit to 20% above lower operating limit. 5. Ramp unit down 10% and before reaching full 10%capacity down ramp and unit stability reverse ramp to up 10%. Check unit stability and response at desired setpoint per rate.
Initial Date Punch

Development SIT – V-Notch

Comments:

Page 45 of 58

Appendix B

Test No: Vendor: Test:

15.4 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – UNIT MAXIMUM-MINIMUM

Procedure: 1. Set unit upper regulation limit to unit max operating limit. 2. Ramp unit to upper regulation limit 3. Verify unit controller does not ramp unit past max operating limit (stable at upper reg limit). 4. Ramp unit down and confirm unit response from max operating/regulation limit is consistent with desired ramp rate without excessive delay. 5. For Hydro Units Only: • Set unit lower regulation limit to unit minimum operating limit • Ramp unit to lower regulation limit • Verify unit controller does not ramp unit past min operating limit • Ramp unit up and confirm until response from min operating/regulation limit is consistent with desired ramp rate without excessive delay.
Initial Date Punch

Development SIT – Unit Max-Min Comments:

Page 46 of 58

Appendix B

Test No: Vendor: Test:

15.5 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – UNIT STOP

Procedure: 1. Load unit to midrange of regulation limits. 2. Set upper and lower regulation limits at ± 10 MW from unit load. 3. Request ISO control. 4. Confirm upper and lower regulation limits, limit unit loading requests.

Initial

Date

Punch

Development SIT – Unit Stop Comments:

Page 47 of 58

Appendix B

Test No: Vendor: Test:

15.6 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – AGC

Procedure: 1. Ramp unit to midpoint of regulation range 2. Vary ACE to force unit to respond to AGC signals up and down by 5-20 MW over a 10-20 minute test period. Confirm unit response is consistent with control outputs and response is consistent with desired ramp rate.
Initial Date Punch

Development SIT – AGC Comments:

Page 48 of 58

Appendix B

Test No: Vendor: Test:

15.7 HATHAWAY DEVELOPMENT SYSTEM COMMUNICATION LINK INTEGRATION TEST – IOC
TO

PLANT

Procedure: 1. Ensure unit is in ISO AGC mode. 2. Remove the serial connection between the IOC and plant control system equipment. 3. Note any abnormalities and changes to the plant control system equipment. NOTE: Unit should alarm and control transfer to DCS. Setpoint should set to unit loading at the time of failure. 4. Re-establish the serial interface 5. Reset Unit to ISO control and confirm control.
Initial Date Punch

Development SIT – IOC to Plant Communication Link Comments:

Page 49 of 58

Appendix B

Test No: Vendor: Test:

15.8 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – MASTER IOC COMMUNICATION LINK
TO

FIELD IOC

Procedure: 1. Endure the unit is in ISO control. 2. Remove the T1 connection at the RIG. 3. Note any abnormalities and changes to the plant control system equipment. NOTE: Unit should alarm and control transfer to plant control system equipment. Set point should set to unit loading at the time of failure. 4. Re-establish the T1 Communications circuit. 5. Reset unit to ISO control and confirm control.
Initial Date Punch

Development SIT – Master IOC to Field IOC Communication Link Comments:

Page 50 of 58

Appendix B

Test No: Vendor: Test:

15.9 HATHAWAY DEVELOPMENT SYSTEM INTEGRATION TEST – RTG COMMUNICATION LINK
TO

MASTER IOC

Procedure: 1. Ensure unit is in ISO Control. 2. Mark plant control system equipment for station to ‘out of service’ on EMS. 3. Note any abnormalities and changes to the plant control system equipment. 4. Plant unit should alarm indicating Master Field communications interrupted, NOT ON AGC Regulation. 5. Mark plant control system equipment for station to ‘in service’ on EMS. 6. Ensure unit is in ISO control; confirm control.
Initial Date Punch

Development SIT – RTG to Master IOC Communication Link Comments:

Page 51 of 58

Appendix B

Test No: Vendor: Test:

16.1 HATHAWAY PRODUCTION SYSTEM INTEGRATION TEST – TRENDING

Procedure: 1. Check unit trending setup on EMS to trend setpoint output and unit net MW. 2. Check unit trending setup on TIS4000 workstation to trend setpoint output and unit new MW from the Field RIG. 3. Check unit trending setup at station to trend setpoint output received from the RIG and unit new MW from the plant control system equipment. 4. When testing is complete make sure copies of all trends are routed to the EMS engineer performing the tests for evaluation. 5. Monitor unit performance factors on EMS during testing on AGC. 6. Verify Unit tuning parameters on Production EMS.
Initial Date Punch

Production SIT – Trending Comments:

Page 52 of 58

Appendix B

Test No: Vendor: Test:

16.2 HATHAWAY PRODUCTION SYSTEM INTEGRATION TEST – RAISE/LOWER STABILITY

Procedure: 1. Check unit for over-shoot on raise. 2. Unit should not exceed raise regulation limit by more than limit deadband. 3. Lower unit on AGC. Unit should stabilize at desired setpoint and match ramp rate. 4. Unit should not exceed lower regulation limit by more than limit deadband. 5. Return unit to operating point at start of test.
Initial Date Punch

Production SIT – Raise/Lower Stability Comments:

Page 53 of 58

Appendix B

Test No: Vendor: Test:

16.3 HATHAWAY PRODUCTION SYSTEM INTEGRATION TEST – AGC, ACE TRACKING
AND

SCHEDULE

Procedure: 1. Ensure unit is in ISO control. 2. ISO places unit on AGC control. 3. Verify unit is following ACE and schedule amount. 4. Vary unit regulation limits to move unit within parameters and verify unit correct response. 5. Return unit to normal operating schedule and limits.
Initial Date Punch

Production SIT – AGC, ACE and Schedule Tracking Comments:

Page 54 of 58

Appendix C

APPENDIX C TEST Punch List
Item 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Date Test Punch List Item Owner Status Punch List Item Status/Resolution Due Date Signoff Initial Signoff Date

55

Appendix D

APPENDIX D - Discrepancy Report Form

Attached is a copy of the Discrepancy Report form. This is to document and track any variances that are found during testing, that could not be corrected during the test. It is important that this form be completed in full detail. It is suggested that all variances be routed to one individual for logging (assignment of discrepancy numbers), and data entry into some type of tracking system, so that reports can be generated as needed. All original copies should be kept in one central location, and used for sign off once re-tested.

56

Appendix D
Srp‚…qÃIˆ€ir…

SAMPLE DISCREPANCY REPORT

SUBMITTED BY:

TEST PLAN #/DESCRIPTION:

DESCRIPTION OF PROBLEM:

RESOLUTION:

REPAIR RESPONSIBILITY

DATE

SUBMITTERS CONCURRENCE

Page 57 of 58

Certification Process

4

CERTIFICATION PROCESS

1. Upon completion of the RIG production test, a test for Ancillary Services (A/S) recertification (scheduled through ISO Client Relations and the ISO Outage Coordination Office) must be conducted within 2 weeks. If the results are mutually satisfactory (to the Generator/Scheduling Coordinator (SC) and ISO), the ISO will declare these A/S test results as final, and re-certify the unit at these new values. 2. If the Generating Unit’s A/S test does not go well (i.e., poor performance, or failure) further tuning and adjustments may be made. Any additional attempts at A/S recertification shall be completed within 4 weeks from the production test checkout. 3. During this period of tuning and A/S re-certification (until the A/S test results reach finality), the unit will retain its previous certified (i.e., non-RIG) A/S status and values, regardless of RIG performance. In this transitional period, the unit may remain on the RIG, or switch back to the former communications/control technology as needed. However, A/S compliance still applies: SCs of units with new RIG installations are encouraged to only bid those services and quantities they have confidence in delivering. 4. On or before the end of the 4 week grace period, the latest A/S test results (including results of failed performance) shall be declared final and the Generating Unit shall only operate via RIG from this point forward. 5. Some small delay is expected between the time the A/S values are made final and their entrance into the ISO Master File due to coordination of ISO Master File changes.

58