Building an app for on-site ZZS and PFAS registration
Companies with a permit report to the competent authority once every five years on which substances of very high concern they emit and what they do to avoid and limit those emissions. That report is filled with observations from five years. If you only start collecting them as the deadline approaches, you end up building it from emails and memories.
What must be recorded about SVHCs
Substances of very high concern (SVHC) are substances that are hazardous to people and the environment; PFAS and asbestos are well-known examples. Activities that require a permit come with a duty to provide information: every five years, the company reports to the competent authority which SVHC it emits to air and to water or the sewer, and which measures it takes to prevent and limit those emissions.
That report does not stand alone. It comes with an avoidance and reduction programme, which has to meet substantive requirements. The programme describes the options for avoiding emissions at source, for example by phasing out the substance or changing the process, and the options for reducing use and emissions in the current process.
These reduction options need information on the efficiency of the measure, its validation, and the reliability and cost of the technique. That is not a text you write in an afternoon; it is a collection of observations, measurements and considerations that builds up over years.
Emissions data is also recorded in an emissions database. What goes into it originates on site: at an emission point, during a measurement, in the event of a malfunction or when the process changes. An app does not solve the reporting, but it makes sure the observation is recorded at the moment someone makes it.
How we build this
The emission point is at the heart of it. A measurement without a point is just a number, and a point without a history is just a spot on a drawing. Everything that is observed is tied to the point where it was observed.
Each point gets its own place, with the substances that can be released there, the route to air or water, and the applicable requirements.
Measurements, malfunctions and visual findings are recorded at the point itself, with time, location and photo.
A measure that has been taken comes with its expected effect, its validation and the observations that follow. This way the supporting evidence grows along with it.
What has been recorded over the years forms the basis for the five-yearly report and for the programme, instead of a reconstruction after the fact.
What the app actually does
Recording at the emission point carries the whole. The rest depends on your processes and on whether you work with an in-house environmental coordinator or with a consultancy.
Opening an emission point
A code at the point opens the right record with its history, so an observation does not end up attached to a mere description.
Recording a measurement
Value, unit, method and conditions. What a measurement is worth depends on how it was taken, so that belongs with it.
A picture with the finding
A leak, a discolouration or a damaged seal is recorded faster with a photo than with a description.
Works without signal
Installations, cellars and outdoor areas rarely have good coverage. The app works locally and syncs later.
Escalating a discrepancy
An exceedance or a malfunction goes straight to the environmental coordinator, with the details needed to assess it.
Building towards the report
Observations are collected per substance and per point, so the five-yearly report comes from the records and not from a search.
Who we build for
Who makes the observation differs from company to company. Four situations.
Process operators
They are the first to see that something deviates. If recording takes more than a few actions, it happens at the end of the shift or not at all.
Environmental coordinators
They build the report and the programme, and don't want to reconstruct it from scattered files every five years.
Consultancies
Anyone reporting for multiple companies wants one way of working and observations recorded in the same way at every site.
Maintenance and technical services
A replaced seal or a modified installation is a measure. It should land in the same track as the measurements.
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
Substance lists are revised, measurement methods change and requirements differ per permit. Substances, points and input fields should be configurable and not hard-coded into the app.
Why Appfront
A measurement without conditions is just a number
How a measurement was taken determines what the value is worth. We record the method and the conditions alongside the result.
The observation belongs to the point
Not to the person, and not to the date alone. We build the recording around the emission point, because the reporting does the same.
Five years is too long to remember
The programme calls for substantiation over a long period. You either build that up as you go, or you invent it afterwards.
We do not assess your emissions
Whether a measure is sufficient is a question for your adviser and the competent authority. We make sure the observations are there.
Security and privacy
Emissions data is sensitive: it touches on permit conditions and on your relationship with the competent authority. We set access per role and per location, give a contractor only the points where they work, and log every access. Whatever is stored locally on the device is encrypted and can be wiped remotely if a phone goes missing.
For this subject, the reliability of the moment is the whole point. A measurement that was adjusted after the value turned out disappointing is no longer a measurement. We record observations immutably with time, location and person, even when synchronisation happens later, and we turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about SVHC registration
For activities that require a permit, a report to the competent authority is due once every five years, covering the SVHCs emitted to air and to water or sewer and the measures taken.
At a minimum, the options for avoiding emissions at the source, and the options for reducing use and emissions in the current process, with information on the efficiency, validation, reliability and cost of the technique.
Yes. PFAS is named as an example of a substance of very high concern, just like asbestos. Which substances are relevant for your site follows from your processes and your permit.
Because the observation happens at an installation, often without good coverage and with gloves on. Whatever can't be done there in a few taps gets filled in later and is then an estimate.
No. The reporting and the programme remain with the company and your adviser. We make sure the observations they are built from are recorded reliably.
Yes. Measurements and alerts can flow through to your maintenance system or environmental file. See our approach to building an app and to custom software.
Where is the measurement from three years ago?
Pick one emission point and ask for the observations of the past few years, with method and conditions included. If that turns into a search through mailboxes, your next report becomes a reconstruction. We build this as a standalone app and as part of a broader app development project.