New Resource Implementation (стр. 6 )

The effective date black out range are the dates that the scheduling coordinator association CANNOT be effective. Please choose a date before or after this range.

Resource ID’s that will be in production after production effective trade date:

Pay attention to the “Deadline to submit changes that cannot be submitted through the Master File user interface (UI) or application programming interface (API) to *****@***com” date. Your scheduling coordinator association letters should be submitted to NRI at least 7 business days prior to this date in order to get processed.

The effective date black out range are the dates that the scheduling coordinator association CANNOT be effective. Please choose a date at least 7 business days after the production effective trade date.

Document Title: SCSelection (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 SCSelection Ver1

Document Title: SCAcceptance (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 SCAcceptance Ver1

Templates for these letters can be found here under “Letter Templates”:

Common problems are:

·  Scheduling Coordinator Selection and Acceptance letters’ effective dates do not match.

·  Scheduling Coordinator letters are submitted too close to the synchronization date of the generator. The process takes 7 business days to complete and cannot be expedited.

·  Letter is not on official letterhead.

f.  24/7 Contact Information form

This is also a required form to complete the RIG point-to-point testing. This form is located under Standard documents. Please submit to *****@***com. The primary contact should be available 24/7 and have access to or be able to obtain real-time information on the output or status of the resource(s) being monitored by the RIG.  If there is a RIG telemetry failure, this contact may be required to report specified changes in the output of the resource(s) until the problem is resolved.  Additional contacts desired would have the ability to troubleshoot RIG related issues or coordinate RIG related work (e. g. SCADA specialist, plant manager).

Document Title: 24HourContact (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 24HourContact Ver1

g.  Device Certificate Request Form for RIGs

Email to *****@***com with the Certificate Signing Request (CSR) file. Allow 10 business days to complete the request. This is a required form for completing the combined RIG point to point and meter testing using the Energy Control Network (ECN) or internet. This document is not needed to be sent to NRI email address.

h.  RIG and/or Metering Pretesting Email Notification

Email notification from interconnection customer to *****@***com and copying the *****@***com stating site has witnessed and approved of the RIG and Metering pretesting. This must be completed prior to scheduling the final telemetry testing with the CAISO. The electrical contractor and telemetry engineering company should perform the pretesting.

Email Subject Line example: 14GEN1234 RIG Pretesting Notification

i.  RIG and Meter ISO Testing Scheduled

Required before synchronization is granted by the CAISO.

STEP 1: The IC should reach out to *****@***com to perform a communications check to the RIG and meters at the site.

STEP 2: Once CAISO has verified communications the Interconnection Customer will submit request through the Fieldwork Support Request form to schedule the Point to Point testing.

Common problems of RIG Point Testing Scheduling are:

·  Not preparing for the CAISO final point to point testing. All CAISO required points should be tested to a Distributive Network Protocol (DNP) Master and should confirm that the RIG is sending the correct values. The values should match the scaling that is in the RIG spreadsheet.

j.  CPS Subscribers Agreement for Remote Intelligent Gateways (RIGs)

CAISO issues digital certificates for use in RIG units according to the practices described in the Certification Practice Statement for Basic Assurance Certification Authority (CPS).
This document can be found here.

Document Title: CPSAgreement (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 CPSAgreement Ver1

k.  Energy Control Network Connectivity (ECN) Security Requirements and Agreement

This document is required to be signed by the Interconnection Customer to open the EMS communication path to the RIG before point to point testing will begin. The document should be signed before a meter is configured in MDAS. This document can be found here.

Document Title: ECNAgreement (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 ECNAgreement Ver1

l.  Distribution Correction Factor Supporting Documentation

If a CAISO Metered Entity is connected to a Utility Distribution Company’s (UDC)/Distribution Provider Distribution System, an approved Distribution Compensation Factor (DCF) must be determined and must be programmed into the meter to reflect the point of delivery at the CAISO Controlled Grid. WDAT or any letter of agreement of DCF from appropriate UDC/Distribution Company/ Interconnection entity must be submitted to NRI prior to programming the ISO Meter with a DCF.

Document Title: DCF (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 DCF Ver1

m.  Meter Exemption Request

If a generator resource CAISO revenue meter is metering the low side of the transformer, a meter exemption request shall be submitted for approval and emailed to *****@***com with the file naming convention listed below. This document can be found here.

Meter Exemption Request Email Subject Line: 14GEN1234 [Complete Project Name] Meter Exemption Request

Document Title: MeterExemption [Device ID] (See above File Naming Convention and Version Control Standards)

File naming example: 14GEN1234 MeterExemption 5912345 Ver1

 

 

8.  Bucket 4 – Trial Operations Approval

a.  Getting To Synchronization

At this point Buckets 1 through 3 items are accepted and checked off and the metering and telemetry point to point testing must be completed. The testing will include a preliminary validation of the meter data. A final validation of metering and telemetry data will be completed after synchronization using generation data.

b.  Interconnection Approval Letter from Participating Transmission Owner (PTO) or Distribution Owner

This letter is required from the PTO granting permission to sync and test the generator. This letter can be used for COD as long as there is clear direction in the letter stating there is no limitation to the connection and generator.

Note: If the letter is a final permission to operate letter as well the letter must be submitted again with the request for COD email.

The letter must include:

·  ISO Resource ID or NRI project number.

·  MW values permitted to be put on the grid for testing.

·  All transmission upgrades are completed, if applicable.

·  All testing and pre-parallel inspection is completed.

Document Title: PTO Sync Approval (See above File Naming Convention and Version Control Standards). Example: 14GEN1234 PTO Sync Approval Ver1

c.  Interconnection Customer Sync Request Email

This is an email stating that the Interconnection Customer is requesting to sync and generate test energy out to the grid. This should not be confused with parallel and back feeding the transformer(s). When CAISO NRI receives this email, the CAISO has 10 days to process the request.

All Bucket 1 through 4 requirements must be received and accepted, including the Participating Transmission Owner Sync Approval letter, before this email shall be sent to NRI.

Email Subject line example: 14GEN1234 Request for Initial Synchronization

d.  Test Energy Schedule

Upon sending the notification of sync email to *****@***com or on request, NRI will send the Interconnection Customer a Test Energy Schedule template to be populated and will be provided to the Scheduling Coordinator. Please refer to the CAISO operating procedure 5320 Resource Trial Operations and Test Energy Process.

9.  Bucket 5 – Trial Operations

a.  CAISO Internal Approval Process for Synchronization

Below is the internal CAISO process of granting initial sync after the Interconnection Customer submits sync request (Section 6.a) after all bucket items have been met. If all bucket items have been accepted the CAISO sync approval process will commence from the request in Section 6.a. Upon CAISO approval, NRI will send the Interconnection Customer an email approving the resource for Initial Synchronization allowing a resource to commence Trial Operations.