NTA 8220 Often an insurance requirement Thermal image tied to the asset

Scope 10 inspection and thermography

Scope 10 is the inspection of electrical equipment for fire risk and is the practical application of NTA 8220. The outcome depends on thermal images, which are only usable if you can trace which asset they show and under what load. Appfront builds the software in which that image is tied to the asset rather than to the visit.

What a scope 10 inspection involves

Scope 10 falls under the SCIOS electrical equipment scheme and covers the inspection of electrical equipment for fire risk. The technical basis is NTA 8220, the Dutch technical agreement that describes how you carry out that assessment. Unlike scope 8, the scheme has no additional fields of work for scope 10, so it makes no separate distinction between an initial and a periodic inspection.

The question scope 10 answers is different from that of the installation inspection. There, the question is whether the installation complies with the standard; here, it is whether something poses a fire risk. That explains why thermography is so central: a connection that runs hot under load is one of the most reliable predictors of an incipient fire, and you will not see that from an insulation resistance measurement.

That creates the problem this software exists to solve. A thermal image on its own says little. It only becomes useful with its context: which asset, under what load, at what ambient temperature, and how it compares with similar points in the same cabinet. If that has to be pieced together at the office from a folder of images and a notebook, there is a good chance an image ends up with the wrong asset or the context is missing.

How we build your scope 10 software

We start with the measurement point. A file built up per visit cannot show how things develop over time, and that development is exactly what makes thermography valuable.

1
Recording measurement points and assets

Distribution boards, connections, busbar trunking, motors and the other assets you assess, each with its own identity. The images and findings are attached to it. Without that structure, comparing across the years is not possible.

2
Defining the context for each measurement

Which data do you record with each image: load at that moment, ambient temperature, emissivity, distance. This is the data that makes an assessment repeatable and that is requested during an audit.

3
Building in sprints

We work in sprints and start with the inspection itself. Your inspector takes an interim version on a real round early on; that is the only way to find out whether linking image to asset is fast enough.

4
Report and handover

We tailor the report format to what your client has to submit to their insurer. This is followed by a handover with a trial round in which we walk through a completed file with the questions your certification body would ask.

What the software actually does

Six components that turn loose images into a file. Which ones you need depends on the scale of the assets you inspect.

Thermal image tied to the asset

Every image is attached to the measurement point where it was taken, not to the visit. At the next inspection it sits alongside last year's image, so a change stands out that you would never spot in an isolated shot.

Context with every measurement

Load, ambient temperature, emissivity and distance are recorded with the image. Without that data, a temperature difference cannot be assessed and the measurement is not repeatable.

On-site identification

A code on the cabinet or asset opens the right measurement point and shows its history. In a switch room with twenty near-identical cabinets, this is what reliably prevents mix-ups.

Findings with urgency and remediation

A deviation is classified by urgency and stays open until the repair has been carried out and verified, ideally with a new image of the same point. That last step is what an insurer wants to see.

Interval per asset or location

The frequency follows from the policy condition or from your own risk assessment and can differ per location. The system schedules ahead and groups everything at the same location, so a round can be planned efficiently.

Report and client portal

The report is generated from the recorded data, with images placed where they belong. Your client retrieves it from a portal in which they see only their own locations, along with the outstanding findings.

Who we build for

Four situations in which scope 10 applies. The difference lies mainly in who pays for the inspection and why.

Certified inspection bodies

The core. If you also carry out installation inspections, it is the same system with different forms; see scope 8. For PV installations there is scope 12.

Work that stems from a policy condition

The majority of assignments. The insurer requires the inspection and wants to see that findings have been remedied. Turnaround time and traceability then weigh more heavily than depth.

Industry with its own electrical engineering department

Plenty of switchgear and motors, where a failure means immediate production loss. Here thermography is not only fire prevention but also predictive maintenance, which argues for a single system.

Real estate and institutions

Many buildings, each with a number of distribution boards. The question is one of central overview: which building was inspected when, and where is something still outstanding towards the insurer.

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 follows from how you work. Thermal images are large and switch rooms rarely have coverage, so offline storage and sensible handling of image sizes are design requirements, not afterthoughts.

