Deelregeling stookinstallaties EBI, PI and PO On-site report

SCIOS inspection reporting, scopes 1-6

The SCIOS sub-scheme for combustion installations covers scopes 1 to 7 and 14, with three work areas per scope: initial special inspection, periodic inspection and periodic maintenance. Appfront builds the software in which your inspector records the report on site and in which the installation history is kept together per scope and per work area.

What the SCIOS scheme requires of your reporting

SCIOS manages a certification scheme with three sub-schemes: combustion installations, electrical equipment and explosion-proof installations. The first covers scopes 1 to 7 and 14. Scope 1 covers atmospheric heating boilers and indirect air heaters, scope 2 covers hot water boilers and air heaters with forced-draught burners, scope 3 covers steam and high-temperature hot water boilers above 105 degrees, scope 4 covers combustion engines and turbines, scope 5 covers special industrial installations and 5a covers solid-fuel installations, and scope 6 covers emission measurements.

The scheme also defines work areas that are just as decisive for your reporting: EBI for the initial special inspection, PI for the periodic inspection and PO for periodic maintenance. An installation goes through these in sequence, and the report looks different for each work area. For a number of scopes, including 6NOx and 14, the scheme has no additional work areas.

For software, this means a generic inspection app is not enough. The required fields differ per scope and per work area, and the installation data from the EBI must still be available at the periodic inspection years later. In practice, we see inspectors working with a word-processor template and the back office retyping it afterwards. That is where the errors arise that surface during an audit by your certification body.

How we build your SCIOS software

We start with the report format per scope and work area. Skip that, and you end up with an app that asks too much for half of the inspections and too little for the other half.

1
Defining scopes and work areas

Which scopes are you certified for, and which work areas do you carry out? For each combination, we determine which data is mandatory, which depends on the installation type and which is only needed in case of rejection. That is the core of the design.

2
Setting up the installation register

The installation is the anchor point, not the inspection. Capacity, fuel, year of construction, burner configuration and the scope it falls under, along with where it is located and which client it belongs to. Everything you need again later hangs off that.

3
Building in sprints

We work in sprints and start with the periodic inspection, because that is where the volume is. Your inspectors get involved and carry out a real inspection with an interim version early on; only then does it become clear whether a form is workable in a boiler room.

4
Report and handover

We align the report format with what your certification body assesses and what your client wants to receive. After that comes a handover to your back office, with a trial run in which we review a completed inspection as if we were the auditor.

What the software actually does

Six components that come up in almost every project. Which ones you need depends on your scopes and on whether you also carry out maintenance.

Forms per scope and work area

An inspection under scope 2 requires different data than an emission measurement under scope 6, and an EBI requires more than a periodic inspection. For each combination, the app shows only the fields that apply, so the inspector does not have to scroll through questions that are not relevant.

Recognising the installation on site

A code on the installation opens the right history: which scope, when the EBI took place, what was rejected last time and whether it has been fixed. In a boiler room with five boilers, that removes any confusion about which installation you are looking at.

Measured values with limits

Flue gas analysis, temperatures, pressures and, under scope 6, the emission values, with the limit that applies to that installation. A value outside the limit is visible straight away rather than only when it's written up at the office.

Defects and remediation

Every defect gets a classification and a status, and stays open until it has been remedied and verified. At the next inspection, the inspector can see what was found last time, which stops them reporting something that has already been resolved.

Deadlines per installation

The inspection interval follows from the installation type and its use, so it differs per installation. The system plans ahead, groups installations at the same location and alerts your planner well before the due date.

Report in your own format

The report is generated from the recorded data, signed by the inspector and stored with the installation. Your client receives it by email or collects it from a portal, and the back office has nothing to retype.

Who we build for

Four situations where this pays for itself. The difference mainly lies in whether you inspect for third parties or for your own installations.

Inspection and maintenance companies

The core case. You inspect for clients, your margin depends on turnaround time per installation and your certification is at stake in the annual audit. Often combined with a work order app that your engineers already use.

Industry with its own installations

Steam boilers, furnaces and dryers under scope 3 and 5, where you are certified yourself or hire in a certified party. If this ties in with your maintenance planning, inspection and maintenance happen in the same round.

Healthcare, education and government

Large building-related installations with an in-house technical department and a contracted maintenance partner. Here, being able to demonstrate compliance to the owner is at least as important as the inspection itself.

Managers of multiple sites

Property managers and facility service providers who manage on behalf of third parties, often alongside their facility management processes. Their need is a central overview across locations.

Not sure about a large project yet?

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

