GADS Open-Source Alternatives: Ultimate Guide for Generator Owners and
Operators
After more than 35 years, GADS Open Source is being officially retired. The
software that started life
in 1986 as MicroGADS, running on an IBM PC/XT under MS-DOS with data submitted
to NERC on
magnetic tape, grew into a tool used by generator owners and operators across
North America. For a
long time, it did exactly what it needed to do.
But the world of NERC GADS reporting has changed considerably. Annual DRI
updates, mandatory
Contributing Operating Condition fields, expanded design data requirements,
renewable unit
reporting, ISO connectivity, and tighter edit validation have all raised the bar
for what GADS software
needs to deliver. The discontinuation notice is also an opportunity to evaluate
what the current
generation of GADS reporting software actually looks like and what utilities are
choosing to replace it.
What Generator Owners and Operators Need from GADS Software
Before evaluating any replacement, it helps to be clear on what the job actually
requires. A GADS
reporting solution in 2026 needs to handle a much wider scope than data entry
and file submission.
Here is what a capable replacement should cover:
Conventional Unit Event and Performance Reporting
The core requirement has not changed. Any replacement must support all event
classifications
defined in the NERC DRI, including outages (U1, U2, U3, PO, MO, SF, and their
extensions),
deratings (D1 through D4, PD, and their extensions), reserve shutdowns, and
non-curtailing events.
Performance reporting must cover all six sections of the 05 format, including
unit time information,
generation performance, starting characteristics, and fuel data. Quarterly
submission to OATI webE-GADS
within the 45-day window is the delivery mechanism, and the replacement software
should
make that process straightforward.
Annual Cause Code and DRI Updates
NERC updates the Data Reporting Instructions every year. Cause code databases
change. New
contributing operating condition codes are added. Amplification code
requirements are clarified. A
replacement that does not keep pace with these updates will fail GADS edit
checks. Look for a
solution that publishes updates within a few weeks of each new DRI release
rather than leaving your
team to manually track changes.
Pre-Submission Edit Validation
NERC's edit rules catch logical errors before they become rejected submissions:
outage hours exceeding period
hours, missing amplification codes on U1 events, inconsistencies between event
and performance data. Strong
validation during data entry, before the file ever reaches webE-GADS, is one of
the most practical things any
GADS software can offer. Teams that have relied on submitting and then reacting
to rejection notices will quickly
appreciate how much time pre-submission checking saves.
Design Data Management
Since 2024, NERC has required additional design data fields beyond the original
nine, covering fossil steam, gas
turbine, combined cycle, hydro, internal combustion, and fluidized bed units.
The 2026 DRI formalizes an annual
review expectation. Replacement software should store and manage all required
design data fields and make it
easy to update unit configuration records without starting from scratch each
year.
Combined Cycle and Co-generation Block Reporting
Combined cycle and co-generation units require block-level reporting that
synthesizes individual gas turbine
and steam turbine unit events into block-level availability data. The DRI
defines two acceptable methods for this:
the Synthesis Event and Performance Method (Appendix L1) and the Fleet-type
Roll-up Method (Appendix L2). A
replacement that handles this automatically, rather than requiring manual
calculation, will reduce both the time
burden and the risk of errors for plants with complex unit configurations.
Renewable Unit Support
Solar and wind GADS reporting operates under a separate set of requirements from
conventional units. As
renewable portfolios have grown, the manual workload for classifying inverter
and turbine-level faults,
distinguishing equipment failures from weather-related derates, and producing
unit-level NERC events has
become a significant burden for compliance teams. Any GADS OS alternative
evaluated in 2026 should be
assessed for renewable capability, not just conventional fossil unit support.
ISO and RTO Integration
Most generator operators participate in one or more ISO or RTO markets. GADS
reporting does not happen in
isolation from those market obligations. Software that connects directly to
dispatch instructions, real-time outage
notifications, and ISO reporting portals reduces the manual coordination that
otherwise falls to operations staff. If
your facility reports to NYISO, PJM, MISO, SPP, CAISO, or another regional
operator, check whether the
replacement handles those regional reporting requirements out of the box.
Audit Trail and Revision Tracking
NERC GADS data is auditable. The DRI's report revision code system exists for a
reason. Any replacement
should maintain a complete history of original submissions and subsequent
revisions, making it possible to
demonstrate compliance with confidence if your data is ever reviewed.
What the Feature Checklist Looks Like
Use this as a starting framework when evaluating any GADS OS replacement:
Feature
What to Expect From Any Replacement
Event and Performance Reporting
Support for all conventional unit types, all event
classifications, and quarterly submission to webE-GADS
Annual DRI Updates
Cause code database updated within weeks of each new NERC DRI
release
Edit Validation
Pre-submission error checking that mirrors NERC edit rules to
prevent rejected files
Design Data Management
Fields for all nine required design data elements plus the
expanded unit-type-specific fields added since 2024
Contributing Operating Condition
Required COC field on every event record, with code validation
and description guidance
Combined Cycle and Co-gen Support
Block-level reporting using synthesis event method or fleet-type
rollup as defined in DRI Appendix L
Renewable Unit Support
Solar and wind GADS event reporting, separate from conventional
fossil and hydro units
Performance Calculations
Automated equivalent hour calculations and availability factor
reporting
Audit Trail
Full revision history and report revision code tracking for
every event and performance record submitted
ISO/RTO Integration
Direct connection to OATI webE-GADS submission portal and
compatibility with regional ISO requirements
What Transition Looks Like in Practice
The most common concern when moving off any long-standing GADS software is
historical data.
Years of event records, performance reports, and unit design data represent a
significant body of
work, and losing access to that history is a legitimate risk. When evaluating
replacements, ask
specifically about data migration support: whether the vendor will assist with
importing historical
records, how existing unit configurations transfer over, and what the typical
timeline looks like
from contract to live submission.
Staff training is the other variable. Personnel who have been entering GADS data
the same way
for years will need time to get comfortable with a new interface. Early
transitions, before a
deadline is pressing, give your team room to learn the new system on real data
without the
pressure of a quarterly submission window bearing down on them. That is exactly
the logic
behind announcing the GADS OS retirement as early as possible.
What Utilities Are Choosing?
For generator owners and operators looking for a direct replacement that goes
well beyond what
GADS Open Source offered, PowerGADS from Integ has become the
most widely used
GADS reporting platform in North America. According to Integ, 70% of all
generating units in the
United States are now reported using their software, and the platform serves as
the GADS
solution for most ISOs and RTOs.
PowerGADS is part of the broader PowerSuite platform from Integ, which also
covers outage
planning and management, NERC standards compliance workflows, and utility
analytics.
If you are transitioning away from GADS Open Source and want to understand what
PowerGADS looks like for your specific unit types and reporting setup, you can
request a demo
or contact us directly.
After more than 35 years, GADS Open Source is being officially retired. The software that started life in 1986 as MicroGADS, running on an IBM PC/XT under MS-DOS with data submitted to NERC on magnetic tape, grew into a tool used by generator owners and operators across North America. For a long time, it did exactly what it needed to do.
But the world of NERC GADS reporting has changed considerably. Annual DRI updates, mandatory Contributing Operating Condition fields, expanded design data requirements, renewable unit reporting, ISO connectivity, and tighter edit validation have all raised the bar for what GADS software needs to deliver. The discontinuation notice is also an opportunity to evaluate what the current generation of GADS reporting software actually looks like and what utilities are choosing to replace it.
What Generator Owners and Operators Need from GADS Software
Before evaluating any replacement, it helps to be clear on what the job actually requires. A GADS reporting solution in 2026 needs to handle a much wider scope than data entry and file submission. Here is what a capable replacement should cover:
Conventional Unit Event and Performance Reporting
The core requirement has not changed. Any replacement must support all event classifications defined in the NERC DRI, including outages (U1, U2, U3, PO, MO, SF, and their extensions), deratings (D1 through D4, PD, and their extensions), reserve shutdowns, and non-curtailing events. Performance reporting must cover all six sections of the 05 format, including unit time information, generation performance, starting characteristics, and fuel data. Quarterly submission to OATI webE-GADS within the 45-day window is the delivery mechanism, and the replacement software should make that process straightforward.
Annual Cause Code and DRI Updates
NERC updates the Data Reporting Instructions every year. Cause code databases change. New contributing operating condition codes are added. Amplification code requirements are clarified. A replacement that does not keep pace with these updates will fail GADS edit checks. Look for a solution that publishes updates within a few weeks of each new DRI release rather than leaving your team to manually track changes.
Pre-Submission Edit Validation
NERC's edit rules catch logical errors before they become rejected submissions: outage hours exceeding period hours, missing amplification codes on U1 events, inconsistencies between event and performance data. Strong validation during data entry, before the file ever reaches webE-GADS, is one of the most practical things any GADS software can offer. Teams that have relied on submitting and then reacting to rejection notices will quickly appreciate how much time pre-submission checking saves.
Design Data Management
Since 2024, NERC has required additional design data fields beyond the original nine, covering fossil steam, gas turbine, combined cycle, hydro, internal combustion, and fluidized bed units. The 2026 DRI formalizes an annual review expectation. Replacement software should store and manage all required design data fields and make it easy to update unit configuration records without starting from scratch each year.
Combined Cycle and Co-generation Block Reporting
Combined cycle and co-generation units require block-level reporting that synthesizes individual gas turbine and steam turbine unit events into block-level availability data. The DRI defines two acceptable methods for this: the Synthesis Event and Performance Method (Appendix L1) and the Fleet-type Roll-up Method (Appendix L2). A replacement that handles this automatically, rather than requiring manual calculation, will reduce both the time burden and the risk of errors for plants with complex unit configurations.
Renewable Unit Support
Solar and wind GADS reporting operates under a separate set of requirements from conventional units. As renewable portfolios have grown, the manual workload for classifying inverter and turbine-level faults, distinguishing equipment failures from weather-related derates, and producing unit-level NERC events has become a significant burden for compliance teams. Any GADS OS alternative evaluated in 2026 should be assessed for renewable capability, not just conventional fossil unit support.
ISO and RTO Integration
Most generator operators participate in one or more ISO or RTO markets. GADS reporting does not happen in isolation from those market obligations. Software that connects directly to dispatch instructions, real-time outage notifications, and ISO reporting portals reduces the manual coordination that otherwise falls to operations staff. If your facility reports to NYISO, PJM, MISO, SPP, CAISO, or another regional operator, check whether the replacement handles those regional reporting requirements out of the box.
Audit Trail and Revision Tracking
NERC GADS data is auditable. The DRI's report revision code system exists for a reason. Any replacement should maintain a complete history of original submissions and subsequent revisions, making it possible to demonstrate compliance with confidence if your data is ever reviewed.
What the Feature Checklist Looks Like
Use this as a starting framework when evaluating any GADS OS replacement:
| Feature | What to Expect From Any Replacement |
|---|---|
| Event and Performance Reporting | Support for all conventional unit types, all event classifications, and quarterly submission to webE-GADS |
| Annual DRI Updates | Cause code database updated within weeks of each new NERC DRI release |
| Edit Validation | Pre-submission error checking that mirrors NERC edit rules to prevent rejected files |
| Design Data Management | Fields for all nine required design data elements plus the expanded unit-type-specific fields added since 2024 |
| Contributing Operating Condition | Required COC field on every event record, with code validation and description guidance |
| Combined Cycle and Co-gen Support | Block-level reporting using synthesis event method or fleet-type rollup as defined in DRI Appendix L |
| Renewable Unit Support | Solar and wind GADS event reporting, separate from conventional fossil and hydro units |
| Performance Calculations | Automated equivalent hour calculations and availability factor reporting |
| Audit Trail | Full revision history and report revision code tracking for every event and performance record submitted |
| ISO/RTO Integration | Direct connection to OATI webE-GADS submission portal and compatibility with regional ISO requirements |
What Transition Looks Like in Practice
The most common concern when moving off any long-standing GADS software is historical data. Years of event records, performance reports, and unit design data represent a significant body of work, and losing access to that history is a legitimate risk. When evaluating replacements, ask specifically about data migration support: whether the vendor will assist with importing historical records, how existing unit configurations transfer over, and what the typical timeline looks like from contract to live submission.
Staff training is the other variable. Personnel who have been entering GADS data the same way for years will need time to get comfortable with a new interface. Early transitions, before a deadline is pressing, give your team room to learn the new system on real data without the pressure of a quarterly submission window bearing down on them. That is exactly the logic behind announcing the GADS OS retirement as early as possible.
What Utilities Are Choosing?
For generator owners and operators looking for a direct replacement that goes well beyond what GADS Open Source offered, PowerGADS from Integ has become the most widely used GADS reporting platform in North America. According to Integ, 70% of all generating units in the United States are now reported using their software, and the platform serves as the GADS solution for most ISOs and RTOs.
PowerGADS is part of the broader PowerSuite platform from Integ, which also covers outage planning and management, NERC standards compliance workflows, and utility analytics.
If you are transitioning away from GADS Open Source and want to understand what PowerGADS looks like for your specific unit types and reporting setup, you can request a demo or contact us directly.