Choose an authorised file
Use CSV or Excel records. Map your column names, preview the values and resolve validation issues.
Checking this workspace…
FROM YOUR FILES TO YOUR NEXT QUESTION
Bring your network
into focus.
Explore your metrics, connect incidents to assets, and see where to investigate next. Your imported records stay in this browser session.
No accounts. No record uploads. No AI service calls.
Follow the evidence
Find repeated events and target gaps. Every finding explains what was counted and what remains unknown.
Put it on the map
Load your GIS export and link it through asset IDs. Public basemap streaming is optional and starts off.
A workspace for internal records
Download and open this file locally, or use your organisation’s approved SharePoint edition. Imports are blocked when this HTML is opened as a public website. Records are held in memory only; refresh or close the page to clear them. Downloaded exports remain on your device.
This is a pilot analysis tool. It does not verify your permission, source accuracy, coverage, or organisational security approval. It is not affiliated with Greater Western Water.
A GUIDED IMPORT
Your columns. A clear contract.
Load any of the three tables independently. Only mapped fields are retained.
CSV / XLSX: up to 8 MB, 10,000 rows, 60 columns, 500 characters per cell. Use plain values and ISO dates; formulas, macros and external workbook links are rejected. GIS: 2,000 features / 50,000 vertices.
Match your fields
Choose one sheet. The first row must contain unique column headings.
Preview · first 5 source rows
Bring a GIS layer
Export a GeoJSON FeatureCollection in EPSG:4326 (longitude, latitude). Points, lines and polygons are supported. Use asset_id to join to your register. Only asset_id, name, asset_type, area properties are retained.
No GIS loaded. Projected MGA / GDA coordinates must be converted before import.
EXPLAINABLE, TRACEABLE FINDINGS
What deserves a closer look?
Suggestions guide investigation. They do not diagnose causes, predict failures or estimate savings.
Incident reporting window
Inclusive dates. Blank boundaries include all imported event dates. Metric cards keep their own reporting period.
YOUR ASSETS, IN CONTEXT
See the network behind the numbers.
Click a feature to see local attributes and linked incident evidence.
Drag to pan · scroll to zoom · arrow keys to pan
A map waiting for your network.
Local geometry · no basemap requestsImport a GIS layer to see real features here.
No example assets have been added.
Optional OpenFreeMap streaming sends your IP address and viewed map area to the provider. Asset properties and incident records are not included in requests. Leave this off if location confidentiality matters. Disabling it stops future requests; it cannot undo requests already sent.
Off. The local map works without a connection.
Map feature list
Keyboard-accessible selection, including overlapping features. First 200 shown.
EVERY NUMBER HAS A DEFINITION
Data, provenance & method.
Check what you supplied, remove a table or download the retained mapped fields.
Metric dictionary & empty templates
Templates contain headings only. Use your authorised records; this edition includes no synthetic or operational records.
How this edition reasons
- Failure counts include only water_burst, sewer_blockage, sewer_overflow and unplanned_outage. Planned works, controlled releases and “other” are shown separately.
- Repeat-event assets have at least two supplied failure records with the same nonblank asset ID in the selected reporting window. Counts do not establish a failure rate without asset exposure and complete reporting.
- Restoration statistics exclude missing values, retain genuine zero values and show their sample size. No restoration value is inferred.
- Metric comparisons use each row’s declared unit, target, direction and reporting period. Unlike metrics are never added together or ranked by an invented score.
- Suggestions are ordered by repeat events, supplied target gaps, restoration durations and evidence gaps, where evidence exists. Fewer than three suggestions can be the correct result.
- GIS locations and incident records join only by exact asset IDs. A point nearby is not evidence that an incident occurred on that asset.
Privacy boundary
There is no application server, telemetry, browser persistence, geocoding, AI API, or corporate-data upload. This file processes selected inputs in memory. CSV exports neutralise spreadsheet formula prefixes. Downloaded files remain on disk. The SharePoint edition places this workspace in an isolated frame without access to the parent page or SharePoint credentials.
The optional connections are public basemap streaming and browser tutorial narration. The map uses bundled MapLibre GL JS and OpenFreeMap; viewed map tiles reveal approximate geography to the provider. Optional voice narration prefers Google UK English Female (en-GB), falling back to a local English voice. A browser voice provider may receive fixed tutorial text; imported data is never spoken.
Libraries: SheetJS CE 0.20.3 (Apache-2.0); MapLibre GL JS 5.6.2 (BSD-3-Clause). See bundled distribution notices. Version 1.0.0 · 13 October 2026.