🆔Module Other related organisations = no longer applicable
Formerly known as Module ondernemingen & verengingen
To comment on a FP:
Date, name: comment
Status Feature Passport
| STATUS | OWNER | DATE |
|---|---|---|
In proposal | Sofie | 29/05/2023 |
In refinement - Design Research | ||
In refinement - Technical Research/Feedback | ||
In development | ||
In QA/ Testing | ||
In Final state |
EPIC = OP-2392: MVP Module ondernemingen en verenigingen
TO DO:
Find a new name for 'Module ondernemingen & verenigingen' because it is confusing and it creates the wrong expectations. For now we will use 'Other related organisations'.
This module will contain all organisations that have a relationship with one ore more administrative units (bestuurseenheden), but that do not comply with the definition of an administrative unit. We do not just want to store all associations and companies.
Definition Administrative unit (LBLOD): Public, administrative organisation attached to a territorially defined area with certain responsibilities within which it can take administrative action.
ANALYSIS
This part of the feature passport is owned by the analyst
Current state
At this moment we have the module 'Bestuurseenheden' to add organisations.
The module 'Personen' contains positions that persons can have within the organisations that are registered in the module 'Bestuurseenheden'.
Problems
Not all organisations we want to add in OP can be defined as Administrative units.
Definition Administrative unit (LBLOD): Public, administrative organisation attached to a territorially defined area with certain responsibilities within which it can take administrative action.
Definitie Bestuurseenheid (LBLOD): Publieke, bestuurlijke organisatie verbonden aan een territoriaal omschreven gebied met bepaalde verantwoordelijkheden waarbinnen het bestuurshandelingen kan stellen.
ACM/IDM also uses the same definition to grant organisations access to Flemish government applications.
Local governments according to the decree of local governments
5° lokale overheden:
a) de gemeenten
b) de districten
c) de provincies
d) de openbare centra voor maatschappelijk welzijn
e) de samenwerkingsvormen, vermeld in deel 3, titel 3, van het decreet van 22 december 2017 over het lokaal bestuur;
f) de intergemeentelijke onderwijsvereniging, vermeld in het decreet van 28 november 2008 betreffende de intergemeentelijke onderwijsvereniging;
g) de welzijnsverenigingen, vermeld in deel 3, titel 4, hoofdstuk 2, van het decreet van 22 december 2017 over het lokaal bestuur;
h) de autonome verzorgingsinstellingen, vermeld in deel 3, titel 4, hoofdstuk 3, van het decreet van 22 december 2017 over het lokaal bestuur;
i) de verzelfstandigde agentschappen die opgericht zijn door een provincie of een gemeente;
j) de polders en de wateringen;
k) de besturen van de erkende kerk- of geloofsgemeenschappen van de erkende erediensten;
Examples of non-administrative units
Examples of organisations that we could not add because they do not meet the definition of an administrative unit:
| Type of organisation | # (est.) | What |
|---|---|---|
Representative bodies (= context of worship services) | 12 active 0 non-active | They are 'hard coded' available in OP, for example, 'Bisdom Hasselt' |
|
|
|
|
|
|
Interlokale vereniging NO MVP (business will decide if and when they want to have this in OP) | ? | This cooperation is mainly used for the realisation of projects limited in size. Among other things, it focuses on sports, libraries, tourism, etc. |
Other organisations to add | ? | TO DO: check the SharePoint list 'LF Organisaties' and talk to the business |
During the impactmapping of 27/06/2023 the classification of PEVA gemeente/provincie was challenged. This needs to be analysed.
TO ANALYSE = OP-2508: Follow up analysis which organisations aren't administrative units, but other related organisations
Conclusion of analysis:
Administrative units
PEVA gemeente
PEVA provincie
Opdrachthoudende vereniging met private deelname
No adminstrative unit
Interlokale vereniging
Consequences:
OP: We will add them in OP as 'administrative units' (bestuurseenheden), because they are compliant to the definiton that is used in the datamodel.
Loket voor Lokale Besturen: It is to be decided if they will have access in Loket voor Lokale Besturen, because according to the legal definition they are no administrative units (Pieter VH will contact the other 'Loketten' of Digitaal Vlaanderen to check this)
🤩 Expectations
1. Functionalities
We want the same functionalities and validations for the new module as in the module 'bestuurseenheden'.
2. Menu items to show
| Menu item | DEV | Comment |
|---|---|---|
Kerngegevens | ✅ | |
Vestigingen | ✅ | |
Bestuursorganen | ❔ | Not MVP Maybe for some of the organisations, not all of them. TO DO: check with the business |
Leidinggevenden | ❌ | We will not sync with Loket, because no data is available (for now). |
Veranderingsgebeurtenissen | ❔ | We will probably not use this unless the business wants this. Therefore we need the status to be editable in de 'Kerngegevens'. TO DO: check with the business |
Gerelateerde organisaties | ✅ | Relations need to be possible between the administrative units in module 'bestuurseenheden' and the organisations of the new module. |
Contactpersonen | ✅ | Not MVP This is a new menu item to register positions (persons) that are no 'leidinggevenden', 'mandataris' or 'bestuurslid'. This menu item is also interresting in the module 'bestuurseenheden', f.e. to register communications officers in a municipality. TO DO: check with business for requirements TO DO: check the SharePoint list 'LF Contacten' for the type of positions the business register so far. |
3. Onboarding of data
Organisations to onboard first, see table with the examples
Representative bodies > data is already hard coded in OP
PEVA gemeente > SharePoint list AGB/APB
PEVA provincie > SharePoint list AGB/APB
Organisations to onboard second
See SharePoint list 'LF organisaties'
4. Sync of data
To be discussed, check the section Discussion points
5. Module persons
Positions created in the the new module should appear also in the persons module.
🕵️♂️ Use Cases
See section expectations
We want to relate organisations from module 'bestuurseenheden' to the new module and vice versa
🤔 Discussion points
What is the smartest and most maintenance-friendly choice? List of pros and cons if applicable.
Do we need to create a separate persons module for positions created in the new module or can we add the data to the existing persons module? To check with Veronique.
New organisations created in LPDC (check with Loket Team) should we add them in OP or niet? To check with Veronique.
Do we want to sync with verenigingenregister?
If an end user creates an association, check if this exists already in verenigingenregister?
SOLUTION
The next two parts of the FP can [sometimes] be worked on simultaneously
Design
This part of the feature passport is owned by the designer
User research
[If there is any user research preceding the wireframe mock-up stage, it needs to be documented here]
Mock-ups
[link to figma mockups + any explanation or extra documentation]
Technical
This part of the feature passport is owned by the technical team
[Information about the technical solutions for expectations that need it - e.g. using mu-search for showing all types of positions in one table.]
After the designer and/or the technical team finish their task, a meeting follows where the solutions are presented. The team exchanges feedback and amends the feature passport where necessary.
Last updated
