Custom e-Suite integration development
e-Suite is the case management system that many Dimpact municipalities use for case-based working. Dimpact is replacing it with PodiumD, a platform of open-source modules that works with the ZGW APIs. Appfront builds integrations between e-Suite and your line-of-business applications, and makes sure those integrations survive the move to PodiumD, so cases and documents aren't entered twice.
What is an e-Suite integration?
e-Suite is the case management system of Dimpact, the cooperative in which dozens of municipalities buy and develop their software together. A request, report or complaint becomes a case, with a status, documents and a case handler, so the municipality can show what happens to every request. Dimpact is replacing e-Suite with PodiumD, built from separate open-source modules that communicate with each other through the ZGW APIs.
Many line-of-business applications run around e-Suite, for permits, taxes, the social domain or public space. Where these aren't integrated, an employee retypes data, or a document is stored twice. And every integration that still talks to e-Suite the old way will have to be redone for PodiumD.
We build integrations that work now and keep working later. Where possible, we use the ZGW APIs, the national standard for case-based working, so the integration connects to PodiumD without rebuilding everything. We look at which route is open to your municipality, and when each module moves over, in the first step, together with you and, where needed, with Dimpact.
No duplicate work
Cases and documents once.
Line-of-business applications connected
Permits, taxes, social domain.
Ready for PodiumD
Built on the ZGW APIs.
How we build your e-Suite integration
We start with your municipality: which line-of-business applications run alongside the e-Suite, which data is still handled by hand, which integrations already exist and how they talk to the e-Suite. Then we decide the route for each integration: via the ZGW APIs where possible, and where that is not yet possible an interim solution that is easy to convert later. We often start with the application that involves the most manual work. The others follow, and we keep the integrations up to date as the e-Suite or PodiumD changes, so the move does not cost you new integrations.
Line-of-business applications, integrations and manual work.
ZGW where possible.
Cases, statuses, documents.
Go-live, monitoring, and the move to PodiumD.
What an e-Suite integration actually does
The components below appear in almost every e-Suite integration. Which ones you need depends on your line-of-business applications and where you are in the move.
Cases
Create and update.
Statuses
Passed on to the resident.
Documents
Stored once.
Line-of-business applications
Connected to the case.
ZGW APIs
The national standard.
Log
Every message recorded.
Who we build an e-Suite integration for
The integration is intended for municipalities that work with the e-Suite and have line-of-business applications that do not yet connect to it well, or that are preparing the move to PodiumD.
Municipalities
Many applications. One case view matters.
Partnerships
Multiple municipalities. One approach matters.
Implementing organisations
Shared tasks for municipalities. Sharing cases matters.
Suppliers
Connecting a line-of-business application.
Technology and integrations
This page is about integrations with the e-Suite and the move to PodiumD. You can read more about the standard itself on our page about the ZGW API integration, about older messages on our page about the StUF integration, and about your own case management system on our page about a custom case management system. You can read about our approach on custom software development.
Why Appfront for your e-Suite integration?
Data retyped between a line-of-business application and the case management system, and integrations that have to be rebuilt during the move, cost a municipality time and money. That is what we build on: cases and documents once, line-of-business applications connected, and integrations that move with you to PodiumD.
Less retyping
Data once.
One case view
Including from line-of-business applications.
Future-proof
On the ZGW APIs.
Security and privacy in an e-Suite integration
The integration processes data on residents and businesses, sometimes special category personal data from the social domain. We only use the data that is needed, access is restricted per integration, and every message is logged. We build in line with the Baseline Informatiebeveiliging Overheid (the Dutch government's information security baseline).
The integration runs in a European data centre or in your municipality's own environment, with encrypted storage and connections. We record the processing in a data processing agreement.
Frequently asked questions about an e-Suite integration
Questions municipalities ask before getting started.
The e-Suite is the case management system from Dimpact, the cooperative of municipalities that buy and develop software together. Requests, reports and complaints become cases, with a status, documents and a case handler, so the municipality can show what happens to every query.
Yes, through PodiumD, a platform of separate open-source modules for contact, forms, the portal and case handling, which communicate with each other via the ZGW APIs. That is why we build integrations to connect to that standard, so that they survive the switch.
The ZGW APIs are the national standard for case-based working in municipalities, with separate interfaces for cases, documents, decisions and catalogues. An integration built on them works with any case management system that supports the standard, including PodiumD.
In principle, any line-of-business application with its own interface, for permits, taxes, the social domain or public space. The integration creates cases, passes on statuses and stores documents with the case. What is possible per application, we look at in the first step.
Not always. An integration that already works via the ZGW APIs can often be carried over. An integration that communicates with the e-Suite in an older way, we convert. We determine what is needed per integration, so you don't have to do everything at once.
The integration reports it and records what went wrong. The message is retried or queued for review, so that no case or document is lost or created twice.
We build in line with the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline) and the agreements for case-based working. Access is restricted per integration, data is encrypted, and every message can be traced in the log.
Line-of-business applications connected to the e-Suite, and ready for PodiumD?
Tell us which line-of-business applications run alongside the e-Suite and where data is currently retyped by hand. We'll show you which route is available for each integration.