🆔FP: Onboarding politie- en hulpverleningszone

To comment on a FP:

Date, name: comment

Status Feature Passport

STATUSOWNERDATE

In proposal

Hajar

24/7/2023

In refinement - Design Research

In refinement - Technical Research/Feedback

In development

In QA/ Testing

In Final state

ANALYSIS

Team that manages data politie- en hulpverleningszones: Gemeentefusies en Regiovorming’ (Beleidscoördinatie & Kennisorganisatie):

  • Nulens Thomas: Projectleider fusies en regiovorming

  • Thaens Norah: Regiovorming (alle vragen over actie beleidscapaciteit)

  • Gemeentefusies: fusies@vlaanderen.be

  • Regiovorming: regiovorming@vlaanderen.be

Data sources

1. SharePointLISTS (one time data conversion)

2. Vlaanderen.be

Data for both politie- en hulpverleningszones is being managed by team ‘Gemeentefusies en Regiovorming’ / Beleidscoördinatie & Kennisorganisatie and is available via Afbakening referentieregio's/ Overzichtstabel Vlaanderen Excel list.

3. KBO (List from KBO Select)

  • KBO list politiezones

KBO-Select_2023-07-27_KBO lijst politiezones.xlsx (= file on SharePoint OP)

The list has 113 politiezones

  • KBO list hulpverleningszones

KBO-Select_2023-07-27_KBO lijst hulpverleningszones.xlsx (= file on SharePoint OP)

The list has 20 hulpverleningszones

Comparison with other (authentic) sources is necessary since the SharePointlist and Vlaanderen.be list above are being managed and kept up to date manually. The number of politiezones in particular are different in all three sources. The number of hulpverleningszones do match in all three sources.

Hajar, 11/08/2023

  • Reached out to datadelivery@minfin.fed.be via mail requesting a list of all active 'Politie-en hulpverleningszones' in the Flemish region. - TBC

Hajar, 11/08/2023

Comparison of metadata in different sources - still ongoing

Hajar, 8/08/2023:

Politiezones: All 3 sources/ lists above show a difference in number of active politiezones in Flanders:

  • SharePointList: 107 politiezones

  • Vlaanderen.be: 106 politiezones

  • KBO Select list: 113 politiezones

--> Compared to the SharePoint list, the KBO Select list has 6 more Politiezones listed as 'active'. These 6 politiezones are also listed in the SharePoint list but as 'niet actief' and 'gefusioneerd' and therefore not included in the count of SharePointList filtered on active politiezones; hence the difference in numbers of active politiezones (KBO Select / SharePointList).

-> Difference between SharePointList and Vlaanderen.be list:

  • PZ_Mechelen_Willebroek_A

    • In Vlaanderen.be list (Regiovorming), Mechelen and Willebroek fall under 5913 PZ Rivierenland (this politiezone is mentioned in both lists).

Hulpverleningszones: The number of hulpverleningszones do match in all three sources. Please note that the name does not always correspond exactly in all three sources; but the match can be deduced from the name, (Vlaanderen.be = NIS and KBO Select= 'gemeentecode van de entiteit') and 'ondernemingsnummer' (KBO Select list) / 'KBOnr' (SharePointList) that it concerns the same hulpverleningszones in all three sources.

-->

--> Vlaanderen.be list compared with KBO Select list based on NIS codes = match.

  • SharePointList_LF: 20 hulpverleningszones

    • SharePointList_LF: 20 ondernemingsnummers but 1 double value:

      • ID: 1175; Title: HVZ BRANDWEER ZONE KEMPEN; KBOnr: 0500915126

      • ID: 1176; Title: HVZ 1 (WEST-VLAANDEREN); KBOnr: 0500915126

      --> 'HVZ 1 (West-Vlaanderen)' (according to KBO, Trendstop, Staatsbladmonitor) ondernemingsnummer: 0500929279

      --> Probably incorrect entry in the SharePointList_LF hence the double value.

  • Vlaanderen.be: 20 hulpverleningszones

  • KBO Select: 20 hulpverleningszones

Hajar, 17/08/2023 Discuss Comparison in Excel with Sofie (and Dries).

After alignment include analysis in Feature Passport.

Politiezones_Comparison

4. Federal Government

