WATER INSIGHTS — INTERNAL DATA EDITIONS
Evaluation release 1.0.0 | 13 October 2026

WHAT YOU ARE DOWNLOADING

Two ways to run the same internal-data workbench:
1. Portable: a self-contained HTML file opened on your computer.
2. SharePoint: a SharePoint Framework web part installed on an internal page.

The public Water Insights website supplies software downloads. It has no
corporate-file upload controls. Neither kit contains corporate records,
synthetic demonstration observations, credentials or an AI-service connection.
Both workbenches start empty. The existing public dashboard, 3D Atlas and
Intelligence Studio remain separate public-evidence tools.

QUICKEST FIRST TEST — PORTABLE

1. Download water-insights-portable-kit.zip from the Downloads page.
2. Extract all files into a local folder.
3. Read START-HERE.txt and DATA_DICTIONARY.md in the kit.
4. Open water-insights-portable.html in a current desktop browser.
5. Explore the empty interface and guide before selecting records.
6. When authorised, select a small CSV/XLSX export or WGS84 GeoJSON file.
7. Select the worksheet, match the fields and review validation before loading.
8. Inspect the reported period, missing values and evidence behind any prompt.

Replacing a table recalculates the workbench. It does not change the original
spreadsheet or automatically save a copy. Clear, reload or close to discard
the working session. Any files you explicitly export remain on your computer.

SHAREPOINT — ADMINISTRATOR HANDOVER

Give water-insights-sharepoint-kit.zip to the administrator responsible for
your SharePoint App Catalogue. Follow INSTALL.md in that kit to deploy the
packaged .sppkg solution, add the application to the intended site and place
the Water Insights web part on a page. A raw HTML file in a document library
is not the SharePoint installation method.

This release uses manual file selection in an isolated browser workspace.
It does not request Microsoft Graph permissions, automatically read document
libraries, connect to corporate GIS services or write anything back to the
tenant. Source and pinned build instructions are included for IT review.
Package build verification is separate from tenant installation testing.
Test the web part and representative authorised exports in your own tenant.

DATA BOUNDARIES

Imported tables, attributes, GIS geometry and calculations are held in the
workbench's page memory. The workbench has no upload route to the public site,
no telemetry, no generative-AI endpoint and no automatic browser storage.
Code can still be inspected by your IT team, and organisation/browser/device
policies continue to apply. Downloaded files do not retain SharePoint access
controls. Treat exports according to your organisation's data rules.

Online map backgrounds are optional and off initially. If enabled, the map
provider receives the geographic tiles requested and normal network metadata,
including IP address. Corporate rows and feature properties are not sent.
Keep the background off if the viewing area itself should not be disclosed.
The local GIS overlay and analysis do not require a public basemap.

Optional tour narration speaks fixed guide text only. The preferred browser
voice is Google UK English Female (en-GB) when available. Your browser may
send that fixed text to its voice provider. Imported data is never narrated.
Leave narration off to use the written guide without a speech service.

INPUTS AND MEANING

CSV/Excel: asset register, incident records and metric tables. Header-only
templates and a dictionary are included. Match your columns explicitly;
check units and time periods. Use a values-only .xlsx export: formula cells,
macros, external workbook links and encrypted files are rejected. The pilot
accepts files up to 8 MB, 10,000 table records and 60 columns. GIS is limited
to 2,000 features and 50,000 vertices; start with a scoped area export.

GIS: GeoJSON in WGS84 longitude/latitude (EPSG:4326), with stable asset IDs
for matching where available. Convert other formats with your approved GIS
tools. A map overlay does not establish hydraulic connectivity or affected
customers, and geographic context does not prove failure causation.

Investigation prompts explain the evidence in the imported extract. Counts
and repair summaries are not population-wide failure rates unless the inputs
establish the appropriate coverage/denominator. The application does not make
automatic operational, funding or causal decisions.

REFRESH AND NEXT STEPS

Use a replacement export to refresh the active session. Automatic SharePoint
library refresh and authenticated corporate GIS integrations are future
integration work requiring the organisation's supported endpoints and access
arrangements. They are not hidden dependencies of the supplied pilot.

Verify ZIP SHA-256 values against the Downloads page if required. The kits
include local build/check evidence. No GWW tenant installation or operational
data validation has been claimed without access to that environment.
Portable file opening and browser imports from end to end still require a
manual check: the automated browser environment permits HTTP previews only.
CSV/XLSX calculation checks used an existing approved public metric; those
populated check files are not included in either kit.

Water Insights is independent analysis tooling, not an official GWW service.
