🆔Non administrative units in module organisaties

Formerly known as Module ondernemingen & verengingen

To comment on a FP:

Date, name: comment

Status Feature Passport

STATUSOWNERDATE

In proposal

Sofie

25/02/2024

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

ANALYSIS

Definition administrative unit

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

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: vzw's

?

For the related organisations of PEVA and VVMW we want to add the related non-administrative units. The business only wants to add basic data.

TO DO: check the SharePoint list 'LF Organisaties' and talk to the business

Current state

This is the state on QA, the changes are not yet visible in PROD

It was decided in FP 'Module Other related organisations' that we will not create separate modules for non-administrative units (create POC: OP-2466). We will add the non-administrative units to the existing module 'Bestuurseenheden' and change the text to Module 'Organisaties'.

Problems

1. We want to add non-administrative units as well so

  • we can add these organisations to the database.

  • we can relate them to via related organisations to administrative units.

2. Do we add one or two extra forms?

At the moment we have one form 'Bestuurseenheden'.

Do we have to add one or more extra forms?

  • one form:

    • Other organisations (Andere organisaties, which contains associations, corporations and feitelijke verenigingen)

  • more forms:

    • Associations & Corporations (Verenigingen en vennootschappen)

    • Feitelijke verenigingen

OP datamodel

Associations and corporations are both registered organisations and have a KBO number.

An exception is the 'feitelijke verenigingen', they are not registered organisations. Where do we put them?

🤩 Expectations

1. Add all new non-administrative units

  • Associations (Verenigingen)

  • Vennootschappen (Vennootschappen)

  • Feitelijke verenigingen?

Change add button = OP-3016

2. Menu items to show

Menu itemDEVComment

Kerngegevens

MVP

Vestigingen

MVP: maatschappelijke zetel + andere vestiging

Bestuursorganen

Not MVP

Maybe for some of the organisations in the future

TO DO: check with the business

Leidinggevenden

We will not sync with Loket, because no data is available (for now).

Veranderingsgebeurtenissen

Not MVP

We will probably not use this unless the business wants this.

TO DO: check with the business

When change events are not available, the status has to be editable in de 'Kerngegevens'.

Gerelateerde organisaties

MVP

Relations need to be possible between the administrative units and non-administrative units.

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. Page kerngegevens data

  • * = Mandatory field?

  • 📝 = Editable field?

  • Ass = Association

  • Feit = Feitelijke vereniging

  • Corp = Corporation

  • Representative Body

  • 🚘 = Autofill

Field*📝AssFeitCorpRepresentative body

Naam

✅🚘

Juridische naam

✅(1)

Alternatieve naam

Type organisatie: • Vennootschap • Vereniging • Feitelijke vereniging

❌ only one option = representatief orgaan

Status

OVO-nummer

❌🚘

KBO nummer

Adres

Busnummer

Provincie

Primair telefoonnummer

Secundair telefoonnummer

E-mail

Website

(1) Exception for municipality (gemeente) and Province (provincie), they are not editable in OP.

4. Page vestigingen

Fields idem as 'Autonoom gemeentebedrijf'

Two options type vestiging:

  • Maatschappelijke zetel

  • Andere vestiging

5. Filters

6. Onboarding of data

  • MVP: Organisations to onboard first:

    • Private OCMW-verenigingen (VVMW's) = OP-3027

    • Vereniging that are participants of OCMW-verenigingen (VVMW's) = OP-3037

  • Not MVP: Organisations to onboard second

    • See SharePoint list 'LF organisaties'

7. Sync of data

8. Module persons

  • not MVP: Positions created should appear also in the persons module.

🕵️‍♂️ Use Cases

  • We want to create relationships between all types of organisations

    • administrative unit can relate to another administrative unit

    • non-administrative unit can relate to an administrative unit

    • feitelijke vereniging can relate to an adminstrative unit

    • ...

🤔 Discussion points

  • One or two extra forms (see section problems) = OP-3039

  • Related organisations: Do we want to be able to add relationships via non administrative units, or only show them? We can add them via the administrative units.

  • NOT MVP: 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