Advanced Metering AMS Attribute/Indicator Solution Discussion

1. Advanced MeteringAMS Attribute/Indicator Solution Discussion Jackie Ashbaugh ERCOT PWG/TX SET Working Groups Joint Discussion

2. TX SET Solution Discussion • AMIT Business Requirements: • BR001 • Ability for the TDSP to notify ERCOT and REP of Record via an automated transaction that an ESIID has a provisioned advanced meter • Note: This will apply to the backlog of meters that have already been provisioned as well as meters that get provisioned going forward • Possible Solutions: Indicate the presence of an AMS meter on an 814_20 • BR001.01 • Ability for the TDSP enrollment responses to indicate the presence of an AMS meter • BR001.02 • Ability to indicate on monthly usage transaction that the meter is an AMS meter • Possible Solution – REQUIRES TX SET change • In order to meet these requirements TX SET recommendation is to add AMS_ in front of the existing meter types in the REF~MT segment (example: AMS_K1, AMS_COMBO). This would be passed in the following transactions: • 814_04 • 814_05 • 814_14 • 814_20 • 814_22 • 867_03 monthly Note: ERCOT does not need to store the AMS meter type for settlement purposes. If the AMS meter type is passed on the 867_03/F, ERCOT has the ability to filter out non-settlement NIDR data from loading into the settlement system. PWG/TX Set Working Groups Joint Discussion

3. TX SET Solution Discussion • AMIT Business Requirement • BR-008 • Ability to perform real-time enrollment switching for AMS meters • Possible Solution – REQUIRES TX SET change • In the TX SET sub team meeting there was discussion to allow customers with AMS meters to call a CR today and the customer be switched today and have non AMS meters continue as they do today with First Available Switch Date. • In order to meet this requirement, ERCOT must be able to determine if a meter is an AMS meter. PWG/TX Set Working Groups Joint Discussion

4. Retail Market Interface Discussion • AMIT Business Requirement • BR002 • Ability for any REP to identify whether any ESIID has an AMS meter or not on an on demand on going basis • Possible Solution – REQUIRES TX SET change or Profile Code change • Ability for ERCOT to display AMS meter indicator in the TDSP ESIID extracts and on the TML. • In order to meet this requirement, ERCOT must be able to determine if a meter is an AMS meter. Note: ERCOT does not need to store the AMS meter type for settlement purposes. If the AMS meter type is passed on the 867_03/F, ERCOT has the ability to filter out non-settlement NIDR data from loading into the settlement system. PWG/TX Set Working Groups Joint Discussion

5. Retail Market Interface Discussion – cont’d • Possible Solution – TX SET change • All MPs must make change to include AMS meter type attribute/indicator in the 814 and 867 transaction series • Could be maintained by 814_20 • Could be used by ERCOT on 867_03/F to filter out non-settlement NIDR data from loading into the settlement system • ERCOT would store the attribute/indicator for display to MPs • Possible Solution - Profile Code change • No transaction change needed • Could use the Meter Data Type field (NIDR/IDR/AMS) as the attribute/indicator • ERCOT would store the Profile Code and use the Meter Data Type field to interpret AMS/non-AMS for display to MPs Note: ERCOT does not need to store the AMS meter type for settlement purposes. If the AMS meter type is passed on the 867_03/F, ERCOT has the ability to filter out non-settlement NIDR data from loading into the settlement system. PWG/TX Set Working Groups Joint Discussion

6. PWG/TX Set Joint Discussion • PROS • CONS PWG/TX Set Working Groups Joint Discussion

7. QUESTIONS? PWG/TX Set Working Groups Joint Discussion