amit update to rms may 16, 2012 andrea o’flaherty smt project manager

AMIT Update to RMS

May 16, 2012

Andrea O’FlahertySMT Project Manager

Overview & Contents

Schedule Update Large Volume Ad Hoc Usage API

Request Third Party

2AMIT Update to RMS - May 2012

Schedule Update

AMIT Monthly Stakeholder Steering Committee Meeting for May is canceled

Monthly Stakeholder Steering Committee Meetings will be held following RMS Lunch Break – Beginning in June

Schedule is updated and is found online at:http://www.puc.state.tx.us/industry/projects/

electric/34610/34610.aspx

AMIT Update to RMS - May 2012 3

Large Volume Ad Hoc Usage API Request Background

The intended use of the Adhoc APIs is to retrieve the usage data from SMT for a specific set of ESIIDs for certain duration. This data is provided in CSV format.

The vehicle for building history is the LSE usage files sent daily via FTP for all the ESIIDs belonging to each ROR.

Recently there have been multiple requests to backfill the entire historical data for all the ESIIDs by a few RORs.

Large requests, using the previous API sizing, have been observed impacting system performance.

The API Usage request/call sizing has been redefined and is documented in the API guide



Large Volume Ad Hoc Usage API Request

Number of ESIIDs(per API Call)

Number of days (per API Call)

Number of API calls per day

Max EstimatedResponse Time

per API Call

1 365 20 24 hours

10 20 20 24 hours

50 4 20 24 hours

100 2 10 24 hours

200 1 10 24 hours

How to Read the Table:A ROR would be able to raise one of the set of calls per day:

• 20 calls containing maximum 1 ESIIDs for the 365 days of data OR

• 20 calls containing maximum 10 ESIIDs for the 20 days of data OR

• 20 calls containing maximum 50 ESIIDs for the 5 days of data OR• 10 calls containing maximum 100 ESIIDs for 2 days of data OR• 10 calls containing maximum 200 ESIIDs for 1 day’s data

Large Volume Ad Hoc Usage API Request

Notes: The maximum number of ESIIDs per call = 200. Exceeding the parameters in the table (see table 3) may

result in call being removed from queue. Notification will not be provided if this occurs.

If a ROR needs to make a large call for historical data that exceeds the above guidelines, it needs to submit a change request with AMIT at http://www.puc.state.tx.us/industry/projects/electric/34610/34610.aspx.

Send to the Smart Meter Texas JDOA PM for the request to be considered.


PWG Focus – Remaining SMT BRs

This includes (in no special order): On Demand Request* Enhanced Email Format Third Party One-Time

LOAs SMT Mobile Application HAN Status Report Consumer Green Button

Federation Content Management

Approaches & News Flash, FAQ, Twitter

Meter Exchange Email Ad Hoc Report Generation

Header HAN Status TDSP De-

Provisioning with Reason Code

On Demand Power Status


* CNP supports ODR for REPs today

Remaining SMT BRs Timeline

Story Boards - May and June Prioritization - June, July Estimation – June, July Re-Prioritization as Necessary – July Scheduling for Development and Deployment

– June, July Design, Build, and Deploy – June – December


Projects Working Group

Holding Web Ex Meetings every Friday from 9-11:00 am

Purpose of the meetings is to work through BRs and Storyboards – finalize, send to Stakeholder Steering for approval

Will be holding a one-day special Third Party Workshop on May 22, 2012 @ ERCOT



?

amit update to rms may 16, 2012 andrea o’flaherty smt project manager

Documents