Detailed tender specification clauses

Flood warning

Use these clauses when rainfall, stage, telemetry, and alert delivery must support operational flood-warning decisions.

copy into tender docsadapt to local climateverify with acceptance tests

Specification clauses

Use these as starting clauses. Replace bracketed values with project-specific values, legal terms, and reviewed performance thresholds before formal procurement.

Clause 1

Warning objective and alert logic

The system shall state whether it supports public warning, road closure, pump control, asset protection, or operational awareness. Alert thresholds, escalation rules, recipients, and latency limits shall be documented.

Bidder evidence:
Alert matrix, threshold table, notification workflow, user roles, and sample alert messages.

Acceptance check:
Buyer triggers a test alert and verifies timing, recipients, escalation, and audit log.

Clause 2

Rainfall and stage measurement

Rainfall and water-level sensors shall be selected for the required range, resolution, response time, and site exposure. Water-level measurements shall reference a documented datum, sensor offset, and installation height.

Bidder evidence:
Datasheets, range and accuracy statements, datum notes, installation drawings, and calibration records.

Acceptance check:
Buyer verifies measurement output, datum references, offset documentation, and sample data during site acceptance.

Clause 3

Telemetry latency and outage behavior

The system shall meet the stated maximum telemetry latency during normal operation and shall store data locally during communications outages. Missing, delayed, and backfilled values shall be identifiable.

Bidder evidence:
Telemetry architecture, communication method, local storage capacity, outage behavior, and sample delayed-data record.

Acceptance check:
Buyer simulates or observes a communications outage and confirms local storage and backfill behavior.

Clause 4

Power autonomy and storm survivability

Stations shall maintain operation for the specified backup-autonomy period under storm conditions, including reduced solar charging where applicable.

Bidder evidence:
Power budget, battery capacity, solar sizing, operating assumptions, and enclosure rating.

Acceptance check:
Buyer checks power system documentation and performs a failover or battery-runtime acceptance check where practical.

Clause 5

Mounting, debris, and submergence risk

Installations shall account for debris impact, scour, sediment, submergence, access during storms, and survivability of mounting hardware and cables.

Bidder evidence:
Site-specific mounting drawings, flood exposure assumptions, cable protection details, and maintenance access plan.

Acceptance check:
Buyer inspects mounted equipment, cable routing, enclosure placement, and debris exposure before acceptance.

Clause 6

Event data and audit trail

The system shall preserve event data, configuration changes, alert history, maintenance logs, and sensor status records for the agreed retention period.

Bidder evidence:
Sample event report, audit log fields, data retention statement, and export method.

Acceptance check:
Buyer exports an event report and verifies timestamps, thresholds, alerts, sensor data, and configuration history.