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.

Selection aid WBU table

The WBU table indicates within which time windows, which traffic restriction measures may be taken by contractors, for maintenance on Provincial roads. This is determined by: The capacity and minimum required residual capacity of the site; the time of day (day, hour); the effect of the type of traffic measure on capacity.

Last change on 29th of May 2024, at 10:53 (CET) | Publication Standard 1.0
Publication category
High-Risk AI-system
Impact assessment
Field not filled in.
Status
In development

General information

Theme

Space and Infrastructure

Begin date

Field not filled in.

Contact information

Voor vragen en opmerkingen kan je terecht bij: digitaalzuidholland@pzh.nl. Wil je bezwaar maken, dan kan je terecht bij de Juridische afdeling van dienst beheer organisatie. https://www.zuid-holland.nl/contact/

Link to publication website

De (tijdelijke) URL is: https://c6ae6fa2db7da44c79581d7e.azurewebsites.net/ Er komt nog een URL waarmee eerst via PZH netwerk moet worden ingelogd. Tevens is het (nog) niet de bedoeling dat deze URL door externe wordt gebruikt. In eerste instantie wordt de WBU doorvertaald in een tabel (zoals nu ook het geval is).

Link to source registration

Niet bekend.

Responsible use

Goal and impact

Using historical data, this algorithm allows you to see what type of closure and traffic measure can be applied to a road. You can also see which times are suitable. The WBU table selection tool is used in part to create the WBU table.


It contributes to reducing operational costs and increasing traffic safety.


-Increasing road safety The CROW96b provides calculation methods to determine at which traffic intensity at which traffic measure may be applied. The current WBU table does not take this into account. Because a web application displays the WBU per type of traffic measure, the requirements from the guideline are always met. This keeps traffic safety guaranteed.


-Operational costs Unlike the old WBU table, the web application makes it possible to calculate the WBU per day. Experience shows that the traffic pattern on a Wednesday and Friday is significantly quieter than on a Tuesday or Thursday. The case study below shows the financial implications of this. Our DBO contractor has scheduled mowing works throughout December in the Hoeksche-Waard. The work will be carried out in accordance with a half lane closure (Fig 1323b). The old WBU table indicates that the WBU is between 09:00 and 15:00. The web application to be created indicates that on Mondays, Wednesdays and Fridays, work can be done from 09:00 to 16:00. This implies that the contractor can work an extra 3 hours per week. This is therefore 12 hours extra per month. By having an extra 12 hours of working time, the contractor will not have to hit the road as often. Assuming that the work is carried out through a pre-warning truck, action truck and end truck, this saves the rental and operational costs of three work vehicles and three drivers. This can save money. This is just an example of one contractor at work. Around 2,400 TVM applications are submitted every year. By applying the WBU application, a large proportion of these applications can probably be processed more efficiently and save costs.

It is plausible, that thanks to the WBU web application, traffic congestion is reduced. This will also save social costs in the form of fewer vehicle loss hours.

Considerations

With the algorithm, there is less disruption for road users. In addition, road safety is increased because the CROW96B guideline is met. There is less congestion and fewer vehicle loss hours.

Human intervention

We are currently testing out the application. We are checking whether it matches our own and road inspectors' findings. In this way, we are trying to filter out any bugs from the tool. The web application is being tested based on our own findings and counts.

Risk management

The following risks have been identified:

- Data of traffic loops is not covering the entire road network of the province > state of play Nov 2021: NO RISK.


Initially, it was uncertain whether sufficient data would be available to predict traffic volumes on all provincial roads. However, based on NDW data and data from the SWUNG2 model, traffic intensities can be predicted per 100-metre road section. The methods behind this, are based on the methods from the noise and air calculation model and thus already proven.


-Calculation rules from CROW cannot be applied > state of play Nov 2021: NO RISK


Within the province of Zuid-Holland, five different deposition methods are used for daily management and maintenance. Using the methods from CROW96b, it is relatively easy to determine, based on traffic intensities, when which barrier can be applied. Point of attention is that we still need to properly mirror these methods with the current WBU.


-Problems during further software development > state of play Nov 2021: SMALL RISK. Risks are tracked and monitored in progress reports.

Legal basis

The algorithm gives an advice/prediction. But it takes into account the applicable guidelines of CROW 96B and APV (general local bye-laws) laid down. And the conditions of Melvin(Reporting disruptions of Infrastructure in the Netherlands).

Operations

Data

- Intensities from NDW traffic data, with interpolation) at certain times of day

-Loop data (how fast traffic drives, how long a vehicle is, to distinguish between truck and passenger cars; intensities)

- Information trajectories with how many lanes and maximum speed

- Planning data in Melvin

- SWUNG 2 model

- Floating car data

Technical design

Operation of the model (2022):

We indicate:

-Which N-road it concerns

- Start and end point indicated in hectometrics

- The type of traffic measure (change lane with right of way)

- The date


We get back:

- An overview of the time periods (per half hour), including a red/green score for each time period on workable hours for the whole week

- The historical profile determines the score of the time periods.

- The historical profile per time period is calculated based on the same time and weekday, of the past weeks (growing history since June 2021)

External provider

Internally developed

Link to code base

Is er nog niet (nov, 2022)

Similar algorithm descriptions

  • The Wmo prediction model provides a prediction of the number of unique users with a prediction horizon of five years. Predictions are made at district level for both the Wmo total and sub-products of the Wmo (Help with Household, Support at Home and Assistive Technology and Services).

    Last change on 7th of August 2024, at 9:45 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • The Wmo forecasting model provides a prediction of the number of unique users and costs of Wmo with a six-year forecast horizon. Predictions are made at district level for both the Wmo total and sub-products of the Wmo (Help with Household, Support at Home and Assistive Technology and Services).

    Last change on 23rd of August 2024, at 14:10 (CET) | Publication Standard 1.0
    Publication category
    Impactful algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • The various algorithms and calculation rules within LVMA work together so that information from video images can be converted to interpretable census data as decision-supporting information for public space steering and policy.

    Last change on 25th of April 2024, at 12:27 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • Support in determining and verifying the WOZ value of residential properties.

    Last change on 12th of December 2024, at 13:48 (CET) | Publication Standard 1.0
    Publication category
    Impactful algorithms
    Impact assessment
    Field not filled in.
    Status
    In use
  • The municipality calculates the WOZ value of each property based on property characteristics and sales prices from the Land Registry and to comparable properties sold around the reference date.

    Last change on 30th of September 2024, at 7:39 (CET) | Publication Standard 1.0
    Publication category
    Other algorithms
    Impact assessment
    Field not filled in.
    Status
    In use