FAQs
All FAQs
< Previous | Showing 211 to 220 | Next > | << Back to FAQ Categories
-
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 Other/General , 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
-
FAQ-54:
Can you provide us Peak Load Contribution (“PLC”) data for after January 2015? We observed that there is a large change in the Large C&I customer counts from October 2014 to December 2014. It appears that a lot of customers left SSO service and then returned within one month. Can you give us a reason for that?
The Peak Load Contribution (“PLC”) is updated and posted to AEP Ohio CBP’s website on a monthly basis. PLC data through 1/31/2015 is currently available in the Data Room. Please note that the PLC value for planning year 2015/16 is 2,954.03 MW, as reported during the AEP-Ohio’s March 23, 2015 Bidder Webcast. This PLC value was estimated using AEP Ohio’s SSO customer numbers as of December 31, 2014.
The change referenced by the bidder is due primarily to the timing of billing cycles. Normally, these are staggered so each customer is billed each month. Occasionally, there will be months during which the length of some customers’ billing cycles will exceed the month being billed. In this case, they won’t receive any bill for the first month, but in the next month they will receive two bills, the earlier of which will reflect the prior month billing. The customer counts for a given month will reflect the number of bills issued, and not the number of customers served.
04/23/2015 in Data
-
FAQ-53:
Are the Peak Load Contribution (“PLC”) values provided in the data room based on PJM's or AEP Ohio territory's average of five summer coincident peaks methodology? Have these values been weather normalized? Was the SOS PLC of 2954.03MW for the 2015/16 delivery year, provided in the Bidder Webcast, calculated based on PJM's methodology? This value reflects about a 15% drop when comparing it to the daily PLCs provided in the data room. Will daily scaling factors get applied to this value starting with June 1, 2015?
The Peak Load Contribution (PLC) value of 2,954.03 MW provided in AEP-Ohio’s March 23, 2015 Bidder Webcast corresponds to DY 2015/16 and was computed based on AEP-Ohio’s total existing Standard Service Offer (SSO) customers as of December 31, 2014. That PLC value was determined in line with PJM’s methodology and has been verified. It is the responsibility of the bidder to interpret possible reasons for PLC changes from year to year. Daily Zonal Scaling Factors will be applied to the PLCs beginning in June 1, 2015. Please see PJM’s Manual 19 for more information on the calculation of Unforced Capacity Obligations.
04/23/2015 in Data
-
FAQ-52:
In Data FAQ #43, you stated that the forecasted SSO PLC of 2,954.03 MWs was “based on AEP Ohio's SSO customer numbers as of December 31, 2014.” If we take the observed migration in the PLC data on 12/31/2014 of roughly 60% and pair it with your stated PLC of 2,954, this implies a total Eligible PLC for 2015/16 of 7288 MWs. This would be over 1,000 MWs below the posted eligible PLC for 2014/15. If the above method is incorrect, how should suppliers derive an eligible PLC for 2015/16? If the above method is correct, how does the PLC drop by over 16% between 2014/15 and 2015/16?
Please note that the PLC value of 2,954.03 MW provided in AEP-Ohio’s March 23, 2015 Bidder Webcast corresponds to delivery year 2015/16 and was computed based on AEP-Ohio’s total existing Standard Service Offer (SSO) customers as of December 31, 2014. That PLC value has been verified. It is the responsibility of the bidder to interpret possible reasons for PLC changes from year to year.
04/23/2015 in Data
-
FAQ-51:
In the PLC and NSPL files in the data room, the total AEP Ohio volumes are constant for the entire period for which the date is provided. Specifically, for every single day since 6/1/14 the SOS and CRES PLCs add up to 8780MW. Can you please describe the how a supplier's PLC obligation will be impacted by customers shutting down or starting up?
An SSO Supplier is responsible for fulfilling all of the requirements of an LSE for the portion of AEP Ohio’s SSO supply that it serves, including, without limitation, energy, capacity, ancillary services, market-based transmission service (excluding NITS), and any other service as required by PJM. The total PY 2015/16 Peak Load Contribution (PLC) is calculated annually and remains unchanged until the next PJM year calculation is performed, regardless of the impact due to load growth or load reduction. Thus, changes in the daily SSO total PY 2015/16 PLC will only reflect migration to or from a CRES provider, and a change in one will always be balanced by an offsetting change in the other.
04/23/2015 in Data
< Previous | Showing 211 to 220 | Next > | << Back to FAQ Categories