Precision Violation Logging Is the Whole Point
Every water utility audit eventually collapses around the same problem: you know violations exist, you have counts, but you can't tell legal from engineering where in the infrastructure they are. A report that says "Building 47 has three illegal connections" is a starting point. A report that says "Building 47 has three illegal connections — two on branches, one directly on the counter" tells the repair team exactly what they're walking into and tells the legal team exactly what the building owner tapped.
The illegal connections locations and illegal motors locations fields are multi-select enumerations across five pipe zones: main pipe, branches, gauges, counters, and a null state. When a team surveys a building and finds an illegal motor siphoning from a branch line, they log that combination — "Yes / 2 / branches" — and that specificity propagates into any downstream enforcement export. The same logic applies to illegal connections. By the time the data reaches a supervisor's summary, the distinction between main pipe violations and counter-level tampering is preserved without any free-text interpretation required.
What the Entrance and Gauge Room Status Fields Actually Protect
Two access-state fields dominate the field team's day: "entrance closed" and "gauge room closed." They are separate fields because they represent separate problems. A closed entrance means the field team couldn't enter the building at all — no building data, no gauge room data, potentially a return trip. A closed gauge room means the team accessed the building but hit a locked or inaccessible gauge compartment. Both situations result in partial records, but they demand different dispatch responses.
The "done" field captures the synthesis: No, Yes, or Gauge Room Pending. Gauge Room Pending is the operational state that results when entrance was open but gauge room access failed — and it is the one status that generates a work queue item for future scheduling. Without this third state, those buildings either get marked "No" (making them indistinguishable from unvisited buildings) or "Yes" (which is a false completion). The three-state outcome is not a convenience — it is what makes the survey data trustworthy at the regional level.
The BUID, Region, and Parcel Triad
Building unique ID, region name, and parcel number form the geographic anchor for every record.
Region name in this version is free text rather than a bounded dropdown, which trades consistency for flexibility across operations that span territories not yet enumerated. Parcel number is integer. BUID is integer. The combination creates a unique, cross-referenceable identifier that links back to cadastral records without requiring database joins.
The "is this a newly added building" boolean flags structures that weren't in the original survey registry — construction that completed after the initial mapping was done. Those buildings don't have existing BUID history, and the flag keeps them distinguishable from re-surveys of known properties.
Leakage found, has well, and building status (In Use / Under Construction / Abandoned / Vacant) round out the infrastructure picture. The distinction between abandoned and vacant matters: abandoned buildings often retain active connections that continue to draw from the network, while vacant buildings are typically between tenants with the supply chain intact and metered. Billing implications differ; so does the enforcement pathway.