Building a TPOD integration
Appfront builds integrations compliant with the TPOD, the application profiles for environmental documents from Geonovum. For each type of document, such as the environmental plan, the environmental vision or a bylaw, an application profile describes how text is structured and annotated, how rules are linked to locations, and which value lists apply. We make sure your planning software or in-house system builds and validates documents according to the right profile, ready for submission together with STOP and IMOW, with no surprises at the end of the process.
What is a TPOD integration?
Under the Dutch Environment and Planning Act (Omgevingswet), environmental documents, such as a municipality's environmental plan, a province's environmental bylaw or a water authority's bylaw, are drawn up and submitted digitally. Standards exist for this: STOP for official publication, IMOW for information on areas of effect and rules, and the TPOD, the application profiles. For each type of document, an application profile describes how the standards are applied.
An application profile specifies, for example, how the text of an environmental plan is divided into chapters and articles, which annotations a rule receives, how a rule is linked to a location and which values from the value lists may be used. In practice, it often only becomes clear at submission that an annotation is missing or a value is not in the list. The document then has to go back, and the schedule slips.
We build custom solutions because authorities and systems differ: which documents you draw up, in which software, how text and map currently come together, and which versions of the profiles apply. The standards are managed by Geonovum and KOOP; we make sure your system works with them.
The right profile
For each type of environmental document, the application profile that applies, implemented in your software.
Checked in advance
Annotations, areas of effect and values checked before anything is submitted.
Together with STOP and IMOW
A document that is ready for submission in combination with the other standards.
How we build your TPOD integration
We start with your documents: which types you produce, which software you use to draft them, how text and map come together, and where submission currently gets stuck. The problems often lie in annotations and areas of effect. That is where we build checks that show what is missing while you are still writing, rather than only at the end.
Your document types, software, ways of working and bottlenecks.
Structure, annotations, areas of effect and value lists.
Checks against the profile, while writing and before submission.
Handover to submission, and maintenance as new versions are released.
What a TPOD integration actually does
The components below feature in almost every TPOD integration. Which ones you need depends on your documents.
Profiles
The right profile for each document type.
Structure
Text structured the way the profile requires.
Annotations
Rules annotated according to the profile.
Locations
Rules linked to areas of effect.
Value lists
Only permitted values.
Validation
Before anything is submitted.
Who we build a TPOD integration for
The integration is intended for anyone who drafts environmental documents or supplies the software for doing so.
Municipalities
The environmental plan. The annotations are the core.
Provinces and water boards
Bylaws. Getting the right profile matters most.
Consultancies
Plans covering multiple municipalities. The check is what you need.
Suppliers
Planning software. The profile built into the product is the core.
Technology and integrations
This page is about integrations according to the TPOD. For official publication, see our page on a STOP integration; for areas of application and rules, our page on an IMOW integration; and for the Omgevingswet (Environment and Planning Act) in general, our page on Omgevingswet software. You can read about our approach at building software.
Why choose Appfront for your TPOD integration?
An environmental plan that comes back at submission costs weeks. We build with that in mind: the right profile, checks while you write, and a document that is consistent and ready to go.
Right first time
Errors caught while writing.
Deadlines met
No document coming back.
Consistency
Profile, STOP and IMOW all line up.
Security and privacy in a TPOD integration
Environmental documents become public, but drafts and working versions are not yet. Access to drafts is set up per role, and every change 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 a TPOD integration
Questions that government bodies and suppliers ask before they get started.
The application profiles for environmental documents from Geonovum. For each type of document, such as the environmental plan, the environmental vision or a bylaw, a profile describes how the standards are applied: structure, annotations, linking to locations and value lists. This allows the Omgevingsloket (the national environmental permitting portal) to show rules by location to anyone who wants to build or do something.
STOP is the standard for official publications, and IMOW is the information model for areas of effect and rules. The TPOD describes, per document type, how the two are applied together. A document must comply with all three to be submitted.
The version that applies to your document and to submission. Profiles continue to be developed; in the first step we establish which version applies, and during maintenance we follow new versions. A new version may mean that existing annotations need to be adjusted; the integration shows which rules are affected.
A missing annotation or a value that is not on the list is spotted as soon as the rule is written, not only at submission. That lets the author fix it straight away.
If your planning software has an interface or extension option, we build the integration into it or alongside it. For suppliers, we build the profile into your own product. Where text is written in a word processor and maps are made in a GIS, we bring the two together so that rules and locations stay in sync.
The integration reports which rules or locations are incorrect, with the reason, to whoever can fix them. After the fix, the document is checked again, so it is delivered correctly the first time. That way the planning of a decision does not stall on a technical error.
For government bodies with their own systems for drafting environmental documents, for consultancies writing for several government bodies, and for suppliers of planning software.
Environmental documents that are right the first time?
Tell us which documents you draft, in which software, and where delivery currently gets stuck. We will show you what the integration looks like under the TPOD.