What we use depends on your situation. In a boiler room or a technical space there is rarely any coverage, so working offline is not a nice-to-have but a requirement; an app that does nothing there ends up being filled in from memory at the office.

If you manage fire alarm systems and want the file for each building in order, see our page on an OAI inspection file.

If you need to demonstrate for each inspection that the inspector was authorised for the scope, see our software for scopes and inspector qualification management.

Native iOS and Android Offline-first storage QR and NFC labels Node.js / Python / .NET PostgreSQL Forms per scope and field of work Import from measuring equipment Flue gas analyser integration PDF reporting with signature Integration with planning and invoicing Client portal Deadline alerts Audit logging of changes Hosting in the EU

Why Appfront

We read your certification scheme first

The required fields per scope and field of work are fixed. We adopt those rather than delivering a generic inspection app that you have to configure yourself.

Joining an inspection

Before we design anything, we spend a day on site. The difference between a form that works and one that gets skipped lies in details that nobody mentions in a meeting room.

Connecting to what you already run

Your planning, your invoicing and your measuring equipment stay as they are. We build the layer in between through integrations, so an inspection doesn't have to be entered in two places.

Honest about our role

We are not a certification body and we do not assess inspections. We build the system your inspector uses to record their work; the technical judgement remains theirs.

Security and privacy

An inspection file contains little personal data, but it does record which inspector drew up which report and under which competence. That is traceable to an individual and touches on their certification. We use that record for its intended purpose, namely demonstrating that a qualified person carried out the inspection, and we focus reporting on the installation rather than the inspector.

More significant is that you work with your clients' data: their installations, their defects and sometimes their production processes. Access is therefore set up per client, with a portal in which a client sees only their own installations. A finalised report cannot be changed silently: a correction is visible as a correction and does not overwrite the original, because a report that can be altered unnoticed after the fact has no value in an audit. How we handle security ourselves is set out in our information security policy; external reports go through our coordinated vulnerability disclosure policy.

Frequently asked questions about SCIOS reporting

Scopes 1 to 7, plus scope 14. Scope 1 covers atmospheric heating boilers and indirect air heaters, scope 2 covers hot water boilers and air heaters with fan burners, scope 3 covers steam and hot water boilers, scope 4 covers combustion engines and turbines, scope 5 covers special industrial installations, with 5a for solid fuels, scope 6 covers emission measurements and scope 7 covers fuel pipework. Scopes 8 to 12 fall under the sub-scheme for electrical equipment, and scope 11 under explosion-proof installations.

They are the work areas within the scheme. EBI stands for initial special inspection (eerste bijzondere inspectie): the inspection in which an installation is assessed for the first time and the baseline situation is recorded. PI is the periodic inspection that recurs after that. PO stands for periodic maintenance (periodiek onderhoud). For your software this distinction is decisive, because the report and the data required differ per work area. For some scopes, the scheme has no additional work areas.

Yes, and we recommend it if you are certified for several scopes. The inspector chooses the scope and work area, and then gets only the fields that belong to it. What you should avoid is a single form for everything, with fields that may or may not apply depending on the scope; that leads to empty fields where nobody can later tell whether they were not applicable or simply forgotten.

Yes, and for this kind of work that is a requirement. Boiler rooms, technical rooms and basements rarely have coverage. The app stores data locally and syncs as soon as there is a connection, showing clearly which reports have not yet been sent. What we explicitly design for is what happens when two inspectors have worked offline on the same installation.

In part, yes. Flue gas analysers and some measuring instruments supply data that can go straight into the report, so nobody has to retype it. What is possible depends on your equipment and on the interface the manufacturer offers; we establish that during the discovery phase rather than promising it up front. Where it is not possible, we keep manual entry as short as we can.

Your certification body checks whether you work in accordance with the scheme; our software provides the evidence that you do. We design the report format so that it contains what the scheme requires, and before handover we walk through a completed inspection as if we were the auditor. The assessment itself remains with your certification body and we do not interfere with it.

Yes. They fall under the electrical equipment sub-scheme and require different forms, but the installation register and the planning behind them are the same. We work out those scopes separately under scope 8 and scope 10, and build them into one system if you do both.

That depends mainly on the number of scopes and work areas you cover, because each one is a separate form. One scope with periodic inspection is a manageable project; five scopes with EBI, PI and PO is considerably more. Integrations with measuring equipment and invoicing come on top of that. We give a well-founded estimate after the discovery phase, not before.

Building SCIOS software?

Tell us which scopes you are certified for and how your reports are currently produced, and we will help you think through the forms per work area, the installation register and the integration with your planning. We build this as a standalone application and as part of a broader custom software or app project.

Edit content