Markets & Operations

eGADS Release Notes

System Requirements

App Version 4.5.1 / DB Version 4.1.1

Release Dates

Training: 1.25.2024
Production: 1.25.2024

About This Release

  1. Vendor fix for a defect where the Card97 time zone designation issue when the event start or end date is within the hour of Fall Daylight Savings hour between 1 to 2 am.
  2. Vendor fix for a defect on the net capacity verification screen where the Corrected Net Capacity was not auto-calculated.
  3. 2024 NERC-compliance update to include a new item in the CARD97 event data: Contributing Operating Condition.
  4. Vendor fix: The PJM Card 97 Event Legacy Format has been updated to transmit and receive the new Contributing Operating Condition Code.
  5. Vendor fix: The PJM Event CSV Format has been updated to receive the new Contributing Operating Condition Code.
  6. Vendor fix: In the Net Capacity Verification Test module, we have modified the program to stop creating Test Index -1 for Hydro and Pump-Storage units. Hydro and Pump-Storage units are treated like any other units: that is, there can only be one In-Period test with Test Index=1. All other Out-Period tests must have test index 2 and above. There is still one exception applied to HD and PS units. Their capacity test can occur before the Season starts. This is due to the fact that many rivers could be frozen between December and February and testing is not possible

More Information

NERC has requested a new data item to be added to the Event Data (Card 97). This is effective as of January 2024. The new data item is called Contributing Operating Condition.

eGADS has been updated to allow the users to select the new Contributing Operating Condition code on the Event data entry screen. Whenever a new event is created, this new code must be selected after 2023. To facilitate the data entry process, the “0 – No Contributing Condition” is filled in by default. The user can click on the down arrow icon of the dropdown list-box to select other valid codes.

Previous Releases

 Version 4

Release Dates
Production: 12.4.2023

Below is a list of frequently asked questions related to the eGADS integration with the Account Manager tool. If you have a question that has not been covered below, please consult the Account Manager Quick Guides on the Account Manager page of or contact

  1. What is eGADS
    • The Generator Availability Data System (eGADS) supports the submission and processing of generator outage and performance data as required by PJM and North American Electric Reliability Corporation (NERC) reporting standards.
  2. What is changing with the eGADs log-in and user account creation process?
    • User accounts will be managed within the Account Manager tool.
    • User authentication will take place through Single Sign On (SSO)
  3. What is Account Manager?
    • Account Manager is the tool used by PJM to provide companies and their users access to PJM Tools.
  4. How do I access the Account Manager Application?
    • The Account Manager application can be accessed via PJM Tools, or by following the Sign In or Register links on the PJM Tools - Account Manager Page.
  5. What functionality exists in Account Manager?
    • Accounts are established for companies and provisioned tool access by the PJM Account Administrator.
    • Company Account Managers (CAMs) can create, manage, and terminate user accounts and provision or revoke access to the tools available in their company account(s)
      • CAMs can lock and unlock user accounts as necessary, and reset passwords for the users associated with their company account.
    • Tool users can request access to tools, view their CAMs, and update their user profiles as necessary.
  6. What are the username and password requirements for Account Manager?
    • Usernames must be between 6 and 12 characters. The first character cannot be a special character. The following special characters are allowed: ()!$~`^_{}.
    • Passwords must meet the following criteria:
      • Password must be between 10-16 characters.
      • Passwords must, at a minimum, contain one uppercase letter, one lowercase letter, one number, and one special character (only: ()!$`~:.,<>=?^_{}[]|)
      • Password cannot contain username, first name, last name, company name.
      • Password cannot be changed more than 5 times in a single day.
      • Passwords must be different than previous 15 passwords.
    • Passwords expire on all user accounts every 127 days and must be changed. Failure to change a password will result in the locking of the user account. Once locked, a CAM must unlock the account.
    • If forgotten, the user may utilize the Forgot Password feature to reset their own password.
      • Providing invalid security answers when using the Forgot Password feature will lock the user account after 4 consecutive attempts.
    • Initial password requests and password changes will need to be completed within 4 hours of receiving a unique password link via email.
    • Automatic logout for sessions that are inactive for 15 minutes.
  7. How do I gain access to the eGADS tool?
    • You must submit the eGADS User Registration Form.
    • To gain access to eGADs through Account Manager, you must set up or have an existing user account. The link to register for a user account can be found on the Account Manager page on listed in question 4.
    • Once the user account is set up, you can request access to eGADs by selecting eGADS read only or eGADS read/write.
    • Your company CAM can approve your access request.
  8. Which access role should I request?
    • Users should request eGADS read only if they have no need to enter data. All other users should request eGADS read/write. Access to individual units will be configured within the eGADS system.
  9. How should I register if I need access to multiple companies/units?
    • Users should register for each individual company using the SUMA feature in Account Manager. You will need to notify PJM of the primary account so this can be linked in eGADS.
  10. Which browsers are supported by the Account Manager tool?
  11. Do I need a PKI certificate?
    • No, you do not need to use a PKI certificate for eGADS.
  12. Will PJM be contact current users, CAMs, or both?
    • PJM will be reaching out to current eGADS users and to CAMs.
      • We will be using the eGADS mailing list to contact current eGADS users with instructions on how to start using the new system, information about the cutover date, and requests for information we will need to link your Account Manager account with your existing eGADS account.
      • We will be reaching out to CAMs with details on the new access permissions.
  13. Are eGADS CAMs separate CAMs?
    • Existing CAMs will be eGADS CAMs. eGADS will be available as another access permission and will be handled by a company CAM.
  14. Do CAMs need to be set up as eGADS CAMs?
    • The eGADS access permission will be handled by CAMs in the same way other access permissions are handled currently.
  15. As a current CAM, I’m not currently seeing eGADS access as an option.
    • The eGADS access permission is being provisioned in the near future. It is not currently available and is not yet visible to CAMs.
  16. How do I become an eGADS CAM using my current Account Manager account?
    • No action is needed on your part. You will be able to handle the eGADS permission when it is provisioned, and all activities will be the same as for other Account Manager access permissions.

 Version 3.60.1

