TDSP Questions:
1. Do you send the same LSE usage file to the Smart Meter Texas (SMT) Portal for REP retrieval and
to ERCOT for settlement purposes?
AEP:
CenterPoint:
Oncor:
TNMP:
Yes
Yes
Yes
Yes
a. If you replace Interval Data on the SMT Portal (e.g., replacing estimated Intervals with
actuals), do you also send the same updates to ERCOT?
AEP:
CenterPoint:
Oncor:
TNMP:
Yes
Yes
Yes
Yes
b. If you replace interval data as a result of working a MarkeTrak issue (e.g. replace
estimated intervals with actuals or redistribute estimated interval values) do you send
the updates to both SMT and ERCOT?
AEP:
CenterPoint:
Oncor:
TNMP:
Yes
Yes
Yes
Yes
2. If all usage information originates from the same meter, why would an 867 for a particular
meter not always match the LSE usage for that same meter?
AEP:
There can be several reasons why the usage information that is used for billing and
intervals in the LSE do not to align. The three items below represent some cases
where AEP Texas’ billed usage may not align to the LSE data.
 Interval estimation routines may not align to register reads.
 System limitations aligning the monthly billed register read to the intervals for
the same time period, and automation of smoothing of intervals when
adjustments to billing are done.
 Service order processes may use readings at the time the action is completed
and not the midnight read.
CenterPoint:
See responses below for question 2b and matrix created by TX SET, reported to
AMWG and RMS—this is the link:
http://www.ercot.com/content/committees/board/tac/rms/amwg/keydocs/2014/07
c.(3)_20130509_TDSP_AMS_Data_Practices_Matrix_FINAL.doc
Oncor:
See responses below for question 2b
a. Approximately what percentage of 867s match the LSE data within the accepted 2
meter multiplier tolerance? Is this data monitored?
AEP:
The majority of our bills do match, but there are the scenarios
mentioned above that may create some inequities. In 2015, the
implementation of a new MDM should address most issues; others
will be addressed manually. Data is not monitored at this time. There
are plans to create reporting to identify these mismatches.
CenterPoint:
99%
Yes, through various reports that are pulled manually.
Currently CNP is working to refine reporting requirements to more
easily and quickly identify issues.
Oncor:
99.5% Not on a regular basis
TNMP:
Unknown. Not currently measured.
b. What are the known mismatch scenarios?
AEP:
See answer to Question 2 above.
CenterPoint:
 Tampering – Approximately 1- week delay in making the appropriate
corrections.
 Switch Meters – Approximately 1-week delay in making the appropriate
corrections
 Power Outage – Estimate(s) are created based upon historical consumption
values. Once Power On is indicated at the meter an automated meter
interrogation signal will be sent to the AMS meter to retrieve actual interval
data replacing estimated values where applicable.
 Using a non-midnight register read
Oncor:





Tampering
meter exchange errors
using a non-midnight register read
delay in changing REP of Record within the back office systems after a switch
an estimated register read is used for 867/810 billing and the MDM
subsequently updates that cycle day’s estimated read when an actual register
read is received for a later day
TNMP:
 Tamper – TNMP does not go back and adjust interval data/register reads in
the MDM when tampering is discovered. This is basically true for most
cancel/rebill scenarios, in that the MDMS data is not adjusted.
 Power Outages – TNMP will currently run VEE against meters that are involved
in a power outage.
 Meter Changeouts – ending register read is obtained and entered into CIS, but
interval data not currently being reflected in the MDMS.
3. Do you maintain metrics associated with MDM/AMS system outages (planned and unplanned)?
AEP:
No
CenterPoint:
No, this would not be prudent use of reporting, our resources and/or systems since
our automated systems always go back to collect any day’s missing interval data that
occurred during the unplanned or planned outage periods of time. For example:
1. CenterPoint Energy’s Unplanned Outage occurred last week on Monday, June
16, 2014- Wednesday, June 18, 2014
a. (Note: June 16-19, 2014 there were a total of 8 Market Notices and 2
Market Calls communicated during this 4 day period):
2. LSE files for June 16, 2014 Monday’s usage were delivered the afternoon of
Wednesday, June 18, 2014 to both ERCOT and SMT.
3. LSE files for June 17, 2014 Tuesday’s usage were also delivered the afternoon
of Wednesday, June 18, 2014 to both ERCOT and SMT.
4. LSE files for June 18, 2014 Wednesday’s usage were delivered during its
normal timeline since systems were restored to normal operations at this
point.
Also, for each day throughout this unplanned outage and multiple times throughout
the day Market Notices were communicated to RMS listserv and CNP’s Competitive
Retailer contacts. CNP provides market notices to these same contacts for both
planned and unplanned outages, however, if there is a problem with this
communication method CNP would like to be notified of the problem so we may
evaluate if changes are necessary.
Note: All of CNP’s AMS meters have internal functionality that allows the meter to
store daily 15-minute interval data for current and prior 365 days.
Oncor:
No
TNMP:
No metrics are maintained, but Market Notices are sent in accordance
with standard communication protocol.
a. Could you track the number of system outages that impact LSE data delivery? Why or
why not?
AEP:
CenterPoint:
Oncor:
TNMP:
Yes
Refer to our response in Question 3 above
Yes – for outages that delay sending the data beyond 11:00 PM
Yes, we could, but we don’t currently do it.
b. Could you provide a snapshot at the workshop of how many outages (planned or
unplanned) you had in April and May that impacted timely delivery of a significant
amount of LSE data (i.e. 5% or more)?
AEP:
CenterPoint:
Oncor:
TNMP
Yes
Refer to our response in Question 3 above
0
Not at this time
c. Can there be a report to quantify the impact of outages?
i. For example; “June had 4 outages that lasted 5 days that impacted 800k ESI IDs”
AEP:
AEP does not currently have a report.
CenterPoint:
Refer to our response in Question 3 above
Oncor:
Oncor can provide a quarterly report of how many LSE file delivery
delays occurred and which days were affected during the quarter.
Oncor does already send market notices if LSE files will be delayed
past 11:00 PM.
TNMP:
Yes, but not currently being done.
4. Do you have validations for extreme high/low LSE interval data? What are the thresholds for
validation? What level validations are in place? Individual intervals, daily sum, monthly sum?
AEP:
AEP Texas has validations in multiple systems that are validated either
monthly or daily. We are continually improving our validation
processes as new conditions present themselves, and as we learn
more about the data.
 Daily usage alert on commercial meters (Head End)
 Spike Check on commercial meters
 Negative consumption
 Estimated Intervals greater than 250kwh
 Time Check of meter reading device / system
 Time Check of meter
 Reverse Energy
 Test Mode
 Meter Identification Check
 Sum Check – Customized routine in place, a more robust