Politiezones dataset downloadportaal

  • Esri Shapefile Politiezone

  • FederalGovernment_Politiezones.xlsx

    • Shapefile converted to Excel but convertion didn't include any readable information about region/ municapalities, provinces, etc.)

  • Export_table_PZFederalGovernment_QGIS.xlsx

    • Used GIS-software (Geographic Information System) QGIS to read the Esri ShapeFile and create the attribute table in Excel, linking Flemish municipalities to politiezones.

    • Awaiting the file(s) with more metadata of the politiezones from the Federal Government:

      --> We can use this file to compare the Politiezones based on Names and amount with the other sources.

Hulpverleningszone (HVZ) dataset downloadportaal

Esri file = uitwisselingsformaat voor geografische informatie

5. GEO.be (partner federal government)

Politiezone dataset catalogus

Extra info + downloads

DESCRIPTION Policezones correspond to the dataset of the territorial delineation of the police zones as determined in the Royal Decrees of April 28, 2000, in accordance with the Law of December 7, 1998, regarding the organization of an integrated police service. This dataset consists of two classes. The first class contains the identification codes, names, and geometries of the different zones; the second class is a class without geometry and corresponds to the table of Belgian municipalities with the police zone to which each of them belongs. The dataset is freely available for download, in the form of zipped shapefiles.

  • Bronidentificatie Namespace: GADP Code datasource : 6c119b1e-e89f-11ec-ba9e-9453308970f2 Data of data revision: 15-06-2022

ACCESS

METADATA DESCRIPTION POLITIEZONE

Hulpverleningszone dataset catalogus

Extra info + downloads

DESCRIPTION Rescue zones correspond to the dataset of the territorial delineation of the rescue zones as determined in the royal decree of February 2, 2009, establishing the territorial delineation of the rescue zones in accordance with the law of May 15, 2007, regarding civil security. This dataset consists of two classes. The first class contains the identification codes, names, and geometries of the different zones; the second class is a class without geometry and corresponds to the table of Belgian municipalities with the rescue zone to which each of them belongs. The dataset is freely available for download, in the form of zipped shapefiles

RD (KB) February 2, 2009: https://www.civieleveiligheid.be/sites/default/files/2009-02-02kb_ii_hulpverleningszones_8.pdf

  • Source Identification Namespace: GADP Code source data: 69e433cf-e89f-11ec-8ae3-9453308970f2 Date of data revision: 19-07-2023

ACCESS

  • Formaten en projecties Distributieformaten: Esri Shapefile Projectiesystemen: EPSG:3812, EPSG:31370Representatietype: vector

METADATA DESCRIPTION HULPVERLENINGSZONE

Sofie: Conclusion on numbers:

  • PZ Politiezone active = 106

  • PZPolitiezone not active = 23

  • HVZ Hulpverleningszone active = 20

  • HVZ Hulpverleningszone not active = 0

In the SharePointlist LF Organisaties we have 6 PZ from Brussels. The business confirmed during workshop (23/8/2023) that we will not onboard them in OP.

Organisation classificiaton

Full overview in Miro: https://miro.com/app/board/o9J_liK62Ew=/?moveToWidget=3458764527105216489&cot=14

Politiezones (PZ)

The local police is organized by politiezones. Some politiezones contain only one municipality, others consist of two or more municipalities

Through various royal decrees, each municipality was classified into a politiezone.

In single-municipality zones, the municipal council, mayor, and college of mayor and aldermen (schepenen) exercise the powers provided for in the municipal law regarding the organization and management of the police force.

The powers of the college of mayor and aldermen and of the mayor regarding organization and management are exercised by the police board (politiecollege).

In multi-municipality zones, the powers of the municipal council regarding the organization and management of the local police force are exercised by the police council (politieraad).

One politiezone can contain several NIS-codes. Based on the politiezone data in the KBO Select list and the list from Vlaanderen.be we can conclude that politiezones could cross municipalities and districts (arrondissementen) but do not cross provinces.

The NIS code is a 5-digit code for geographical areas in Belgium. The first digit indicates the province, the second digit indicates the district (arrondissement) and the last three digits represent the municipality. Municipality codes can be accessed through Statbel.

Flanders is divided into politiezones with zone codes ranging from 5345 to 5462

