> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/water-1.md). # Water ### Overview The Water Usage dashboard tracks total water consumption, water cost, and hot-water temperature across the estate. It also surfaces a Sankey distribution view across floors and resources, making it an essential tool for both finance reporting and [HTM 04-01 compliance](/uma-knowledgebase/data-and-reporting/insights/water-legionella-detection-guide.md) Use this dashboard to: * Monitor consumption against expected usage and detect leaks * Convert water consumption to cost (£) for finance reporting * Demonstrate hot-water temperature compliance (HTM 04-01) * Identify the heaviest-use fixtures and target retrofits * Detect out-of-hours flow that signals stuck flushes or leaks *** ### Dashboard Structure The dashboard is organised into four tabs: 1. **Monitoring** 2. **Data** 3. **Map** 4. **Floor Heatmap** A metric switcher toggles every chart between **Water Consumption** and **Water Cost**. *** ### Tab 1 — Monitoring #### Total Water Consumption *KPI card.* Total consumption (litres or m³) for the period. #### Total Water Cost *KPI card.* Total cost (£) for the period, calculated from consumption, tariff, and standing charge. #### Water Temperature Trend *KPI card with thermal indicator.* Average hot-water temperature for the period, with HTM 04-01 status: * 🟢 PASS — Maximum hot-water temperature ≥ 55°C * 🔴 FAIL — Maximum hot-water temperature < 55°C Water stored or distributed below 55°C presents a Legionella risk. #### Water Consumption Trend *Line chart with Hourly / Daily / Weekly granularity tabs.* Water consumption over time, with optional cost overlay. *Use it to:* spot leaks (a flat baseline rising overnight is a leak signature) and benchmark consumption against expected demand. #### Water by Resource *Horizontal bar chart with Top N / Bottom N controls.* Resources or zones ranked by total water consumption or cost. *Use it to:* identify the heaviest-use fixtures — typically toilets, showers, and kitchens — for targeted retrofit programmes. #### Water by Weekday *Bar chart.* Water consumption or cost by day of the week. *Use it to:* detect out-of-hours flow that signals leaks or stuck flushes. #### Water Across Floors and Resources *Sankey flow diagram.* A hierarchical flow from **Floor → Resource Type → Individual Resource**, with ribbon width proportional to consumption. *Use it to:* present the building's water-flow story in a single image, suitable for executive and sustainability reporting. *** ### Tab 2 — Data #### Water Data Table *Sortable data grid.* Water consumption readings (m³) per resource with timestamps. Supports CSV, JSON, and PDF export. *** ### Tab 3 — Map #### Water Map View *Interactive geographic map.* Buildings plotted on a world map, colour-coded by total consumption. *Use it to:* compare water performance across sites and prioritise efficiency programmes. *** ### Tab 4 — Floor Heatmap #### Water Floor Heatmap *Colour-coded overlay on an interactive 2D floor plan.* Water density rendered directly onto the building's floor plan. *Use it to:* find consumption hotspots — typically wet rooms, kitchens, and plant areas. *** ### Filters & Controls * Building, Floor, Resource, Resource Type * Date range with presets and custom ranges * Granularity tabs on trend chart * Top N / Bottom N selectors on resource ranking * Metric switcher: Consumption / Cost *** ### Tips * Hot-water temperature dips frequently correlate with boiler-cycle timing — share findings with mechanical and electrical engineering teams. * A sudden water-volume spike with no occupancy spike often signals a stuck flush or leak. * Use the HTM 04-01 PASS / FAIL indicator as evidence in monthly compliance reporting. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/data-and-reporting/analytics-pro/dashboard/water-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.