[Developers]

Regulatory Reporting

A water utility compliance officer has a quarterly AWWA Water Audit submission due in two weeks. She opens the Regulatory Reporting module, finds the pre-configured audit report type, generates the report from current op

Category: Api DomainsLast Updated: Feb 24, 2026
api-domainsaicompliance

Overview#

A water utility compliance officer has a quarterly AWWA Water Audit submission due in two weeks. She opens the Regulatory Reporting module, finds the pre-configured audit report type, generates the report from current operational data, and submits it. The platform records the submission date and tracks the report through review until it is accepted by the regulator. Meanwhile, the NERC CIP compliance checklist she initialised from the framework catalog is showing three overdue requirements, each flagged automatically because their deadlines have passed without a completion record. The Regulatory Reporting domain manages the full lifecycle of regulatory reports and compliance checks for utility organisations, from pre-built report type definitions through submission tracking and scorecard monitoring.

Key Features#

  • 8 pre-configured regulatory report types including EIA Form 861, SAIDI/SAIFI, AWWA Water Audit, and PHMSA Annual
  • 6 compliance framework catalogs with 55 individual requirements across NERC CIP, EPA SDWA, EPA CWA, PHMSA Pipeline, ISO 55000, and EN 13306
  • Report lifecycle tracking from draft through generation, submission, and acceptance or rejection
  • Compliance check initialisation from framework requirement catalogs with automatic scheduling
  • Compliance scorecard with per-framework compliance rate calculation
  • Overdue report and compliance check detection with deadline monitoring
  • Evidence URL attachment for completed compliance checks
  • Report statistics aggregation showing status distribution and overdue counts
  • Organisation-scoped data with tenant isolation and authenticated access

Use Cases#

Regulatory reporting requirements cut across multiple utility sectors. Primary industries served include electric power, water and wastewater, and natural gas distribution.

  • Generating regulatory compliance reports for utility operations across multiple jurisdictions
  • Initialising and tracking compliance check schedules from standard framework requirements
  • Monitoring compliance scorecards to identify gaps and prioritise remediation efforts
  • Tracking report submission lifecycle with deadline monitoring and overdue alerting

Integration#

The Regulatory Reporting domain is self-contained with static report type and compliance framework definitions. All queries are scoped by organisation with tenant isolation.

Open Standards#

  • NERC CIP (CIP-002 to CIP-013): The module ships a built-in compliance framework catalog covering all twelve NERC Critical Infrastructure Protection standards, scheduling and tracking each requirement check (categorisation, access management, patch cycles, incident response, and supply chain) for electric utility organisations.
  • ISO 55000 (Asset Management): ISO 55000 is included as an international compliance framework with eight pre-defined requirement checks spanning asset management policy, strategic planning, lifecycle cost analysis, risk management, and performance monitoring.
  • EN 13306 (Maintenance Terminology): The EU maintenance standard EN 13306 is implemented as a compliance framework with six recurring checks covering preventive maintenance, condition-based maintenance, KPI benchmarking (MTBF, MTTR, availability), and technician competency.
  • IEEE 1366 (Electric Power Distribution Reliability): The SAIDI/SAIFI monthly reliability report type is explicitly defined as per the IEEE 1366 standard, enabling electric utilities to produce regulator-ready reliability indices.
  • 49 CFR Part 192 (PHMSA Pipeline Safety): The PHMSA pipeline compliance framework maps directly to specific CFR 192 sections, including leak surveys (s. 192.723), cathodic protection (s. 192.465), regulator station inspections (s. 192.739), and operator qualification (Subpart N).
  • AWWA M36 (Water Audits): The annual Water Audit report type is generated per the American Water Works Association M36 methodology for non-revenue water analysis.
  • GraphQL: All queries and mutations for report lifecycle management and compliance check tracking are exposed through a typed GraphQL API, enabling interoperable integration with third-party portals and dashboards.

Last Reviewed: 2026-02-24 Last Updated: 2026-04-14

Ready to Build?

Get started with our APIs or contact our integration team for support.