PFAM Working Group

PFAM Working Group February 22, 2012 Meeting Summary

PFAM Working Group Meeting Summary

Meeting Date Wednesday, February 22, 2012 Time 10 a.m. to 12:30 p.m.

Location Teleconference Facilitator AUC staff

1 Introductions: Name Company Mike Choboter AESO Juanito De Jesus ATCO Electric Enrique Nino ATCO Electric Anne Glass AUC Maria Baitoiu AUC Will Chow AUC Lori Harnack Cognera Corp. Marcelo Maciel Direct Energy Trevor Martin Direct Energy Brian Neufeld ENMAX Encompass Yvonne Dickson ENMAX Power Leo Scarcelli ENMAX Power Lisa Zuger EPCOR Distribution & Transmission Inc. Joel Milne-Epp EPCOR Energy Alberta Inc. Angela Corsi FortisAlberta Inc. Tina Dulguerov FortisAlberta Inc. Ngan Duong Just Energy Misti Jeter ista North America

2 Definition for each of the following adjustment reason codes (as found in the AUC Rule 021: Settlement System Code): The scope of the meeting is to standardize the PFAM reason codes used for the RSA transactions and to provide a clear description for each of the reason codes. 2000 – Meter read obtained after final settlement The majority of distributors use this reason code for cases when estimate meter reads are used for the final settlement and an actual read comes in after. This relates only to cumulative meters. The group discussed under what reason code should customer-phone-in reads be placed if they are used for final settlement, but a corrected read comes in after. The group agreed that this should be reflected under the meter read error reason code (2005). For interval meters, DIM transactions are generated for both actual and estimated meter reads. One retailer suggested that, for situations where a corrected DIM is issued after final, reason code 2005 should always be used, regardless of whether the DIM was an actual or an estimate. Given this, it would be hard to see the reason code 2000 for interval meters.

Disposition: Final Page 1 of 3 PFAM Working Group February 22, 2012 Meeting Summary

One concern was raised regarding the use of multiple reason codes for a PFAM. The group agreed that only one reason code should be used for all records in an RSA set and that the reason should be the most relevant one at the time the data is replaced. The group agreed with the following description for the 2000 reason code: The code should be used for cumulative meters only for cases where a WSD marked as an estimate is produced at final and a read is obtained after the final. 2001 – Meter multiplier error This reason code should apply to corrections for PT, CT or meter multipliers errors (i.e. for when the information regarding PT, CT or meter multiplier is wrong, and not for when their physical characteristics have changed). 2002 – Crossed meter The group discussed whether address errors should be considered under this reason code or not. The group agreed that address errors should be included along with physical changes under this reason code and these situations should be reflected in the definition wording. 2003 – Apparatus or meter malfunction The group discussed whether to use this code for meter data management system errors as well problems with the physical meters (other than the ones regarding crossed meter errors, meter multiplier and meter read errors). Further suggestions were made to change the definition for the metering system to include the software related to the meter data collection and then errors pertaining to the metering system should be under 2003 reason code. But as one party mentioned, this would not deal with calculation and communication errors. Another suggestion was to put this under the calculation error reason code (2008), but retailers want that code to be specifically for load settlement calculation errors and not to include meter data calculation errors. To depict all the situations it was agreed that the PFAM reason code name be changed to: meter hardware or software malfunctions. Also, the description should make it clear that load settlement software is not included, but rather it deals with any kind of errors regarding the physical characteristics of a meter or the meter data management system, excluding crossed meter, meter multiplier and meter read errors. 2004 – Theft or meter bypass It was clarified that this code would be used only for cases where theft was identified after final settlement. 2005 – Meter read error As determined in the discussion for reason code 2000, the customer-phone-in reads that are later corrected after final, should use the code 2005. Also, the group agreed that the description should clarify that this code should be used in situations where replacement DCMs and DIMs are sent after final. 2006 – Connection error Some parties use this for physical connection problems and some use it for when there is disagreement between energize and de-energize status resulting in volumes being allocated incorrectly. The group agreed that the physical connection errors should be part of reason code 2003 and the code 2006 should involve only errors from misinformation in the system regarding status. The group also agreed to change the name to better reflect this to: Energize and de-energize status error. 2007 – Enrolment error The group agreed that this error code should be used for situations where an incorrect retailer of record is assigned to a site for a period that was already final settled. One party suggested that there are also situations when there is no retailer of record assigned to a site and this should be included under this code. The group discussed that this would be more of a connection error as the enrolment is not made to the wrong retailer, but is not made at all. The group agreed that for this situation parties should use the 2006 reason code. 2008 – Calculation error The group agreed that the definition of the reason code should clarify that this code deals with errors from calculations in the settlement systems, including profiling class errors.

Disposition: Final Page 2 of 3 PFAM Working Group February 22, 2012 Meeting Summary

3 Other discussion issues: One party raised the concern that changes from Measurement Canada could lead to the need of having new reason codes for PFAMs. It was discussed that until the implementation of Measurement Canada changes, the reason codes should not be modified and that errors that might result from these changes would probably be classified under reason code 2003. Discussion arose regarding adding an Other reason code for situations that are not identified under any of the nine existing codes. One party suggested that as long as it is defined when should it be used, it would help them in validating the information for those situation not captured by the defined codes. After some discussion, the group agreed that there is no need for adding the extra code, and it was suggested that if new situations arise that are not reflected in the existing codes, the party indentifying those should put them through the RIM system for comments. The AUC asked the present parties to go back and look over their PFAM history or to think of other situations that are not covered under the existing reason codes and to please notify us, so that the definitions can be revise accordingly. ACTION: Parties to identify any situations that do not fit into the current reason codes description and to notify us.

Disposition: Final Page 3 of 3