Multi-Site Water Shop Monitoring with ADDAN5W

Map the treatment route at each outlet

Record the source, storage, treatment stages, dispensing boundary and any return or reject streams relevant to the project. Water shops can use different equipment or layouts, so a shared report needs an explicit map of what each point represents. The same label should not silently refer to different physical stages at different outlets.

Identify the operating question for each measurement. The customer may need visibility of supply continuity, filter-related operating conditions, tank recovery or unexplained quantity differences. The selected points should support those decisions rather than add readings that have no defined local response.

Connect the installed ADDAN5W arrangement

Use the actual ADDAN5W product and system information as the starting point, then verify the installed equipment and available interfaces. Record the model, configuration and point identities included in the proposed connection. A multi-outlet scope should identify any older or different arrangement that needs separate verification.

Keep supplied measurement functions distinct from the wider shop operation. Payment records, franchise administration or other business systems require their own confirmed interface and scope when requested. The monitoring proposal should describe the selected water and equipment records precisely, with the required integration evidence available before acceptance.

Verify source, production and dispensing quantities

Identify the physical boundary and unit for every meter. A source quantity, treated-water quantity and dispensing quantity can differ for legitimate process reasons. Retain storage change, reject or cleaning flows and other relevant paths before interpreting a residual.

Use aligned opening and closing periods and keep meter conversion, resets and replacement traceable. The central report should distinguish measured totals from estimates and unavailable intervals. A branch with missing evidence should remain visibly qualified instead of appearing to have zero use or perfect reconciliation.

Put filter and membrane events beside the readings

Record the maintenance activity, component identity, time and responsible person. Differential pressure, flow and other selected observations can help explain operating changes when their measurement points and conditions are known. A change in demand or valve position can also affect the pattern.

The responsible water-treatment and quality specialists determine how operating evidence informs maintenance and product decisions. A filter pressure trend does not establish that the produced water meets every quality requirement. Keep the appropriate analytical and quality records linked to their actual method and owner.

Create a branch record that staff can maintain

Give local staff a practical way to record inspection, cleaning, component replacement and an observed problem. The record should identify the relevant equipment and period without requiring a long narrative for every routine action. Preserve corrections and the person who made them.

A local exception should lead to a specific check. Staff need to know whether the issue concerns a stale reading, a supply interruption, an instrument comparison or a maintenance task. Central reviewers should see the response and finding, not only whether an alert was acknowledged.

Demonstrate the portfolio permission model

Define who can view one shop, several shops or the complete portfolio. Separate viewing, event correction and configuration permissions. Test the actual proposed accounts with representative records so the customer can verify that a branch user sees the intended information and central staff can carry out their review.

Confirm site onboarding, account administration and recurring services in the quotation. A shared dashboard does not remove the physical work, interface checks and local training needed at each outlet. The proposal should make those costs and responsibilities visible before the rollout schedule is agreed.

Accept one outlet and one additional configuration

The first trial should verify the installed points, source comparison, operating event and export. Include a communication interruption and demonstrate how current and recovered information are distinguished. The local manager should be able to identify the record and the action expected from staff.

Choose the next outlet to test a meaningful difference, such as equipment configuration, source arrangement or connectivity condition. Retain the extra mapping and installation work required. A rollout template becomes useful when it identifies both the common fields and the checks that remain specific to each branch.

Keep water-quality and service decisions accountable

The customer's responsible quality team approves applicable product criteria, analytical methods and disposition. The monitoring record can preserve selected observations and maintenance context, while the authorised team determines the conclusion. A central view should not imply that every outlet has completed the same quality procedure merely because its gateway is online.

Send the outlet list, treatment diagrams, installed ADDAN5W information, sample records and current maintenance process. Identify branch contacts, the central operating owner and the relevant water-treatment specialist. The proposed scope can then connect a manageable first rollout with the evidence required for consistent ongoing review.

Define a reproducible branch close procedure

Agree when an outlet's operating period is considered complete and which records must be present. The branch reviewer should confirm meter boundaries, maintenance events and any unresolved data gap before the central report treats the period as closed. Keep a provisional state where the evidence is still being reconciled.

If a late receipt, corrected event or recovered measurement changes the account, retain the original publication and the authorised revision. The central team should see the reason and affected outlet without having to compare screenshots manually. A clear close procedure also makes recurring gaps visible: a particular device, shift or record source can be investigated using repeated evidence. This is more useful than carrying an unexplained number forward until the next reporting period.

Plan installation, continuity and operating handover

The installation proposal should identify the field equipment, available interfaces, local power, mounting conditions and communication path for the accepted point list. Suitable LoRaWAN points with 4G backhaul are selected against the actual site survey and reporting requirement. The local team supplies access and the relevant specialist participation for the physical work and reference checks.

Before commissioning, agree what evidence each test should produce. Include point identity, unit conversion, an appropriate independent comparison and the handling of unavailable observations. Where the supplied architecture retains records during an interruption, verify recovery with original acquisition times. A recovered historical record and a live notification are separate functions in the acceptance schedule.

Handover includes installed photographs, the accepted configuration, operating instructions, an export demonstration and a list of open actions with owners. Assign routine instrument checks, user administration, communication service and the replacement process. A later change to equipment, operating conditions or reporting rules should have an effective date and a review of the affected acceptance evidence.

Compare the complete quoted scope

Request separate lines for equipment, configuration, installation, specialist verification and recurring services. Identify work supplied by the customer or an existing contractor, together with the access and information needed to complete it. The quotation should make the proposed result and each dependency understandable before procurement.

Use current quotations for the selected equipment and actual site arrangement. The project estimate should account for practical maintenance and replacement as well as first installation. Agree the initial acceptance boundary and the evidence required before extending the same configuration to additional assets or locations.

Connect the decision to the project

Use Water management, Addan5w, Water utilities to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.

Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.

Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.

Sources and method

The ADDAN5W page supplies existing product context. Measurement, maintenance and quality responsibilities are confirmed against the actual outlet equipment and customer procedures; no portfolio performance or universal compatibility claim is assumed.

Frequently asked questions