A RESTful API is an application program interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data.

Representational state transfer (REST), which is used by browsers, can be thought of as the language of the Internet. Now that cloud usage is on the rise, various application programming interfaces (APIs) are emerging to expose Web services and REST is a logical choice for building APIs that allow end users to connect and interact with cloud services. RESTful APIs are used by many sites, including Google, Amazon, Twitter and LinkedIn.

A RESTful API breaks down a transaction to create a series of small modules, each of which addresses a particular underlying part of the transaction. This modularity provides developers with a lot of flexibility but can also be challenging for developers to design from scratch. Currently, the models provided by Amazon Simple Storage Service (S3), OpenStack Swift and Cloud Data Management Interface (CDMI) are most popular.

RESTful APIs explicitly take advantage of HTTP methodologies defined by the RFC 2616 protocol. They simply use "PUT" to change the state of or update a resource, which can be an object, file or block; "GET" to retrieve a resource; POST" to create that resource; and "DELETE" to remove it.

The current GADS OS software has been updated to support General Electric's Operational Excellence program data requirements and uploads that utilizes the GE RESTful APIs.

Today is June 1st and the start of the 2016 Summer Verification Test Period. The test period runs from June 1 through August 31, 2016. All units in the PJM Capacity Market must test to their Summer Installed Capacity during this time. Additionally, all units, with the exception of Hydro, Pumped Hydro and Diesel, must ambient correct their test data. Also, Hydro and Pumped Hydro units must perform their once per year test during this period.

The due date for data submission is September 30, 2016. Any generator not submitting a Summer test, without due cause, will be considered 100% forced out for the entire Summer period of June 1 through November 30, 2016.

There is no tolerance given to test results. All units must test to their exact Installed Capacity Value or greater.

When a unit fails its verification test, a derating event should be placed in GADS to cover the deficiency. If this is done by the operator, the test result and the derating amount will be added and then compared to the Total ICAP Commitment Amount. If the derating is input by PJM, only the test result will be compared to the Total ICAP Commitment Amount and could result in an ICAP Shortfall.

The rules for verification testing can be found in Manual 21 on the PJM web site under the tab Documents/Manuals.

If you have any questions or concerns, please contact one of the PJM GADS Administrators at gadssupport@pjm.com.

Starting June 1, 2016, monthly audits for compliance with PJM Manual 10 will be performed on all PJM eGADS planned and maintenance outages and deratings. 

Manual 10 “Pre-Scheduling Operations” states:

1. All planned outages and deratings must be scheduled no less than 30 days prior to the operating day in which the planned outage or derating is to commence. (Section 2.2.1)
2. All maintenance outages and deratings must be scheduled no less than 3 days prior to the operating day in which the maintenance outage or derating is to commence. (Section2.3.2) 

Please read the document on the PJM eGADS webpage entitled “Scheduled Events (Planned & Maintenance)” at this link for more detailed information: http://www.pjm.com/markets-and-operations/etools/egads.aspx 

Keep in mind that compliance is not limited to the most recent eGADS reporting month, but will typically be performed on the existing and most recent Delivery Years.