Canonical source
Keep a stable WaterPesa domain record above replaceable vendor, meter and payment systems.
Migration
Map every incumbent customer, account, service point, meter, CIU, payment and configuration identifier to canonical WaterPesa records without throwing history away.
Answer first
WaterPesa preserves source-system identity alongside canonical IDs so migration exceptions, collisions and orphan records are visible before cutover.
Outcomes
Keep a stable WaterPesa domain record above replaceable vendor, meter and payment systems.
Show where the value came from, which version produced it and what changed next.
Turn exceptions into owned work with measurable resolution rather than passive dashboards.
Capabilities
Capability-based permissions and tenant scoping keep each workflow inside its authorized boundary.
Significant state transitions are appended to an auditable event stream with correlation IDs.
External systems integrate through normalized adapters and versioned contracts.
The repository includes seeded flows so stakeholders can inspect the intended operating sequence before live integration.
“For every cubic metre entering the system: where did it go, what happened commercially, what action was taken, and what measurable result followed?”WaterPesa product invariant · derived from the connected Notion product specification
FAQ
The recommended architecture supports overlay and adapter-based deployment so WaterPesa can prove value before any replacement decision.
Raw/source data and external references are preserved, while normalized records are versioned instead of rewriting past evidence.
Start with a bounded area, named data sources, baseline period, measurable success criteria and a predefined path to expansion if targets are met.
Keep exploring