Delegated Regulation

Step 1: Identification of the relevant data

Before a self-declaration is completed, data holders, in coordination with the ITS Contact Point, can check whether they collect, share or update data affected by Delegated Regulation (EU) 2017/1962. The relevant data is divided into two categories (types of static, historical and observed travel and traffic data and types of dynamic travel and traffic data) and listed in detail in the annex to the Delegated Regulation, which can be found using the following link. The actors also check which category the data belongs to and which level of service the data corresponds to.

Step 2: Provide the relevant data through the National Access Point (www.mobilitaetsdaten.gv.at)

If data holders collect, share or update data listed in the Annex to Delegated Regulation (EU) 2017/1926, the associated metadata must be recorded on the National Access Point, www.mobilitaetsdaten.gv.at. The above-mentioned timeline for each service level must be taken into account.

Step 3: Fill in the self-declaration form and collect all required Annex information

In the download area, the self-declaration form for data holders to declare compliance with Delegated Regulation (EU) 2017/1926 can be downloaded. The form must then be completed entirely and truthfully and signed by an authorized signatory. The required annexes are listed on the form and can be put together in a format of your choice or together with the accompanying documents.

Step 4: Submit the filled-in self-declaration, including Annexes

The completed and signed form, including the necessary annexes, can be sent by e-mail in PDF format to kontakt@ivs-stelle.at.

According to Delegated Regulation (EU) 2017/1926 data holders are obliged to provide types of static, historical and observed travel and traffic data or types of dynamic travel and traffic data that they are collecting, sharing or updating, at the National Access Point (www.mobilitaetsdaten.gv.at). This data must comply with the requirements regarding the accessibility, exchange and re-use of the respective data. Data holders ensure that the data provided is regularly updated. All stakeholders involved (data holders and data users) work together to report data errors immediately and correct any data inaccuracies identified as soon as possible. The obligations of data holders are listed in more detail in the respective self-declaration.

Step 1: Identification of the relevant services

Before a self-declaration is completed, travel information service providers, in coordination with the ITS Contact Point, can check whether they are affected by Delegated Regulation (EU) 2017/1926. This is the case if they use the data listed in the Annex to provide multimodal travel information or, if agreed with data holders, for other purposes.

Step 2: Fill in the self-declaration form and collect all required Annex information

In the download area, the self-declaration form for travel information service providers to declare compliance with Delegated Regulation (EU) 2017/1926 can be downloaded. The form must then be completed entirely and truthfully and signed by an authorized signatory. The required annexes are listed on the form and can be put together in a format of your choice or together with the accompanying documents.

Step 3: Submit the filled-in self-declaration, including Annexes

The completed and signed form, including the necessary annexes, can be sent by e-mail in PDF format to kontakt@ivs-stelle.at

Travel information service providers rely on up-to-date static, historic, observed and dynamic travel and traffic data to provide travel and traffic information services. They provide route planning results to other information service providers upon request. Data shall be reused in a neutral, non-discriminatory and unbiased manner.

If travel information service providers act as data users, they are obliged, according to Delegated Regulation (EU) 2017/1926, to keep data, that they use to provide multimodal travel information or for other purposes, up to date in coordination with the data holders and to report inaccuracies immediately to the data holders. The obligations of travel information service providers are listed in more detail in the respective self-declaration. 

The declaration refers to Article 9 ‘Assessment of compliance’ of the Delegated Regulation:

Data holders and travel information service providers declare that they comply with the requirements set out in Articles 3 to 8 of the Delegated Regulation (EU) 2017/1926. Depending on the role, the following documents must be provided to the ITS contact point:

a) a description of the travel and traffic data accessible via the national access point, the information on the quality thereof and the conditions of reuse of that data (Entry on the National Access Point mobilitaetsdaten.gv.at and Accompanying Documentation)

b) a description of the travel information services available including connections with other services where applicable (Accompanying Documentation)

c) an evidence-based declaration of compliance with the requirements set out in Articles 3 to 8 (the respective Self-Declaration can be found in the download area)

d) the licence or contractual agreements with travel information service providers (Annex and Accompanying Documentation)

The ITS Contact Point randomly checks the correctness of the submitted declarations and their annexes.

Partition of transport modes and transport means and included services, such as

Scheduled transport such as:

Air, rail including high speed rail, conventional rail, light rail, cableways, long-distance coach, maritime including ferry, inland waterways, metro, tram, bus, trolley-bus.

Transport on demand such as:

Shuttle bus, shuttle ferry, dial-a-ride services, taxi, car-sharing, car-pooling, car-hire, ride-sharing, bike-sharing, bike-hire, bike-rental, e-scooter sharing.

Personal transport such as:

Car, motorcycle, bicycle, scooter, walking.

1. TYPES OF THE STATIC, HISTORIC AND OBSERVED TRAVEL AND TRAFFIC DATA

1.1.    Level of service 1

a) location search (origin/destination):

i) addresses (building number, street name, postcode);

ii) topographic places (city, town, village, suburb, administrative unit);

iii) points of interest (related to transport information) to which people may wish to travel;

b) trip plans: operational calendar, mapping day types to calendar dates;

c) location search (access nodes) – for scheduled transport and transport on demand where relevant:

i) identified access nodes;

ii) geometry/map layout structure of access nodes;

d) trip plan computation – for scheduled transport and transport on demand where relevant:

i) connection where interchanges may be made;

ii) default transfer times at interchanges;

iii) network topology and routes/lines (topology);