Release Dates
Training: 2.7.2023
Production: 2.7.2023

About This Release

Minor database upgrade to 3.60.1.

New Features

Vendor fix for a defect when evaluating cross-year “PE” and “ME” events submitted by the utility users using the 05-07 NERC format.

The NERC reporting format has a rule that says if an event crosses from one year into the next, the submission file must break the event into two so that the first event ends on 12/31 2400 in the first year and starts again in next year’s submission file as 01/01 0000. Most utility clients use the NERC 05-07 file format and break up the on-going events between years into two events.

Normally this is not a problem. For example, if an RS event crosses into the next year, it becomes an RS event that ends on 12/31 2400 and another RS event that starts again on 01/01 0000. For Full Outages such as U1, MO, PO or any derate event, there is also no problem because eGADS recognizes the cross-year events and allows for exceptions. eGADS knows that these are really one event instead of two and will not increase the count of Number of Outages.

However, we overlooked the PE and ME events. For example if the user submits a cross-year PE event between 2021 and 2022, the first piece of the event would have ended in 1/1/2022 00:00. When they try to submit the second piece of the event eGADS will throw an error because the second piece of the event started on 1/1/2022 00:00 with the same event type PE. There is a NERC rule that says a PE event cannot immediately fallow’s another PE event.

This release fixes this problem by recognizing the exception of the cross-year and will not throw an error.

 Version 3.12.3

Release Dates
Training: 5.5.2020
Production: 5.5.2020

About This Release

Minor version upgrade to 3.12.3.

New Features

The cause codes are updated as per NERC’s 2020 Cause Code spreadsheet published in the NERC website. The Overlapping De-rate logic has been updated to allow a de-rate to start with more available capacity than another overlapping that started earlier. The Verification Test System has been updated with new data tracking points as per PJM specifications.

User Guide PDF

App Version 3.13.1

Release Dates
Training: 3.22.2022
Production: 3.22.2022

About This Release

Minor app version upgrade to 3.13.1.

New Features

JAVA Certificate Renewal.

DB Version 3.19.1

Release Dates
Training: 5.25.2021
Production: 5.25.2021

About This Release

Minor database upgrade to 3.19.1.

New Features
  • NERC added 4 new Cause Codes:
    • 9138, High Water Level in Tailrace (too much water), to be used by Hydro Units:
    • 5792, Engine Overspeed Trip, to be used by Diesel/ Internal Combustion Engine Units
    • 5692, Turbine Overspeed Trip Test - Jet Engine, to be used by CT and CC Units
    • 5292, Turbine Overspeed Trip Test - Gas Turbine, to be used by CT and CC Units
  • The Ad-Hoc Report has been enhanced to allow retired units to be included in the report as long as the retired unit was in commission during part of the report period.