Custom IMOW integration development
Appfront builds integrations with the Information Model for the Environment and Planning Act (IMOW). This is used to annotate rules and policy in planning documents: which activity, which location, which standard. We connect your own systems to those objects: making or checking annotations before submission, and using OW objects from published documents in your own software, such as a permit system or a map viewer.
What is an IMOW integration?
Under the Environment and Planning Act (Omgevingswet), planning documents such as environmental plans, regulations and visions are published digitally and made available through the Digital Environment and Planning System (Digitaal Stelsel Omgevingswet). The text follows the standard for official publications. The Information Model for the Environment and Planning Act, IMOW, describes the objects used to annotate that text: which activity a rule concerns, which location it applies to, and which standard applies. Application profiles specify for each type of document how this must be done.
Annotating is precise work. A rule attached to the wrong location appears in the wrong place on the map. An error in the objects leads to a rejected submission. On the other hand, organisations want to use the annotated data: which rules apply to this plot, which activities require a permit here. That data sits in the system, but not in their own systems.
We build custom software because the integration must match your role: are you drafting documents and wanting to check or generate annotations, or do you want to use published data? Which planning software you use, which version of the standards applies, and how the result should reach your systems, we examine in the first step. The standards are managed by Geonovum and the national government; we make sure your software works with them.
Annotations that are correct
OW objects linked to the right text components, with activities, locations and standards as the application profile requires.
Checked in advance
Checks against the rules of IMOW and the application profile, so that a submission is not rejected.
In your own systems
OW objects from published documents in your permit system, map viewer or dashboard.
How we build your IMOW integration
We start with your role and your systems: whether you draft or use documents, which software you use, and where things currently go wrong.
Whether you draft or use documents, your planning software, the types of documents, and the version of the standards.
The OW objects you need, and checks against IMOW and the application profile.
Annotations for submission, or OW objects from the system into your own systems.
Testing with real documents, go-live, and management when new versions of the standards arrive.
What an IMOW integration concretely does
The components below come up in almost every IMOW integration. Which ones you need depends on your role.
OW objects
Rule texts, activities, locations, area designations and standards.
Annotating
Objects linked to the right text components.
Locations
Areas of operation and geometry for the rules.
Validation
Checks against IMOW and the application profile.
Reading out
OW objects from published documents for your own systems.
Audit log
A record, per submission or read-out, of what was done and with what result.
For whom we build IMOW integrations
The integration is intended for anyone who drafts or uses planning documents.
Municipalities
The environmental plan and amendments. Checking before submission is the core.
Provinces and water boards
Regulations with many locations. Areas of operation matter most.
Consultancies
Drafting documents for clients. Annotating is what is needed.
Users of the data
Permits, advice or property. Reading out to your own systems is the core.
Technology and integrations
This page is about integrations with the Information Model for the Environment and Planning Act. For the Environment and Planning Act in general, see our page on Environment and Planning Act software; for permits, our page on permit software; and for applicants, our page on an application dossier app. You can read about our way of working under custom software development.
If you want to check environmental documents against the application profiles before submission, see our page on a TPOD integration.
If you need to submit data on risk sources under the Information Model for External Safety, see our page on an IMEV integration.
If you want to use terms from a glossary in your own systems, see our page on a SKOS integration.
For submitting decisions and regulations to the LVBB, see our page on a STOP integration.
Why Appfront for your IMOW integration?
A rule in the wrong place on the map gives a resident the wrong answer. We build on that: annotations that are correct, checks in advance, and data that is usable in your own systems.
Fewer rejections
Checking in advance catches errors before submission.
Right on the map
Rules are tied to the correct locations.
Data you can use
OW objects in your own systems, not only in the system.
Security and privacy in an IMOW integration
The integration processes planning documents and draft versions that are not yet public. Access is set up by role, and every submission and retrieval 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 IMOW integration
Questions that governments and consultancies ask before starting.
The Information Model Environment Act (Informatiemodel Omgevingswet) describes the objects used to annotate the text of environmental documents, such as activities, locations and standards. It is used together with the standard for official publications and the application profiles per type of document.
STOP describes how official publications are drawn up and delivered. IMOW describes the objects that annotate the content. An application profile, TPOD, specifies for each type of environmental document which features of both must or may be used.
Yes. Before delivery, the OW objects are checked against the rules of IMOW and the application profile, with clear messages about what is missing or incorrect. This means an error is fixed before delivery, rather than after a rejection, when the schedule is already under pressure.
Yes, for published documents. Rules, activities and locations from the national system can be fed into your permit system, map viewer or dashboard, so you can see per location what applies. We will determine the right route in the first step. Changes to a document are tracked, so your systems show the same version as the national system.
Often, yes, provided that software has an export or interface. The integration complements what the planning software does not, such as a custom check or using the data in other systems. The planning software remains the place where the document is drafted.
The standards are regularly given new versions. In maintenance, we adapt the integration to them so your submissions and retrievals keep working.
For government bodies and consultancies that draft many documents and want their own checks, and for organisations that need data from environmental documents within their own processes.
Environmental documents with annotations that are correct?
Tell us whether you draft or use planning documents, which software you have, and where things currently go wrong. We will show you what the integration would look like.