validation in new MDM
 Zero consumption - Resolved at monthly billing
 Usage on inactive meters - Resolved at monthly billing
 Memory issues (Intervals/RR)
AEP Texas does have an interval sum check on the days that we have a
register read and intervals for the same time period. This is performed
daily.
CenterPoint:
Yes. The thresholds for validation are comparable to Premises’
historical usage values. Validations are in place for all intervals, daily
and monthly sums.
Oncor:
See Appendix A for Oncor’s VEE process (excerpt from the Uniform
Business Practice “Validating, Editing, And [SIC] Estimating (VEE)
Interval Data”)
TNMP:
*** All VEE logic is planned for review and subject to change. The
following represents as-is. ***
 Validation – there are numerous data quality checks that occur in
either the MDMS or in our CIS, but they can be summarized as
follows:
o Usage High (300% of historical like day)

o Usage Low (35% of historical like day)
o Usage on Inactive Meter
o No Usage on Active Meter
o Interval Counts
o Sum Check (in process, not yet deployed)
Estimation Algorithms
o Linear Interpolation
o Two week like days historical
o Historical
5. What known AMS Interval Data issues are you working on or have plans to fix?
a. For example: Oncor gap retrieval, AEP sum check, usage estimation method during
outages, meter data that spans a meter exchange
AEP:
 Implementation of new MDM will provide more robust validation on the interval
data including enhanced estimation processes to align the daily register read to
the interval data.
 AEP Texas plans to utilize meter event, interval status codes, and the identification
of circuit information in our estimation processes. The following are a few other
items we will be addressing in exception processing.
• Consecutive days with zero consumption (daily instead of monthly)
• No register reads received/No Intervals received after consecutive days
• Interval Gap recovery from the head end system to be turned on after tested.
CenterPoint:
Estimated usage is performed throughout a power outage for an AMS meter. CNP is
currently testing a custom enhancement to estimations during an outage which is
anticipated to be implemented by the end of 2014.
Oncor:
 Limited gap retrieval was implemented on June 9, 2014; Oncor is
implementing its functionality in stages over the next few months.
 Oncor is reviewing our meter exchange processes.
 Oncor is reviewing data processing associated with switches and the timing of
the REP of Record changes within the back office system synch processes.
TNMP:
 Interval data gaps due to meter changeouts
 VEE during power outages
 Smooth interval data/register reads in the MDM for cancel/rebill activity
6. How does the VEE process impact interval data during power outages and DR events?
AEP:
Currently our MDM is not aware of an outage at a meter level, although, AEP Texas will
provide zeroes to market for known large outages. Future plans will include meter and
interval status codes to aid in the estimation processes if received at the meter level. In
addition, circuit information will be available to estimate in large areas.
CenterPoint:
CNP understood DR to be Disaster Recovery events– if so see responses to question 3 (power
outage response) and question 5 (AMS Interval Data issues working on) provided by CNP
above.
Oncor:
When a power outage prevents the transmittal of data from the meter to the data
center, Oncor will estimate the consumption. Oncor utilizes its Meter Data
Management System (MDMS) to perform estimation routines related to register reads
and 15-minute interval usage data during periods of time in which this information
was not received as part of the daily meter reading processes.



Residential consumption (kWh) data will be estimated based on a prioritized set of
rules including a customer’s historical data (i.e., same day or like day), ERCOT load
profile data so that all (96) 15-minute intervals have a value when reported to
ERCOT for settlement purposes. The ERCOT load profile will take priority over
same day or like day data for estimating residential customer intervals.
Non-residential consumption (kWh) data will also be estimated based on a
prioritized set of rules including a customer’s historical data (i.e., same day or like
day), ERCOT load profile data so that all (96) 15-minute intervals have a value
when reported to ERCOT for settlement purposes. For non-residential customers,
the intervals are shaped for the day’s total kWh based on same day data.
Oncor recently implemented gap retrieval. While it is currently in the stabilization
and rollout phase, once fully implemented, it will be able to go back and retrieve
several days of actual usage once communication is restored, and the actual usage
will go through the VEE process and then replace the estimated data.
TNMP:

No impact on DR events (assuming Demand Response), as power is still supplied to
the meter and communication is assumed.

During power outages, VEE will occur and estimates will be loaded into the MDM and
subsequently sent to SMT. In the future, TNMP intends to prevent VEE from executing
on meters where outages have occurred.
Appendix A