NERC Compliance Intelligence Packet · v2.0

From Square One to Autonomous Compliance

A comprehensive technical and strategic foundation for DataPhleet — covering NERC terminology, standards, RSAW methodology, and the full AI architecture required to build the most capable automated compliance engine in the market. Authored by Brady Jenkins, former NERC standard author and compliance officer.

NERC O&P Standards IBR: PRC-028/029/030 RSAW Automation Real-Time AI Architecture Competitive Intel

$1.25M

Max NERC penalty per day, per violation

15 mo

Max interval between CIP-010 vulnerability assessments

100+

Active NERC reliability standards in force

New IBR standards in enforcement: PRC-028/029/030

The Core Problem DataPhleet SolvesCompliance evidence lives in SharePoint folders, email threads, OEM portals, and engineers' laptops. Every audit is a scramble. Every new standard means hiring another consultant. There is no real-time awareness — only reactive firefighting. dp:Bots change this by making compliance a continuous automated process, not a periodic panic.

Author's Note — Brady Jenkins, GCP EnergyI served as a NERC compliance officer and participated in the standards development process — including voting on and drafting early iterations of protection and operations standards. What I learned: compliance is 20% understanding the standard and 80% consistently gathering, organizing, and presenting evidence. That 80% is exactly what AI automates best.

Who Must Comply

Registered Entities — DataPhleet's Customer Universe

Every DataPhleet prospect is a registered entity with NERC. Understanding their function determines which standards apply — and therefore which dp:Bot modules they need.

🏭 Generator Owner (GO) + Generator Operator (GOP)

Primary DataPhleet customer. Owns and/or operates generating units. Must comply with PRC, MOD, FAC, and VAR standards. New IBR owners face immediate PRC-028/029/030 obligations. Legacy synch owners need MOD-026/027 and PRC-024 automation.

Pain point: Model validation, RSAW completion, and disturbance reporting are labor-intensive. One missed submission can trigger a CME.

⚡ Transmission Owner (TO) + Transmission Operator (TOP)

Secondary target. FAC, TOP, VAR, and IRO standards. Key concern is voltage support, reactive power coordination, and transmission planning documentation. Real-time reactive compliance (VAR-001/002) requires continuous monitoring — ideal dp:Bot function.

⚖️ Balancing Authority (BA)

Manages real-time load/generation balance. BAL, IRO, and TOP standards. Increasingly important as IBR penetration disrupts traditional frequency response. Real-time frequency monitoring and AGC compliance are automation opportunities.

🌞 IPP / Renewable Developer

Solar, wind, storage — fastest-growing segment. Many are new to NERC with no in-house expertise. PRC-028/029/030 hit them immediately at COD. Don't know what they don't know. Highest willingness to pay for automation.

⚠️

The Closer: Real NOV Penalty Math

A single NERC NOV for a High VRF violation can run $50K–$500K+. Duke Energy paid $10M for a CIP violation package in 2023. A mid-sized utility with 15 generators across 8 standards has hundreds of requirements to track quarterly. DataPhleet's annual subscription, even at $250K, delivers positive ROI from the first avoided violation. Lead every enterprise conversation with this math.

02 · Master Reference

Acronym & Terms Glossary

NERC operates in a dense acronym ecosystem. Use the global search bar above or the filter below to find any term instantly.

