Custom app for sewer inspection and pumping station rounds
An observation is made once: in the manhole, alongside the camera vehicle or at the pumping station. Everything after that is a derivative of it. Since 2020 the inspector no longer converts their observation into a class themselves, and that makes the demands on that single record higher than ever.
Why the field now has to capture more
In its March 2019 classification methodology, Stichting RIONED states that from January 2020 the application of the classification is decoupled: inspectors record in detail what they observe, and it is then up to asset managers to apply the classification. That shifts the weight: the judgement is made later, by someone who was not there, on the basis of what you wrote down.
Coding follows NEN-EN 13508-2, in the Netherlands the edition with the national part from March 2021. This standard describes the internal condition of pipes, manholes and inspection chambers in codes. A line consists of the condition aspect code with three characterisations, the third of which comes from the RibX protocol, and there are separate tables for pipes and for manholes. These are choices made at the time of observation that cannot be reliably reconstructed from a video afterwards. The old standards NEN 3398 and NEN 3399 were withdrawn on 28 January 2020.
Pumping stations are different, and that confusion trips up many tenders. The coding in NEN-EN 13508-2 applies to gravity-fed external sewerage; pressure mains and pumping stations fall outside its scope. So there is no national coding to fall back on for the pumping station round. What gets noted is whatever your own round prescribes, which is why pumping station rounds so often stay on paper: no file format enforces them.
How we build this
Here the input is the product. What an inspector has to tap in the manhole determines whether the file can later support a judgement.
Which objects, which observations, which fields are mandatory. For pumping stations nobody prescribes this, so you define it yourself.
Code, characterisations and extent are chosen at the time of observation and not reconstructed afterwards. For that, the input has to present the options instead of an empty field.
In a manhole, under a viaduct or out in the countryside, there is no coverage. That is the normal situation, so offline is the design, not the fallback.
A record is only finished once it arrives unchanged in the file where classification takes place. That is where things go wrong, and usually only becomes visible in the next round.
What the app actually does
Coding at the point of observation carries everything else. What you record alongside it depends on what you inspect.
Coding at the point of observation
Condition aspect, characterisations and extent in a single action. Whatever is not recorded here can no longer be classified later.
Identifying the object on site
A code on the manhole or pumping station opens the right object with its history. That puts an end to notes like "the manhole near the school".
Images with location and time
For an obstacle or a situation that does not fit a code. An image with a timestamp makes a record verifiable instead of disputable.
Works underground and along the road
Everything is stored locally and synchronised later, keeping the original timestamp. Nobody should have to wait for a bar of signal.
The pumping station round and its measurements
Running hours, levels, pump pattern and faults according to the round you define yourself. Because there is no national coding for this, configurability is not a luxury.
Escalating urgent issues immediately
Subsidence, a blockage or a pumping station that fails to start. That report should leave the field before the round is finished.
Who we build for
Whoever does the fieldwork determines where the emphasis lies. Four situations.
Inspection and cleaning companies
You supply observations on which someone else bases their judgement. If you also work on collection and cleaning, see waste collection and recycling.
Municipal outdoor services
Rounds along gullies, manholes and overflows alongside regular work. The question is not whether anyone is looking, but whether it comes back into the file. That file lives in the sewer software.
Maintenance of pumping stations and pumps
Electromechanical work in places with no coverage, with a round that differs per client. If it concerns water treatment, see water technology.
Consultancies and supervisory bodies
You walk along and want your samples in the same series as the contractor's. See also the inspection app.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
The coding has been revised and will be revised again, and a pumping station round differs per asset manager. Everything to do with codes, fields and rounds should be configurable.
If you clean gullies and want to record per gully what the crew found, take a look at our app for gully cleaning and route planning.
Why Appfront
Offline is the normal situation here
Manholes, embankments and rural areas have no coverage. We build offline as the starting point, preserving the original timestamp.
The choice belongs with the observation
We present the coding at the moment the inspector looks. Coding afterwards from images produces a series that differs slightly from what was actually there.
An object without a code is not an object
We code manholes and pumping stations so that an observation lands on the right object. Without that, merging remains manual work with errors in it.
We do not classify in the field
Since 2020, assigning classes has been the asset manager's job. We build the app that records, and leave the judgement where it belongs.
Security and privacy
What an inspector records is later used to allocate funds and weigh liability. Who can see what is therefore stricter here than with an ordinary work order: a contractor should see their own assignment, not a competitor's work. We set access per role, per assignment and per area, and log every access.
The integrity of the observation matters just as much. A record that can be quietly updated afterwards loses its value precisely when there is a dispute about what was visible in that manhole. We record observations, measurements and images immutably, with time, place and person, even when synchronisation happens later, and we turn a correction into a visible correction alongside the original value. How we handle security ourselves is set out in our information security policy; reports from outside go through our coordinated vulnerability disclosure policy.
Frequently asked questions about the sewer app
No. RIONED describes how, since January 2020, applying the classification has been decoupled: inspectors record in detail what they observe, and asset managers then apply the classification. If a client still asks you to supply classes, that is an agreement between the two of you and not a requirement of the standard.
Yes, that is the starting point. In the Netherlands this means the edition with the national part from March 2021. The old standards NEN 3398 and NEN 3399 were withdrawn on 28 January 2020. Because code lists are revised, we keep them configurable.
Yes, and here that is no side issue. In a manhole, under a viaduct and in rural areas there is no coverage. Everything is recorded locally and synchronised later, preserving the original time, because the moment of observation is part of the observation.
Yes, but on a different basis. The coding of NEN-EN 13508-2 applies to external gravity sewers; pumping stations and pressure mains fall outside that scope. There is therefore no national coding for the pumping station round. We build the round the way you have defined it, with the measurements and checkpoints you want in it, and keep it configurable.
They go to the asset management file, where the classification is applied and the planning follows from it. That is a different product; see the sewer software. We test the handover between the two with real files.
No. An inspection van has its own system for imaging and control, and we leave that alone. We focus on the work around it: rounds without a camera, manhole inspections, pumping stations and gullies. We handle data exchange through integrations.
Yes. Every client has its own requirements for what is recorded. We configure that per assignment instead of leaving your inspectors to remember which client wants which fields. If you want to add the maintenance work, see maintenance software.
That depends on the number of object types, whether the pumping station round is included, and whether data is exchanged with an existing asset management package. Coding with offline working is usually usable quickly; the data exchange takes more. We give a substantiated estimate after the discovery phase.
Want to know whether your field registration holds up as evidence?
Take an inspection from last year and see whether someone who wasn't there can assign a class to it without pulling up the video. If they can't, something was not recorded in the field. We build this as a standalone app and as part of a broader app development project.