Custom app for recording noise and vibration exposure
An employee's daily exposure is determined by two things: the level of what they operate and how long they do it. The first is in a measurement report. The second is recorded nowhere, because the roster shows who was there, not who stood next to the saw bench and for how long.
Where the dose really builds up
Above a daily exposure of 80 dB(A), hearing protection must be available; above 85 dB(A), wearing it is mandatory; and the limit value of 87 dB(A) applies at the ear, so with the protection factored in. For hand-arm vibration, the action value and limit value are 2.5 and 5.0 m/s², and for whole-body vibration they are 0.5 and 1.15 m/s².
All four of these values are doses over an eight-hour working day. That means the answer to whether someone exceeded them is not found in a single measurement but in a sum of time. And in most companies, that time is not recorded anywhere at the level that matters.
In practice, this disappears into the average. A department gets a single figure, and the employee who spends all day on the loudest machine vanishes into that same figure along with colleagues who rotate. If a hearing damage claim is made, that average is no justification.
Then there are the moments a daily dose does not capture. A peak is not an average: the peak action values are 135 and 137 dB(C), and a single bang can cause damage even if the rest of the day was quiet. If you want to record that, you have to do it at the moment it happens.
How we build this
The core is the task on the shop floor. Who performed which action and for how long, with the machine involved, is the input on which the entire calculation rests.
A code on the machine starts the task with the corresponding level, without anyone having to search through a list.
The time keeps running until the task is closed or handed over. That is more accurate than filling in an estimate afterwards.
A peak, faulty damping or missing hearing protection is reported at the moment itself, with an image attached.
The tasks land in the exposure file, where the daily dose per person is built up and checked.
What the app actually does
Recording the task and its duration carries the whole system. What else you need depends on how varied the work is and whether you use agency workers.
Start a task with a scan
A code on the machine or workstation opens the right task. If people have to search, they don't register.
Duration without estimates
The time runs alongside the work instead of being filled in afterwards, because an estimate after the fact always comes out too low.
Record a spot measurement
A reading from a handheld meter is saved together with the conditions, because without them a value cannot be properly assessed.
Report a peak
A bang or a blast disappears into a daily dose. The app records it separately, with the time and location.
Works without signal
Halls, basements and outdoor sites rarely have coverage. The app works locally and syncs as soon as there is a connection.
Check protection
Whether the required hearing protection was present and working is part of the exposure, not something for a separate notebook.
Who we build for
Who does the recording differs per company. Four situations.
Operators
They know exactly how long they stood somewhere, but only at that moment. A day later, it is an estimate.
Foremen
They allocate the work and so, in practice, determine who receives which dose.
Health and safety coordinators
They need data per person, and usually get an average per department.
Agency workers and rotating staff
Someone who joins for a week fits none of the fixed assumptions. That is exactly where the file breaks down.
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
Machines get replaced, tasks shift and standards are revised. Tasks, levels and units of measurement should be configurable and not hard-coded into the app.
Why Appfront
Time is half of the standard
A level without a duration is not a dose. We build the duration first, because that is exactly what is recorded nowhere else.
Filling it in afterwards comes out too low
Nobody overestimates how long they stood at a noisy machine. That is why we let the time run alongside the work.
A peak deserves its own record
What disappears into an average also disappears from the file. With us, peaks get their own track.
We don't carry out your measurements
Measuring and assessing remains the job of your occupational health and safety specialist. We make sure the data underneath is correct.
Security and privacy
Exposure data can be traced back to individual employees, and a record of who stood where and for how long is also a record of where someone was. That calls for restraint. We set access by role, show a foreman his own team rather than the rest of the company, and log every access. Whatever is stored locally on the device is encrypted and can be wiped remotely if a device is lost.
For this subject, the reliability of the moment is the whole point. A task duration that was shortened afterwards because the dose came out worse than hoped is no longer a record. We store tasks immutably with time, location and person, even when the sync happens later, and make a correction a visible correction alongside the original line. How we handle security ourselves is described in our information security policy.
Frequently asked questions about exposure registration on the shop floor
Because a roster says who was there, not who stood at which machine for how long. The daily dose depends on that second part, and it only arises on the shop floor.
No. A phone microphone is not a measuring instrument. The app records which task lasted how long and stores readings from your own meters, with the conditions alongside.
For noise, 80 and 85 dB(A) as action values and 87 dB(A) as the limit value at the ear. For hand-arm vibration, 2.5 and 5.0 m/s², for whole-body vibration, 0.5 and 1.15 m/s².
Yes. Production halls and outdoor sites rarely have coverage. The app works locally and syncs as soon as there is a connection again, preserving the original time.
In the exposure file, where the daily dose per person is built up and checked. We describe that file on our page about noise and vibration exposure software.
That is precisely the point. Scanning instead of searching and few fields, so that someone understands it in five minutes. See our approach to building an app.
Do you know how long your people stood at the loudest machine?
Take one team and one week, and try to work out per person how many hours were spent at which machine. If that cannot be established, your daily dose is an assumption. We build this as a standalone app and as part of a broader app development project.