Acronym	Full Name	Definition & Significance	Type
NERC	North American Electric Reliability Corporation	The regulatory body that develops and enforces mandatory reliability standards for the Bulk Electric System in North America. Regulated by FERC in the US. Think of NERC as the "rule-maker"; Regional Entities (REs) are the enforcers.	Org
FERC	Federal Energy Regulatory Commission	US federal agency that regulates interstate electricity transmission and approves NERC standards. NERC reports to FERC. FERC issues Order 2023 (IBR interconnection reform) — directly drives PRC-028/029/030 urgency.	Org
BES	Bulk Electric System	The transmission network and generation resources above certain thresholds (typically 100kV+, or generators ≥20MVA) subject to NERC jurisdiction. Defining "BES" is itself a compliance exercise — get it wrong and you're either over- or under-registered.	Tech
RE	Regional Entity	NERC delegates compliance monitoring to regional entities: WECC (West), SERC (Southeast), RF (ReliabilityFirst/Midwest), MRO (Midwest), NPCC (Northeast), TRE (Texas). They conduct audits, spot checks, and process self-reports.	Org
WECC	Western Electricity Coordinating Council	Regional Entity for the Western Interconnection — everything west of the Rockies. Critical for GCP Energy's Utah, Nevada, and California territories. Valley Forge project will be WECC-regulated.	Org
SERC	SERC Reliability Corporation	Regional Entity covering most of the Southeast US. Relevant for Desserey's Memphis/Southeast/Florida territory. Different enforcement culture than WECC — generally more stringent on documentation.	Org
GO	Generator Owner	Entity that owns generating units. Must register with NERC/RE and comply with FAC-002, MOD series, PRC series, VAR-002. Primary DataPhleet customer. Note: GO and GOP can be the same entity or different (e.g., developer owns, O&M firm operates).	Org
GOP	Generator Operator	Operates generating units in real time. May be same as GO or a separate O&M firm (e.g., NAES for Valley Forge). Has distinct compliance obligations in many standards — both GO and GOP may need separate RSAWs for the same standard.	Org
TO	Transmission Owner	Owns transmission facilities above 100kV. Complies with FAC, TOP, and protection standards. Often a regulated utility (Rocky Mountain Power, PG&E, Duke). Key stakeholder for interconnection agreements.	Org
TOP	Transmission Operator	Operates the transmission system in real time. Also the prefix for TOP reliability standards (TOP-001 through TOP-003). Same entity as TO in many cases, but the distinction matters for applicable standards.	Org
BA	Balancing Authority	Integrates resource plans, maintains load-resource balance, and supports interconnection frequency. Major obligations under TOP, IRO, and BAL standards. Example: PacifiCorp (Rocky Mountain Power) serves as the BA for much of the Intermountain West.	Org
RC	Reliability Coordinator	Highest level of authority in real-time operations. Has the "big picture" view and can issue binding directives. Examples: CAISO, SPP, ERCOT serve as their own RCs. The RC is who the BA and TOP ultimately answer to during emergencies.	Org
RTO	Regional Transmission Organization	FERC-approved organization that manages wholesale electricity markets and transmission across a multi-state footprint. RTOs (PJM, MISO, SPP) and ISOs (CAISO, NYISO, ISO-NE) impose compliance obligations on generators that are additive to NERC standards — both layers must be satisfied. DataPhleet Phase 6 target market.	Org
PJM	PJM Interconnection	Largest RTO in North America by load (~180,000 MW, 65M people, 13 states + DC). Manages wholesale markets and transmission for the Mid-Atlantic and Midwest. GOs in PJM territory comply with both NERC standards (enforced by ReliabilityFirst RE) AND PJM-specific obligations: seasonal capability tests, primary frequency response verification, PJM dynamic model submissions, and interconnection agreement compliance. DataPhleet Phase 6 primary target — 250+ GW in PJM's interconnection queue.	Org
MISO	Midcontinent Independent System Operator	RTO covering 15 states and Manitoba, Canada (~170,000 MW). Second-largest RTO. MISO-specific GO compliance includes generator availability reporting, outage coordination, MISO model data submissions, and capacity performance obligations. Growing renewable interconnection queue makes this a key Phase 6 market.	Org
CAISO	California Independent System Operator	ISO operating California's transmission grid (~65,000 MW). Also serves as its own RC. CAISO-specific compliance includes resource adequacy reporting, must-offer obligations, CAISO dynamic model validation, and metering/telemetry requirements. Critical for GCP Energy's Western territory (Utah feeds into CAISO-adjacent WECC footprint).	Org
ERCOT	Electric Reliability Council of Texas	Unique — ERCOT operates outside FERC jurisdiction (Texas is its own grid island). Has its own reliability standards (not NERC O&P), its own market protocols, and its own compliance monitoring. Generators in ERCOT do not file NERC RSAWs — they comply with ERCOT Protocols instead. A standalone DataPhleet ERCOT module would be a separate product. Favad's Houston base makes this a natural future market given Texas's massive renewable growth.	Org
RF	ReliabilityFirst	NERC Regional Entity covering the Midwest and most of PJM's footprint (Ohio, Michigan, Indiana, Pennsylvania, West Virginia, and parts of surrounding states). RF conducts compliance audits for GOs in PJM territory — meaning a PJM generator has both RF (NERC enforcement) and PJM (market/interconnection enforcement) as compliance authorities.	Org
FERC Order 2023	FERC Order 2023 — Interconnection Reform	Landmark 2023 FERC rule reforming the generator interconnection process across all RTOs/ISOs. Requires cluster-based study processes, faster timelines, and stricter readiness deposits. Drives a surge of new GO registrations — each needing both NERC and RTO compliance from COD. Direct demand driver for DataPhleet Phase 6 ISO/RTO modules.	Process
RSAW	Reliability Standard Audit Worksheet	The structured audit document produced by NERC/REs that defines exactly what evidence a registered entity must provide to demonstrate compliance. The core dp:Bot output target — every bot workflow must ultimately produce a completed, evidence-backed RSAW.	Process
CMEP	Compliance Monitoring and Enforcement Program	NERC's program under which Regional Entities monitor, audit, and enforce standards. Defines all audit types: compliance audits (3–5 year cycle), spot checks, investigations, self-reports, and self-certifications. The framework dp:Bots must operate within.	Process
NOV / NOP	Notice of Violation / Notice of Penalty	NOV: formal notice of a compliance violation. NOP: public notice after the violation is settled. NOPs are published on NERC's website — searchable, public, and damaging to reputation. The fear of a public NOP is often a stronger motivator than the penalty itself.	Process
FFT	Find, Fix, Track	NERC's self-reporting mechanism for lesser violations. Entity identifies a violation, fixes it, tracks remediation, and reports to the RE. Often results in reduced or zero penalty. dp:Bots detecting gaps before auditors is the ultimate FFT enabler.	Process
CAP	Corrective Action Plan	Formal plan submitted to the RE outlining how a compliance violation will be remediated. Must include milestones, responsible parties, and completion dates. PRC-030 requires CAPs for unexpected IBR trips. dp:Bots can auto-generate CAP templates and track milestone completion.	Process
VSL	Violation Severity Level	The severity tier of a violation: Lower, Moderate, High, Severe. Determines penalty magnitude. Defined per-requirement in each standard. dp:Bots must assess VSL exposure automatically when evidence gaps are detected — this drives the urgency of the alert to the compliance officer.	Process
VRF	Violation Risk Factor	The reliability risk of a violation: Low, Medium, High. Defined per-requirement. High VRF + High VSL = maximum penalty exposure. DataPhleet sales pitch: a single High/High violation can exceed your annual subscription cost.	Process
COD	Commercial Operation Date	The date a generating facility begins commercial operation and compliance obligations officially start. Many compliance timelines (first RSAW due, model submission deadline) are keyed to COD. Critical for Valley Forge planning — compliance clock starts at COD.	Process
IA	Interconnection Agreement	Legal agreement between the generator and transmission owner defining technical requirements for grid connection. Often contains compliance obligations that flow directly into NERC standards (protection settings, model submission deadlines).	Process
PRC	Protection & Control	Family of NERC standards governing protection systems, relay settings, disturbance monitoring, and IBR performance. PRC-024 (ride-through), PRC-028/029/030 (IBR-specific) are the most active enforcement areas. Brady's core domain.	Standard
MOD	Modeling	Standards requiring GOs/TOPs to maintain accurate dynamic and steady-state models. MOD-025 (P/Q capability), MOD-026/027 (dynamic model validation — Brady's specialty), MOD-032 (data for planning studies) are the key requirements.	Standard
FAC	Facilities Design, Connections, and Maintenance	Standards covering interconnection studies (FAC-002), facility ratings (FAC-008), and vegetation management (FAC-003). FAC-002 triggers at new facility COD. FAC-008 pairs with HaloPhase DLR technology for continuous ratings documentation.	Standard
VAR	Voltage and Reactive	Standards for reactive power capability and voltage control. VAR-001 (TOP/BA voltage control), VAR-002 (generator reactive scheduling) require continuous real-time monitoring — ideal dp:Bot function tied to SCADA data streams.	Standard
CIP	Critical Infrastructure Protection	Cybersecurity standards (CIP-002 through CIP-014). Separate domain from O&P but increasingly intersecting. Frenos.io's territory. DataPhleet Phase 5 opportunity — don't dilute the O&P focus in early phases.	Standard
IBR	Inverter-Based Resource	Solar PV, wind, and battery storage resources connected via power electronic inverters. Behave fundamentally differently from synchronous generators — no natural inertia, voltage-following controls, trip risk during excursions. Subject to PRC-028/029/030 as of 2025–2026.	Tech
SGR	Synchronous Generator Resource	Traditional generator (gas, steam, hydro, nuclear) with rotating mass directly synchronized to grid frequency. Provides natural inertia and reactive support. Subject to MOD-026/027, PRC-024, VAR-002. Brady's 25-year expertise domain.	Tech
GFM / GFL	Grid-Forming / Grid-Following	GFL: standard IBR mode — follows existing grid voltage/freq. Majority of installed IBRs. GFM: advanced mode — can set voltage/freq reference (behaves like a synchronous generator). GFM is the future; GFL is the compliance problem today.	Tech
LVRT / HVRT	Low / High Voltage Ride-Through	Capability to remain connected during voltage excursions. LVRT: stay connected through low voltage (fault clearing). HVRT: stay connected through high voltage (load rejection). PRC-024 and PRC-029 define the mandatory ride-through curves. Failed LVRT = tripped generator = potential cascade.	Tech
PSS	Power System Stabilizer	Control system on synchronous generators that damps inter-area oscillations by modulating AVR excitation. MOD-026 requires validation of PSS model and settings against field test data. Brady has hands-on commissioning experience with PSS on large generators.	Tech
AVR	Automatic Voltage Regulator	Generator excitation control system that regulates terminal voltage. MOD-026 governs AVR model verification. The AVR model (.dyr file) submitted to the RE must match actual machine behavior demonstrated in field tests — the core MOD-026 compliance task.	Tech
SCADA	Supervisory Control and Data Acquisition	Real-time monitoring and control system. Primary data source for compliance automation — telemetry, alarms, setpoint verification, reactive output monitoring. dp:Bots connect via SCADA APIs to enable continuous compliance monitoring.	Tech
PMU	Phasor Measurement Unit	High-speed (30–120 samples/sec) measurement device providing GPS-synchronized voltage/current phasors. Generates the high-fidelity data dp:Bots need for real-time PRC-028/030 event detection and evidence collection. Protocol: IEEE C37.118.	Tech
DR	Disturbance Recorder	Captures high-resolution oscillographic data during fault events (COMTRADE format). PRC-002/028 govern DR installation and data submission. dp:Bots automatically detect DR trigger conditions, collect COMTRADE files, and format submission packages.	Tech
PSS/E	Power Systems Simulation for Engineering	Siemens PTI software used by most utilities and REs for power flow and dynamic studies. MOD-026/027 model files submitted for compliance are typically in PSS/E format (.dyr dynamic, .raw power flow). dp:Bots must be able to parse and validate these files.	Tech
DLR	Dynamic Line Rating	Real-time calculation of actual transmission line thermal capacity based on current weather conditions. HaloPhase's core technology. Enables FAC-008 continuous facility ratings documentation — a first-of-kind dp:Bot integration opportunity no competitor offers.	Tech
POI	Point of Interconnection	The electrical boundary where the generator's facilities end and the TO's system begins. Many compliance measurements (reactive output, voltage level, protection settings) are referenced to the POI. Must be clearly defined in the IA and RSAW evidence.	Tech

03 · Standards Library

NERC O&P Standards — Complete Reference

All applicable Operations & Planning standards. Each card links to the dp:Bot automation opportunity. PRC-028/029/030 are the primary beachhead — click to expand for full requirement breakdowns.

🔵 PRC — Protection & Control | 🟢 MOD — Modeling | 🟡 FAC — Facilities | 🔴 VAR — Voltage & Reactive

PRC-024-3

Generator Frequency & Voltage Ride-Through

Mandatory ride-through curves ALL generators must stay within. Non-compliance = trips = NOPs. Synch + IBR.

High Enforcement

PRC-025-2

Generator Relay Loadability

Generator protection relays must not trip during recoverable disturbances. Major evidence burden — relay setting sheets, coordination studies.

High Priority

PRC-027-1

Coordination of Protection Systems

GOs coordinate protection for BES faults. Detailed documentation of coordination studies and as-left settings required.

Synch Focus

PRC-002-2

Disturbance Monitoring & Reporting

DR installation and oscillographic data submission for BES events. dp:Bot parses COMTRADE files and populates event reports automatically.

High Enforcement

PRC-028-1 🆕

Disturbance Monitoring for IBRs — Effective April 2026

IBR owners install and maintain DME; submit data within 30 days of qualifying event. dp:Bots auto-detect events, collect DR files, format R4 submission packages, track calibration schedules.

NEW · IBR · Priority 1

PRC-029-1 🆕

Frequency & Voltage Ride-Through for IBRs

IBR settings must comply with ride-through curves. With 20–200 inverters per plant, manual verification is impossible. dp:Bot parses OEM setting files and auto-verifies each inverter.

NEW · IBR · Priority 1

PRC-030-1 🆕

Unexpected IBR Event Mitigation

IBR unexpected trips require root cause analysis and CAP submission. dp:Bots cross-reference event data vs. PRC-029 curves, auto-detect qualifying trips, pre-populate CAP templates.

NEW · IBR · Priority 1

PRC-019-2

Coordination of Voltage Protection

Generators coordinate voltage protection settings with applicable TO. Documentation and setting verification automatable.

Synch + IBR

MOD-025-2

Verification of Real & Reactive Power Capability

GOs verify and report actual P/Q capability every 5 years. dp:Bots ingest SCADA test data and auto-populate MOD-025 capability reports.

Modeling

MOD-026-1/2

Generator Excitation Control Model Verification

Validate AVR/PSS dynamic models against field test data. Brady's core domain. OMICRON/Doble test exports → PSS/E comparison → RSAW auto-population.

Brady's Domain

MOD-027-1/2

Turbine/Governor Model Verification

Verify governor/turbine dynamic models match actual machine behavior. Governor frequency response testing and model benchmarking required.

Modeling

MOD-032-1

Data for Power System Modeling

TOPs and BAs collect and submit steady-state and dynamic data for planning studies. dp:Bots automate data collection from source documents.

Modeling

FAC-002-3

Facility Interconnection Studies

Interconnection studies required for new facilities. Compliance clock starts at COD. Critical for Valley Forge and all new-build projects.

COD Trigger

FAC-008-3

Facility Ratings

TOs establish and document thermal/voltage/stability ratings for all BES elements. Pairs with HaloPhase DLR for continuous automated ratings documentation.

TO Focus

VAR-002-4.1

Generator Operation for Voltage Stability

GOs operate at voltage schedules specified by TOP/BA. Automated verification of reactive output vs. schedule is ideal dp:Bot real-time function.

Real-Time

VAR-001-5

Voltage and Reactive Control

TOPs and BAs monitor and control voltage levels. Real-time monitoring obligations pair with dp:Bot continuous SCADA ingestion architecture.

Real-Time

IBR Deep Dive

PRC-028 / 029 / 030 — Full Requirement Breakdown

PRC-028-1 · Disturbance Monitoring & Reporting for IBRs

Effective April 2026 · Applicability: GO with IBR ≥20 MVA at 100kV+

▼

R1: Install DME meeting functional specs (sampling rate, accuracy, channel requirements)
R2: Maintain DME in service — maximum allowable downtime between required tests
R3: Calibrate DME per manufacturer schedule; maintain calibration records
R4: Submit disturbance data within 30 calendar days of event notification

dp:Bot targets:

Auto-detect qualifying events via SCADA/PMU data stream
Auto-trigger R4 data collection, COMTRADE file packaging, and RE submission
Calibration schedule tracking with automated alerts at 30/14/7 day thresholds
RSAW auto-population with equipment specs, calibration records, and event logs

PRC-029-1 · Frequency & Voltage Ride-Through for IBRs

Most consequential new IBR standard · Requires settings verification for every inverter

▼

R1: Configure IBR settings within LVRT/HVRT/UFRT/OFRT ride-through performance curves
R2: Verify settings are actually implemented — inverter commissioning data required
R3: Submit verification evidence to RE — settings sheets, OEM docs, test data
R4: Remediate non-conforming settings within defined timelines

Scale problem: A 100MW solar plant = 150+ individual inverters, each needing settings verification. Manual review is impossible at scale.

dp:Bot targets:

Ingest OEM inverter setting files (XML/JSON) and auto-verify vs. NERC curves per inverter
Flag non-conforming inverters with specific remediation instructions
Generate R3 evidence packages with per-inverter settings summaries
Track R4 remediation timelines and auto-generate close-out evidence

PRC-030-1 · Unexpected IBR Event Mitigation

Triggered by disturbance events · Root cause analysis + CAP required

▼

R1: Detect and identify unexpected trips within 30 days of an event
R2: Conduct root cause analysis (firmware, protection settings, comms delay, etc.)
R3: Develop and submit a Corrective Action Plan (CAP) to the RE
R4: Implement corrective actions and provide evidence of completion

dp:Bot targets:

Cross-reference disturbance event data with PRC-029 curves to identify "unexpected" trips automatically
Generate R1 notification packages with supporting event data within hours of trigger
Pre-populate CAP templates with event data, timeline, and suggested remediation
Track CAP milestone completion and generate R4 close-out evidence

Synch Generator — The Blue OceanMOD-026/027 model validation, PRC-024 relay verification, and VAR-002 reactive scheduling for the legacy synchronous fleet (200,000+ MW nationally) is massively underserved. Every competitor is chasing IBR. DataPhleet + Brady Jenkins expertise owns this market. Siemens Energy engagement is your proof of concept.

04 · RSAW Mastery

What is an RSAW — and Why It's Everything

The Reliability Standard Audit Worksheet is the single most important document in NERC compliance. Every dp:Bot must ultimately produce RSAW-ready evidence packages. This is non-negotiable.

The RSAW Is the ProductIt doesn't matter how good your data is, how sophisticated your model is, or how compliant your facilities actually are — if the RSAW isn't complete, accurate, and evidence-backed, you fail the audit. DataPhleet's competitive advantage is that dp:Bots produce audit-ready RSAWs automatically, not just data dashboards.

R1, R2…

Numbered Requirements — each must be addressed separately in the RSAW

M1, M2…

Measures — the specific evidence NERC/RE will look for per requirement

VSL

Violation Severity Levels (Lower/Moderate/High/Severe) — drive penalty magnitude

VRF

Violation Risk Factor (Low/Medium/High) — determines enforcement priority

RSAW Anatomy

Dissecting an RSAW — Every Field Explained

Using PRC-029-1 R1 as the working example. dp:Bot automation targets are called out for each section.

Entity Information Block

Contains: NCR Number (unique NERC entity ID), registered entity name, applicable function (GO/GOP/TO), Regional Entity name, audit period start/end dates, and compliance monitoring type.

dp:Bot target: Pull from entity registration database. Auto-populate from CRM. Update audit period from RE notification alerts automatically.

Applicable Requirements Table

Lists each Requirement (R1, R2…) with full verbatim text, applicable entity functions, effective date, and whether it applies to this specific entity.

dp:Bot target: Parse the official NERC standard. Map requirements to entity functions automatically. Flag inapplicable requirements as N/A with documented justification. Keep current when NERC revises standards.

Measures (Evidence Specification) — The Core of Automation

For each Requirement, Measures define exactly what evidence constitutes compliance. Example for PRC-029 R1: "Evidence may include inverter setting files, OEM documentation confirming ride-through capability, commissioning test reports showing ride-through curves."

This is the core of RSAW automation. dp:Bots are programmed to collect each specific Measure's evidence type. The KB must encode every Measure for every standard.

Evidence Submitted Section

Entity fills in: document name, document date, description, and how it satisfies the Measure. Each evidence item must be logged with a document ID.

dp:Bot target: Auto-generate this entire section from the evidence collection pipeline. Each document is assigned an ID, tagged to a specific Measure, and logged with collection timestamp and source system. Full chain of custody.

Compliance Narrative — Where Claude API Shines

Free-text field where the entity explains how they comply. Auditors use this to determine if they need to look deeper. Weak narratives invite deeper scrutiny.

dp:Bot target: LLM-generated compliance narrative (Claude API) based on collected evidence. Technically accurate, professionally worded, references specific evidence items by ID. A good narrative reduces audit friction significantly.

VSL Self-Assessment & Gap Alerting

If compliance is not fully met, the entity must self-assess the Violation Severity Level (Lower/Moderate/High/Severe).

dp:Bot target: Automatically detect gaps in evidence, pre-flag potential VSL exposure, and alert the compliance officer before submission with specific remediation guidance. Convert reactive panic into proactive action.

RSAW Automation Pipeline

📡

Ingest

SCADA/PMU/PI

→

🔍

Detect

Event engine

→

📄

Collect

Evidence harvest

→

✅

Verify

Auto-validate

→

✍️

Write

LLM narrative

→

📬

Submit

RE portal

05 · Architecture & Code

Building the dp:Bot Intelligence Stack

The full technical architecture from raw grid data to audit-ready RSAW. Six layers, each with specific technology choices. Then three production-relevant code patterns for the engineering team.

Data Ingestion — Real-Time & Historian

Connect to every entity data source. Real-time SCADA for event detection. PI/AVEVA Historian for trend compliance data. Document stores for evidence files. OEM portals for inverter/relay settings exports.

OSIsoft PI Web APIAVEVA HistorianREST APIsIEEE C37.118 (PMU)Modbus/DNP3SharePoint Graph APISFTP (OEM data)

Event Detection & Triggering Engine

Rules engine that monitors L1 streams and fires compliance triggers when thresholds are crossed. NERC thresholds for each standard encoded as configurable YAML rule definitions. Real-time alerting to compliance officer dashboard.

Apache KafkaStream processingRules YAML configWebSocketsAlerting engine

Standards Knowledge Base (RAG-Enabled)

Structured database of every applicable standard: all R#, M#, applicable functions, VSL/VRF tables, evidence type specs, and deadlines. The "compliance brain" — stored as vector embeddings for semantic querying. Auto-updated when NERC issues new/revised standards.

PostgreSQLChromaDB (vectors)NERC standards parserRAG pipelineStandards diff engine

Evidence Collection & Verification Bots

Standard-specific dp:Bots that harvest, classify, and verify evidence. Inverter setting parsers for PRC-029. DR file (COMTRADE) parsers for PRC-028. Relay setting parsers (SEL/GE/ABB) for PRC-024. PSS/E .dyr parsers for MOD-026/027. Each bot knows exactly which documents satisfy which Measures.

Python botsCOMTRADE parserSEL/GE settings parsersPSS/E .dyr parserPDF/XML parsersComputer vision (scanned docs)

AI Reasoning & RSAW Generation (Claude API)

LLM-powered layer that takes collected evidence, assesses compliance status, detects gaps, and writes the RSAW compliance narrative. Claude API with RAG over the standards KB ensures technically accurate, audit-ready narratives. Gap detection alerts compliance officer with specific remediation guidance.

Claude API (Anthropic)RAG retrievalGap detection logicNarrative generationVSL self-assessment AI

Compliance Portal & RSAW Delivery

Customer-facing portal: review auto-generated RSAWs, approve or edit before submission, manage evidence chain of custody, track audit timelines, real-time compliance dashboards. Full audit trail for every document and decision. RE portal submission integrations.

React/Next.jsFastAPI backendPostgreSQL + S3Digital signaturesRE portal integrationsRole-based access

Code Patterns

Production-Ready Code — Three Core Patterns

Pattern 1 — RSAW Automation Engine (Core Bot Class)

Python · dp:Bot RSAW Core
# dp:Bot — RSAW Automation Engine · DataPhleet Core
from dataclasses import dataclass
from typing import List
from datetime import datetime
import anthropic

@dataclass
class EvidenceItem:
    doc_id: str
    doc_name: str
    doc_date: datetime
    requirement_ref: str   # e.g. "PRC-029-1 R1"
    measure_ref: str       # e.g. "M1.1"
    file_path: str
    source: str            # "SCADA"|"OEM"|"Manual"|"CMEP_Portal"
    verified: bool = False

class DpBotRSAWEngine:
    def __init__(self, entity_ncr: str, standard: str):
        self.entity_ncr = entity_ncr
        self.standard = standard
        self.client = anthropic.Anthropic()
        self.evidence_store: List[EvidenceItem] = []

    async def generate_narrative(self, req: str, evidence: list) -> str:
        """Claude API generates audit-ready compliance narrative."""
        prompt = f"""You are a NERC compliance engineer writing an audit narrative.
Standard: {self.standard}, Requirement: {req}
Evidence collected: {[e.doc_name for e in evidence]}

Write a concise technical compliance narrative (3-5 sentences) that:
1. States compliance status clearly
2. References specific evidence documents by name
3. Uses accurate NERC/power systems terminology
4. Is written for a Regional Entity auditor audience
Return ONLY the narrative text."""

        r = self.client.messages.create(
            model="claude-opus-4-5",
            max_tokens=500,
            messages=[{"role": "user", "content": prompt}]
        )
        return r.content[0].text

    async def build_rsaw(self) -> dict:
        """Full RSAW assembly pipeline — collect, verify, narrate."""
        rsaw = {'entity_ncr': self.entity_ncr, 'standard': self.standard,
                'generated_at': datetime.utcnow().isoformat(), 'requirements': []}
        for req in self.get_requirements():
            evidence = await self.collect_evidence(req)
            gaps = self.detect_gaps(req, evidence)
            narrative = await self.generate_narrative(req, evidence)
            rsaw['requirements'].append({
                'req': req, 'compliant': len(gaps) == 0,
                'evidence': evidence, 'gaps': gaps, 'narrative': narrative
            })
        return rsaw

Pattern 2 — Real-Time Event Detection for PRC-028/029/030

Python · Event Detection Engine
# NERC threshold definitions — update when standards revise
NERC_THRESHOLDS = {
    "voltage_low_pu":  0.90,  # <90% → potential PRC-029 event
    "voltage_high_pu": 1.10,  # >110% → potential PRC-029 event
    "freq_low_hz":     59.5,  # <59.5 Hz → PRC-024 concern
    "freq_high_hz":    60.5,  # >60.5 Hz → PRC-024 concern
    "var_deviation":   0.05,  # >5% from schedule → VAR-002
}

class RealTimeComplianceMonitor:
    def __init__(self, entity_ncr: str):
        self.entity_ncr = entity_ncr
        self.event_queue = asyncio.Queue()

    async def monitor_stream(self, data_stream):
        """Continuously monitor live telemetry for compliance triggers."""
        async for point in data_stream:
            for event in self._evaluate_point(point):
                await self.event_queue.put(event)
                await self._dispatch_bot(event)

    def _evaluate_point(self, point) -> list:
        triggered, v_pu = [], point.voltage_kv / point.nominal_kv
        if v_pu < NERC_THRESHOLDS["voltage_low_pu"]:
            triggered.append({
                "type": "VOLTAGE_LOW", "value": v_pu,
                "timestamp": point.ts,
                "standards_triggered": ["PRC-028-1", "PRC-030-1"],
                "bot_workflows": ["prc028_r4_collect", "prc030_r1_detect"]
            })
        return triggered

    async def _dispatch_bot(self, event: dict):
        for wf in event["bot_workflows"]:
            asyncio.create_task(self._run_workflow(wf, event))

Pattern 3 — PRC-029 Inverter Settings Verifier

Python · PRC-029 Auto-Verifier
# PRC-029 mandatory LVRT curve — (voltage_pu, min_time_seconds)
PRC029_LVRT = [(0.00,0.15),(0.15,0.15),(0.50,3.00),(0.90,10.0)]

class PRC029Verifier:
    def verify_inverter(self, inv_id: str, settings: dict) -> dict:
        result = {'inverter_id': inv_id, 'compliant': True, 'violations': []}
        lvrt = settings.get('lvrt_setpoints', [])
        for v_thresh, t_min in PRC029_LVRT:
            t_cfg = self._find_time(lvrt, v_thresh)
            if t_cfg < t_min:
                result['compliant'] = False
                result['violations'].append({
                    'req': 'PRC-029-1 R1', 'v_pu': v_thresh,
                    'required_s': t_min, 'configured_s': t_cfg,
                    'fix': f"Increase LVRT at {v_thresh}pu: {t_cfg}s → ≥{t_min}s"
                })
        return result

    def verify_plant(self, settings_dir) -> dict:
        """Verify all inverters; return plant-level compliance summary."""
        results = [self.verify_inverter(f.stem, json.loads(f.read_text()))
                   for f in settings_dir.glob("*.json")]
        ok = sum(1 for r in results if r['compliant'])
        return {'total': len(results), 'compliant': ok,
                'rate_pct': round(ok/len(results)*100,1), 'detail': results}

06 · Build Roadmap

18 Months to Market Leadership

Sequenced by market urgency (IBR compliance crisis hits April 2026), technical dependency order, and revenue generation potential. Each phase ships working product to paying customers.

Phase 1 · Months 1–3

Foundation — Standards KB + RSAW Engine

Ingest all O&P standards into the knowledge base with vector embeddings. Build the RSAW population engine with Claude API narrative generation. Manually curate evidence templates for PRC-028, PRC-029, PRC-030, MOD-026, MOD-027. Deliver first working dp:Bots to beta GO/IBR customers. This is shippable and chargeable immediately.

Standards DBRSAW EngineClaude APIBeta customers

Phase 2 · Months 3–6

Live Data — Connect to Grid Telemetry

PI Web API connector, SCADA REST adapters, IEEE C37.118 PMU listener. Deploy real-time event detection engine. Inverter settings parsers for top 5 OEMs (SMA, Sungrow, ABB, GE, Huawei). PRC-029 settings auto-verifier deployed to first utility customers. April 2026 PRC-028 enforcement creates urgency — this phase must ship before then.

PI Web APIEvent detectionOEM parsersPRC-028 ready

Phase 3 · Months 6–9

Synch Generator Module — The Blue Ocean

MOD-026/027 model validation bots: ingest OMICRON/Doble test exports, compare against PSS/E models, generate comparison reports. PRC-024 relay settings verifier for SEL/GE/ABB relay formats. VAR-002 real-time reactive schedule monitoring. Target: Siemens Energy, NAES, large gas and hydro GOs. This is the blue ocean — no competitor covers this market well.

MOD-026/027SEL/GE parsersPSS/E integrationSiemens target

Phase 4 · Months 9–12

Customer Portal + Compliance Dashboard

Production-grade compliance officer portal. Real-time compliance status dashboard per standard. RSAW review/approve workflow with digital chain of custody. RE portal submission integrations (WECC, SERC, RF). Audit preparation package generator. Self-certification and FFT workflow automation. This is the "product" that enterprise sales requires.

PortalDashboardRE integrationsEnterprise sales

Phase 5 · Months 12–18

Predictive AI + Transmission Owner Market

Predictive compliance gap detection — AI flags emerging risks before violations occur. CIP-007/010 cybersecurity module (adjacent market, CIP enforcement is intense). Transmission Owner market: FAC-008, VAR-001. HaloPhase DLR integration for FAC-008 continuous facility ratings. National RE coverage: WECC, SERC, RF, MRO, NPCC all live.

Predictive AICIP moduleTO marketHaloPhase DLR

Phase 6 · Months 18–24

ISO/RTO Compliance Modules — The Next Frontier

NERC O&P standards are the universal baseline — every GO in North America must comply regardless of RTO membership. But ISO/RTO-specific requirements are additive: generators in PJM, MISO, CAISO, SPP, ERCOT, and NYISO territory face a second compliance layer on top of NERC that no existing tool handles well.

PJM first — largest RTO in North America by load (65M+ people, 13 states). PJM-specific obligations include: generator performance testing (seasonal capability tests), primary frequency response verification, PJM-specific dynamic model submission (separate from NERC MOD but related), and interconnection agreement compliance triggers at COD. ReliabilityFirst (RF) is the NERC RE for most of PJM — dual compliance layer means dual RSAW exposure.

Then MISO, CAISO, SPP — each with their own tariff-based compliance requirements, generator performance obligations, and market participation rules that dp:Bots can automate. CAISO is critical for GCP Energy's Western territory (Utah, Nevada, California).

This phase positions DataPhleet as the only platform covering both the universal NERC layer AND the regional RTO/ISO layer — a capability no competitor is even attempting.

PJM moduleMISO moduleCAISO moduleSPP/ERCOTDual-layer compliance

Why ISO/RTO Compliance Is a Separate and Significant Market FERC Order 2023 (interconnection reform) and the explosive growth of renewable interconnection queues in PJM, MISO, and CAISO are creating a surge of new GOs who face both NERC obligations AND RTO-specific compliance requirements simultaneously — starting at COD. PJM alone has over 250 GW of generation in its interconnection queue. Most of these developers have never navigated either compliance layer. DataPhleet with Phase 6 modules serves them end-to-end from day one.

ISO/RTO Market Layer

Beyond NERC — The ISO/RTO Compliance Opportunity

NERC standards are the federal floor. ISO/RTO requirements are the regional ceiling. Generators in organized markets face both — and no tool currently covers the full stack.

🏛️ What is an RTO/ISO?

A Regional Transmission Organization (RTO) or Independent System Operator (ISO) manages wholesale electricity markets and transmission across a defined footprint. They operate under FERC jurisdiction and impose their own compliance requirements on top of NERC standards.

Think of it as: NERC = federal building code. RTO = local zoning laws. You must comply with both. A generator in PJM answers to NERC/RF (the RE) AND to PJM directly for market and interconnection obligations.

💡 Why This Matters for DataPhleet

GridStrong's own navigation says "NERC & ISO Compliance Officers" — they know this market exists but have no meaningful ISO-specific automation. Every competitor is in the same position.

A dp:Bot that handles both the NERC RSAW AND the PJM generator performance report in a single workflow is a genuinely unique product. FERC Order 2023 is accelerating new interconnections in PJM and MISO — these developers need dual-layer compliance from COD day one.

RTO/ISO	Footprint	Load (MW)	Key GO Compliance Obligations	DataPhleet Priority
PJM Mid-Atlantic + Midwest	13 states + DC	~180,000 MW	Seasonal capability testing, primary frequency response verification, PJM-specific dynamic model submission, interconnection agreement obligations	Phase 6 · First
MISO Midwest + South	15 states + Manitoba	~170,000 MW	Generator availability reporting, outage coordination, MISO model data submissions, capacity performance obligations	Phase 6 · Second
CAISO California	California + small Nevada	~65,000 MW	Resource adequacy reporting, must-offer obligations, CAISO dynamic model validation, metering and telemetry requirements	Phase 6 · Third
SPP Central US	14 states	~100,000 MW	Generator interconnection compliance, SPP-specific protection requirements, outage scheduling obligations	Phase 6
ERCOT Texas	Most of Texas	~90,000 MW	Unique — ERCOT is not subject to FERC jurisdiction but has its own protocols. Operates as both RC and market operator. Separate compliance framework entirely.	Standalone module
NYISO New York	New York State	~38,000 MW	Capacity market obligations, NYISO interconnection compliance, generator performance testing, ancillary service qualification	Phase 6

ERCOT Is a Special Case ERCOT operates outside FERC jurisdiction — it has its own reliability standards (not NERC), its own market rules (ERCOT Protocols), and its own compliance monitoring. It's essentially a separate compliance universe. A dedicated ERCOT module would be a standalone product rather than an extension of the NERC platform. Worth exploring as a separate offering given Texas's massive and growing renewable fleet — Favad's Houston base makes this a natural market.

Competitor	Core Model	IBR/PRC-028/030	Synch MOD-026/027	Real-Time Data	RSAW Auto-Complete	DataPhleet Edge
GridStrong.ai Elevate Consulting + SaaS	Consulting workflow tool	Strong (IBR-first)	Limited	File uploads only	Templates, not auto	True automation vs. consulting wrapper. Brady's synch expertise.
Frenos.io OT Cybersecurity / CIP	Digital twin + pen testing	CIP only, not O&P	Out of scope	Strong (OT focus)	No RSAW	Different domain. Potential partner (CIP+O&P bundle).
Parsons SigmaFlow Enterprise BPM / Workflow	Generic process automation	Custom config req'd	Custom config req'd	Needs integration	Manual workflow only	NERC-native vs. generic tool. No domain expertise built-in.
V-Comply Multi-industry GRC	Generic GRC platform	Surface-level	No technical depth	No grid integration	Document mgmt only	Deep O&P expertise vs. compliance checklist tool.
DataPhleet dp:Bots AI-native automation	Fully automated bots	PRC-028/029/030 native	MOD-026/027 + Brady IP	PI/SCADA/PMU native	Complete auto-generation	The only end-to-end automated platform with live data + RSAW generation

Competitive One-Pager · Print-ready

DataPhleet · dp:Bots for NERC Compliance

Autonomous Compliance.
Real-Time. Audit-Ready.

The only AI-native platform that connects to live grid data, verifies compliance against every applicable NERC O&P standard, and delivers complete RSAW packages — automatically, continuously, without consultants.

PRC-028 / 029 / 030 MOD-026 / 027 VAR-002 FAC-002 PRC-024 + 10 more standards

The Problem

Manual Evidence Hunt

Compliance evidence scattered across SharePoint, emails, OEM portals, and engineer laptops. Every audit is a fire drill.

No Real-Time Awareness

Compliance events happen in milliseconds. Traditional tools only look backward — after the violation has already occurred.

IBR Compliance Crisis

PRC-028/029/030 hit thousands of solar, wind, and storage owners in 2026. Most have no compliance process at all.

Penalty Exposure

$1.25M/day/violation maximum. One High-severity NOV can exceed an entire year of compliance software spend.

The dp:Bot Solution

Live Data Ingestion

Connects to OSIsoft PI, SCADA, PMU, and OEM portals. Monitors compliance thresholds in real time, 24/7.

Automated Evidence Collection

Standard-specific bots harvest every document, verify every setting, parse every file — automatically when triggered.

AI-Generated RSAWs

Claude API writes technically accurate, audit-ready compliance narratives. Every RSAW section populated — zero manual effort.

Gap Detection & Alerts

Compliance gaps detected before auditors find them. FFT-ready self-report packages generated automatically.

Standards Covered

PRC-028

IBR Disturbance Monitoring

PRC-029

IBR Ride-Through

PRC-030

IBR Event Mitigation

PRC-024

Generator Ride-Through

MOD-026

AVR/PSS Model Verification

MOD-027

Governor Model Verification

MOD-025

P/Q Capability Reporting

VAR-002

Reactive Scheduling

Why DataPhleet Wins

Consultants needed to complete RSAWs with dp:Bots

<5 min

From triggering event to RSAW evidence package ready

24/7

Continuous real-time compliance monitoring vs. periodic review

Competitors (GridStrong, etc.)

RSAW completionConsultants do it

Real-time monitoringNo

Synch gen (MOD-026/027)Limited

OEM inverter parsingNo

Pricing modelPer standard/per site

DataPhleet dp:Bots

RSAW completionFully automated

Real-time monitoringPI/SCADA/PMU native

Synch gen (MOD-026/027)Brady Jenkins IP

OEM inverter parsingTop 5 OEM adapters

Pricing modelPlatform subscription

Why Brady Jenkins + DataPhleet

Standard Author Credibility

Brady participated in drafting and voting on early NERC O&P standards. We don't just know what auditors look for — we helped define it.

True Automation, Not Consulting

dp:Bots complete RSAWs autonomously. Competitors' "automation" is still humans in the loop — ours is not.

Synch Generator Blue Ocean

200,000+ MW of legacy gas, hydro, and steam generation needs MOD-026/027 compliance. Every competitor is chasing IBR. We own the legacy fleet.

Real-Time = Peace of Mind

Continuous 24/7 monitoring means you will never be surprised by an audit again. The $1.25M/day penalty is the closer.