If you want to keep the file for your fixed fire-extinguishing systems in order, take a look at our software for the inspection file of fixed fire-extinguishing systems.

Native iOS and Android Offline-first storage Thermal images with raw measurement data QR and NFC labels on cabinets Node.js / Python / .NET PostgreSQL Asset tree with measurement points Time series per measurement point Context with every capture PDF reporting with images Client portal per customer Integration with scheduling Audit logging of changes Hosting in the EU

Why Appfront

The image belongs to the point

Loose images in a folder produce a report that is useful only once. By linking each image to a measurement point, you build a series that says something about how things develop.

Context makes it repeatable

A temperature difference without load and ambient temperature cannot be assessed. We enforce that context at the time of capture, because it cannot be added afterwards.

Turnaround time matters commercially

Your client is waiting for the report for their insurer. By completing the file on site, the week of write-up between inspection and delivery disappears.

Alongside what already runs

Your scheduling and invoicing stay in place. We build the layer in between using integrations, so an inspection is never entered twice.

Security and privacy

The file contains little personal data, but it does record which inspector drew up which report and under which competence. That is needed to show that a qualified person did the work, and it also touches on their certification; we therefore focus reporting on the asset rather than on the inspector.

What weighs heavier is the nature of the information. Outstanding fire risks in your client's premises are sensitive towards their insurer and, after a fire, towards an investigator. Access is therefore strictly per client, with a portal that shows only their own locations. Images are timestamped and the underlying measurement data is kept exactly as it was recorded; a finalised report cannot be altered silently, and a correction is visible as a correction. That is not just an audit requirement: in a damage claim, this file becomes evidence. 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 scope 10

Scope 8 covers the fixed electrical installation and whether it meets the standard; scope 10 covers the inspection of electrical equipment for fire risk and is the application of NTA 8220. They sit within the same SCIOS scheme but answer a different question, and the reports look different. If you do both, we build one system with two forms on the same asset register; see also scope 8.

Not as a general legal obligation. In practice, the assignment usually stems from a policy condition: insurers make periodic fire-risk inspections mandatory for commercial premises. The usual obligations around safe work equipment and installations also continue to apply, and these partly run in parallel. We cover the employer side on the NEN 3140 page.

Because a temperature on its own says nothing. A connection at fifty degrees is normal under full load on a warm day and a cause for concern under half load in winter. Without load, ambient temperature, emissivity and distance, the image cannot be assessed or repeated. That is why we enforce this data at the time of capture; adding it afterwards is not an option, because by then nobody remembers it.

That follows from the policy condition and from the risk assessment of the asset; it is not a fixed interval set by law. In practice, we see cycles that differ per location and per asset type. Because the interval is not uniform, we make it configurable per asset or per location rather than per client, and the system plans ahead so that a round can be organised efficiently.

Usually yes, and it is worth doing because the raw measurement data is in the file. Besides the image, many cameras also store the temperature matrix and the settings, which makes it possible to redo an assessment later with a different emissivity. Exactly what is available differs per brand; we establish that during the discovery phase rather than promise it up front.

Yes, and here that is a requirement. Switch rooms and technical basements have poor coverage, and thermal images are large as well. The app stores data locally and syncs as soon as there is a connection, showing clearly which captures have not yet been sent. We explicitly design how image formats are handled, because a day of inspections quickly produces hundreds of captures.

Yes, and in insurance work this is the most requested feature. Each client gets a portal with their own locations, the reports and the outstanding findings with their urgency. Repairs can be reported there, after which your inspector verifies them with a new image of the same spot. That is exactly what an insurer wants to see, and it saves your back office a lot of email traffic.

That depends on how deeply you model the objects, whether the camera integration is included and whether a client portal is needed. The inspection app with images linked to the object is usually usable quickly; the portal and the camera integration cost more. We give a well-founded estimate after the discovery phase, once we know what equipment your inspectors work with.

Building a Scope 10 file system?

Tell us how many objects you inspect and how your images currently end up in the report, and we will help you think through the object register, the context for each capture and the portal for your client. We build this as a standalone application and as part of a broader project involving custom software or an app.

Edit content