Discovery
AuraScore 83/100

Municipal Water Utility Telemetry Discovery Report

Structure discovery insights regarding non-revenue water loss, aging telemetry, and SCADA modernization for municipal utilities.

Deploy this template following preliminary meetings with municipal water directors and utility operators. It analyzes leakage rates, supervisory control limitations, and funding avenues to scope digital metering projects.

Template

Role: Senior Municipal Water Solutions Consultant specializing in smart water metering, SCADA telemetry, and acoustic leak detection.

Context

  • Municipal Authority: {{municipality_name}}
  • Distribution Network Scale: {{water_distribution_scale}}
  • Non-Revenue Water Level: {{non_revenue_water_rate}}
  • Existing SCADA System: {{legacy_scada_vendor}}
  • Capital Funding Mechanism: {{funding_mechanism}}
  • Operational Pain Points: {{operational_pain_points}}

Task

Generate a Municipal Water Utility Telemetry Discovery Report summarizing infrastructure vulnerabilities, loss reduction opportunities, and procurement pathways to prepare for technical validation.

Method

  1. Characterize the operational footprint of {{municipality_name}} based on {{water_distribution_scale}}.
  2. Quantify economic and water resource loss implications highlighted by {{non_revenue_water_rate}}.
  3. Audit integration limitations and protocol constraints associated with {{legacy_scada_vendor}}.
  4. Correlate field operator challenges in {{operational_pain_points}} with automated telemetry solutions.
  5. Map procurement timeline requirements against parameters dictated by {{funding_mechanism}}.
  6. Formulate high-priority use cases focusing on pressure management and early burst detection.
  7. Outline required data access permissions needed before initiating an on-site pilot.

Constraints

  • MUST evaluate non-revenue water severity strictly against data in {{non_revenue_water_rate}}.
  • MUST NOT provide binding civil engineering cost estimates.
  • Analysis must highlight interoperability challenges with {{legacy_scada_vendor}}.
  • Recommendations must align directly with the grant or bonding terms in {{funding_mechanism}}.

Output format

Deliver a diagnostic discovery report divided into the following sections:

  1. Executive Summary (under 200 words synthesizing the water loss challenge)
  2. Telemetry and Distribution Assessment (systemic review of network scale and SCADA gaps)
  3. Economic Impact Breakdown (analysis of lost revenue and operational overhead)
  4. Qualification Roadmap (table of milestone gates, required data access, and procurement steps)

Self-review

  • Ensure {{legacy_scada_vendor}} compatibility risks are explicitly analyzed.
  • Verify that all operational pain points in {{operational_pain_points}} are addressed.
  • Confirm that the output adheres strictly to the four designated section headers.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-discovery
energy-utilities
water-utility
smart-metering
scada