Custom IMEV integration development
Appfront builds integrations to the IMEV, the Information Model for External Safety (Informatiemodel Externe Veiligheid). Dutch authorities use it to record data on the storage, use and transport of hazardous substances, and that data is brought together in the Register for External Safety Risks (Register Externe Veiligheidsrisico's). We connect your own system to the register via its API, with validation against the model, so data is never keyed in by hand and is right first time.
What is an IMEV integration?
The Information Model for External Safety, the IMEV, describes how government bodies record data on external safety risks: the storage, use and transport of hazardous substances, and the surrounding areas that must be taken into account. This data is brought together in the Register of External Safety Risks. The model is managed under the auspices of Geonovum, and the register offers an API through which data can be submitted and validated against the model.
In practice, data about a risk source sits in the system of an environmental service or municipality, for example attached to a permit or an enforcement case. For the register, it is often still entered by hand or uploaded as a file. A change to a permit reaches the register late, or not at all. And an error against the model only surfaces at the check stage.
We build custom solutions because government bodies and systems differ: where the data currently sits, which risk sources you manage, how permits and enforcement are organised, and which version of the model applies. The model and the register are managed by others; we make sure your system works with them.
Following the model
Data on risk sources from your own system, translated into the IMEV.
Via the API
Submission and updates via the register's API, without manual entry.
Validated first
Every submission checked against the model, with errors returned to whoever can resolve them.
How we build your IMEV integration
We start with your data: where the risk sources are held now, who manages them, how changes are handled, and how they currently reach the register. Often not all the data the model requires is already in your own system. We map this out so it is clear what needs to be added at source.
Your risk sources, systems, managers and current submission process.
Your data translated into the IMEV, with validation.
Submission and updates, with feedback on errors.
Go-live, monitoring, and maintenance when new versions of the model are released.
What an IMEV integration actually does
The components below feature in almost every IMEV integration. Which ones you need depends on your role.
Translating
Your data into the IMEV.
Validating
Checking against the model.
Submitting
Via the register's API.
Updating
Changes to permits passed on immediately.
Retrieving
Data from the register for your own use.
Audit log
Every submission logged.
Who we build IMEV integrations for
The integration is intended for authorities and suppliers that manage data on external safety.
Environmental services
Many risk sources under management. Submission is the core.
Municipalities
Permits and enforcement. Updating matters most.
Safety regions
Data needed for advice. Retrieving is what is required.
Suppliers
Systems for government bodies. The model is the core.
Technology and integrations
This page is about integrations to the IMEV. For environmental services, see our page on software for environmental services; for the Environment and Planning Act (Omgevingswet), our page on an IMOW integration; and for information models, our page on MIM integration. You can read about how we work under getting software built.
Why Appfront for your IMEV integration?
A risk source that lags behind its permit in the register gives a misleading picture of safety. That is what we build on: data structured according to the model, submitted via the API, and validated before it is passed on.
Up to date
Changes appear in the register straight away.
Right first time
Validated against the model.
Less manual work
No manual data entry.
Security and privacy in an IMEV integration
Data on hazardous substances and risk sources is partly confidential. The integration supplies only what the register requires, connections are encrypted, and every submission is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about an IMEV integration
Questions that government bodies ask before getting started.
The External Safety Information Model: agreements on how government bodies record data on external safety risks, such as the storage, use and transport of hazardous substances. It describes which data is needed and how the pieces relate.
The data recorded under the IMEV is brought together in the External Safety Risk Register. The register has an API through which data can be submitted, and it validates that data against the model.
The version the register currently requires. The model continues to evolve; in the first step we establish which version applies, and during maintenance we track new versions. A new version may add or change data; we explain what that means for your source system.
From your own permit, supervision or case management system, where they are held alongside a permit or case. We map out what is missing so it can be added at the source.
The integration reports which data is incorrect, with the reason, to whoever can fix it. After correction, data is resubmitted. The log shows what has happened.
Yes, for your own use, for example to see which risk sources are nearby when reviewing a permit application. Which data is available depends on the register and your role.
For environmental services and authorities with many risk sources in their own systems, and for suppliers of permit, enforcement and case management systems who want to submit to the register. A supplier that builds the integration into its own product helps all its customers at once, without each authority needing its own integration.
Keep the register up to date, without manual work?
Tell us where your data on risk sources is held, who manages it, and how it currently reaches the register. We will show you what the integration would look like.