In one environment, record which processes your organisation has, what they do and which applications support them.
Example Company B.V.
Example
Process
Handle request
Case management system
Document management
Planning
Process
Invoicing
Accounting
Email system
Process
Customer contact
manual work
This is what a map looks like: which application supports which process.
Sound familiar?
You have no up-to-date list of the applications in your organisation. A few colleagues know which system supports which process; the rest sits in scattered spreadsheets. With a tender, migration or audit, you work it out all over again.
Your processes and applications in one overview
You also see processes without an application, processes with several applications for the same work and applications that support no process.
All processes at a glance
You see the processes per department or domain, with owner and purpose.
Purpose and steps per process
For each process you read what it delivers and which steps it goes through.
Your application landscape
You see each application with its owner and supplier.
Process and application connected
For each process you see which applications support it. For each application you see which processes depend on it.
What you record
01
Processes
Name, purpose, owner and steps.
02
Applications
Name, supplier, owner and function.
03
The relationship
Which application supports which process or process step.
04
Links between applications
Which data one application passes to another.
How it works
Is your data already in another system, such as a service management tool? Then you connect that source to the platform.
1
You load your existing list of applications and processes using a spreadsheet template.
2
You connect each application to the processes it supports.
3
Owners of processes and applications add their own details through forms.
4
Dashboards and lists show the overview per process, application or department.
When you use this
Tender or contract renewal You see which processes an application affects before you decide.
Migration or replacement You see the impact before you start.
Audit or security assessment You show which applications support which processes and who the owner is.
Reorganisation or merger You put two landscapes side by side.
The rules
What you manage
Owners per process and per application
Forms that owners use to update their details
Lists per department, domain or target group
Email notifications when data is outdated or a field is missing
Who may see and change what
How much time does it take?
How quickly you have a first overview depends on your sources and your wishes. We determine that together in an initial conversation. You provide access to your sources and appoint a point of contact. Clappform connects the sources, checks the data and builds the overview.
Jij
Gives access to your sources and appoints a point of contact.
Clappform
Connects the sources, checks the data and builds the overview.
Built on the Clappform platform
Frequently asked questions
1
Do I need to record everything at once?
No. You start with the processes and applications you know and fill in the overview step by step.
2
Can I use my existing application list?
Yes. You load a spreadsheet using a template.
3
Who keeps the data up to date?
The owners of processes and applications, via forms. You get a notification when data is outdated.
4
Can I retrieve data from other systems?
Yes, you connect existing sources to the platform.
5
Does it align with a reference architecture?
Yes. The platform follows the Common Ground principles: reuse of data, a modular structure and open standards.
6
Who has already done this?
Several municipalities build their overview with the platform, such as Regio Alkmaar and the Municipality of Arnhem. Read the customer cases for the details.
Schedule a demo with your own list of applications and processes.