Stormwater Environmental Compliance
Stormwater environmental compliance — ECA registry, MECP reporting, water quality monitoring, effluent tracking, environmental incidents, species-at-risk, and IDDE programs.
ECA Compliance
MECP Reports
IDDE Response
Effluent Tracking
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
7Delegated to
5Stormwater asset inventory, GIS
SWM facility maintenance, sediment tracking
Compliance orders, enforcement actions
Dashboards, trend analysis
Alert distribution, stakeholder notifications
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
3 capability groups comprising 7 discrete capabilities — each with API surface, business rules, and data ownership.
Environmental Compliance Approval registry with all conditions, amendment tracking, compliance status, and expiry/renewal management.
ECA Records
All ECAs for stormwater facilities — permit number, issue date, amendment history, conditions list, compliance status.
Conditions Tracking
Every ECA condition tracked individually — monitoring frequency, reporting deadlines, effluent limits, operational requirements.
Compliance Status
Real-time compliance status per condition — COMPLIANT, NON_COMPLIANT, PENDING_REVIEW — with evidence linkage.
Renewal Management
Expiry/renewal tracking — automated reminders at 12, 6, and 3 months before ECA expiry.
Ministry of the Environment, Conservation and Parks annual and incident reporting — automated data compilation, submission tracking, and deadline management.
Annual Reports
Annual monitoring reports per ECA — automated data compilation from monitoring programs.
Incident Reports
Spill/bypass/exceedance incidents reported to MECP — SAL notification within required timelines.
Submission Tracking
All submissions tracked — date, method, confirmation, MECP response, follow-up requirements.
Deadline Management
Report deadline management — automated reminders and escalation for overdue submissions.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
4 entities with 4 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
7 RESTful endpoints across 5 resource groups — plus 5 domain events for async integration.
/api/v1/stormwater-environmental/ecas
ECA registry with conditions and compliance status
/api/v1/stormwater-environmental/ecas/{ecaId}/conditions
ECA conditions and compliance tracking
Ecosystem
Products that depend on this module
2 Civic products consume Stormwater Environmental Compliance — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
ECA Compliance Tracking
Exceedance Detection
IDDE Response
MECP Report Submission
System Availability
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Stormwater Environmental Compliance
Request an architecture brief, integration guide, or live demo environment for your team.