ITS Observatory Workshop 2 User requirements survey and input/output definition

Size: px

Start display at page:

Download "ITS Observatory Workshop 2 User requirements survey and input/output definition"

Phillip Arnold
6 years ago
Views:

1 ITS Observatory Workshop 2 User requirements survey and input/output definition Simon Edwards & Phil Blythe Transport Operations Research Group Newcastle University

2 Questionnaires (Oct-Dec 2015) Two main questionnaires developed as part of the ITS-O user requirement identification process: A large-scale general questionnaire to maximise the coverage of the different user groups and understand exactly their needs as either information provider to, or user of, the ITS-O Distributed to 13,138 recipients 114 responses A questionnaire targeted at public authorities Distributed to the public authorities network of the Consortium including the ERTICO Public Authorities Sector Platform (~ 100 recipients) 9 responses

3 Results of the General Questionnaire 3

4 Who Responded 4

5 How Organisations get their Information How often do you search for information related to ITS? Where do you go to search for ITS information? How often do you succeed in your search? 5

6 Difficulties Finding Information What are the main obstacle(s) for finding ITS information? 6

7 Why Organisations Need Information For what purpose(s) do you need ITS information? 7

8 What Information Organisations Need What kinds of ITS information do you need? For which type of ITS do you need information? 8

9 What Information Organisations would Provide Which kinds of information would you publish in the ITS Observatory? 9

10 How Organisations would Provide Information Which of the following is/are important to you for adding information? 10

11 ITS-O Features # 1 ITS Projects 79% rank this feature as important or very important 11

12 ITS-O Features # 2 Link to Evaluation Results 74% rank this feature as important or very important It is not only knowledge of ITS deployments that is sought, but how successful those deployments are

13 ITS-O Features # 3 = Knowledge Base of Benefits 70% rank this feature as important or very important This corresponds well to the impact and evaluation results question 13

14 ITS-O Features # 3 = Technology and Market Trends 70% rank this feature as important or very important

15 ITS-O Features 59% rank this as important or very important This would provide a complementary visual aid to the query report 64% of respondents rank this feature as important or very important 15

16 ITS-O Features 63% rank the above features as important or very important 16

17 ITS-O Features Respondents are more neutral about these features

18 ITS-O Features 18

19 PA Questionnaire Summary of Findings PAs need ITS content: To review results of R&D projects To plan and evaluate future ITS deployment Type of content required: Impacts, benefits and costs EU and national policy and legislation ITS deployment status Obstacles in collecting content (at present): Knowing who to contact to get the information Difficulty in understanding other data in a relevant, applicable local context Difficulty accessing relevant reports Most popular types of information that PAs would publish: ITS project information Location and description of existing and planned ITS deployments Challenge: long term maintenance/ updating/ curating of content Respondents are largely undecided whether they would be responsible for this 19

20 Interviews Interviewee City of Vienna ITS Hellas Region of Central Macedonia University of Patras Trainose SA (national railway operator) Hellastron (Hellenic Association of Toll Road Network) Athens International Airport Egnatia Motorway SA Ministry of Infrastructure, Transport and Networks Hellenic Association of Mobile Applications Companies Piraeus Container Terminal SA Ministry of National Development Anav (business association of passenger transport by bus) Huawei Ministry for Economic Development ISIS (Study institute for Systems integration) Fondazione Caracciolo ACI Cellint Thetis Inovalab SRL DITCM Norwegian Road Administration Directorate for National Roads & Motorways RACC ITS Ukraine Transport for London Transport Technology Forum Country Austria Greece Greece Greece Greece Greece Greece Greece Greece Greece Greece Hungary Italy Italy Italy Italy Italy Italy Italy Italy Netherlands Norway Poland Spain Ukraine UK UK 20

21 Findings Overview - Output We are clear what people want from the ITS-O and how they will use it We have a clear understanding of the differences in priority requirements between public authorities and the private sector Most organisations already have existing search mechanisms that work for them, and often on a daily or at least weekly basis However, ITS-O could provide a one stop shop, defragmenting the search process and making it quicker and more complete, right down to a micro-level including (for example) identifying the right contact person 21

22 Findings Overview - Input The quality of the outputs is dependent on the quality of the inputs Data capture must be as quick and simple as possible We must consider the completeness of inputs, including more confidential data and content and how that is managed We must address the maintenance and updating of data and content going forward beyond the end of the project We must clearly define the relationship with data and content suppliers

23 Conclusions There is broad agreement on types of data and content to be presented in the ITS-O, its scope, and how it will be used There is agreement on keeping the ITS-O simple and accessible to all There is a consensus view that not all data or content can be free access The main areas that must be examined in more detail, and will be linked to other key areas of the project - such as the Operational Plan and the Sustainability Strategy - will be: How to verify data and content quality Ongoing maintenance and updating of data, content and ITS-O platform Defining the role for data and content providers, including incentives 23

24 Simon Edwards Senior Research Associate Newcastle University Phone: +44 (0) Thank You for Listening!

Deliverable D4.3.4: Guidelines and proposals for the revision of ITS architecture in Bulgaria. ITS Bulgaria

Deliverable D4.3.4: Guidelines and proposals for the revision of ITS architecture in Bulgaria ITS Bulgaria December, 2013 PROJECT INFORMATION Title: Acronym: EoI Reference number: Programme: Intelligent