NERC GADS Reporting Made Easy
Automate quarterly reporting with eDatasheet and AVEVA PI, and turn every outage into a decision you can act on.
EIS OI understands the complexity of power generation: not just the processes with the equipment, but the additional regulatory and market interactions. Utilizing these information silos to meet regulatory requirements and also drive operational decisions requires a partner with experience successfully implementing these projects – EIS OI is that partner.
EIS OI works to replicate common solutions across the power generation industry, providing each partner with the gained knowledge and experience. Our team works to drive local ownership in future solutions by training and templatizing solution components.
Enquire Today
Not Ready to Talk?
Contact us to explore the services that interest you and to receive industry white papers and valuable insights.
AVEVA-Endorsed Integrator
EIS is an AVEVA-endorsed operations system integrator, trusted to deliver Operational Intelligence projects in power generation.
- AVEVA-endorsed operations integrator
- Regulatory and market know-how
- Proven across power generation
30+ Years of OI Delivery
For over 30 years our consultants have delivered successful Operational Intelligence projects.
- Successful OI projects delivered
- Solutions replicated across the industry
- Templatized for local ownership
Real-Time Data Analytics
Our experts deliver access to real-time data and analytical tools to ensure every decision is an informed decision.
- Real-time data access
- Analytical tools for every decision
- Regulatory and market insight in one place
Know exactly where your fleet is losing money, and why.
You already own most of this stack
Built on what’s already running
- One set of numbers, floor to boardroom
- No separate export tool to buy or build
- Templates repeat unit after unit
eDatasheet closes the gap
- Operators explain the outage in the same system
- Feeds performance, NERC and recordkeeping
- Nothing re-typed at quarter-end
AI that can query all of it
- Ask a plain question, get a sourced answer
- Spot fleet-wide patterns, not just one-unit issues
- No report to build first
CONNECT isn’t a link in a chain. It’s the hub everything connects through.
Data and assets feed in from below. Power BI, AI and every application draw from the same CONNECT hub above, not a straight line.
- Remote assets, AVEVA apps and third-party sources in
- AI/ML, enterprise visualization and custom apps out
Source: AVEVA, aveva.com/en/solutions/connect
● ● ● AVEVA CONNECT — platform architecture
Attributes, not generic tags
Build the template once. Every unit, every site, every report inherits it.
● ● ● PI System Explorer — Unit Template: Attribute Templates
23 raw tags gets you NERC GADS
The same template, 30 tags more, gets you full performance monitoring too.
This unit carries 177 attributes today, and only 53 are raw. The raw-tag count scales with what you ask the system to do; the template builds the rest itself.
- Common plant attributes, built once
- Already satisfies NERC GADS requirements
● ● ● PI System Explorer — Unit Template: Analysis Templates
The NERC DRI, operationalized
These aren’t just formulas. They’re the NERC DRI’s own equations, calculated the same way every time, continuously, in Asset Framework instead of a spreadsheet.
The GADS event frame generator sits right inside the unit template, so every GADS event is captured the same structured way, unit after unit.
● ● ● PI System Explorer — Facility Template: Rollup Analysis
One level up: the site rollup
The site template already leverages rollup for the daily performance metrics you’d report anyway. It isn’t bolted on. It’s built into the template.
One screen, every level
Fleet, plant or unit: the same hierarchy, live. Expand it and the embedded Power BI pane updates with it, from cost drivers to the full fleet comparison, without leaving the page.
● ● ● AVEVA CONNECT — Fleet Command · Hierarchy
A trip opens its own PI Event Frame. Automatically.
Event Frames start either way: tripped automatically by a plant event, or opened by hand later. Same record either way, and it’s queryable in real time the moment it exists.
● ● ● Power BI — Units & Events (live GADS board)
Every unit. Every event. One board.
When a unit trips, the event timestamps itself. Add the detail later, and always see what’s still outstanding, not just at quarter-end.
● ● ● eDatasheet — GADS Data Entry
eDatasheet is the other way an Event Frame starts: by hand.
For a planned outage, nothing in PI triggered it digitally before now, so the operator opens the Event Frame directly. Even an automatic trip still needs this step. The signal can start it, but a person has to fill in what the signal can’t capture.
- Operator picks the cause and fills in the detail
- Saved right inside the same system
What it adds up to
lost in 14 days. 78% of it, operators explained themselves.
That operator-entered cause doesn’t just explain the dollars. It feeds performance tracking, NERC reporting and regulatory recordkeeping from the same entry.
● ● ● Power BI — Overview (live, full fleet)
● ● ● Power BI — Market (MISO hubs vs. fleet sites)
Price context, same screen
Market location and conditions change in real time, so the cost of an outage does too. Seeing cost and market price together is what lets you act in real time.
Already on the floor. Now driving decisions.
Asset Framework and PI Vision are standard tools in most plants. Build in Asset Framework and PI Vision shows plant-level metrics from the same real-time data points the floor already runs on.
● ● ● AVEVA PI Vision — Unit Performance: Actual vs Expected
Unit performance, from the same tags
Local visuals built on tags already on the unit template. The exact same calculations, rolled up for management, not a separate set of numbers.
● ● ● AVEVA PI Vision — Plant Operations: Day Ahead vs Real-Time
Same market data, front line
Day-ahead schedule against real-time generation, with the RT–DA price delta right beside it, used to decide what to do right now.
Ask the fleet directly
What traditional GADS reporting really costs you
Few units, clean data systems
Typical utility plant
Multiple units / older systems
GADS reporting with eDatasheet
Quarterly reporting, solved.
The NERC upload template is always ready, not assembled at quarter-end. The same eighteen fields NERC requires are already filled in, and always show what’s still outstanding.
| 07 | UtilityID | UnitID | ReptYear | E# | Rev | StartDate | StartTime | EndDate | EndTime | Type | GAC | NAC | Dom | Cause | Amp | COC | Description | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 07 | DEMO | RB-U3 | 2026 | 0047 | 0 | 1003 | 0800 | 1003 | 2212 | U3 | 594 | 561 | Y | 3620 | 04 | 0 | GSU oil weep | |
| 07 | DEMO | HW-U2 | 2026 | 0048 | 0 | 1014 | 1059 | awaiting entry | U2 | pending operator entry | ||||||||
NERC GADS Quarterly Upload, Card 07 Event Record (demo data)
When it’s time to file, AVEVA PI DataLink, already part of the stack, pulls this straight into the upload format on demand. No separate export tool to buy or build.
Automate quarterly NERC GADS reporting with eDatasheet and AVEVA PI.
Traditional GADS Reporting
eDatasheet GADS Reporting
How it works
Enter Data
Event Frames
Quality Checks
Submit Reports
Get the most out of your OT data with AI.
Initial Consulting
Implementation Services
Ongoing / Managed Services
Continuous improvementPeriodic reviews to expand use cases as data maturity grows.
Frequently Asked Questions
Straight answers to the NERC GADS reporting and Fleet Command questions power generators ask most.
What is NERC GADS reporting, and why does it take so long?
GADS is the quarterly generating unit availability reporting that plants submit to NERC. Done the traditional way it is Excel driven and manual, which can take one dedicated resource anywhere from 1-2 days a month for a few units with clean data systems to 4-7+ days a month for multiple units on older systems.
How does eDatasheet simplify quarterly GADS reporting?
Operators enter events in eDatasheet as they happen. AVEVA PI Event Frames capture and contextualize the event, proactive quality checks look for accuracy and completeness, and the report is compiled for submission. No quarter-end scramble.
Do we need to replace our PI System?
No. Asset Framework, PI Vision and PI DataLink are standard in most plants already. eDatasheet adds the one thing missing: manual entry for event frames, GADS causes and the configuration values no sensor can capture.
How many raw tags does GADS reporting need?
In our demo unit, 23 raw tags are enough to satisfy NERC GADS. About 30 more tags give you full performance monitoring from the same template. That unit carries 177 attributes, and only 53 are raw tags; the template builds the rest.
How do trips and outages get recorded?
A trip can open its own PI Event Frame automatically, timestamped the moment it happens. Planned outages, or the detail a signal cannot capture, are entered by the operator in eDatasheet, who picks the cause and saves it in the same system.
How does the quarterly NERC upload work?
The NERC upload template is always ready, not assembled at quarter-end. When it is time to file, AVEVA PI DataLink pulls the data into the upload format on demand, followed by a quick review and upload.
What is Fleet Command?
Fleet Command pairs AVEVA PI with eDatasheet, taking you from historian to Asset Framework to AVEVA CONNECT with AI built in at the CONNECT level. It gives you one view for the fleet, the plant and the unit, with Power BI cost and market views alongside. Our demo uses simulated plants and data.
Can AI really query our plant data?
When every unit is built on the same Asset Framework template, the data becomes a structured source AI can query at the unit or fleet level. EIS also offers AI services, from readiness assessment and use case workshops to implementation and ongoing model monitoring.
How do we get started?
Book a demo. Our team will discuss your units, your current PI System and your reporting needs, then agree a plan with you.