Please note: The algorithm descriptions in English have been automatically translated. Errors may have been introduced in this process. For the original descriptions, go to the Dutch version of the Algorithm Register.
Fireworks dashboard
- Publication category
- Impactful algorithms
- Impact assessment
- Field not filled in.
- Status
- In use
General information
Theme
Begin date
Contact information
Link to publication website
Responsible use
Goal and impact
The aim is efficient deployment of boas on fireworks nuisance during the months of October to December.
Queries are used to unlock specific information on fireworks registrations. Reports from different nuisance categories are filtered to identify fireworks nuisances as best as possible. In this way, it is possible to filter mentions of fireworks nuisances from other nuisance categories, such as the youth nuisance category.
Information from reports are combined in the fireworks dashboard with information from the enforcement system. Postcodes, street names, neighbourhoods/neighbourhoods, weekdays and parts of the day are accessed and displayed (summarised) in the dashboard. In no case are personal data processed in the dashboard. Addresses (postcode/residence, etc.) of suspects or persons involved are not included in the dashboard. It concerns only data on date, time, location and other categories of nuisance.
Considerations
Every year, many nuisances are caused by fireworks outside the permitted times. Fireworks are used to commit vandalism, with damages to public spaces running into tens of thousands of euros every year. And besides the physical danger in setting off fireworks, it also generates many complaints. It is important that we can preventively monitor the early setting off of fireworks and also increase the chance of catching violations. This is only possible by anticipating as much as possible where and when violations occur. Responding immediately to a nuisance report is not always possible. In addition, there is a processing time between registering a report and picking it up, so the chance of being caught is virtually nil with this working method. This makes it more efficient and effective to deploy enforcers in an information-driven manner.
Human intervention
Registration of data is manual. No automatic decisions, forecasts or opinions are generated. The information in the fireworks dashboard is translated into deployment advice by the data analyst (employee).
Risk management
No risks are seen in using this dashboard.
Legal basis
Fireworks Decree 2.3.6 (domain I)
Links to legal bases
Operations
Data
Police reports, MOB (public outdoor space reports), situational observations from City Control software.
Technical design
The dashboard is a report in Cognos software. Queries are used to unlock specific information about fireworks registrations. Reports from different nuisance categories are filtered.
External provider
Similar algorithm descriptions
- By being able to enforce fireworks nuisance in a better and more targeted way, we can properly enforce the General Local Bye-Law (APV).Last change on 12th of July 2024, at 9:41 (CET) | Publication Standard 1.0
- Publication category
- Impactful algorithms
- Impact assessment
- DPIA, ...
- Status
- In use
- Smart deployment (optimal allocation) of road inspectors on the main road network based on historical and current incidents.Last change on 17th of May 2024, at 9:11 (CET) | Publication Standard 1.0
- Publication category
- Other algorithms
- Impact assessment
- Field not filled in.
- Status
- In use