1 / 1

Large Volume Ad Hoc Usage API request

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.

chancellor-wheeler
Download Presentation

Large Volume Ad Hoc Usage API request

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 sizing has been redefined and is documented in the API guide • Summary of Changes in API Usage Request Sizing • How to Read the Table A ROR would be able to raise one of the set of requests per day: • 20 requests containing maximum 1 ESIIDs for the 365 days of data OR • 20 requests containing maximum 10 ESIIDs for the 20 days of data OR • 20 requests containing maximum 50 ESIIDs for the 5 days of data OR • 10 requests containing maximum 100 ESIIDs for 2 days of data OR • 10 requests containing maximum 200 ESIIDs for 1 day’s data. • Notes: • The maximum number of ESIIDs per request = 200. • Exceeding the parameters in the table (see table 3) may result in request being removed from queue. Notification will not be provided if this occurs. • If a ROR needs to make a large request 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. Table 3: Adhoc Meter Usage Message Sizing

More Related