Custom OAI inspection file development
Appfront builds files for building owners, managers and installers who manage or maintain emergency evacuation alarm systems: per building, the installation with its programme of requirements, certificate and inspection reports, maintenance and logbook entries, shortcomings 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 shortcoming doesn't disappear into a report in a drawer.
What is an OAI inspection file?
An evacuation alarm system (OAI, ontruimingsalarminstallatie) alerts the people in a building when they need to leave it. The Dutch Building Decree for the Built Environment (Besluit bouwwerken leefomgeving) sets out which buildings need such a system and requires it to be inspected periodically. Certification and inspection follow schemes managed by CCV. Each installation therefore builds up a file: 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 listing deficiencies arrives, gets forwarded and is lost. The installer knows whether a deficiency has been fixed, but the building manager may not. An organisation with many buildings cannot easily see when a certificate expires. And when the inspection body visits, everything has to be gathered together.
We build custom because the file must match 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 alarm system is connected, and which reporting your owner and competent authority require. What is mandatory for your buildings is determined by you together with your advisor or the competent authority.
One file per installation
Programme of requirements, certificate, inspection reports, maintenance and logbook for each building in one place, for the owner, building manager and installer.
Deficiency through to repair
Deficiencies from an inspection, with owner and deadline, tracked until they are repaired and the repair is documented.
Inspections planned ahead
For each installation, the date of the next inspection and the validity of the certificate, with 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, transferred from your folders.
Deficiencies with owner and deadline, and the logbook of faults, shutdowns and test alarms.
Inspection planning, advance notifications, reporting per building and across your portfolio, and ongoing management afterwards.
What an OAI inspection file does in practice
The components below feature in almost every OAI file. Which ones you need depends on your buildings.
Installations
For each building, the installation with its programme of requirements, implementation and components.
Certificates
Certificate and inspection reports, with dates and validity.
Deficiencies
Findings from inspections, with owner, deadline, repair and evidence.
Audit log
Faults, shutdowns, test alarms and maintenance, with date and who carried them out.
Planning
The next inspection and certificate expiry dates, with advance notification.
Reporting
Per building, and for the portfolio as a whole, the status of installations and deficiencies.
Who we build OAI inspection files for
The file is intended for anyone who manages or maintains evacuation alarm systems.
Property managers
Organisations with many buildings. Planning and deficiencies per building are at the heart of it.
Schools and care institutions
Buildings with many people. The logbook and repairs matter most.
Installers
Maintenance companies with many clients. A file per client and installation is what they need.
Municipalities
Owners of their own buildings and supervisors. Reporting per building is at the heart of it.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore 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 EVC inspection file?
An evacuation alarm has to work when it is needed. That is what we build around: a file that is accurate, deficiencies that get fixed, and inspections that do not get forgotten.
File ready
Everything is ready for an inspection: requirements, certificate, reports, maintenance and log.
Remediation you can demonstrate
A deficiency stays visible until the fix has been documented.
Portfolio at a glance
For many buildings, a single overview shows where a certificate is about to expire or something is still outstanding.
Security and privacy for an EVC inspection file
The file holds information about the safety of buildings and installations. Access is set up by role: the installer sees the installations under their maintenance, the manager sees their own buildings.
The file runs in a European data centre, with encrypted storage and daily back-ups. The log can also be kept up to date on a phone while on site.
Frequently asked questions about an EVC inspection file
Questions that building managers and installers ask before getting started.
An evacuation alarm system: the installation that warns people in a building when they need to leave, often combined with a fire detection system.
The Dutch Building Works in the Living Environment Decree (Besluit bouwwerken leefomgeving) sets out which buildings need an EVC and requires that it is inspected periodically. Certification and inspection follow schedules managed by the CCV. Which rules apply to your buildings is something you should establish with your adviser or the competent authority.
For each installation: the requirements specification, the certificate, the inspection reports, the maintenance records, the log, and the deficiencies with their remediation.
Yes, with their own access. The installer records maintenance and remediation, and the manager sees the status.
Every deficiency from an inspection report gets an owner and a deadline, and stays visible until the remediation has been recorded with evidence.
Yes. Where an EVC works together with a fire detection system, both can sit in the same file, each 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. Custom development makes sense for many buildings and several parties, or when deficiencies and the log need to stay under your own control.
An EVC inspection file that is ready for the inspection?
Tell us how many buildings and installations you have, who maintains them and where the file stands today. We will show you what the file, the deficiencies and the schedule look like.