FAQs
Data
< Previous | Showing 81 to 90 | Next > | << Back to FAQ Categories
-
FAQ-78:
How many reasonable arrangement customers are taking service under SSO? Also, please provide the peak load (MW) for the reasonable arrangement customers under SSO.
There are three (3) customers under Reasonable Arrangements in the AEP Ohio service territory that have been approved by the Public Utility Commission of Ohio (“Commission”) under R.C. 4905.31. Since the end of 2014, the Commission has approved requests from all three (3) of these Reasonable Arrangement customers to begin purchasing capacity and energy from CRES providers. These customers have obtained confidential treatment and have secured protective orders relative to their agreements. Information that is publicly available related to these filings are available from the Commission. The aggregate load that can purchase capacity and energy from CRES providers under these approvals from the Commission is approximately 347.5 MW.Should these customers purchase energy and capacity from CRES providers, these customers would continue to have Reasonable Arrangements with AEP Ohio for purposes of purchasing transmission and distribution service and their contract termination dates are: June 1, 2015 for the Globe Metallurgical arrangement; January 1, 2019 for the Eramet Marietta arrangement; and December 31, 2015 for the TimkenSteel Corporation arrangement. Any migration by a Reasonable Arrangement customer to a CRES provider is reflected in the hourly load data posted to the CBP website as would any other migration of customers from SSO to a CRES provider.
10/21/2015 in Data
-
FAQ-73:
Is it possible for AEP Ohio to provide additional updated Hourly Load Data beyond May 31, 2015?
The Hourly Load and Customer Count data in the Data Room is updated through June 2015. No further data will be provided until the next data update on or around October 20, 2015.
09/23/2015 in Data
-
FAQ-67:
Has there been any change in the way day after SSO load data is determined and posted to PJM from the energy only transaction ended May 31 2015 and the full requirements transactions beginning June 1 2015 ?
No. There has been no change to either the way the data is determined or the way it is posted.
08/27/2015 in Data
-
FAQ-65:
As of 12/31/2014, the SSO Peak Load Contribution ("PLC") is 39.89% (3502/8780) of the total AEP Ohio PLC, based off of the PLC data in the Data Room. The delivery year 2015/16 SSO PLC value of 2,954.03 MW provided in the Bidder Webcast is based on five highest coincident peaks in 2014. I am trying to estimate the total PLC for AEP Ohio based on both shopping and SSO customers. Can you please confirm whether or not the 2954.03 MW has been weather normalized? Could you please provide the total PLC of AEP Ohio based on both shopping and SSO customers?
As noted previously in the Webcast, and FAQs 52 and 53, the PLC value of 2,954.03 MW provided in AEP-Ohio’s March 23, 2015 Bidder Webcast was based on AEP-Ohio’s total Standard Service Offer (SSO) at the time of the five highest coincident peaks experienced by PJM in 2014 for SSO (non-shopping only) customers as of December 31, 2014. AEP Ohio is not performing or providing any analysis with this number. The estimated MW-measure of 2,954.03 is provided for reference purposes only. As indicated in the webcast and in earlier FAQ responses, the amount of actual quantity to be delivered depends on many factors. These factors include, without limitation, migration of SSO-customers, and PJM Manual 19 weather adjustments. Consistent with the response provided in FAQ 52, it is the responsibility of the bidder to interpret possible reasons for PLC changes from year to year, and this would include, without limitation, migration and PJM’s weather normalization. Additionally, a total PLC for PY 15/16 for AEP Ohio for both Competitive Electric Retail Service (“CRES”) and SSO customers is not available.
05/06/2015 in Data
-
FAQ-61:
The 2014 Weather Normalized Coincident Peak Load for AEP provided by PJM with the results of the third incremental auction for planning year 2015/16 is 10,840.5 MW. Does this equal the sum of AEP Ohio’s PLCs associated shopping and non-shopping customers?
The AEP-Ohio PLC for shopping and SSO customers is a subset of the 10,840.5MW CP for RPM zonal load. The remainder represents additional RPM loads throughout the AEP Zone.
04/27/2015 in Data
-
FAQ-59:
In the AEP-Ohio Government Aggregation file some of the largest entities listed are “AREP Migration to BLUESTAR DUNS”, “Mass Transition”, “DTE Integrys” and “Glacial Agera”. Since these are not names of towns, cities or counties, should they be part of the government aggregation data file? Please let us know if the entities are mislabeled and the data belongs in the file, or if the data should not be in the government aggregation file.
Thank you for bringing this to our attention. The corrected file has been posted to the Data Room.
04/24/2015 in Data
-
FAQ-58:
I calculated an estimate of the daily zonal scaling factor (DZSF) based on the PLC data provided by AEP Ohio and 2014 weather normalized peak load data provided on PJM’s website. Should the DZSF I calculated be applied to the PLC data provided by AEP Ohio?
PJM will scale the daily PLCs uploaded by AEP-Ohio to a zonal RPM load target by calculating and applying a daily zonal scaling factor (DZSF), which varies daily. For more explanation regarding zonal scaling factors, please visit the PJM web site or contact a PJM Customer Representative.
04/24/2015 in Data
-
FAQ-57:
Were the historical PLC figures available in the Data Room calculated using the same methodology as the DY 2015/16 Peak Load Contribution (PLC) value of 2,954.03 MW provided in the Bidder Webcast?
Yes. The DY 2015/16 Peak Load Contribution (PLC) value of 2,954.03 MW corresponds to AEP-Ohio’s total Standard Service Offer (SSO) customers as of December 31, 2014. This value and the historical PLC figures posted on the AEP-Ohio’s website were determined in line with the methodology outlined in PJM’s Manual 19.
04/24/2015 in Data
-
FAQ-56:
Did AEP Ohio participate in the ARR allocation process for delivery year 2015/16? If so, will SSO Suppliers get the ARR credits? Did AEP Ohio use AEPOhio_Residual_AGG as the sink? Could you please provide the nominated paths? Will AEP Ohio transfer the nomination rights to SSO suppliers for the ARR allocation process for delivery year 2016/17?
Yes, AEP Ohio participated in the ARR allocation process on behalf of SSO Suppliers for the SSO Load procured in the 1st and 2nd ESP III Auctions for delivery year 2015/16. SSO Suppliers will get the ARR credit for this delivery year. AEPOhio_Residual_AGG was used as the sink. AEP Ohio will transfer the nomination right to SSO Suppliers that win tranches of the 24-month and 36-month products so they can participate in the ARR allocation process for delivery years 2016/17 and 2017/18 (if applicable). No data regarding the ARR allocation process will be provided at this time.
04/23/2015 in Data
-
FAQ-55:
Please confirm the following formula to determine an SSO Supplier’s UCAP obligation for their portion of SSO Load is correct: UCAP MW = PLC MW * Fixed Pool Requirement * AEP Zonal RPM Scaling Factor * Daily Zonal Scaling Factor. Is there any other adjustment that will be made to the PLCs by the EDC?
Assuming that you refer to PY 2015/16 and beyond, the calculation of AEP Zone’s Daily Unforced Capacity Obligation (UCAP) will be done as described by PJM in its Manual 18: “PJM Capacity Market” Section 7: “Load Obligations". The equation for determination of the UCAP obligation is as follows: Daily UCAP Obligation = Obligation Peak Load (MW) x Final Zonal RPM Scaling Factor x Forecast Pool Requirement where:Obligation Peak Load = Sum of Zone’s Area Obligation Peak Load Contributions (PLCs) x Daily Peak Load Scaling Factor
No other adjustment will be made to the PLCs by AEP Ohio to determine UCAP obligation.
04/23/2015 in Data
< Previous | Showing 81 to 90 | Next > | << Back to FAQ Categories