iv) transport operators;

v) timetables;

vi) planned interchanges between guaranteed scheduled services;

vii) hours of operation;

viii) facilities of access nodes (including platform information, help desk/information points, ticket booths, lifts/stairs, entrances and exit locations);

ix) vehicles, including their accessibility (such as low floor, wheelchair accessible, pram accessible) and accessibility of on-board services (such as toilets);

x) accessibility of access nodes, and paths within an interchange (such as existence of lifts, escalators);

xi) existence of assistance services (such as existence of on-site assistance);

e) trip plan computation:

i) road network (including segregated lanes for bus/taxi);

ii) cycle network (cycle tracks, cycle lanes, bus-and-cycle lanes, on-road shared with vehicles, on-path shared with pedestrians);

iii) pedestrian network and accessibility facilities.

1.2.    Level of service 2

a) location search – for transport on demand and personal transport:

i) location of parking places (on and off-street), including accessible parking places for persons with disabilities and persons with reduced mobility;

ii) Park & Ride stops;

iii) Park & Drive stops;

iv) bike-sharing stations;

v) car-sharing stations;

vi) secure bike parking (such as locked bike garage);

vii) scooter parking zones;

b) information service:

i) where and how to buy tickets for scheduled transport, including retail channels, fulfilment methods, payment methods;

ii) where and how to pay for parking, including retail channels, fulfilment methods, payment methods;

c) auxiliary information – for scheduled transport and transport on demand where relevant:

i) basic common standard fares:

— fare network data (fare zones/stops and fare stages),

— standard fare structures (point to point including daily and weekly fares, zonal fares, flat fares);

ii) vehicle facilities, including classes of carriage, on-board Wi-Fi, capacity and access conditions for bicycles.

1.3.    Level of service 3

a) detailed common standard and special fare query – for scheduled transport and transport on demand where relevant:

i) passenger classes (classes of passenger such as adult, child, senior, student, military/veteran, passenger with disability and passenger with reduced mobility, and qualifying conditions, and classes of travel);

ii) common fare products (access rights such as zone/point-to-point including daily and weekly tickets/single/return, eligibility of access, basic usage conditions such as validity period/operator/time of travel/interchanging, standard point-to-point fares prices for different point-to-point pairs including daily and weekly fares/zonal fare prices/flat fare prices);

iii) special fare products (offers with additional special conditions such as promotional fares, group fares, season passes, aggregated products combining different products, and add-on products such as parking and travel, minimum stay);

iv) basic commercial conditions such as refunding, replacing, exchanging or transferring;

v) basic booking conditions such as purchase windows, validity periods, routing restrictions zonal sequence fares, minimum stay;

b) information service – for transport on demand: how to book demand-responsive transport services, including retail channels, fulfilment methods, payment methods;

c) trip plans:

i) detailed cycle network attributes (surface quality, side-by-side cycling, shared surface, on/off road, scenic route, ‘walk only’, turn or access restrictions, e.g. against flow of traffic);

ii) parameters needed to calculate an environmental factor such as greenhouse gas emissions per vehicle type or passenger mile or per distance walked;

iii) parameters needed to calculate fuel consumption of conventional and alternative fuels;

d) trip plan computation: estimated travel times by day type and time-band by transport mode/combination of transport modes.

1.4.    Level of service 4

a) historic travel and traffic data on delays – for scheduled transport and transport on demand where relevant;

b) observed data on delays and passing time – for scheduled transport:

i) length of, and when possible the reason for, delays of at least 60 minutes for rail passenger services (in accordance with Article 19 of Regulation (EU) 2021/782);

ii) length of, and when possible the reason for, delays in departure of more than 90 minutes for sea and inland waterways passenger services (in accordance with Article 18 of Regulation (EU) No 1177/2010);

iii) length of, and when possible the reason for, delays in departure from a terminal of more than 120 minutes for regular bus and coach passenger services with a scheduled distance of 250 km or more (in accordance with Article 19 of Regulation (EU) No 181/2011);

iv) length of, and when possible the reason for, flight delays at departure of at least 120 minutes; and flight delays at arrival of at least 180 minutes (in accordance with Articles 5 and 6 of Regulation (EC) No 261/2004);

c) observed data on cancellations – for scheduled transport:

i) cancellations, and when possible the reason, of rail passenger services;

ii) cancellations, and when possible the reason, of sea and inland waterways passenger services;

iii) cancellations, and when possible the reason, of regular bus and coach services with a scheduled distance of 250 km or more;

iv) cancellations, and when possible the reason, of flights;

d) information on parking tariffs.

2. TYPES OF THE DYNAMIC TRAVEL AND TRAFFIC DATA

2.1.    Level of service 1

Passing times, trip plans and auxiliary information:

i) disruptions, such as network closures and/or diversions, and when possible, the reason;

ii) real-time status information, such as estimated departure and arrival times of services, delays, cancellations, guaranteed connections monitoring;

iii) status of access node features (including dynamic platform information, operational lifts/escalators, closed entrances and exit locations) – for scheduled transport.

2.2.    Level of service 2

a) information service on parking tariffs – for transport on demand and personal transport;

b) availability check and location – for transport on demand and personal transport where relevant:

i) car-sharing availability and location, bike-sharing availability and location, scooter-sharing availability and location, and other vehicle-sharing availability and location;

ii) car parking spaces available (on and off-street).

2.3.    Level of service 3

Occupancy information of the vehicle – for scheduled transport and transport on demand where relevant.