Custom OAI inspection file development
Appfront builds files for building owners, managers and installers who manage or maintain emergency evacuation alarm systems: for each building, the installation with its programme of requirements, the certificate and inspection reports, maintenance and logbook entries, deficiencies from inspections with an owner and a deadline, and the date of the next inspection. So the file is ready when the inspection body arrives, and a deficiency doesn't disappear into a report in a drawer.
What is an OAI inspection file?
An emergency evacuation alarm system (ontruimingsalarminstallatie, OAI) warns the people in a building when they need to leave it. The Dutch Building Decree (Besluit bouwwerken leefomgeving) specifies which buildings need such a system and that it must be inspected periodically. Certification and inspection follow schemes managed by the CCV. This creates a file around each installation: requirements, certificate, inspection reports, maintenance and a logbook.
In many organisations that file sits in a folder in the technical room or is scattered across mailboxes. An inspection report with deficiencies comes in, gets forwarded and is lost. Whether a deficiency has been fixed is known to the installer, but not to the manager. An organisation with many buildings doesn't know exactly where a certificate is about to expire. And when the inspection body arrives, everything has to be gathered together.
We build custom software because the file has to fit your buildings and your way of working: how many buildings and installations you have, who maintains and inspects them, how the logbook is kept, whether a fire detection system is linked to it, and what reporting the owner and the competent authority want. What is mandatory for your buildings is determined by you together with your adviser or the competent authority.
One file per installation
Programme of requirements, certificate, inspection reports, maintenance and logbook for each building in one place, for owner, manager and installer.
Deficiency to resolution
Deficiencies from an inspection with an owner and a deadline, until they are fixed and verified.
Inspections planned ahead
For each installation, the date of the next inspection and the validity of the certificate, with an advance notification.
How we build your OAI inspection file
We start with your buildings: how many installations there are, who maintains and inspects them, and where the file currently lives.
Your buildings and installations, maintenance and inspection parties, logbooks, and the reporting you need.
For each installation, the programme of requirements, certificate, inspection reports and maintenance, migrated from your folders.
Deficiencies with an owner and a deadline, and the logbook of faults, shutdowns and test alarms.
Inspection planning, advance notifications, reporting per building and portfolio, and ongoing management afterwards.
What an OAI inspection file actually does
The components below appear in almost every OAI file. Which ones you need depends on your buildings.
Installations
Per building, the installation with its requirements specification, implementation and components.
Certificates
Certificate and inspection reports with date and validity.
Defects
Findings from inspections with owner, deadline, remediation and evidence.
Log
Faults, shutdowns, test alarms and maintenance, with date and who was involved.
Planning
The next inspection and certificate expiry, with an advance notification.
Reporting
The status of installations and defects per building and across the portfolio.
Who we build an EWS inspection file for
The file is intended for anyone who manages or maintains emergency warning systems.
Property managers
Many buildings with installations. Scheduling and defects per building are the core.
Schools and care institutions
Buildings with many people. The logbook and remediation matter most.
Installers
Maintenance for many clients. What you need is a file per client and installation.
Municipalities
Own buildings and oversight. Reporting per building is the core.
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
This page covers evacuation alarm systems. For emergency lighting, see our page on inspection records for emergency lighting; for inspection reports, our page on SCIOS inspection reporting; and for the scheduling of an inspection company, our page on inspection planning. You can read about our approach at building software.
Why Appfront for your EWS inspection file?
An emergency warning system has to work at the moment it is needed. That is what we build on: a file that is accurate, defects that get fixed, and inspections that are not forgotten.
File ready
At an inspection everything is to hand: requirements, certificate, reports, maintenance and logbook.
Remediation demonstrable
A defect stays visible until the remediation has been demonstrated.
Portfolio at a glance
For many buildings, a single overview shows where a certificate is expiring or something is still outstanding.
Security and privacy for an EWS inspection file
The file contains information about the safety of buildings and installations. Access is set up per role: the installer sees the installations under maintenance, the manager sees their own buildings.
The file runs in a European data centre, with encrypted storage and daily backups. The logbook can also be kept up to date on a phone in the building.
Frequently asked questions about an EWS inspection file
Questions that building managers and installers ask before they start.
An emergency warning system: the installation that warns people in a building when they need to leave it, often combined with a fire alarm system.
The Dutch Building Decree (Besluit bouwwerken leefomgeving) determines which buildings need an EWS and that it must be inspected periodically. Certification and inspection follow schemes managed by the CCV. What applies to your buildings is something you establish with your adviser or the competent authority.
Per installation: the requirements specification, the certificate, the inspection reports, maintenance, the logbook and the defects with their remediation.
Yes, with their own access. The installer records maintenance and remediation, and the manager sees the status.
Every defect from an inspection report gets an owner and a deadline, and stays visible until the remediation has been recorded with evidence.
Yes. Where an EWS works together with a fire alarm system, both can be kept in the same file, with their own certificates and reports.
Check that first. Some maintenance companies have a portal with reports, and that is enough for a single building. A custom solution makes sense with many buildings and multiple parties, or when defects and the logbook need to be under your own control.
An EWS file that is ready for the inspection?
Tell us how many buildings and installations you have, who maintains them and where the file currently lives. We will show you what the file, the defects and the scheduling look like.