> ## Documentation Index > Fetch the complete documentation index at: https://docs.wayak.io/llms.txt > Use this file to discover all available pages before exploring further. # Regulatory compliance reporting > Compile and format regulatory submissions from operations data and regulation documents on a recurring schedule Energy utilities operate under extensive regulatory oversight from NERC, FERC, state public utility commissions, and environmental agencies. Compliance reporting requires pulling data from SCADA, meter systems, operations databases, and environmental monitoring — then formatting it to exact regulatory specifications. Each report cycle demands weeks of analyst time for data gathering, validation, and formatting, and a single error can trigger penalties or mandatory re-filings. Wayak automates the reporting pipeline. A playbook queries your operational data sources, validates the figures against regulatory definitions stored in a knowledge space, and produces formatted reports on a recurring schedule. An agent lets compliance officers investigate data points, trace figures back to source records, and answer ad-hoc regulatory questions. *** ## What you need * **Operations database** — generation output, capacity factors, forced outage rates, and dispatch records * **Meter data management system** — customer consumption totals, peak demand readings, and loss calculations * **Environmental monitoring system** — emissions readings, discharge measurements, and permit compliance data * **Regulatory requirements** — upload NERC reliability standards, FERC filing templates, state PUC reporting requirements, and EPA emissions reporting guidelines * **Internal reporting procedures** — upload your data validation checklists, signoff workflows, and filing calendars **Semantic layer:** Define these in your ontology before setting up the agent. | Component | Name | Definition | | --------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | Object | Filing | Maps to the `filings` table in the compliance system. Represents a single regulatory submission with period, type, and status | | Object | Generation Unit | Maps to `units` in the operations database. Represents a power generation asset with capacity, fuel type, and operating characteristics | | Metric | Capacity Factor | Actual generation output / maximum possible output for a unit over a reporting period | | Metric | Forced Outage Rate | Hours of forced outage / (hours of forced outage + operating hours) for each generation unit | | Dimension | Regulatory Body | Groups filings by regulator (NERC, FERC, State PUC, EPA) | | Dimension | Filing Frequency | Classifies reports by submission frequency (monthly, quarterly, annual) | See [building a semantic layer](/quickstart/build-semantic-layer) for a step-by-step guide. *** ## Agent setup Go to **Agent Space** → **New agent**. | Field | Value | | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Regulatory Compliance Analyst | | **Role** | Energy Regulatory Reporting Specialist | | **Goal** | Compile regulatory report data from operations systems, validate figures against regulatory definitions, trace data lineage, and answer compliance queries | > You are a regulatory reporting specialist for an energy utility. You compile data from generation, transmission, distribution, and environmental systems for regulatory submissions. You validate every figure against the applicable regulatory definition, flag discrepancies, and provide data lineage so auditors can trace any number back to its source. You reference the specific regulatory standard or filing requirement for every data point. You prepare validated drafts — final signoff is always a human responsibility. Grant access to: * Operations database (generation output, outage records, dispatch logs) * Meter data management system (consumption totals, peak demand, losses) * Environmental monitoring system (emissions, discharge data) * Regulatory requirements knowledge space * Internal reporting procedures knowledge space * Filing and Generation Unit objects, Capacity Factor and Forced Outage Rate metrics **Trigger:** User asks the agent to compile data for a specific regulatory filing. 1. Identify the filing type and reporting period from the user's request. 2. Load the applicable regulatory template and required data fields from the regulatory requirements knowledge space. 3. Query the operations database for generation, outage, and dispatch data for the reporting period. 4. Query the meter data management system for consumption, peak demand, and loss figures. 5. If the filing includes environmental data, query the environmental monitoring system for emissions and discharge readings. 6. Aggregate and format the data according to the regulatory template structure. 7. Return the compiled data with cell-level source references for audit traceability. **Trigger:** User asks the agent to validate a compiled report or a specific data point. 1. Load the compiled data for the specified filing. 2. Run cross-checks defined in the internal reporting procedures (e.g., generation output must reconcile with fuel consumption, losses must fall within expected ranges). 3. Compare calculated metrics against regulatory thresholds and prior-period values for reasonableness. 4. Flag any validation failures with the specific check, expected range, and actual value. 5. Return a validation summary with pass/fail results and items requiring manual review. **Trigger:** User asks the agent to trace a specific figure in a report back to its source. 1. Identify the data point in the compiled report. 2. Trace the aggregation path from the report cell back to the source query and table. 3. Pull the individual source records that contribute to the aggregated figure. 4. Document the calculation method and any transformations applied. 5. Return the lineage chain from report cell to source record, with the calculation formula at each step. *** ## Automation ### Playbook: Quarterly regulatory filing preparation Set the trigger to **Schedule — Quarterly** on the 10th day after quarter-end, allowing time for operational data to settle before compilation begins. The workflow compiles, validates, and packages quarterly regulatory submissions: 1. **Query** generation output, forced outage hours, and capacity data for the quarter from the operations database. 2. **Query** customer consumption totals, peak demand, and system loss calculations from the meter data management system. 3. **Query** emissions and environmental compliance data from the environmental monitoring system. 4. **Action** — aggregate and format the data according to each regulatory template (NERC, FERC, state PUC, EPA as applicable). 5. **Condition** — run validation checks. If any check fails, create a review task and flag the affected filing section. 6. **Action** — generate the formatted draft report for each regulatory body. 7. **Delivery** — distribute draft reports for review and signoff. * **Email** — send each draft report to the assigned compliance analyst for review and signoff * **Slack** — post a summary to `#regulatory-reporting` with filing status, validation results, and any flagged items * **Email** — notify the VP of Regulatory Affairs when all drafts are ready for final review Click **Run now** to test with the most recent quarter's data, then toggle to **Active**. *** ## What's next Analyze consumption patterns across facilities to identify waste and recommend efficiency improvements. See the full list.