Design Methods

2.1 Executable Principles & Basis

Effective monitoring system design requires adherence to a set of executable principles — not abstract guidelines, but actionable rules that can be verified during design review and acceptance testing. Each principle is grounded in a specific technical or regulatory basis, ensuring that design decisions are defensible and traceable. The following twelve principles form the foundation of every design decision in this guide.

1. Tiered Monitoring Design: Classify all monitoring points by risk level and function (baseline/trend vs. early warning). Higher-risk points receive more frequent sampling, redundant sensors, and faster alarm latency. Basis: risk management and regulatory grading frameworks.
2. Representativeness First (Groundwater): Indicator validity depends entirely on well construction quality and screened interval alignment with the target aquifer. No amount of sensor sophistication compensates for a poorly constructed or improperly purged well. Basis: hydrogeology and sampling theory.
3. Early Warning Latency Targets (Drinking Water): Define maximum detection-to-alarm time for each node (e.g., ≤1–5 minutes for intake nodes). This target drives sensor selection, communication architecture, and alarm rule design. Basis: operational safety requirements.
4. Hybrid Online + Offline Monitoring: Online sensors provide continuous signals for trend and early warning; offline laboratory sampling provides legal defensibility and confirmation of compliance. Neither alone is sufficient. Basis: compliance auditing requirements.
5. QA/QC as Architecture, Not a Report Step: Calibration schedules, drift checks, and data flags must be enforced in the data pipeline, not added as a post-processing step. Basis: data governance and audit requirements.
6. Time Synchronization as a Functional Requirement: All monitoring points must maintain bounded time error (≤2 s for plant nodes, ≤30 s for wells). Without time sync, event correlation and source tracing are unreliable. Basis: event correlation requirements.
7. Fail-Safe Alarming: Define explicit system behavior for missing or invalid data. For critical nodes, "no data" must trigger an alarm — silence must never be interpreted as "all is well." Basis: safety engineering principles.
8. Maintainability by Design: Use standard connectors, documented interfaces, and hot-swappable modules where possible. Design for the O&M team's skill level and spare parts availability. Basis: lifecycle cost (LCC) reduction.
9. Security-by-Segmentation: Isolate OT (operational technology) networks from IT networks. Apply least-privilege access, enforce audit logs, and maintain firmware update policies. Basis: ICS/OT security best practices.
10. Evidence Chain Completeness: Store calibration certificates, laboratory reports, and tamper events with immutable timestamps and access logs. Every data point must have a traceable lineage. Basis: compliance and audit requirements.
11. Environmental Hardening: Select enclosure ratings, corrosion-resistant materials, and surge protection appropriate for the site's environmental extremes. Basis: reliability engineering and site survey data.
12. Graceful Degradation: Define a minimal monitoring set that remains operational when partial failures occur. Critical indicators must remain available even when secondary systems fail. Basis: resilience engineering.

2.2 Failure Causes & Recommendations

Field experience across groundwater and drinking water monitoring deployments reveals recurring failure patterns. Understanding these patterns — their root causes, typical symptoms, and prevention strategies — is essential for robust system design. The table below summarizes the eight most common failure mechanisms, with specific avoidance recommendations and verification methods.

2.3 Core Design & Selection Logic

The design selection process follows a structured decision tree that begins with the monitoring object type and progressively narrows to a specific station class, instrument set, and QA/QC intensity. This systematic approach ensures that design decisions are consistent, auditable, and appropriate for the site's specific risk profile and operational constraints.

Figure 2.1: Core Design Selection Decision Tree — From Monitoring Object Type to Station Class and Instrument Configuration

For Groundwater Wells, the decision path evaluates risk level (High/Medium/Low), power availability (Mains/Solar/Hybrid), and communications feasibility (Cellular/LoRa/Offline) to arrive at Station Class GW-1, GW-2, or GW-3. For Drinking Water Chain nodes, the path evaluates node criticality (Intake/Disinfection/Outlet), required alarm latency (≤1 min/≤5 min/≤15 min), and redundancy requirements (N+1/Dual/Single) to arrive at Station Class DW-A, DW-B, or DW-C.

Design Step Sequence

1. Define compliance indicators required by applicable regulations
2. Classify all monitoring points by type and risk level
3. Choose station class using the decision tree
4. Select sensors and redundancy level for each station class
5. Define sampling frequency and data transmission intervals
6. Design communications and power architecture
7. Define QA/QC rules and calibration schedule
8. Define alarm matrix with thresholds, hysteresis, and escalation paths
9. Define integration interfaces and O&M procedures

2.4 Key Design Dimensions

Every monitoring system design must be evaluated across seven key dimensions that collectively determine whether the system will meet its operational, regulatory, and lifecycle objectives. These dimensions provide a structured framework for design review and acceptance testing, ensuring that no critical aspect is overlooked.