Mapping PZ

Hulpverleningszones (HVZ)

De hulpverleningzones are the organisational structure of the fire services. More information is available via https://www.civieleveiligheid.be/nl/zonewerking

Mapping HVZ

New fields = are being refined

To discuss with the business which new fields are needed.

Probably valuable to add NIS codes and Zone codes as new fields?

Applicable to all administrative units (see the same item in FP AGB/APB and FP IGS)

  • Naam volgens KBO

  • Verkorte naam

  • Naam volgens statuten

Name discussion

  • Which source are we going to use regarding the name of politie- en hulpverleningszones? - to discuss with business.

  • Hulpverleningszones: minor name differences in the three sources:

    • 'HVZ' instead of Hulpverleningszones

    • 'Brandweer' instead of 'HVZ Brandweer xxx'

  • Politiezones: more significant differences in the three different sources.

During the KAR workshop (23/8/2023) the following patterns were defined

For PZ

PZ + collective name or municipality(ies) + enumeration of municipalitities

  • PZ HEKLA: Hove, Edegem, Kontich, Lint en Aartselaar

  • PZ Aalst: Aalst

  • PZ Assenede/Evergem: Assened en Evergem

For HVZ

HVZ (without 'Brandweer) + name

Werkingsgebied

NO MVP

See OP-2672: Refinement of field 'werkingsgebied'

📁 MODULE Bestuurseenheden

If not specified, the requirements for PZ and HVZ are the same.

Search page

https://organisaties.abb.lblod.info/bestuurseenheden

Filters

  • Soort eredienst Don't show this filter when one of the new administrative units is selected.

  • Type bestuur: add the options

    • Politiezone

    • Hulpverleningszone

Apply contextual filters where possible.

Columns in results table

  • Naam (default sorting)

  • Type bestuur

  • Provincie

  • Gemeente

  • Status

Kerngegevens (core data)

Fields

FieldsMandatoryEditableComments

Naam*

✅

✅

Type bestuur*

✅

❌

Regio*

auto

❌

Derived from primary address Will be added automatically in the geographical relationships

Status*

✅

✅

KBO nummer

✅

✅

Validation: you can only add a KBO number once. If a double KBO number is registered, show the link to the organisation that has the KBO number

SharePoint identificator

❌

✅

Link to the SharePoinlist Organisaties

OVO-nummer

auto

❌

Do not show on edit page

Adres*

✅

✅

CRAB functionality

Straat*

✅

✅

Manual input of address

Huisnummer*

✅

✅

Manual input of address

Busnummer

✅

✅

Manual input of address

Postcode*

✅

✅

Manual input of address

Gemeente*

✅

✅

Manual input of address

Provincie*

✅

✅

Manual input of address

Country

✅

✅

Manual input of address

Primair telefoonnummer

❌

✅

Add standard helptext under input field

Secundair telefoonnummer

❌

✅

Add standard helptext under input field

E-mail

❌

✅

Add standard helptext under input field

Website

❌

✅

Add standard helptext under input field

Vestigingen (sites)

Set up the same as the other administrative units.

Type of sites:

  • Maatschappelijke zetel

  • Hoofdcommissariaat (this option was added on 25/10/2023, see ticket OP-2795)

  • andere vestigingen? - to discuss with business

The address of the 'maatschappelijke zetel' should be the address that is in the LF list.

❌ Betrokken Lokale Besturen (local involvements)

Betrokken lokale besturen where created specifically for worship services.

We will extend the related organisations with different type of relationships so we can display the relationship with local governments in the related organisation's menu-item

❌ Bestuursorganen (governing bodies)

For now we will NOT show the governing bodies in OP and we will NOT capture 'mandaten' or 'bestuursleden' or 'leidinggevenden'.

We will create governing bodies, but hide them for the end users.

This might change in the future because a new proposal to change the decree is in the making.

The governing bodies should be developed, it's needed for the 'Leidinggevenden', but not be shown on the page.

❌ Leidinggevenden (executives)

Set up is not the same as the other administrative units.

This info should be provided by the business departement Gemeentefuses en Regiovorming

There are no 'leidinggevenden' saved via Loket and the business don't want to register them at the moment.

Veranderingsgebeurtenissen (change events)

Type of change event > Resulting status

  1. Oprichting > Actief

  2. Naamswijziging > Actief

  3. Wijziging werkingsgebied > Actief (= new change event) NON MVP

  4. In ontbinding > Actief

  5. In vereffening > Actief

  6. Ontbonden en vereffend > Niet actief

  7. Fusie > Actief OR Niet actief

    • MVP?

    • Variations possible for merger of politie- en hulpverleningszones (resulting from a merger of 2 or more municipalities or separate from this - e.g. mergers to join forces in order to work more efficiently):

      • One zone can take over the other zone. One zone stays active, and the other zone(s) that is/are part of the merger all get the status non-active.

      • All zones that are part of the merger get the status non-active and a new zone with an active status will be created

    • Frequency of mergers for politiezones can be multiple per year. Mergers of hulpverleningszones are less frequent.

We will not provide the merger change event to endusers because:

For PZ

  • Untill now the mergers only take place once a year, usually at the first of january (same as mergers of municipalities). The mergers of PZ are not caused by mergers of municipalities, but there might be cases in the future.

For HVZ

  • There hasn't been a merger of HVZ yet, but there might be in the future.

When a merger take place the developers will do this manually via the backend.

Question NO MVP: Can we foresee the option 'fusie' (= merger) and show the text 'Please send a mail to the helpdesk with all necessary information regarding the merger.':

  • Type veranderingsgebeurtenis

  • Beschrijving

  • Link naar besluit

  • Datum veranderingsgebeurtenis

  • Betrokken organisaties (+ resulterende status)

Fields change events

Foresee the fields on the printscreen for all 6 change events.

To check with the business: Will they add the 'oprichting' change event retroactively for PZ/ HVZ (same for IGS and AGB/APB), or only adding this for new PZ/HVZ that are created. (zo ja, kan de business deze data aanleveren?) - ook voor de andere

Adding change events retroactively

Not MVP. The business wants to add the change events retroactively, but they have to provide the data to accomplish this.

TO DO Sofie: request the missing data from the business

For PZ

  • Oprichting

  • Naamswijziging

  • Fusie

For HVZ

  • Oprichting

  • Naamswijziging

Gerelateerde organisaties

  • a province

  • a municipality

In the future automatically via geographical relationships.

Validation rules > not to implement, we can check this via queries = no MVP

Question: Should we implement this validation rules or should we check this via queries? - MVP

  1. One politiezone could cross municipalities and districts but do not cross provinces:

    • First digit of all the NIS-codes linked to one politiezone should be the same.

    • Second digit (indicates district) and the last 3 digits (indicates municipality) of all the NIS-codes linked to one politiezone can be different.

= No hard validation, just a warning (since this is only based on KBO Select and Vlaanderen.be list. SharePoint list doesn't include NIS-codes/ gemeentecodes)

  1. One politie- of hulpverleningszone can encompass one or multiple municipalities, but a municipality cannot have multiple politie- of hulpverleningszones.

= Hard validation

📁 MODULE Personen > not applicable at the moment

Search page

https://organisaties.abb.lblod.info/personen

N/A? - hangt af van leidinggevenden en bestuursorganen - gaan we die al dan niet opnemen? - to discuss with business

Contactgegevens

Posities

🤩 Expectations

🕵️‍♂️ Use Cases

🤔 Discussion points

1. How can we capture new politie- en hulpverleningszones in the OP?

LOW is responsible for these administrative units. To discuss with them in depth.

2. Who will be the editors for politie- en hulpverleningszones in OP?

LOW > names?

3. Should we add the 'oprichting' change event retroactively for PZ/ HVZ (same for IGS and AGB/APB), or only adding this for new PZ/HVZ that are created?

See section change events

4. New fields

  • Probably valuable to add NIS codes (for both HVZ and PZ) and Politiezone codes (only PZ) as new fields?

  • See section new fields

5. Leidinggevenden (executives)

Set up is not the same as the other administrative units.

This info should be provided by the business departement Gemeentefuses en Regiovorming

6. Name discussion

Which source are we going to use regarding the name of politie- en hulpverleningszones?

Fixed patterned is defined during the KAR workshop

See section new fields

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.

PreviousIGS conceptnota (NL)NextFP: Onboarding OCMW-verenigingen

Last updated