Home‎ > ‎

Recommendations



Towards new regional ITS decrees

First regional ITS decrees (BR, FL, W) were created as a result of the European ITS Directive.

New regional ITS decrees, implementing the European Delegated Acts, are unavoidable. The final result of these new regional ITS decrees is that all authorities that are active in a region (at the regional and at the urban level) will be encouraged (and after some time forced) to ensure that important static and dynamic datasets are published as open data (in the appropriate European standards), and this for:
A good example of such a decree, with the same final result, is the "GIPOD decree", which forces cities and communes from 1 January 2017 onwards against monetary penalties to exchange information on restrictions on the public domain such as roadworks).

Note that from a strict legal perspective the Delegated Acts are already binding and do not need to be converted into new national and regional legislation; doing so is considered useful to create more local momentum.

Minimal version of an (urban) ITS action plan: chapter in the mobility plan

Intelligent Transport Systems (ITS)

ITS stands for new services allowing an optimal use of the multimodal infrastructure, that are often based on data and new technology. Examples of these services are information services, mobility management services, enforcement services, demand management services and (mobile) payment and reservation services. These services "play out" in all mobility domains such as the traffic domain, the goods transport domain, public transport and shared mobility, parking ...

Open data

To make public and private ITS services possible, (static and dynamic) open data are essential, and this for all mobility domains. The City of <x> fully supports the principle that all non-privacy-sensitive data should be considered as open data.

For this reason, the city will always examine if an open data component should be part of a tender or an agreement when awarding new concessions or subcontracting (for instance for parking concessions or parking guidance systems). When doing this, the city will ensure that important mobility data are published as open data, and that it therefore remains the owner of this data.

Standard open data component in tenders (eg in the parking domain) 
(eg for concessions of parking facilities, or of parking guidance systems)

Technical formal
Description: 

To further professionalise open data and to be compatible with all market players, the City of <x> offers the data as much as possible in a European format (such as the Datex II format). Use: compatibility with large players on the market of the navigation, mapping and ITS sector, conformity with European legislation. In this way parking data can be automatically read and ‘understood’ by systems that also use the data of other cities and countries.

Via the proxy of the supplier and the <open data portal of the City of <x>> <the regional open data portal> the following static and dynamic datasets on off-street parking will therefore be published as open data. 

Static data (bundled in 1 dataset)
Dynamic data

Quality control

Condition: the final result will be validated by an external party as part of the delivery of the contract.


Url’s that direct to the above-mentioned datasets will be provided by the supplier.

A preliminary version of the datasets is first provided to the client. After validation of the data by a party that is appointed by the city, any remarks regarding the quality will be incorporated by the supplier as part of the delivery of the contract.

Annex to existing agreements
(eg for existing concessions)

As an addition to article <x> of its concession agreement, operator <x> makes the data of its off-street parking facilities on the territory of the City <x> available allowing the City to publish this data as open data.
 
The representation of the data will be based on the principle: 
If the occupancy of the facilities is between 0% - 80%, this occupancy will be published as "free". If the occupancy is between 80% and 100%, the exact number if parking places will be published.
 
Operator <x> makes this data available via a digital interface, to which the City <x> is given access. The data will be published in the DATEX II format, according to the parking profile developed by ITS.be, that is already implemented by the City <x> for parking facilities that it is operating itself. In this case the data of operator <x> will be made available via the open data portal of the City <x>. This has the following advantages: the City <x> does not have to manipulate the data, the systems of operator <x> are not charged as the data portal buffers the data, and developers of parking-apps can take this extra data-feed on-board in their applications.
Comments