Report on updated definition for “innovative bus system” D 2 · 2018-05-30 · Deliverable 2.1 Page 1 of 135 Version 2.0 Date of issue June 1st 2016 Nature of Deliverable External

Deliverable 2.1 Page 1 of 135

Version 2.0

Date of issue June 1st 2016

Nature of Deliverable External

Dissemination Level Public

Status Final

This project has received funding from the European Union’s Horizon 2020 research and innovationprogramme under grant agreement N° 636300.

Coordinator: UITP – International Association of Public Transport

Report on updated definition for“innovative bus system”

D 2.1

Issued by Project Director

Daniela Carbone

Emanuele Proia

ASSTRA

Michele Tozzi

UITP


SUMMARY SHEETProgramme Horizon 2020Contract N. 636300Project Title European Bus Systems for the Future 2Acronym EBSF_2Coordinator UITP – International Association of Public TransportProject Director Michele Tozzi, [email protected] http://ebsf2.euStarting date 1 May 2015Number of months 36 months

Deliverable N. 2.1Deliverable Title Report on updated definition for “innovative bus system”Version 2.0Date of issue June 1st 2016Distribution [Internal/External] ExternalDissemination level PublicAbstract This deliverable reports the main outcomes of the activities performed in Task 2.1 to

develop an up-to-date framework of bus system user needs and functionalrequirements. Capitalizing on the results of the previous EBSF project, a completeupdating and integration of user needs and functional requirements have beenelaborated. This conceptual framework is intended to support bus stakeholder infurther research and implementation activities for better service to city dwellers, and,at the end, better urban living.The user needs assessment and the functional requirements assessment are in factessential to re-shape the bus system, which requires innovative methods for serviceprovision or, at least, a rethinking of existing methods and solutions.

Keywords Bus System Concept, User Needs, Functional Requirements, TechnologicalInnovations

This report is subject to a disclaimer and copyright. This report has been carried out under a contract awarded by theEuropean Commission, contract number: 636300No part of this report may be used, reproduced and or/disclosed, in any form or by any means without the prior writtenpermission of UITP and the EBSF_2 consortium. All rights reserved.Persons wishing to use the contents of this study (in whole or in part) for purposes other than their personal use are invitedto submit a written request to the following address:UITP International Association of Public TransportRue Sainte-Marie 6- 1080 Brussels


INTERNAL DISTRIBUTIONParticipant N° Participant organisation name Country

1 Coordinator Union Internationale des Transports Publics - UITP Belgium2 Régie Autonome des Transports Parisiens - RATP France3 Iveco France SA - IVECO France4 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. - FRAUNHOFER Germany

5 Hübner Gummi- und Kunststoff GMBH - HUEBNER Germany

6 DigiMobee SAS - DIGIMOBEE France

7 Centro de Estudios e Investigaciones Técnicas - CEIT Spain

8 Chalmers Tekniska Hoegskola AB - CHALMERS Sweden

9 Compañía del Tranvía de San Sebastián, SA (CTSS) – DBUS Spain

10 IRIZAR S Coop - IRIZAR Spain

11 D’Appolonia S.p.A. - DAPP Italy

12 EvoBus GmbH - EVOBUS Germany

13 Volvo Bus Corporation - VBC Sweden

14 Pluservice srl - PLUSERVICE Italy

15 Universidad Politécnica de Madrid - UPM Spain

16 Actia S.A. - ACTIA France

17 Teknologian Tutkimuskeskus - VTT Finland

18 MEL-SYSTEM Italy

19 Ineo Systrans – INEO France

20 Stuttgarter Strassenbahnen AG - SSB Germany

21 Associazione Trasporti - ASSTRA Italy

22 Pilotfish Networks AB - PILOTFISH Sweden

23 Start Romagna SpA - START ROMAGNA Italy

24 FIT Consulting Srl - FIT Italy

25 Hogia Public Transport Systems AB - HOGIA Sweden

26 Trapeze ITS UK Limited - TRAPEZE Switzerland

27 Digigroup Informatica srl - DIGIGROUP Italy

28 Transports de Barcelona SA - TMB Spain

29 TIS PT, Consultores em Transportes, Inovação e Sistemas, SA - TISPT Portugal

30 Rupprecht Consult - Forschung & Beratung GmbH - RUPPRECHT Germany

31 Keolis SA - KEOLIS France

32 Syndicat Mixte des Transports pourle Rhone et l agglomeration Lyonnaise - SYTRAL France

33 Transport for London – TFL UK

34 Università degli Studi di Roma La Sapienza – UNIROMA1 Italy

35 Verband Deutscher Verkehrsunternehmen - VDV Germany

36 Promotion of Operational Links with Integrated Services, Association Internationale - POLIS Belgium

37 Tekia Consultores Tecnologicos S.L - TEKIA Spain

38 Innovative Informatikanwendungen in Transport-, Verkehrs- und Leitsystemen GmbH - INIT Germany

39 Union des Transports Publics - UTP France

40 Västtrafik AB - VTAB Sweden

41 Commissariat à l’Energie Atomique et aux Energies Alternatives - CEA France

42 Consorcio Regional de Transportes de Madrid - CRTM Spain


EXTERNAL DISTRIBUTIONEntity Short name Country Contact personEuropean Commission - INEA EC INEA - Mr. Walter Mauritsch

DOCUMENT CHANGE LOGVersion Date Main area of changes Organisation Comments

0.1 Dec. 10th, 2015 ASSTRACreation of structure, draftand main content

0.2 Dec. 11th,2015Document reviewInfrastructurerequirement analysis

CRTM

0.3 Dec.27th,2015Document reviewOperation requirementanalysis

FRAUNHOFER

0.4 Jan. 12th, 2016

Document review – AllChaptersSystem requirementanalysis

UITP

1.0 Jan. 19th,2016 Final Version ASSTRA1.1 Feb. 26th 2016 Quality check UITP, ASTRA

2.0 June 1st 2016Final Version afterquality check

UITP

CONTRIBUTING PARTNERSCompany Names Company Info

ASSTRADaniela CarboneEmanuele Proia

Associazione TrasportiPiazza Cola di Rienzo 80/a, Rome 00192, Italy

UITP Michele TozziInternational Association of Public TransportRue Sainte-Marie 6, B-1080 Brussels, Belgium

CHALMERSMariAnne KarlssonStig FranzénOscar Rexfelt

Chalmers Tekniska Hoegskola ABGoeteborg 41296, Sweden

CRTMAntonio GarciaNatalia Sobrino VázquezLaura Delgado

Consorcio Regional de Transportes de MadridPlaza del Descubridor Diego de Ordás, nº 3, planta baja. 28003Madrid, Spain

DBUSEduardo GonzalezJavier Vallejo

Compañía del Tranvía de San Sebastián, SA (CTSS)Fernando Sasiain, 720015 Donostia-San Sebastián, Spain

DIGIMOBEEDominique DescolasEmmanuel de Verdalle

DigiMobee SASRue de la Banque 16, Paris 75002, France

FRAUNHOFERThoralf KnoteFrank SteinertBettina Von Hagens

Fraunhofer-Gesellschaft zur Förderung der angewandtenForschung e.V.Hansastrasse 27c, Muenchen 80686, Germany

KEOLIS Emmanuel FarguesKeolis SA20 rue le Peletier75320 PARIS Cedex 09, France

RATPAnne HashizumeYo KaminagaiVeronique Berthault

Régie Autonome des Transports ParisiensQuai de la Rapee 54 Lac B71, Paris 75012, France

SSB Markus WiedemannStuttgarter Strassenbahnen AGSchockenriedstraße 50, 70565 Stuttgart, Germany

START ROMAGNAMarco CiuffoliniC. ZuccherelliF. Fuzzi

Start Romagna SpAVia A. Spinelli, 140, 47521 Cesena (FC), Italy

SYTRAL [email protected]; Syndicat Mixte des Transports pourle Rhone et l agglomeration


Lyonnaise21 Boulevard Marius Vivier Merle,69003 Lyon, France

TFLSimon ReedDavid Fell

Transport for London14 Pier WalkLondon SE10 0ES, UK

TMBFrancesc Gonzalez BalmasJosep Ma ArmengolIsabel Criado

Transports de Barcelona SACarrer 60, núm. 21-23Sector A, Polígon Industrial de la Zona Franca08040 (Barcelona), Spain

UTPAnne MeyerPhilippe Chokomert

Union des Transports Publics17, rue d'Anjou, France75 008 Paris, France

VDVJens SchmitzAnnika StienenMicheal Weber-Wernz

Verband Deutscher VerkehrsunternehmenKamekestraße 37, 50672 Köln, Germany

VTAB

Andreas AlmquistRoger VahnberJennifer ElsrenHanna Bjork

Västtrafik ABDrottningtorget,411 03 Göteborg, Sweden

VTTJuhani [email protected]@vtt.fi

Teknologian TutkimuskeskusVuorimiehentie 3, Espoo 02150, Finland

ACRONYMS3iBS – Intelligent, Innovative, Integrated Bus SystemD – DeliverableEBSF - European Bus System of the FutureEBSF 2 – European Bus System of the Future 2FR – Functional RequirementITS – Information and Telecommunication SystemUN – User NeedUNA – User Need AreaWT – Work ToolWP – Working Package


INDEXSUMMARY SHEET............................................................................................................................................................... 2

INTERNAL DISTRIBUTION .................................................................................................................................................. 3

EXTERNAL DISTRIBUTION ................................................................................................................................................. 4

DOCUMENT CHANGE LOG................................................................................................................................................. 4

CONTRIBUTING PARTNERS............................................................................................................................................... 4

ACRONYMS ......................................................................................................................................................................... 5

INDEX................................................................................................................................................................................... 6

INDEX OF FIGURES ............................................................................................................................................................ 9

INDEX OF TABLES .............................................................................................................................................................. 9

1 Executive Summary................................................................................................................................................... 10

2 Partners’ Contribution................................................................................................................................................ 11

3 Introduction ............................................................................................................................................................... 123.1 WP2 Work Plan ............................................................................................................................................... 133.2 Task 2.1 Work Plan ......................................................................................................................................... 16

4 Structure of the report................................................................................................................................................ 18

5 The methodology for the “Innovative Bus System Concept” update ........................................................................... 195.1 3iBS Database updating .................................................................................................................................. 205.2 Link between User Needs and EBSF_2 six topics............................................................................................ 205.3 Work Tool 1 ..................................................................................................................................................... 22

User needs updating......................................................................................................................................................... 22

User needs integration ..................................................................................................................................................... 23

User needs updating: RESULTS ...................................................................................................................................... 235.4 Work Tool 2 ..................................................................................................................................................... 26

6 Evaluation of User Needs achievement by topic ........................................................................................................ 326.1 Background ..................................................................................................................................................... 326.2 Energy management strategy and auxiliaries................................................................................................... 34

User needs from previous project............................................................................................. 34User needs integration by partner ............................................................................................ 35

6.3 Driver Assistance............................................................................................................................................. 37User needs from previous project............................................................................................. 37User needs integration by partner ............................................................................................ 38

6.4 Vehicle design ................................................................................................................................................. 39User needs from previous project............................................................................................. 39User needs integration by partner ............................................................................................ 42

6.5 IT Standard introduction in existing fleets......................................................................................................... 44User needs from previous project............................................................................................. 44User needs integration by partner ............................................................................................ 47

6.6 Intelligent Garage and predictive maintenance................................................................................................. 48User needs from previous project............................................................................................. 48User needs integration by partner ............................................................................................ 51

6.7 Urban infrastructure ......................................................................................................................................... 52User needs from previous project............................................................................................. 52User needs integration by partner ............................................................................................ 54

7 Relevance of Functional Requirements ..................................................................................................................... 577.1 Background ..................................................................................................................................................... 57


7.2 Approach and objectives.................................................................................................................................. 587.3 System requirements ....................................................................................................................................... 59

TOPIC 1: Energy Management Strategy and Auxiliaries ......................................................... 60TOPIC 2: Driver Assistance...................................................................................................... 60TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)................................................ 61TOPIC 4: IT Standard introduction in existing fleets ................................................................ 63TOPIC 5: Intelligent Garage and predictive maintenance........................................................ 65TOPIC 6: Urban Infrastructure.................................................................................................. 66

7.4 Vehicle requirements ....................................................................................................................................... 68Main areas for the vehicle requirements .................................................................................. 68TOPIC 1: Energy Management Strategy and Auxiliaries ......................................................... 69TOPIC 2: Driver Assistance...................................................................................................... 70TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)................................................ 72TOPIC 4: IT Standard introduction in existing fleets ................................................................ 76TOPIC 5: Intelligent Garage and predictive maintenance........................................................ 78TOPIC 6: Urban Infrastructure.................................................................................................. 78Summary of results and conclusions........................................................................................ 78

7.5 Infrastructure requirements .............................................................................................................................. 79Main areas for infrastructure requirements .............................................................................. 79TOPIC 1: Energy Management Strategy and Auxiliaries ......................................................... 80TOPIC 2: Driver Assistance...................................................................................................... 80TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)................................................ 80TOPIC 4: IT Standard introduction in existing fleet .................................................................. 80TOPIC 5: Intelligent Garage and predictive maintenance........................................................ 81TOPIC 6: Urban Infrastructure.................................................................................................. 82Summary of results and conclusions........................................................................................ 89

7.6 Operation requirements ................................................................................................................................... 92Main areas for operation requirements .................................................................................... 92TOPIC 1: Energy Management Strategy and Auxiliaries ......................................................... 93TOPIC 2: Driver Assistance...................................................................................................... 94TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)................................................ 95TOPIC 4: IT Standard introduction in existing fleets ................................................................ 96TOPIC 5: Intelligent garage and predictive maintenance......................................................... 99TOPIC 6: Urban Infrastructure................................................................................................ 102Summary of results and conclusions...................................................................................... 103

8 Conclusions............................................................................................................................................................. 104

TOPIC 1 - ENERGY MANAGEMENT STRATEGY AND AUXILIARIES............................................................................. 105

User needs – Integration ................................................................................................................................................ 105

Functional requirements ................................................................................................................................................ 106

TOPIC 2 - DRIVER ASSISTANCE .................................................................................................................................... 106



TOPIC 3 - VEHICLE DESIGN (CAPACITY, ACCESSIBILITY, MODULARITY) ................................................................. 108



TOPIC 4 - IT STANDARD INTRODUCTION IN EXISTING FLEETS ................................................................................. 111




TOPIC 5 - INTELLIGENT GARAGE AND PREDICTIVE MAINTENANCE ......................................................................... 115



TOPIC 6 - URBAN INFRASTRUCTURE ........................................................................................................................... 117

User needs –Integration ................................................................................................................................................. 118


9 Annexes .................................................................................................................................................................. 124

Annex 1 – USER NEEDS UPDATING: RESULTS ........................................................................................................... 124

Energy Management Strategy and Auxiliaries .............................................................................................................. 124

Driver Assistance............................................................................................................................................................ 125

Vehicle Design ................................................................................................................................................................ 126

IT Standard introduction in existing fleets .................................................................................................................... 129

Intelligent Garage and predictive maintenance............................................................................................................. 132

Urban Infrastructure ....................................................................................................................................................... 134


INDEX OF FIGURES

Figure 1 – Interactions among WP n. 2, n. 4 and n. 6. ......................................................................................................... 12Figure 2 – Interaction among Task 2.1 and Task 2.2........................................................................................................... 14Figure 3 – Methodology of the work .................................................................................................................................... 19Figure 4 – Screenshot of the 3Ibs electronic database (elaborated by the author).............................................................. 20Figure 5 – Link between User Needs and the six topics ...................................................................................................... 21Figure 6– WT 1 - User needs updating................................................................................................................................ 23Figure 7– WT 1 - User needs integration............................................................................................................................. 23Figure 8 – WT 1 - User needs updating: RESULTS............................................................................................................. 24Figure 9 – WT 1 - User needs from previous project ........................................................................................................... 25Figure 10 – WT 1 - User needs integration by partner ......................................................................................................... 26Figure 11 – Example of statistical treatment of data ............................................................................................................ 30Figure 12 – Example of FRs relevance by sheets................................................................................................................ 31Figure 13 – Structure of work for vehicle requirements........................................................................................................ 68Figure 14 – Structure of work for infrastructure requirements. ............................................................................................. 79Figure 15 – Structure of work for operation requirements. ................................................................................................... 92

INDEX OF TABLESTable 1 – General schedule of WP2.................................................................................................................................... 15Table 2 – Working plan of the Task 2.1 ............................................................................................................................... 17Table 3 – GANTT of the Task 2.1 activities ......................................................................................................................... 17Table 4 – Vehicle categories ............................................................................................................................................... 27Table 5 – User needs achievement for Topic 1 ................................................................................................................... 34Table 6 – User needs integration for Topic 1 ....................................................................................................................... 35Table 7 – User needs achievement for Topic 2 ................................................................................................................... 37Table 8 – User needs integration for Topic 2 ....................................................................................................................... 38Table 9 – User needs achievement for Topic 3 ................................................................................................................... 41Table 10 – User needs integration for Topic 3 ..................................................................................................................... 43Table 11 – User needs achievement for Topic 4.................................................................................................................. 46Table 12 – User needs integration for Topic 4 ..................................................................................................................... 48Table 13 – User needs achievement for Topic 5.................................................................................................................. 50Table 14 – User needs integration for Topic 5 ..................................................................................................................... 51Table 15 – User needs achievement for Topic 6.................................................................................................................. 53Table 16 – User needs integration for Topic 6 ..................................................................................................................... 55Table 17 – List of contributing partners to Work Tool 2........................................................................................................ 58Table 18 – System Requirements identified as relevant for Topic 1 and related user needs areas ...................................... 60Table 19 – System Requirements identified as relevant for Topic 2 and related user needs areas ...................................... 61Table 20 – System Requirements identified as relevant for Topic 3 and related user needs areas ...................................... 63Table 21 – System Requirements identified as relevant for Topic 4 and related user needs areas ...................................... 65Table 22 – System Requirements identified as relevant for Topic 5 and related user needs areas ...................................... 66Table 23 – System Requirements identified as relevant for Topic 6 and related user needs areas ...................................... 67Table 24 – Vehicle Requirements identified as relevant for Topic 1 and related user needs areas ...................................... 69Table 25 – Vehicle Requirements identified as relevant for Topic 2 and related user needs areas ...................................... 71Table 26 – Vehicle Requirements identified as relevant for Topic 3 and related user needs areas ...................................... 74Table 27 – Vehicle Requirements identified as relevant for Topic 4 and related user needs areas ...................................... 77Table 28 – Vehicle Requirements identified as relevant for Topic 5 and related user needs areas ...................................... 78Table 29 – Infrastructure Requirements identified as relevant for Topic 4 and related user needs areas ............................. 81Table 30 – Infrastructure Requirements identified as relevant for Topic 5 and related user needs areas ............................. 82Table 31 – Infrastructure Requirements identified as relevant for Topic 6 and related user needs areas ............................. 89Table 32 – Operation Requirements identified as relevant for Topic 1 and related user needs areas .................................. 94Table 33 – Operation Requirements identified as relevant for Topic 2 and related user needs areas .................................. 95Table 34 – Operation Requirements identified as relevant for Topic 3 and related user needs areas .................................. 96Table 35 – Operation Requirements identified as relevant for Topic 4 and related user needs areas .................................. 99Table 36 – Operation Requirements identified as relevant for Topic 5 and related user needs areas ................................ 101Table 37 – Operation Requirements identified as relevant for Topic 6 and related user needs areas ................................ 102


1 Executive SummaryThe overall objective of EBSF_2 is to increase the attractiveness and improve the imageof bus systems in urban and suburban areas by demonstrating, evaluating and validatingin real operational scenarios the potential impact of technological innovations indeveloping efficient answers to both citizens and bus stakeholders’ needs.In order to reach this objective, WP2 “Setting the scenarios” starts off by investigating theneeds of bus systems’ users.Previous European projects on bus systems (EBSF, 3iBS, ZeEUS) have already identifiedthe user needs, but in the last years many changes have occurred and in some casestechnological innovations have substantially modified them. Thus the first step has beenthe update of the existing database of user needs. Secondly, the collected informationhave fed the analysis of the most innovative requirements for system and sub-systems(vehicle, infrastructure and operation) identified in EBSF and reviewed according to the sixpriority topics which represent the key research areas EBSF_2 is committed to work on.This Deliverable “Report on updated definition for innovative bus system” is the output ofTask 2.1 “Innovative Bus System Concept Update”. According to the objectives of thetask, this document reports on the analysis and update of both user needs and systemand subsystem requirements impacting vehicle, infrastructure and operation.For the analysis of user needs, two working tools for each of the EBSF_2 priority topicshave been elaborated. The first one has been designed to analyse if the user needs, asdefined in 2008 within EBSF, can still be considered “innovative”, i.e. they need furtherresearch and development activities, or they can be considered “achieved” because theyalready represent the state-of-the art in European bus systems. The second one lists the“new” user needs, i.e. user needs not identified in EBSF but recognised today as relevantto increase the attractiveness and improve the image of bus systems.The EBSF system and subsystem requirements, further updated within 3IBS, arequalitative expressions of functions that a bus system should include in order to satisfy theneeds of all stakeholders impacted by buses (i.e. regular and non-regular users,operators, authorities, industries, and other road users). For the purpose of task 2.1 theexisting database of requirements have been analysed by means of a consultation ofseveral project partners (PT associations, PT operators, PT manufactories, universities,researches companies, etc.) in order to identify their degree of relevance in thedeployment of innovative bus systems. As a result, the requirements which can greatlycontribute to the improvement of a bus system vis-a-vis the six EBSF_2 priority topicshave been identified.


2 Partners’ ContributionCompany Sections Description of the partner contributionASSTRA Chapters 1

to 9Main text, edition and revision;WT1: creating and filling;WT2: creating,filling and statistical elaboration for vehicle requirements;

CHALMERS Chapters 6and 7

RevisionWT1: fillingWT2: filling

CRTM Chapters 4,6 and 7

Text, edition and revisionWT1: fillingWT2: proposed methodology to analyze answers, filling and statistical elaborationfor infrastructure requirements

DBUS Chapters 6and 7

WT1: fillingWT2: filling

DIGIMOBEE Chapters 6and 7


FRAUNHOFER Chapters 6and 7

Text, edition and revisionWT1: fillingWT2: filling and statistical elaboration for operation requirements

RATP Chapters 6 WT1: filling;UITP Chapters 1

to 9Text, edition and revisionWT1: fillingWT2: filling and statistical elaboration for system requirements

UTP Chapters 6and 7


VDV Chapters 6and 7

WT1: proposals and commentsWT2: proposals and comments

VTT Chapters 6and 7

WT1: proposals and commentsWT2: proposals and comments


3 IntroductionThe main objective of WP2 – Setting the scenarios is to: define the test scenarios for theTechnological Innovations (TI) and the evaluation framework used to assess theachievement of the project goals. The other WP aims are:

Update and extend the main needs and the most innovative requirementsidentified for system and sub-systems (vehicle, infrastructure and operation)within the EBSF project in relations to the priority research topics identified by theCall with the involvement of public transport authorities and operators;

Defines in what appropriate format(s) the achieved improvements and learningswill be made available to the stakeholders as part of the evaluation work carriedout in WP 4 and WP6.

Figure 1 – Interactions among WP n. 2, n. 4 and n. 6.

Among the others, this calls for a specific activity (Task 2.1) which is the review andupdate of the definition of “Innovative Bus System”, as developed within the EBSF Project.D 2.1 reports about such activity.

The WP defines in whatappropriate format(s)

the achievedimprovements and

learnings will be madeavailable to the bus

stakeholders


3.1 WP2 Work PlanWP2 comprises the following four tasks: Task 2.1: Innovative Bus System Concept Update.

Revise the main users’ needs identified in EBSF by means of desk researchbased on sector publications and studies, and data collection involving publictransport authorities and operators within the consortium or associated to theproject to perform the transferability exercise later;

Elaborate the collected information in the framework of the analysis of the mainand most innovative requirements for system and sub-systems (vehicle,infrastructure and operation) identified in EBSF in relation to the priority researchtopics identified by the Call;

Format the results in order to be discussed, analyzed and integrated by the taskpartners that will be involved and consulted via workshops, conference calls andquestionnaires addressed via e-mail;

Elaborate the update of the requirements and of the definition of “innovative bussystem” on the basis of the results from the consultation process.

Task 2.2: Definition of Validation Objectives and Test Scenarios

Set the validations objectives of each priority research topic according to thetechnological innovations (TI) to be implemented, and base, on the overallobjective of the project, (increase attractiveness and improve the image of bussystems within a context of efficiency and sustainability concerns) therequirements set in the Task 2.1, and the main relevant bus domain strategies;

Define a test scenario for each research topic which contains the implementedtechnological innovations at the different sites, based on the validation objectivesestablished within this task.

Task 2.3: Development of evaluation framework including definition ofperformance targets and KPI selection

Define the evaluation framework; Develop performance targets to translate the validation objectives in clear and

measureable achievements; Derive appropriate Key Performance Indicators (KPI) sets in order to measure the

degree of target achievement.

Task 2.4: Definition of the Measurement Methodology and Plan

Complete the setting of performance targets and KPI’s by an enclosingmeasurement methodology and plan, specifying data needs and collectionprocedures;

Guarantee the comparability between the different sites as much as possible byany KPI also with regard to allow for a transferability of results as investigated inWP 4.


Figure 2 – Interaction among Task 2.1 and Task 2.2

The following four deliverables are to be produced within WP 2:

D2.1) Report on Updated Definition for “Innovative Bus System” [Month 9]The deliverable will summarise the updated requirements for the systems vehicle,infrastructure and operation according to the needs of the stakeholdersD2.2) Report on Test Scenarios and Validation Objectives [Month 6]For each research topic the validation objectives according to the technological to beimplemented at the demo sites will be summarized.D2.3) Report on Evaluation Framework [Month 11]Following the identified validation objectives D2.3 will describe the individual testscenarios per research topic including the selected quantitative and non-quantitativeperformance targets. It will further contain a list of the chosen quantitative and qualitativeKPIs per demo site with a definition of each KPI.D2.4) Measurement Plan Report [Month 13]Building on D2.3 in this deliverable the to-be-collected data for the chosen KPI’s will bedefined together with a description on how the data will be collected by the individualdemos.

The validationsobjectives of each

priority research topic(Task 2.2) will be set

according to theTechnological

Innovations to beimplemented, and basedon the requirements set

in the task 2.1.


The following table represent the general schedule of WP2:

1 2 3 4 5 6 7 8 9 10 11 12 13

MA

Y

JUN

JUL

AU

G

SEP

OC

T

NO

V

DEC JA

N

FEB

MA

R

APR

MA

Y

D2.1) Report onUpdated Definitionfor “Innovative BusSystem” [Month 9]

D2.2) Report on TestScenarios andValidation Objectives[Month 6]

D2.3) Report onEvaluationFramework [Month11]

D2.4) MeasurementPlan Report [Month13]

Table 1 – General schedule of WP2

Task

Month 2015-2016


3.2 Task 2.1 Work PlanThe table below summarizes the working plan by reporting the actions performed, whofulfilled the action and the deadlines. For the sake of clarity, the actions are grouped inseveral sub-tasks: Analysis and update of the main EBSF user needs. User needs updating Analysis of User needs by topics Analysis of the main and most innovative system and sub-systems requirements Delivery of D 2.1

Sub Task Action Who? Deadline

Analysis andupdate of themain EBSF userneeds.

Analysis of 3iBS results and check ofthe main 3iBS User requirementscoherency with regard to the calltopics. Sending to Task 2.1 partners

ASSTRA 22/07/2015

Validation of the 3iBS User Needsanalysis

Task 2.1 partners 31/07/2015

Predisposition of a list of the main3iBS User needs (Work Tool 1) toperform an updating and integration ofUN.

ASSTRA 07/08/2015

User needsupdating

Sending a WT 1 to Task 2.1 partnersand all the partners within consortiumfor checking, updating and integration.

ASSTRA 07/08/2015

All the partners fulfill the template andsend it to ASSTRA.

Task 2.1 partners 30/08/2015

Analysis of Userneeds by topics

Collection of all the results andpredisposition of User Needs sheetsby topic.

ASSTRA 15/09/2015

Analysis of themain and mostinnovativesystem and sub-systemsrequirements

Predisposition of System and Sub-system requirements Work Tool (WT2)to perform an updating of theFunctional Requirements.

ASSTRA 15/09/2015

Sending WT 2 to some Task 2.1partners to fulfill and update.

ASSTRA 22/09/2015

Sending User Needs sheets by topicto some Task 2.1 partners.

ASSTRA 02/10/2015

EBSF_2 WP2 - Task 2.1 Meeting Task 2.1 partners 26/10/2015


Sub Task Action Who? Deadline

Task 2.1 partners fulfill the templateand send it to:

o UITP: System Requirements;o ASSTRA: Vehicle Requirements;o CRTM, RATP, CHALMERS:

Infrastructure Requirements;o FRAUHNOFER: Operation

Requirements.

Task 2.1 partners,

UITP, ASSTRA,CRTM, RATPCHALMERS,FRAUHNOFER

18/11/2015

The responsible partners have toprocess the Work Tool 2 data andshare it with the partners

Task 2.1 partners,UITP, ASSTRA,CRTM, RATPCHALMERS,FRAUHNOFER

27/11/2015

Delivery ofD 2.1

First draft of the different chapter ofD2.1 (Report on Updated Definition forInnovative Bus System) for revision

ASSTRA andTask 2.1 partners

10/12/2015

Revision of the D2.1 draft 0 Task 2.1 partners 31/12/2015

Validation and consolidation of theD2.1

ASSTRA andTask 2.1 partners

By 22/01/2016

Delivery of the final D2.1. ASSTRA 31/01/2016

Table 2 – Working plan of the Task 2.1

The GANTT of WP 2 Task 2.1 is illustrated in the following Table 3.

Table 3 – GANTT of the Task 2.1 activities

Months 2015-2016

STEPS

1 2 3 4 5 6 7 8 9

MA

Y

JUN

JUL

AU

G

SEP

OC

T

NO

V

DEC

JAN

Analysis and update of EBSF Stakeholder, Areaof investigation, UNsAnalysis of the main and most innovativerequirementsValidation of the EBSF User RequirementsanalysisDesign of work toolsMailing work tools to the PartnersCollection of data and Partner experiencesEBSF_2 WP2 - Task 2.1 MeetingAnalysisDraft of D 2.1 and ValidationD 2.1 "Report on Updated Definition forInnovative Bus System"


4 Structure of the reportDeliverable 2.1 is structured in the following chapters:Chapter 5 presents the multi-step methodology developed to deliver an up-to-dateframework of bus system user needs and functional requirements, by capitalizing on theresults of the previous EBSF and 3iBS project.Chapter 6 reports the results of the analysis performed through the Work Tool 1 to selectthe user needs that can be still considered innovative. For each priority topics the selecteduser needs are graphically summarised in sheets which show the relative level ofachievement.Chapter 7 - Relevance of Functional Requirements describes how the application of theWork Tool 2 methodology to the EBSF/3iBS database of functional requirements, allowedidentifying the most significant features by priority topic This means that the systemrequirements, as well as vehicle, infrastructure and operation requirements which cangreatly contribute to the improvement of a bus system with respect to the six EBSF_2priority topics have been identified.Main results by priority topic are presented in Chapter 8.


5 The methodology for the “Innovative BusSystem Concept” update

The methodology developed to review and update the innovative bus system concept, asit was settled within the previous projects EBSF and 3iBS, is shown in Fig.3. The work hasbeen organized in four main activities (blue cells), namely:

a) 3iBS DATABASE UPDATINGb) LINK BETWEEN USER NEEDS AND EBSF_2 SIX TOPICSc) WORK TOOL 1d) WORK TOOL 2

Each main activity is structured in one or more sub activities (orange cells). For some ofthem, specific sheets (green cells) have been developed to analyse and review theelements, i.e. user needs and functional requirements, which together define the“innovative bus system concept” as developed in EBSF.

MAIN ACTIVITY SUB ACTIVITY OUTPUTS

Figure 3 – Methodology of the work

NN

Y

A) 3iBS DATABASEUPDATING

B) LINK BETWEENUSER NEEDS ANDTHE SIX TOPICS

C) WORK TOOL 1

D) WORK TOOL 2

VALIDATIONBY PARTNER

USER NEEDSUPDATING:RESULTS

USER NEEDSACHIEVEMENT

SHEETS BYTOPIC

USERNEEDS

UPDATING

USER NEEDS

INTEGRATION

STATISTICALTREATMENT OF

DATA

RELEVANCE OFFUNCTIONAL

REQUIREMENTS


5.1 3iBS Database updatingThe first step was the selection of the main User Needs and Functional Requirementsextrapolated from a database developed within the 3iBS project (2012-2015) and basedon the definition of the innovative bus system developed within the EBSF Project (2008-2012). A screenshot of the electronic database is shown in Fig.4.The analysis was aimed at updating the set of User Needs (UN) and FunctionalRequirements (FR) with regard to the ESBF_2 topics. ASSTRA considered only the mostinnovative user needs and functional requirements; redundant user needs have beenremoved.

Figure 4 – Screenshot of the 3Ibs electronic database (elaborated by the author)

* Partner’s activity with Work Tool 1; the name was “user requirements” in the 3iBs project but the meaning is“user needs” like in previous project EBSF. Partners have decided to use the definition of EBSF.

The results of the selection performed by ASSTRA have been integrated and completedby task 2.1 partners.

5.2 Link between User Needs and EBSF_2 six topicsIn the next step, the link between the main User Needs and the six priority topics, whichrepresent the key research areas EBSF_2 is committed to work on, has been identified.The activity has been performed by ASSTRA and the results have been validate andintegrated by task 2.1 partners.


Figure 5 – Link between User Needs and the six topics

As an example, Figure 5 shows the table which summarizes the outcomes of the task. Inthe first column, the eleven categories of “User needs Area”, extrapolated from 3IBSproject, are listed namely:

1. Safety and securityThis area assembles all those statements that impact on the level of safety and securityassured by the bus system.

2. Service performance (Service regularity and punctuality)This class groups the needs related to factors like regularity, punctuality and speed thataffect the performance of the bus transport offer.

3. Comfort, cleanness and quality feeling/perceptionIn this domain all needs linked with the perceived quality are listed, with special but notunique attention to factors like comfort and cleanness.

4. Accessibility to vehicles and infrastructuresThis area refers to accessibility issues in a system approach, thus tackling bothinfrastructures and vehicles. It does not include references to the access to information onthe bus system as this item is specifically dealt with in the following area.

5. Information to passengers, relational and behavioural issuesThis domain concerns all the information related needs, comprising both technologicaland behavioural features linked to the access to propel level of knowledge.

6. Modal integration and additional/flexible servicesIn this class the issue of integration, exclusively among PT modes, is tackled together withthe expectations related to the provision of additional services to meet a flexible traveldemand.

7. Environmental issuesThis area groups the statements impacting on the environmental performance of the bussystem.

8. MaintenanceFollowing the inputs mainly from PT operators, an area dedicated to maintenance relatedissues was created grouping those needs reflecting a more efficient and effectiveorganization of this activity.

9. Pricing and commercial policiesThis area refers to all commercial measures related to the bus system aiming atenhancing revenues, e.g. fare policies and transport advertising.

TOPIC 1 TOPIC 2 TOPIC 3 TOPIC 4 TOPIC 5 TOPIC 6

USER NEEDS AREA MAIN USER NEEDS

EnergyManagementStrategy and

Auxiliaries

DriverAssistance

Vehicle Design(Capacity,

Accessibility,Modularity)

IT Standardintroduction inexisting fleets

IntelligentGarage andpredictive

maintenance

UrbanInfrastruc

ture

Accessibility to vehicles andinfrastructures

Adoption of new technologies (e.g.information tech.) to not createbarriers for certain categories of users

X X X


Easy and fast boarding/alighting ofpassengers X X

Accessibility to vehicles andinfrastructures Integration bus and shelter designs X X


Platforms sized to host all waitingpassengers X

Comfort, cleanness andquality feeling/perception

Attention to ergonomics andstandardisation of driver place andtasks

X X


10. Economic and operation issuesThis class concerns the needs impacting on the decrease of operating costs, thustouching factors like the return on investment, the cost effectiveness/efficiency, theeconomic and financial solidity of operators.

11. Urban development and quality of lifeThis area concerns the interface between the bus system and the surroundingenvironment, comprising not only the modal integration private-public modes towardsseamless mobility, but also the overall interaction between urban land use and transport,the concept of integrated planning and the contribution of the bus system to reducingtraffic congestion and supporting city development.

For each user need area, the user needs selected as relevant are reported in in thesecond column. On the whole, approximately sixty user needs have been extrapolatedform the 3IBS database and used for the current analysis.Columns 3 to 8, report the EBSF_2 six priority topics:

1. Energy management Strategy and Auxiliaries2. Driver Assistance3. Vehicle Design (Capacity, Accessibility, Modularity)4. IT Standard introduction in existing fleets5. Intelligent Garage and predictive maintenance6. Urban infrastructure

For each of them, task 2.1 partners have selected the coherent user needs, i.e. the userneeds that can be satisfied by further research and development on the 6 areas.

5.3 Work Tool 1ASSTRA has designed a methodology in order to define the achievement of eachindividual User Need set in 2008 within the EBSF project, in collaboration with the publictransport operators and authorities, associations and research institutes involved in WP2.The first Work Tool consists of two worksheets to perform the updating and, whereneeded, the integration of the EBSF User Needs list.

User needs updatingThe first worksheet is designed to analyse if the user needs, as defined in 2008 withinEBSF, can still be considered “innovative” since they need further research anddevelopment activities or they can be considered “achieved” because they alreadyrepresent the state-of-the art in European bus systems. The worksheet is organized infourteen columns and based on the main user needs selected from the previous activities(see section 4.1 and 4.2 ); the partners have been asked to fill the sheet indicating if theuser needs are achieved or not.


An example is reported in Fig.6:

Figure 6– WT 1 - User needs updating

User needs integrationIn the second worksheet ASSTRA asked to task 2.1 partners to identify new User Needsdealing with the eleven User Needs Areas presented above and the 6 EBSF_2 prioritytopics. As a matter of fact, since 2008 bus systems and related mobility behaviours andusers’ needs have changed.The worksheet 2 is organized in ten columns, and several lines for the different sources.An example is reported in Fig.7.

Figure 7– WT 1 - User needs integration

In the first column, the eleven categories of “User needs Area” extrapolated from the 3IBSproject are listedThe second column shows as an example a few New User Needs Identified by companies/ associations Involved.In columns 3 to 8 Task 2.1 partners are required to indicate the coherency with the sixpriority topics (as already explained).Finally, in columns 9 and 10, Task 2.1 partners are required to specify for each new userneed the source (who and when published, web address, etc.) and specifying the name ofthe EBSF_2 partner providing the source of information.

User needs updating: RESULTSThe contributions provided by the task partners on the user needs updating, have beensummarized into a comprehensive Excel file, which contains several sheets, one for eachtopic.The degree of achievement (“achieved” means that the User Need isn’t innovative and itis less relevant for the definition of EBSF_2 System and Sub-System Functional

USER NEEDS AREA MAIN USER NEEDS

EnergyManagem

entStrategy

andAuxiliaries

Is URachieved? [Y/N]

DriverAssistan

ce


VehicleDesign

(Capacity,Accessibility,Modularity)


IT Standardintroduction in existing

fleets

Is URachieved?

[Y/N]


maintenance


UrbanInfrastru

cture


1Accessibility to vehicles andinfrastructures

Adoption of newtechnologies (e.g.information tech.) to notcreate barriers for certaincategories of users

X X X


Easy and fastboarding/alighting ofpassengers

X X


………………….. X X

TOPIC 6TOPIC 5TOPIC 4TOPIC 3TOPIC 2TOPIC 1

TOPIC 1 TOPIC 2 TOPIC 3 TOPIC 4 TOPIC 5 TOPIC 6

USER NEEDS AREA NEW USER NEEDSKey elements

EnergyManagementStrategy andAuxiliaries

DriverAssistance

Vehicle Design(Capacity,


IT Standardintroduction inexisting fleets


maintenance

UrbanInfrastructure

SOURCE (who and whenpublished, web

address, ect)

CONTACT(specify the name ofthe EBSF_2 partner

providing the sourceof information)

1 Service performanceReduce breakdowns during the

serviceX x

"Quaderno per ladiffusione degli

ITS" 2012- ASSTRApublication

ASSTRA

2 MaintenanceIncrease life of insulating materialsand rubber pipes in the engine room

due to high temperaturesx x x

“RaccomandazioniAsstra per lafornitura di

autobus 2014”

ASSTRA

3 Sevice performanceImprove energy efficiency for

climatizationx x

“RaccomandazioniAsstra per lafornitura di

autobus 2014”

ASSTRA


Requirements) has been calculated in percentages, as shown in the example below about“Driver assistance”.

Figure 8 – WT 1 - User needs updating: RESULTS

Columns 1 and 2 are the same as Figure 7. In the following columns (Figure 8), Task 2.1partners are required to indicate the degree of achievement for each user Need. In thelast two columns the average percentages of achievement are shown.These worksheets represent the database of the “User Needs sheets by topic” that will beanalyzed in the next section.


User needs from previous projectThe results achieved through the WORK TOOL 1 results have been developed insummary sheets, which show the selected user needs by topic and their level ofachievement (in percentage). ASSTRA elaborated a sheet for each one of the six prioritytopics identified by the proposal. An example of the sheet dealing with the topic “Energymanagement Strategy and Auxiliaries” is reported below.This logical approach permits to focus the attention on both the individual user needs andthe users needs area through their relative level of achievement in order to help policymakers and different stakeholders to take decision during the demo phases.

Figure 9 – WT 1 - User needs from previous project

- Achieved means that the User Need is not considered innovative and it is less relevantfor the definition of EBSF_2 System and Sub-System Functional Requirements.- Level of achievement is used to photograph the state of the art and identify (with aquantitative attribute) the user need areas that need further research and development.This graphic representation facilitates the reading through a clear visual summary of theresults. The green/red parts represent the average (%) of yes/no regarding theachievement of the user needs belonging to the same area.User needs integration by partner


The sheet shown below has been developed by ASSTRA to summarize all the new userneeds suggested by the task contributors. In the frame of the analysis, a “new user need”is a need that has not been identified as such in the previous projects. For each of themthe relative topic, user need area and source is specified

Figure 10 – WT 1 - User needs integration by partner

5.4 Work Tool 2The functional requirements identified by ASSTRA as relevant for the analysis through theupdate of the 3iBS database (as already explained in section 5.1 3iBS Databaseupdating), can be grouped into four areas which refer to the bus as a system and - at thesame time – characterize the key functional components of the bus system as the vehicle,the infrastructures and the related operational concepts and practices. The four areas are: System Vehicle (Sub-system); Infrastructure (Sub-system); Operation (Sub-system).


The functional requirements related to each area are then divided in several categoriesfollowing the 3iBS project classification. As an example, the 8 categories for the sub-system “vehicle”, extrapolated from the Work Tool 2, are reported in Table 4.

VEHICLE

1 DRIVER'S CABIN MANAGEMENT

1.1 Functional issues management

1.2 Ergonomic and comfort issues management

1.3 Safety and security issues management

2 PASSENGER’S AREA MANAGEMENT

2.1 Internal layout and internal flow management

2.2 Provide an attractive design

2.3 Information management

3 MODULARITY MANAGEMENT

3.1 Inside layout modularity management

3.2 Global geometry modularity management

3.3 Provide modular conception & fabrication

4 IT APPLICATION ON BOARD MANAGEMENT

4.1 Provide interface between the vehicle andfunctions/devices on board

4.2 IT System Architecture management

5 GUIDANCE MANAGEMENT

5.1 Guidance, external interaction and steering strategiesmanagement

5.2 Assisted guidance system management

5.3 Stop approaching system management

6 ENVIRONMENT, ENERGY SAVING MANAGEMENT

6.1 Fuel consumption management

6.2 Leakage management

7 STRATEGIC SUB SYSTEM MANAGEMENT

7.1 Provide fire protection

8 MAINTENANCE MANAGEMENT

8.1 Assure maintainability

Table 4 – Vehicle categories

The Work Tool 2 summarizes the selected functional requirements (about 200) in oneexcel file, divided into 4 spreadsheets according to the area they refer to. The 4spreadsheets present a similar structure and are organized in nine columns, and severallines for the different sources. An example for each sheet is reported below.


- System requirements

- Vehicle requirements (Sub-System)

- Infrastructure requirements (Sub-System)

- Operation requirements (Sub-System)

In the first column all the selected “Functional requirements” are listed and divided bycategories.In the second column the partners are asked to indicate for each Functional Requirement(FR) the user needs area the requirement refers to or deals with. The following userneeds areas (UNA), as identified in EBSF, have been considered for the analysis:

1. Urban development and quality of life2. Accessibility to vehicles and infrastructures3. Comfort, cleanness and quality feeling/perception4. Economic and operation issues5. Environmental issues

FUNCTIONAL REQUIREMENTS USER NEEDS AREA

TOPIC 1:Energy

ManagementStrategy and

Auxiliaries

TOPIC 2:Driver

Assistance

TOPIC 3: VehicleDesign (Capacity,


TOPIC 4: ITStandard

introduction inexisting fleets

TOPIC 5:Intelligent Garage

and predictivemaintenance

TOPIC 6:Urban

InfrastructureCONTACT

Enable punctuality of the service in line with the publishedscheduleEnable accessibility for all in all zones (buses and stations,connections)

Enable the collection and analysis of mobility demand dataOffer specific services to passengers or the publicAllow a concept of priority for PTEfficient contingency management in order to minimisedelays occuring


TOPIC 1: EnergyManagementStrategy andAuxiliaries

TOPIC 2: DriverAssistance



TOPIC 4: ITStandard


TOPIC 5: IntelligentGarage andpredictive

maintenance

TOPIC 6:Urban


1. Driver's cabin management1.1 Functional issues managementKeep driver informed on the state of the vehicleAllow drivers to access to all controlsAllow drivers to greet passengersAllow driver to give information to passengersAllow drivers to check that passengers comply with regulations






TOPIC 4: ITStandard



maintenance

TOPIC 6:Urban


1. Running way requirements managementAssure the safe driving of the bus on every weather conditionand timeAssure the strength to the bus weight and its circulation

Allow giving priority to bus circulation over the rest of the trafficAllow the circulation of the bus and the visibility of the driver notbe hindered by any obstacleAllow buses to negotiate speed reducing construction and otherobstacles on the running-way in a satisfactory manner






TOPIC 4: ITStandard



maintenance

TOPIC 6:Urban


1. Manage the preparation for service1.1 Service organisation management Plan the network to minimize lines changesServe traffic’s generator areasDesign the network together with the other PT modesEnsure as reliable as possible travel timeConsider the fare collection system when designing the busservice/networkConsider the bus service needs in the city planning, in thedefinition of the city master plan


6. Information to passengers, relational and behavioural issues7. Maintenance8. Modal integration and additional/flexible services9. Pricing and commercial policies10. Safety and security11. Service performance

In the columns 3 to 8, the partners are asked to indicate, according to their knowledge andexperience how relevant each Functional Requirement is with respect to the six prioritytopics, listed below:

1. Energy management Strategy and Auxiliaries2. Driver Assistance3. Vehicle Design (Capacity, Accessibility, Modularity)4. IT Standard introduction in existing fleets5. Intelligent Garage and predictive maintenance6. Urban infrastructure

The level of relevance can be expressed by grading between 0 and 3 in the drop downbox, where:

0 = No relevancy – The functional requirement is not relevant for the prioritytopic.

1 = Low level – The functional requirement is little relevant for the prioritytopic.

2 = Moderate level – The functional requirement is not completely relevant forthe priority topic.

3 = High level – The functional requirement is completely relevant for thepriority topic.

n/a. = The functional requirement is not judged

Moreover the partners had the possibility to integrate the selected database by proposingnew FRs, which have not been considered in the previous projects.


Statistical treatment of dataThe data collected through the WORKTOOL2 have been processed in an Excel File.For each FRs’ area a partner (or a group of partners) have been identified asresponsible for the statistical elaboration of the data, namely UITP for SYSTEM REQUIREMENTS; ASSTRA for VEHICLE REQUIREMENTS; CRTM, Chalmers, RATP for INFRASTRUCTURE REQUIREMENTS; FRAUNHOFER for OPERATION REQUIREMENTS.

The partners, leaded by ASSTRA, agreed on common rules for the statistic elaborationand the outcomes to be delivered. Fig.11 shows as an example the data elaboration forthe functional requirements dealing with the “vehicle” area and concerning topic 1”Energy Management Strategy and Auxiliaries” and topic 2 “Driver Assistance”; thecells highlighted follow the below indications: Cells are highlighted in red when the relevance of the functional requirement to

the topic is high for at least ≥50% of the responding partners ; Cells are highlighted in orange when the relevance of the functional

requirement to the topic is moderate for at least ≥50% of the respondingpartners ;

Cells are highlighted in dark red when the functional requirement is consideredhigh relevant for the topic by all the responding partners; they are consideredone of the most relevant requirements.

A functional requirement is not relevant for the topic when all the partners(100%) answer 0 for all the priority topics.

Figure 11 – Example of statistical treatment of data

Relevance of Functional RequirementsThe results of the statistical analysis are summarised in simple tables to clearly list therequirements which have been considered most relevant by the partners involved inthe analysis. The level of relevance is graphically shown with coloured icons, asfollows: An orange cross, if the level of relevance is moderate (score 2) for the ≥50%

of the partners ; A red cross if the level of relevance is high (score 3) for the ≥50% of the

partners ;


Two red cross if the level of relevance is high (score 3) for all the respondingpartners

An example, concernig the vehicle, is reported below.

Energy Management Strategy and Auxiliaries

Functional requirements MODERATERELEVANCE

HIGHRELEVANCE

6. Environment, energy saving management

6.1 Fuel consumption management

Allow the bus to meet the network performancerequirements of its specific service

6.2 Leakage management

Use fluids eco-friendly and hazard free

Figure 12 – Example of FRs relevance by sheets


6 Evaluation of User Needs achievement by topic

6.1 BackgroundThe European Bus System of the Future (EBSF) project was based on the considerationthat the bus is the most universal solution for a balanced and sustainable urbandevelopment from an economic, environmental and social standpoint. Therefore, in orderto improve the usage of public transport, the project was committed to improve theattractiveness of bus systems for all types of stakeholders. This can be achieved only byapplying a comprehensive system approach, built on the needs of people that benefit fromthe service on a daily basis, the community that defines the nature of public transport, thecompany that manages and operate the fleetas well as the manufactories that provide thevehicles.Thus, one of the first tasks of EBSF was represented by the definition of the needs of themajor bus stakeholders, operators and authorities and to transform them into systemrequirements, in order to define a common system approach.The outcomes of thisanalysis was a list of user needs that indicated the main areas for innovation and thepotentials to overcome the negative perception that passengers can have of the bus.The analysis of user needs started with an extensive information collection andharmonization of the existing documents, data, studies, researches, and surveys at local,national and European levels. The final results were validated by the EBSF consortium,and assessed externally via the consultation of the EBSF User Group. Needs wereinvestigated in order to determine, from the different bus-transport stakeholders’ point ofview, the functionalities required by the new system, and also to analyse the performancescenarios to be tested.In the frame of the 3IBS Project (2012-2015), an intelligent tool was implemented for themanagement and performance assessment of Bus System requirements, as defined inthe EBSF project. This tool, developed by D’Appolonia and customised for the 3iBSproject, links together User needs, Key Performance Indicators (KPIs) and system andsub-system requirements in order to facilitate the analysis of the EBSF results. The toolhas been implemented and made available as a web application on the 3iBS web site andit is freely accessible for all registered users.Chapter 6 presents the results of the users’ needs analysis performed through aconsultation process among the partners of Task 2.1 and based on the Work Tool 1(extensively described in section 5.3).The outcomes are reported in the following sections (6.2 to 6.7) in graphic sheets whichshow the user needs selected as relevant by priority topic and their level of achievement(in percentage). This logical approach permits to focus the attention on both the individualuser needs and the user needs areas through their relative level of achievement in orderto support policy makers and bus stakeholders in identifying the main for further researchand implementation activities.

Two types of sheets are reported for each topic: User needs from previous project, to present their level of achievement according

to the state of the art of the European bus systems. User needs integration by partner, to summarize all the user needs suggested by

the task contributors, i.e. users’ needs which have not been identified as such inthe previous projects.


For a correct understanding of the graphic elaborations, it is worth highlighting thefollowing: A user need is considered “achieved” if according the consultation process it

cannot be considered innovative anymore and, therefore it is less relevant for thedefinition of EBSF_2 System and Sub-System Functional Requirements.

The “level of achievement of the user needs areas” is used to photograph thestate of the art and characterize with a quantitative attribute (in percentage) theuser need areas that need further research and implementation activities. Thisgraphic representation facilitates the cross-analysis of the results through a clearvisual summary. The green and red areas represent respectively the averagepercentage of positive (yes) and negative (no) answers regarding the achievementof the user needs.


6.2 Energy management strategy and auxiliaries

User needs from previous project

Energy management Strategy andAuxiliaries

User needs

Achieved

User needs areaLevel of

achievement ofthe User Needs

Area%Y %N

Comfort on bus and station 0 100

Comfort, cleannessand quality

feeling/perception

Improved overallattractivity/image of the PTsystem

0 100

Possibility of monitoring thecomfort in the vehicle

0 100

Suitable heat and airconditioning systems

50 50

Applying new recommendedprocurement rules (warranty,vehicle’s availability, functionalspecifications, penalties of allsorts...)

50 50

Economic andoperation issues

Management tools for thecollection and improvement ofdriving styles

0 100

High energy efficiency ofvehicles

16,6 83,4

Environmentalissues

Precise and periodic controls ofpolluting emissions

33,3 66,7

Recyclability of the vehicle andof its parts

0 100

Reduce engine noise 40 60

Healthy working environment 75 25 Safety and security

Table 5 – User needs achievement for Topic 1

Regarding the topic 1 “Energy management strategy and auxiliaries”, the consideredareas and the connected levels of achievement (%) are reported below:

1. Comfort, cleanness and quality feeling/perception (12,5%);2. Economic and operation issues (25%);3. Environmental issues (12,6%);4. Safety and security (75%).


In particular, the following UNs have been classified with a percentage of achievement “0”: About the first area, “Comfort on bus and station”, “Improved overall

attractivity/image of the PT system” and “Possibility of monitoring the comfort inthe vehicle”;

About the second area, “Management tools for the collection and improvement ofdriving styles”;

About the third area, “Recyclability of the vehicle and of its parts”.

User needs integration by partner

Energy management Strategy andAuxiliaries

User needs User needsarea SOURCE CONTACT

Driving smoothness

Comfort,cleanness and

qualityfeeling/perception

“User Quality Survey2014”

CRTM

Low operating costsEconomic and

operation issuesEBSF2 USER REQ.SHEET_complete

UITP

Smart E-mobility fleet andinfrastructure Environmental

issues

“Personal Interview” CRTM

Vehicle electric charge andtemporally storage in the busterminals

n.a. RATP

Increase life of insulatingmaterials and rubber pipes inthe engine room due to hightemperatures

Maintenance“Raccomandazioni

Asstra per lafornitura di autobus

2014”

ASSTRA

Improve energy efficiency forclimatization

Serviceperformance

“RaccomandazioniAsstra per la

fornitura di autobus2014”

ASSTRA

Electric climatization



ASSTRA

Improve energy storage system



ASSTRA

Increase commercial speed:inclusion of parking controldevices inside the bus, mobilityservice, etc.

"EMT Action Plan2014"

CRTM

Table 6 – User needs integration for Topic 1


LEGEND:SOURCE: Who and when published, web address, etc.CONTACT: The name of the EBSF_2 partner providing the source of information.

The partners decided to add some user needs concerning the following areas:1. Comfort, cleanness and quality feeling/perception2. Economic and operation issues3. Environmental issues4. Maintenance5. Service performance

Regarding the “Energy management Strategy and Auxiliaries”, the partners integrationsconcern mainly the electrification of the vehicle; indeed, the additions affect themes likethe vehicle electric charge and the energy storage systems.At the same time, the integrations refer to the vehicle climatization and the requirement toreduce the energy consumption; indeed this aspect results essential to achieve an optimalstatus of comfort for the passenger.


6.3 Driver Assistance


Driver Assistance

User needsAchieved



Area%Y %N

Attention to ergonomics andstandardization of driver placeand tasks

25 75 Comfort, cleannessand quality

feeling/perceptionImproved overallattractivity/image of the PTsystem

0 100


50 50 Economic andoperation issues

Standardization of components 0 100

High energy efficiency ofvehicles

20 80Environmental

issues

Continuous training ofmaintenance personnel alsowith the support of multimedia

40 60 Maintenance

Absence/minimize of obstacleson the pathway to the bus stop

50 50

Safety and security

Availability of instant alertdevices for drivers

60 40

Healthy working environment 75 25

Improved driver assistancesystem

0 100

Improved training for drivers 33.3 66.7

On line assistance in case ofemergency

50 50

Possibility for the driver tocontrol the trajectory whateverroad or weather condition

33.3 66.7


The following levels of achievement (%) have been identified for the user needsareas dealing with topic 2 “Driver Assistance: Comfort, cleanness and qualityfeeling/perception (12,5%);


Economic and operation issues (25%); Environmental issues (20%); Maintenance (40%); Safety and security (44%).

In particular, the following UNs have been classified with a percentage of achievement “0”: About the first area, “Improved overall attractivity/image of the PT system”; About the second area, “Standardization of components”; About the fifth area, “Improved driver assistance system”.


Driver Assistance


Smooth driving



“User Quality Survey2014”

CRTM

EBSF2 USER REQ.SHEET_complete

UITP

Low operating costs Economic andoperation issues


UITP

Reduced energy use n.a. CHALMERS

Reduction of emissionsEnvironmental

issues n.a. CHALMERS



The partners decided to add some user needs concerning the following areas: Comfort, cleanness and quality feeling/perception Economic and operation issues Environmental issues

Regarding the topic 2 “Driver assistance”, the integrations proposed by partners concernmainly the “economic and operation issues”; indeed the partners proposals regard thereduction of operating costs and of the energy use.Moreover the “environmental issue” is also considered with the need to reduce theemissions of the vehicle through an assisted driving.


6.4 Vehicle design


Vehicle design (Capacity, Accessibility,Modularity)

User needsAchieved



Area%Y %N

Adoption of new technologies(e.g. information tech.) to notcreate barriers for certaincategories of users

33.3 66.7

Accessibility tovehicles and

infrastructures

Easy and fast boarding/alightingof passengers 0 100

Integration bus and shelterdesigns 0 100

Attention to ergonomics andstandardization of driver placeand tasks

50 50


feeling/perception

Cleanness (bus, stop andstation) 16.6 83.4

Comfort on bus and station0 100


0 100

Possibility of monitoring thecomfort in the vehicle 0 100

Reduction/elimination of internalnoise ,vibrations and ‘odours" 20 80

Suitable heat and air condit.systems 40 60



User needsAchieved



Area%Y %N


50 50


Development of externalmodularity to adapt the serviceto the demand (impact onoperating costs)

0 100


0 100

Standardization of components0 100

High energy efficiency ofvehicles 16.6 83.4

EnvironmentalissuesRecyclability of the vehicle and

of its parts 20 80

Clear identification of theentrance/exit doors and ofreserved seats

83.3 16.7

Information topassengers,

relational andbehavioural issues

Easy and accessible information(bus, stop and station) 50 50

Possibility of using extraservices like telephone andinternet (on the bus and at thestation/stop)

40 60

Reliability/availability ofpassengers informationsystems, especially on tripchanging, traffic and "next stop"

50 50

Bus seating capacity adaptableto the local network and specificneeds of the operator/city

50 50 Modal integrationand



User needsAchieved



Area%Y %N

Development of externalmodularity to adapt the serviceto the demand (impact on travelcomfort)

0 100

additional/flexibleservices

Adaptable driver cabin when thedriver is in charge of ticketselling

0 100Pricing and

commercial policiesFlexible vehicle solutions forticketing and space for ticketingequipments

25 75

Healthy working environment75 25

Safety and securityControl of door opening/closingfree of risk for passengers 50 50

Fire fighting devices (enginecompartments) 0 100

Higher transport capacity0 100

Service performanceStandardization and easyinstallation of on boardtelemetric components (AVMS,ticketing, passenger informationdevices, telediagnostic box andcommunication gateway)

20 80

Intermodality PT and bike0 100

Urban developmentand quality of lifeAttractive and welcoming design

(bus - in particular exteriors -and station/stop)

0 100


The following levels of achievement (%) have been identified for the user needs areasdealing with topic 3 “Vehicle design”,: Accessibility to vehicles and infrastructures (12%);


Comfort, cleanness and quality feeling/perception (19%); Economic and operation issues (13%); Environmental issues (19%); Information to passengers, relational and behavioural issues (54%); Modal integration and additional/flexible services (25%); Pricing and commercial policies (12,5%); Safety and security (40%); Service performance (10%); Urban development and quality of life (0%).

In particular, the following UNs have been classified with a percentage of achievement “0”:

About the first area, “Easy and fast boarding/alighting of passengers” and“Integration bus and shelter designs”;

Regarding the second area, “Comfort on bus and station”, “Improved overallattractivity/image of the PT system” and “Possibility of monitoring the comfort inthe vehicle”;

About the third area, “Development of external modularity to adapt the service tothe demand (impact on operating costs)”, “Management tools for the collection andimprovement of driving styles” and “Standardization of components”;

Regarding the sixth area, “Development of external modularity to adapt the serviceto the demand (impact on travel comfort)”;

About the seventh area, “Adaptable driver cabin when the driver is in charge ofticket selling”;

Regarding the eighth, “Fire fighting devices (engine compartments)”; About the ninth, “Higher transport capacity”; Regarding the tenth, “Intermodality PT and bike”.




Bicycle rack in the bus Accessibility tovehicles andinfrastructure


Full accessibility, for all citizensindependently from theirphysical or social status


UITP

Smart E-mobility fleet andinfrastructure

Environmentalissues “Personal Interview” CRTM


Maintenance“Raccomandazioni

Asstra per lafornitura di autobus

2014”

ASSTRA




Improve energy efficiency forclimatization

Serviceperformance



ASSTRA

Electric climatization



ASSTRA




ASSTRA

Define occupancy levelsaccording to their routes "Personal Interview” CRTM



CRTM

To allow the entry by all doorsand ticketing machine beforeand onboard the vehicle; smarttechnologies (NFC, QR, etc.)

Pricing andcommercial

policies"EMT Action Plan

2014"CRTM

Positive absorption of electricbuses components in thevehicle designs (harmoniousexteriors and interiors)



n.a RATP

Status upgrade for buses, asurban objects, to be accepted indense urban zones


n.a RATP

Improved commercial speedEBSF2 USER REQ.SHEET_complete

UITP

Low operating costsEBSF2 USER REQ.SHEET_complete

UITP




The partners decided to add some user needs concerning the following areas:

Accessibility to vehicles and infrastructure; Environmental issues; Maintenance; Service performance; Pricing and commercial policies; Comfort, cleanness and quality feeling/perception; Economic and operation issues.

The topic “Vehicle design (Capacity, Accessibility, Modularity)” concerns manifold userneeds, that influence the most of the considered areas. The need to improve the serviceperformance is confirmed, in order to achieve new economic improvements. Newelements regarding the mobile ticketing and the full accessibility of the vehicle arementioned.

6.5 IT Standard introduction in existing fleets


IT Standard introduction in existingfleets

User needsAchieved



Area%Y %N


40 60Accessibility to

vehicles andinfrastructures


0 100Comfort, cleanness

and qualityfeeling/perception


33.3 66.7

Economic andoperation issuesEfficient fleet management, also

through collaboration busmanufacturers/ITS developers

50 50

Standardization of components 0 100



User needsAchieved



Area%Y %N

Easy and accessible information(bus, stop and station)

42.9 57.1




28.6 71.4


57.1 42.9

Adoption of structural standard:linked with systems (remoteconnections) and outsidedevices

0 100

Maintenance

Easy, but detailed, on boarddiagnosis without use ofexternal diagnostic device (pc,tester, diagnostic workstation,etc)

16.6 83.4

Improved telediagnostic andpre-analysis of potential sub-systems failure (preventivemaintenance)

0 100

Reduction of maintenance time(duration and frequency):increase in LCC of components

0 100

Standardisation and easyinstallation of on board telematiccomponents ( telediagnosticbox)

14.3 85.7

Standard. of communicationprotocols between vehicles andback-office

0 100

Integration between the differenttypes of networks (transport,information and ticketing)

0 100

Modal integrationand

additional/flexibleservices



User needsAchieved



Area%Y %N

Flexible vehicle solutions forticketing and space for ticketingequipments

40 60Pricing and

commercial policies

Improved driver assistancesystem

0 100

Safety and securityOn line assistance in case ofemergency

33.3 66.7

Easy diagnosis andidentification of errors tofacilitate the role of systemcontroller

0 100

Easy collection of data tocontrol, evaluate and adapt theservice

28.6 71.4

Service performance

Efficient fleet management 33.3 66.7

Knowing the passenger load inreal time

0 100

Standardisation and easyinstallation of on boardtelemetric components (AVMS,ticketing, passenger informationdevices, telediagnostic box andcommunication gateway)

33.3 66.7

Improved management of trafficlights and priorities for PT(green wave)

40 60Urban development

and quality of life


The following levels of achievement (%) have been identified for the user needs areasdealing with topic 4 “IT Standard introduction in existing fleets:

Accessibility to vehicles and infrastructures (40%); Comfort, cleanness and quality feeling/perception (0%); Economic and operation issues (27,7%); Information to passengers, relational and behavioural issues (42,8%); Maintenance (5,1%);


Modal integration and additional/flexible services (0%); Pricing and commercial policies (40%); Safety and security (11,1%); Service performance (23,8%); Urban development and quality of life (40%).

In particular, the following UNs have been classified with a percentage of achievement “0”:

Regarding the second area, “Improved overall attractivity/image of the PT system”; About the third area, “Standardization of components”; Regarding the fifth area, “Adoption of structural standard: linked with systems

(remote connections) and outside devices”, “Improved telediagnostic and pre-analysis of potential sub-systems failure (preventive maintenance)”, “Reduction ofmaintenance time (duration and frequency): increase in LCC of components” and“Standard. of communication protocols between vehicles and back-office”;

About the sixth area, “Integration between the different types of networks(transport, information and ticketing)”;

Regarding the eighth, “Improved driver assistance system” and “Easy diagnosisand identification of errors to facilitate the role of system controller”;

About the ninth, “Knowing the passenger load in real time”.








UITP

Reduce installation time takento install equipment on-boardbus

Maintenance3iBS deliverable :WP26 / "TfL BusPre-Preparation"

DIGIMOBEE

Use of plug'n play ITS modulescompliant with ITxPT based onmodular/flexible IT architecture.

Serviceperformance

3iBS deliverable :WP26 / "TfL BusPre-Preparation"

DIGIMOBEE

Open data for real timeinformation of the serviceperformance


CRTM

Define occupancy levelsaccording to their routes "Personal Interview” CRTM




Different apps for information ofthe service based on open data

Information topassenger


CRTM



policies


CRTM



The partners decided to add some user needs concerning the following areas: Environmental issues Economic and operation issues Maintenance Service performance Information to passenger Pricing and commercial policies

Regarding the “IT Standard introduction in existing fleets” it emerges the necessity toimprove the IT systems mainly in order to gain better service performances.

6.6 Intelligent Garage and predictive maintenance


Intelligent Garage and predictivemaintenance

User needsAchieved



Area%Y %N


0 100Comfort, cleanness

and qualityfeeling/perception



User needsAchieved



Area%Y %N


40 60


Efficient fleet management, alsothrough collaboration busmanufacturers/ITS developers

0 100

Adoption of structural standard:linked with systems (remoteconnections) and outsidedevices

0 100

Maintenance

Continuous training ofmaintenance personnel alsowith the support of multimedia

0 100


14.3 85.7


0 100

Reduction of maintenance time(duration and frequency):increase in LCC of components

0 100

Standardisation ofcommunication protocolsbetween vehicles and back-office

0 100


20 80 Safety and security



User needsAchieved



Area%Y %N

Easy collection of data tocontrol, evaluate and adapt theservice

0 100

Service performance

Efficient fleet management 0 100


16.6 83.4


The following levels of achievement (%) have been identified for the user needs areasdealing with topic 5 “Intelligent Garage and predictive maintenance”,: Comfort, cleanness and quality feeling/perception (0%); Economic and operation issues (20%); Maintenance (2,4%); Safety and security (20%); Service performance (5,5%).

In particular, the following UNs have been classified with a percentage of achievement “0”: About the first area, “Improved overall attractivity/image of the PT system”; Regarding the second area, “Efficient fleet management, also through

collaboration bus manufacturers/ITS developers”; About the third area, “Adoption of structural standard: linked with systems (remote

connections) and outside devices”, “Continuous training of maintenance personnelalso with the support of multimedia”, “Improved telediagnostic and pre-analysis ofpotential sub-systems failure (preventive maintenance)”, “Reduction ofmaintenance time (duration and frequency): increase in LCC of components” and“Standardisation of communication protocols between vehicles and back-office”;

Regarding the fifth area, “Easy collection of data to control, evaluate and adapt theservice” and “Efficient fleet management”;







UITP



Reduce installation time takento install equipment on-boardbus

Maintenance

3iBS deliverable :WP26 / "TfL BusPre-Preparation"

DIGIMOBEE




ASSTRA




ASSTRA

Optimization of vehicular flow indepot


UITP



The partners decided to add some user needs concerning the following areas: Economic and operation issues Environmental issues Maintenance

Regarding the “Intelligent Garage and predictive maintenance” it emerges the need tooptimize the logistic in maintenance protocols with the help of IT Systems. Moreover, theimprovement of the quality of the material could answer to the growing efforts to whom thevehicles are subjected. It was important to facilitate the vehicles flow to and from thedepots.


6.7 Urban infrastructure


Urban infrastructure

User needsAchieved



Area%Y %N


0 100

Accessibility tovehicles and

infrastructures

Easy and fast boarding/alightingof passengers

0 100

Integration bus and shelterdesigns

0 100

Platforms sized to host allwaiting passengers

28.6 71.4

Cleanness (bus, stop andstation)

0 100


feeling/perceptionComfort on bus and station 0 100


0 100

Optimization of timetables andconnections/transfers

42.9 57.1Economic and

operation issues

Easy and accessible information(bus, stop and station)

42.9 57.1




28.6 71.4


42.9 57.1



User needsAchieved



Area%Y %N

Integration between the differenttypes of networks (transport,information and ticketing)

0 100Modal integration

andadditional/flexible

servicesMore bus lines feeding railwaysstations

83.3 16.7

Absence/minimize of obstacleson the pathway to the bus stop

28.6 71.4Safety and security

Knowing the passenger load inreal time

0 100Service performance

Intermodality PT and bike0 100

Urban developmentand quality of life

Pavements free from triphazards and unnecessaryobstacles - free and safemovement

28.6 71.4

Reduction of traffic andcongestion

20 80

Attractive and welcoming design(bus - in particular exteriors -and station/stop)

0 100

Seamless travel16.6 83.4

Improved management of trafficlights and priorities for PT(green wave)

66.6 33.4

Increase of number of buscorridors

50 50


The following levels of achievement (%) have been identified for the user needs areasdealing with topic 6 “Urban infrastructure: Accessibility to vehicles and infrastructures (7,2%); Comfort, cleanness and quality feeling/perception (0%);


Economic and operation issues (42,9%); Information to passengers, relational and behavioural issues (38,1%); Modal integration and additional/flexible services (41,6%); Safety and security (28,6%); Service performance (0%); Urban development and quality of life (16%).

In particular, the following UNs have been classified with a percentage of achievement “0”: About the first area, “Adoption of new technologies (e.g. information tech.) to not

create barriers for certain categories of users”, “Easy and fast boarding/alighting ofpassengers” and “Integration bus and shelter designs”

Regarding the second area, “Cleanness (bus, stop and station)”, “Comfort on busand station” and “Improved overall attractivity/image of the PT system”;

Regarding the fifth area, “Integration between the different types of networks(transport, information and ticketing)”

About the seventh area, “Knowing the passenger load in real time”; Regarding the eighth area, “Intermodality PT and bike” and “Attractive and

welcoming design (bus - in particular exteriors - and station/stop)”.




Open data for real timeinformation of the serviceperformance

Serviceperformance


CRTM



CRTM

Promotion of bus lanes,busways and traffic-light priorityfor the buses, BRT


Different apps for information ofthe service based on open data

Information topassenger

“EMT Action Plan2014"

CRTM

Innovative bus shelterconcepts: efficient (solarpanels), internet, bike; VMP

Comfort andquality “Personal Interview” CRTM

Smart E-mobility fleet andinfrastructure Environmental

issues


Vehicle electric charge andtemporally storage in the busterminals

n.a. RATP




To facilitate connection with"new modes" (carsharing) andpark&ride

Urbandevelopment and

quality of life


Bus priority= HOV, Expresslines, traffic lights, priority laneswith new technologies…


Bus terminals as urban assetsincluded in the cityscapes (vs.as optimized transport hubs)

“Recommandationset outils pour laconception des

gares routières” -RATP déc 2015

RATP

Co-design of bus terminals withlocal authorities and serviceproviders

n.a. RATP



policies

“EMT Action Plan2014"

CRTM

Easier transfers Accessibility tovehicles and

infrastructures


Full accessibility, for all citizensindependently from theirphysical or social status


UITP

Positive business models forbus terminals Economic and

operation issues

n.a. RATP

Improved commercial speedEBSF2 USER REQ.SHEET_complete

UITP



The partners decided to add some user needs concerning the following areas: Service performance; Information to passenger; Comfort and quality; Environmental issues; Urban development and quality of life; Pricing and commercial policies; Accessibility to vehicles and infrastructures; Economic and operation issues.


A lot of user needs are connected to this topic. Some of them ask to improve theaccessibility of the passengers through new technologies, in order to upgrade theintermodality and the interoperability.


7 Relevance of Functional Requirements

7.1 BackgroundWithin the EBSF Project a bus system has been defined as a complex systemcharacterized by “the synergic superposition of vehicle, infrastructure and operation”,where the properties of the whole system do not merely correspond to the sum of theproperties of its parts.As a result, the bus system definition delivered at the end of project is based, amongothers elements, on a set of functional requirements which represent a coherent andconsistent list of features that the whole system has to include in order to satisfy theneeds of the bus stakeholders. The requirements have been identified thorough a bottom-up approach which was built on consolidated system engineering methodologies wherethe requirements of the system stem directly from the stakeholders’ needs. More than 500user needs have been collected from all the bus system’s stakeholders (regular and non-regular users, operators, authorities, industries, and other road users) and then translatedinto precise statements with targets to be meet by the innovative bus system (i.e. theEuropean Bus System of the Future).When the definition of the system requirements specifications have been consolidated,the project partners have defined the detailed requirements to be fulfilled by the threesubsystems of the EBSF, namely the vehicle, the infrastructure and the operations.The vehicle requirements represent the basic features for innovative urban/suburbanbuses and are intended to support the manufacturers in the development of their nextgeneration products. Among the other, the requirements focus on driver’s cabin,passengers’ area, modularity, IT applications.The infrastructure requirements are the specifications of the functional requirements of theinfrastructures that will make possible for the EBSF to operate in urban and suburbanareas. They cover a wide set of topics like design, intermodality and accessibility, safetyand perceived security for staff, bus users and non-users.Finally, the operations requirements are the main features of the EBSF operation systemwhich consider all the operational phases of the service: preparation for service, enteringinto service, running service, failures during the service, maintenance and depotmanagement.Starting from the architecture described above, in the frame of the 3IBS Project, systemand sub-system requirements have been carefully reviewed and linked together and witha set of Key Perfomance Indicators (KPIs) in order to directly link system components withthe performance criteria able to evaluate them.The reworked database has been then used to populate the Coral Tree tool, developed byD’Appolonia and customised for the 3iBS project as a tool for management andperformance assessment of Bus System requirements. The tool, which is able to managehierarchic structure of concepts and their mutual relationships, has been implemented andmade available as a web application on the 3iBS web site.The main improvement with respect to the previous database consists in the linkage of theEBSF systems and sub-system requirements with User Needs and a set of KPIs, in orderto improve the “usability” of the EBSF database, by implementing specific searchfunctions, as well as directly link the components of the system with their performancecriteria.


7.2 Approach and objectivesBy applying the Work Tool 2 methodology (extensively described in section 5.4) to the3iBS database of functional requirements, the most significant features have been identifyby priority topic This means that the system requirements, as well as vehicle,infrastructure and operation requirements which can greatly contribute to the improvementof a bus system with respect to the six EBSF_2 priority topics have been identified.The work of this subtask has been divided into 3 main steps: Collection of Work Tool 2 data from partners;

The partners of task 2.1 that filled in Work Tool 2 are listed in the following table bypriority topic. Overall, they are associations of PT stakeholders, PT operators, PTauthorities, universities and knowledge providers. Please note that Digimobeecontributed only to topic n.4 and n. 6 because of its specific knowledge andinvolvement in the project activities dealing with such topics.

Partners

Topic 1:Energy

Strategyand

Auxiliaries

Topic 2:Driver

Assistance

Topic 3:VehicleDesign

Topic 4: ITStandard

introductionin existing

fleet

Topic 5:Intelligent

Garage andpredictive

maintenance

Topic 6:Urban

infrastructure

ASSTRACHALMERSCRTMDBUSDIGIMOBEEFRAUNHOFERUITPUTP

TOTAL 7 7 7 8 8 7

Table 17 – List of contributing partners to Work Tool 2

Statistical analysis by priority topic to identify the most relevant requirements;The data collected through the Work Tool 2 have been processed in an Excel File.The statistical analysis has been performed by different task partners (see section5.4) according to a common methodology defined by the contributing partners andaimed at updating the requirements’ database developed in the previous projectsvis-à-vis the EBSF_2 priority topics.

Main results and conclusions. Coherently with the user needs analysis, the main outcomes of the data analysis

have been elaborated in tables with clear visual elements in order to make theupdate of the requirements’ database as understandable as possible for thereader.


7.3 System requirementsThe EBSF system requirements, further updated within 3IBS, can be considered as aqualitative expression of functions that a bus system should include in order to satisfy theneeds of all stakeholders impacted by bus systems (i.e. regular and non-regular users,operators, authorities, industries, and other road users). Overall, 342 functions have beenoriginally identified as relevant for a bus system in order to fulfill a list of about 500stakeholders’ needs.The present analysis is based on a specific sub-set of requirements – “systemrequirements for the evolution of bus systems” - which focuses on the main potentialareas of innovation in which existing bus systems might evolve. Since a variety of bussystems exists today, developed to the meet very different mobility needs and behaviors,and they can also vary greatly because of the city environment where they operate, thepotential evolution of bus systems have been analysed according to 4 bus solutions,namely: BHLS (Bus with High Level of Service), an enhanced bus system that operates on

dedicated infrastructures to combine the flexibility of buses with the efficiency ofrail;

BHLS Lite, similar to BHLS but with less stringent requirements on vehicle,infrastructure and operations;

Classic lines, mostly urban and sub-urban lines with a rather high capacity butlower frequency;

Local Lines, offering short and local service into districts.All together the above technologies cover a wide spectrum of bus solutions, if not all ofthem, in operation across European cities.For the purpose of task 2.1 the complete list of 47 system requirements for the evolutionof bus systems have been taken into account and analysed though the Work Tool 2, inorder to identify their degree of relevance in the deployment of innovative bus systemswith respect to the 6 EBSF_2 priority topics.The system requirements for the evolution of bus systems are not grouped in sub-categories, as it is the case for vehicle, infrastructure and operation requirements.Nevertheless it is relevant to stress that they refer to the following six concepts, asstrategic functions for the evolution of bus systems: Responding to passengers’ needs; Responding to social and environmental needs; Responding to the needs of cities; Promoting political support and relevant legislation; Securing global leadership; Call for strategic research agenda for urban bus systems.

Overall the outcomes of the statistical analysis performed and based on the answers of 8WP2 partners (see Table 17), show that 24 out 47 system requirements are relevant(either moderate or high relevance) for the deployment of innovative bus systems withrespect to the EBSF_2 priority topics, and none-of them is not relevant at all (i.e. has beenconsidered not significant for all the priority topics by all the respondents). The results ofthe analysis by topics are summarised in the following paragraphs.


TOPIC 1: Energy Management Strategy and AuxiliariesAccording to the respondents’ experience (see Table 18), the implementation of strategiesor solutions dealing with Energy Management and Auxiliaries are able to positively impactwhat a bus system can do in order to: Contribute to a more sustainable city, (high relevance for 50% of the respondents),

and Enable the lowest Life Cycle Cost, (high relevance for 50% of the respondents).

Lower energy consumption of buses’ internal combustion engine thanks to more efficientauxiliaries and on-board sub-systems as well as strategies such as reducing the heat lossvia the design and insulation of buses or decreasing the release of air during passengerboarding/alighting, can greatly contribute to reduce the consumption and emissions of thevehicle and its operational costs.At the same time an efficient energy management can positively impact the introduction ofmore modern propulsion technologies (e.g. electric buses) in urban bus fleets byincreasing the electric-only drive range of the vehicles.

Topic 1: Energy Management Strategy and Auxiliaries


HIGHRELEVANCE

Contribute to a more sustainable city

Enable the lowest Life Cycle Cost

Functional requirements USER NEEDS AREAS

Contribute to a more sustainable city - Urban development and quality of life- Environmental issues

Enable the lowest Life Cycle Cost - Economic and operation issues- Maintenance

Table 18 – System Requirements identified as relevant for Topic 1 and related user needs areas

The selected requirements clearly refer to user needs dealing with urban developmentand quality of life as well as environmental issues, which refer to all the inhabitants of acity where the buses run, economic and operation issues, which impact the operator ofthe bus system, and maintenance, since the Life Cycle costs can be positively impactedby lower maintenance costs.

TOPIC 2: Driver AssistanceA large number of driver assistance systems already exist for cars and trucks, but veryoften they do not take into account the public transport specificities where the driver needsto keep to schedule and starts/stops frequently. Moreover they do not take into accountdifferences between the driver’s need for feedback in e.g. diesel compared to electricbuses. Improvements of driving assistance systems in terms of information channels,


content, and modality to inform the driver and enhance the drivers’ learning process,represent a challenge for the next generation of bus systems.

The respondents have highlighted how improving driving assistance tools can greatlyimpact the passengers’ comfort and the perception of safety (Enable customer care in allaspects – moderate relevance for 50% of the respondents), reduce the travel time(Guarantee improved commercial speed on the entire PT-trip – high relevance for the62,5% of respondent), as well as reduce the risk of injuries (Enable a service safe forpedestrians or road-users – moderate relevance for 50% of the respondents). The mostrelevant requirements are reported in Tab 19.

Topic 2: Driver Assistance


HIGHRELEVANCE

Enable customer care in all aspects(comfort, access to information,access to fares, etc)

Guarantee improved commercialspeed on the entire PT-trip

Enable a service safe for pedestriansor road-users



- Comfort, cleanness and qualityfeeling/perception

- Service performance

Guarantee improved commercialspeed on the entire PT-trip - Service performance

Enable a service safe for pedestriansor road-users - Safety and security


The requirements selected as relevant answer mostly to the needs of bus users, eitherregular or occasional, and the road users (including pedestrian). As a results, the increaseof comfort, safety and security as well as service performance thanks to innovative eco-driving technologies can contribute to increase the modal shift in favour of buses.

TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)Applying new design options for the design and layout of buses may contribute toefficiency improvements of the service by mainly optimising accessibility and internalpassenger flow, reducing dwell time at bus stops and, consequently, improvingcommercial speed of the vehicles.In this context, the task partners have considered highly relevant 7 system requirements(see Table 20). Among them, Allow comfortable standing and seating for passengers is


considered key by the 87,5% of the respondents. The need to give high importance topassengers’ comfort and flow in the design of all the element of the system is highlightedalso by the requirements Enable optimal seating capacity for specific needs and Enablepassengers to safely board and alight the vehicle, considered high relevant by the 75% ofthe respondents, and Enable customer care in all aspects (62,5 of the respondents).

Topic 3: Vehicle Design (Capacity, Accessibility, Modularity)


HIGHRELEVANCE


Enable capacity to be adapted todemand

Enable optimal seating capacity forspecific needs

Enable passengers to safely boardand alight the vehicle

Allow comfortable standing andseating for passengers

Enable the physical protection ofpassengers, staff and surroundingpeople in case of accident and attack

Enable the level of modularityrequired by the specific level ofservice



-

Enable capacity to be adapted todemand -

Enable optimal seating capacity forspecific needs -




Allow comfortable standing andseating for passengers - Service performance



Enable the physical protection ofpassengers, staff and surroundingpeople in case of accident and attack

- Safety and security


-


In terms of bus design, also the necessity to have a modular vehicle flexible enough to beadapted to different operational conditions (different demand levels) is relevant for aninnovative bus system. The requirements Enable the level of modularity required by thespecific level of service and Enable capacity to be adapted to demand are highly relevantfor the 62,5% of the respondents. Finally, Enable the physical protection of passengers,staff and surrounding people in case of accident and attack refers to safety and security ofpassengers, drivers and road users.

TOPIC 4: IT Standard introduction in existing fleetsThe main innovation is to pass from vertical/proprietary solutions to fully interoperableones both at onboard and back-office levels. This new approach will permit to avoid ITsupplier dependency for IT systems and to open up for competition. Moreover, it will offereasier scalability to an IT-architecture open and interoperable, dissociation of hardwareand software, competitiveness of IT solutions with same safety level. For PT Operatorsand Authorities, the efficient introduction of a standard IT architecture will offer a faster,easier and cost-effective interoperability of PT systems at metropolitan and regional level.Indeed the challenge is to take into account the co-existence with IT systems alreadyinstalled in existing bus fleets to offer a full IT interoperability.According to the respondents, the most relevant functional requirements that could beachieved at system level thanks to the introduction of IT standard in existing bus fleets aredealing with the need to provide complete and timely information to the PT users duringthe entire trip, from the planning to the efficient door-to-door navigation (see Table 21).

Topic 4: IT Standard introduction in existing fleets


HIGHRELEVANCE

Enable punctuality of the service inline with the published schedule

Efficient contingency management inorder to minimise delays occuring

Guarantee complete and permanenttravel information outside the vehicle

Guarantee complete and permanenttravel information inside the vehicle




HIGHRELEVANCE

Allow seamless travel and mobility

Guarantee easy access to basicinformation, like routes, timetables,travel time, schedules

Enable use of modern technologiesto collect and to predict demand, tooptimize route and frequency

Guarantee accurate real timeinformation, mainly but not only incase of service disruption, to avoidtrip uncertainty

Allow accurate information aboutconnections to ease the use of thePT-system


Enable punctuality of the service inline with the published schedule - Service performance

Efficient contingency management inorder to minimise delays occuring - Service performance

Guarantee complete and permanenttravel information outside the vehicle

- Information to passengers, relationaland behavioural issues


Guarantee complete and permanenttravel information inside the vehicle


Allow seamless travel and mobility

- Service performance- Modal integration and additional/flexible

services- Information to passengers, relational

and behavioural issues- Urban development and quality of life



- Economic and operation issues


- Economic and operation issues- Service performance

Guarantee accurate real timeinformation, mainly but not only incase of service disruption, to avoid





HIGHRELEVANCE

trip uncertainty



- Modal integration and additional/flexibleservices


5 requirements dealing with information systems have been considered high relevant onaverage by the 55% of the respondents. The other selected requirements refer to theneed to provide high quality service performance, mainly in terms punctuality, frequency,route optimized to the demand and integration of different modes of transport, namely: Enable use of modern technologies to collect and predict demand, to optimize the

route and the frequency, high relevancy for 50% of the respondents; Allow seamless travel and mobility, moderate relevancy for 65% of the

respondents; Enable punctuality of the service in line with the published schedule, moderate

relevancy for 50% of the respondents; Efficient contingency management in order to minimise delays occuring, moderate

relevancy for 50% of the respondents;

If we look at the user needs area, the two groups of selected requirements answer mostlyto the passengers’ needs, in terms of Information to passengers, relational andbehavioural issues, Service performance and Modal integration and additional/flexibleservices, but also to the needs of PT operators and authorities, since the implementationof fully interoperable IT standards can significantly reduce some operational andmaintenance costs (Economic and operation issues) of the fleets. Finally, a link betweenthe overall improvement of the level of service and the need of cities has been identified,in terms of Urban development and quality of life.

TOPIC 5: Intelligent Garage and predictive maintenanceTopic 5 is very specific and deals with the adoption of innovative solutions to changeparadigm for the diagnostic and the maintenance of vehicle fleets. Examples of potentialareas for innovations are new algorithms for predictive maintenance, vehicle automationtechnologies for bus depot management and IT systems for new maintenanceprocedures.As a consequence, it is not surprising that only 2 system requirements have beenconsidered relevant to this domain (see Table 22). The first one (High relevant for 50% ofthe respondents) refers to the impact of improved maintenance strategies on the busattractiveness because of the passengers’ perception of quality and comfort. Differently,the requirement Enable the lowest Life Cycle Cost highlights the potential of solutions forintelligent garage and predictive maintenance in reducing buses’ operational costs.


The functional requirements selected as relevant are, on one side, expression of theneeds of PT users, in terms of Comfort, cleanness and quality feeling/perception andService performance, and on the other side they clearly refer to the need of PT operatorsand authorities to face with economic, operation and maintenance issues.

Topic 5: Intelligent Garage and predictive maintenance


HIGHRELEVANCE

Maintain attractiveness all alongthe life cycle to avoid theperception of obsolescence

Enable the lowest Life Cycle Cost




- Maintenance- Service performance



TOPIC 6: Urban InfrastructureRethinking the interface between the bus and urban infrastructure, in particular bus stopsand terminal (by harmonising vehicle layout and bus-stop design) but also intermodalhubs and running ways, can greatly contribute to the creation of cities with a high qualityof life. Passengers’ experiences of bus stops and terminals could determine theirperception and acceptance of the whole bus system.

The functional requirements selected as relevant for this domain are shown in Table 23.The respondents have highlighted how removing accessibility constraints for allpassengers and enabling an easy and safe flow to and from the bus are key elements torise the attractiveness of the bus system; the requirements Enable accessibility for all inall zones and Enable passengers to safely board and alight the vehicle have beenconsidered high relevant by the majority of the respondents (respectively 75% and 50% ofthem).The impact of urban infrastructures on the performances of the service is stressed by therequirements Allow a concept of priority for PT and the related Guarantee improvedcommercial speed on the entire PT-trip; both high relevant for the half of the respondents.Finally an optimized interface between the bus and the city can Enable a service safe forpedestrians or road-users (high relevance level for 62,5% of the respondents) andContribute to a more sustainable city (high relevancy level for 50% of the respondents).


Topic 6: Urban Infrastructure


HIGHRELEVANCE

Enable accessibility for all in allzones (buses and stations,connections)

Allow a concept of priority for PT

Contribute to a more sustainablecity

Guarantee improved commercialspeed on the entire PT-trip

Enable a service safe forpedestrians or road-users

Enable passengers to safelyboard and alight the vehicle



- Accessibility to vehicles and infrastructures- Urban development and quality of life

Allow a concept of priority for PT - Service performance- Urban development and quality of life


- Urban development and quality of life- Environmental issues


Enable a service safe forpedestrians or road-users - Safety and security

Enable passengers to safelyboard and alight the vehicle

- Safety and security- Accessibility to vehicles and infrastructures


In terms of user needs areas, the optimization of bus-related urban infrastructures canrespond to the needs of the PT and road users in terms of Accessibility, ServicePerformance and Safety and Security, but also contribute to improve the urbanenvironment and create structural links between urban planning and transport planning.


7.4 Vehicle requirementsThis section explains the results of the WT2’s elaboration; the outcomes have beenrepresented in tables (using the tools described in the Paragraph 2.3 D “Relevance ofFunctional Requirements”) and explained by comments.The analysis has been managed according to the definitions provided by the EBSFDeliverable n. 1.4.2.

Figure 13 – Structure of work for vehicle requirements.

Main areas for the vehicle requirements

The FRs dealing with the vehicle, as one of the system elements, are based on theDeliverable 1.4.2. Vehicle Requirements of EBSF. Vehicle FRs are 48 and are classifiedunder the following 8 areas, each of them containing several sub areas.

1. Driver's cabin management (11 requirements): functional issues management,ergonomic and comfort issues management, safety and security issuesmanagement.

2. Passenger’s area management (4 requirements): internal layout and internalflow management, provide an attractive design, information management.

3. Modularity management (5 requirements): inside layout modularitymanagement, global geometry modularity management, provide modularconception & fabrication.

4. IT application on board management (6 requirements): provide interfacebetween the vehicle and functions/devices on board, IT System Architecturemanagement

VEHICLE REQUIREMENTS

1 DRIVER'S CABINMANAGEMENT

2 PASSENGER’S AREAMANAGEMENT

3 MODULARITYMANAGEMENT

4 IT APPLICATION ONBOARD

MANAGEMENT

5 GUIDANCEMANAGEMENT

6 ENVIRONMENT,ENERGY SAVINGMANAGEMENT

7 STRATEGIC SUBSYSTEM

MANAGEMENT

8 MAINTENANCEMANAGEMENT

PRIORITY TOPICS

1 Energy managementStrategy and Auxiliaries

2 Driver Assistance

3 Vehicle Design(Capacity, Accessibility,

Modularity)

4 IT Standard introductionin existing fleets

5 Intelligent Garage andpredictive maintenance

6 Urban infrastructure

USER NEEDS AREAS

1 Urban development andquality of life

2 Economic and operationissues

3 Pricing and commercialpolicies

4 Maintenance

5 Environmental issues

6 Modal integration andadditional/flexible

services

7 Information topassengers, relationaland behavioural issues

8 Accessibility to vehiclesand infrastructures

9 Comfort, cleanness andquality

feeling/perception

10 Service performance(Service regularity and

punctuality)

11 Safety and security


5. Guidance management (13 requirements): guidance, external interaction andsteering strategies management, assisted guidance system management, stopapproaching system management.

6. Environment, energy saving management (4 requirements): fuel consumptionmanagement, leakage management.

7. Strategic sub system management (1 requirement): provide fire protection.8. Maintenance management (4 requirements): assure maintainability.

TOPIC 1: Energy Management Strategy and Auxiliaries



HIGHRELEVANCE

3. Modularity management3.2 Global geometry modularity managementEnsure coupling/uncouplingadditional trailer to adapt significantlythe bus capacityEnsure coupling/uncoupling otherbuses to combine several lines on acommon segment6. Environment, energy saving management6.1 Fuel consumption managementAllow the bus to meet the networkperformance requirements of itsspecific serviceFunctional requirements USER NEED AREAS3. Modularity management3.2 Global geometry modularitymanagement

- Economic and operation issues- Modal integration and additional/flexible

services- Comfort, cleanness and quality

feeling/perception- Service performance

6. Environment, energy saving management6.1 Fuel consumption management - Environmental issues

- Service performance- Economic and operation issues

Table 24 – Vehicle Requirements identified as relevant for Topic 1 and related user needs areas

Regarding the topic 1 “Energy Management Strategy and Auxiliaries”, for the FR “Allowthe bus to meet the network performance requirements of its specific service” belonging tothe “Environment, energy saving management” area, results that the 62,5% of the sampleexpressed a HIGH LEVEL (3) OF RELEVANCE.

Moreover, it results that several FRs have a MODERATE LEVEL (2) OF RELEVANCE.


For the “Modularity management” area: Ensure coupling/uncoupling additional trailer to adapt significantly the bus capacity

(50%); Ensure coupling/uncoupling other buses to combine several lines on a common

segment (50%).

The obtained results seem to show that the topic 1 “Energy Management Strategy andAuxiliaries” has a little relevance in the context of the characteristics of the vehicle.Indeed, only one FR results strongly relevant among all the FRs considered.Obviously, the objective is to continue to implement the characteristics of the vehicleaccording to the Energy management topic.

TOPIC 2: Driver Assistance



HIGHRELEVANCE

1. Driver's cabin management1.1 Functional issues managementKeep driver informed on the state ofthe vehicle

Allow drivers to access to all controls

1.2 Ergonomic and comfort issues managementProvide an ergonomic driver’sworkplace4. IT Application on board management

4.1 Provide interface between the vehicle and functions/devices on boardProvide a good interface for thedriver5. Guidance management5.1 Guidance, external interaction and steering strategies managementAllow the driver to control histrajectoryProvide the driver with sufficientvisibility for drawing alongside thestopping areaAllow the driver to view and controlthe area swept by the rear overhang,when pulling out and in bends5.2 Assisted guidance system managementHelp driver following a unique,correct and repeatable trajectoryevery times

Help driver to follow a driving profile


Topic 2: Driver Assistance5.3 Stop approaching system managementHelp driver doing precise, regularand repeatable dockingFunctional requirements USER NEED AREAS1. Driver's cabin management1.1 Functional issues management - Maintenance

- Economic and operation issues- Safety and security- Service performance

1.2 Ergonomic and comfort issuesmanagement



4. IT Application on board management

4.1 Provide interface between thevehicle and functions/devices onboard



- Safety and security- Service performance- Economic and operation issues

5. Guidance management

5.1 Guidance, external interactionand steering strategies management

- Safety and security- Service performance- Comfort, cleanness and quality feeling

5.2 Assisted guidance systemmanagement

- Service performance- Comfort, cleanness and quality feeling- Safety and security- Economic and operation issues

5.3 Stop approaching systemmanagement

- Service performance- Safety and security


Regarding the topic 2 “Driver Assistance”, several FRs have been approached with aHIGH LEVEL (3) OF RELEVANCE.

Regarding the “Driver's cabin management” area: Keep driver informed on the state of the vehicle (75%); Allow drivers to access to all controls (50%); Provide an ergonomic driver’s workplace (50%).

About the “IT Application on board management” area: Provide a good interface for the driver (75%).


For the “Guidance management” area: Allow the driver to control his trajectory (75%); Help driver following a unique, correct and repeatable trajectory every times

(75%); Help driver to follow a driving profile (75%); Help driver doing precise, regular and repeatable docking (75%).

Moreover, it results that several FRs have a MODERATE LEVEL (2) OF RELEVANCE

About the “Guidance management” area: Provide the driver with sufficient visibility for drawing alongside the stopping area

(62,5%); Allow the driver to view and control the area swept by the rear overhang, when

pulling out and in bends (50%).

The topic 2 «Driver Assistance» is strongly connected with the vehicle. The pertinent FRsare certainly linked to the driver, both in terms of comfort and in terms of knowledge of thestate of the vehicle. This feature also produces the need to inform the user by ITS.Moreover, the theme of the safety both in terms of driving style and in terms of reductionof accidents results deeply connected with the topic.

TOPIC 3: Vehicle Design (Capacity, Accessibility, Modularity)



HIGHRELEVANCE

1. Driver's cabin management1.1 Functional issues management

Allow drivers to greet passengers

1.2 Ergonomic and comfort issues managementProvide an ergonomic driver’sworkplaceDesign of the driver’s cabin: allowdriver to operate in comfort1.3 Safety and security issues managementProvide a good view of drivers"surroundingsProtect the driver from noisepollution

Protected driver from collisions

2. Passenger’s area management (Life on board)2.1 Internal layout and internal flow managementAllow the operator to upgrade thevehicle equipment and fittings




HIGHRELEVANCE

2.2 Provide an attractive designCreate, maintain and customise amodern image of the bus3. Modularity management3.1 Inside layout modularity managementAllow the operator to change thevehicle equipment, fittings and layout3.2 Global geometry modularity managementEnsure coupling/uncouplingadditional trailer to adapt significantlythe bus capacityEnsure coupling/uncoupling otherbuses to combine several lines on acommon segment3.3 Provide modular conception & fabricationDesign and build the bus as anassembling of elementary standardmodules5. Guidance management5.1 Guidance, external interaction and steering strategies management

Avoid injury or disturbance topassengers waiting at stops

5.2 Assisted guidance system managementHelp driver following a unique,correct and repeatable trajectoryevery times

Help driver coupling trailers or otherbuses

Functional requirements USER NEED AREAS1. Driver's cabin management1.1 Functional issues management - Information to passengers, relational

and behavioural issues- Comfort, cleanness and quality

feeling/perception- Accessibility to vehicles and

infrastructures- Service performance

1.2 Ergonomic and comfort issuesmanagement






HIGHRELEVANCE

1.3 Safety and security issuesmanagement

- Safety and security- Economic and operation issues- Comfort, cleanness and quality feeling

2. Passenger’s area management (Life on board)

2.1 Internal layout and internal flowmanagement


- Maintenance

2.2 Provide an attractive design


- Service performance- Information to passengers, relational

and behavioural issues3. Modularity management

3.1 Inside layout modularitymanagement


- Accessibility to vehicles andinfrastructures

- Service performance- Maintenance- Economic and operation issues

3.2 Global geometry modularitymanagement

- Economic and operation issues- Modal integration and additional/flexible

services- Comfort, cleanness and quality

feeling/perception- Service performance

3.3 Provide modular conception &fabrication

- Economic and operation issues- Maintenance

5. Guidance management

5.1 Guidance, external interactionand steering strategies management - Safety and security

5.2 Assisted guidance systemmanagement

- Service performance- Safety and security- Comfort, cleanness and quality

feeling/perception- Economic and operation issues


Regarding the topic 3 “Vehicle Design (Capacity, Accessibility, Modularity)” all the FRsconsidered report a HIGH LEVEL OF RELEVANCE (3).


For the “Driver's cabin management” area, we have: Allow drivers to greet passengers (50%); Provide an ergonomic driver’s workplace (50%); Design of the driver’s cabin: allow driver to operate in comfort (50%); Provide a good view of drivers" surroundings (62,5%); Protect the driver from noise pollution (62,5%); Protected driver from collisions (62,5%).

About the “Passenger’s area management (Life on board)” area: Allow the operator to upgrade the vehicle equipment and fittings (62,5%); Create, maintain and customise a modern image of the bus (75%).

Regarding the “Modularity management” area: Allow the operator to change the vehicle equipment, fittings and layout (75%); Ensure coupling/uncoupling additional trailer to adapt significantly the bus capacity

(75%); Ensure coupling/uncoupling other buses to combine several lines on a common

segment (75%); Design and build the bus as an assembling of elementary standard modules

(75%).

For the “Guidance management” area: Avoid injury or disturbance to passengers waiting at stops (50%); Help driver following a unique, correct and repeatable trajectory every times

(50%); Help driver coupling trailers or other buses (50%).

The topic 3 “Vehicle Design” is especially relevant for the vehicle. Many FRs have beenconsidered highly relevant for the vehicle.

About the “Driver Cabin” is confirmed the importance to study a good vehicle design inorder to ensure an optimal guide both in terms of visibility and in terms of comfort.The vehicle’s design should ensure to modulate regarding the needs of the users,providing, at the same time, a modern image and attractiveness of the transportation. Thetopic is strongly connected with the theme of the vehicle’s modularity both in terms ofexternal modularity (add and subtract modules according to the passengers flow) and interms of internal modularity (increasing and decreasing the capacity of the bus).Moreover, the vehicle should be designed with resistant material in order to ensure thesafety of the passengers.


TOPIC 4: IT Standard introduction in existing fleets



HIGHRELEVANCE

1. Driver's cabin management1.1 Functional issues managementKeep driver informed on the state ofthe vehicle2. Passenger’s area management (Life on board)2.3 Information managementInclude devices for exchanginginformationInform passengers and potentialpassengers about PT and otherservices4. IT Application on board management

4.1 Provide interface between the vehicle and functions/devices on boardProvide a good interface for thedriver4.2 IT System Architecture managementProvide integrated systemarchitecture

Provide open system architecture

System architecture: integrate thirdparties devices, support the properprotocolProvide a modular on board ITsystem

Functional requirements USER NEED AREAS1. Driver's cabin management

1.1 Functional issues management

- Economic and operation issues- Maintenance- Safety and security- Service performance

2. Passenger’s area management (Life on board)

2.3 Information management


- Safety and security- Pricing and commercial policies- Comfort, cleanness and quality

feeling/perception4. IT Application on board management


Functional requirements USER NEED AREAS

4.1 Provide interface between thevehicle and functions/devices onboard


- Service performance- Information to passengers, relational

and behavioural issues- Safety and security- Economic and operation issues

4.2 IT System Architecturemanagement

- Maintenance- Service performance- Economic and operation issues- Modal integration and additional/flexible

servicesTable 27 – Vehicle Requirements identified as relevant for Topic 4 and related user needs areas

Regarding the topic 4 “IT Standard introduction in existing fleets”, several FRs have beenapproached with a HIGH LEVEL (3) OF RELEVANCE:

Regarding the “Passenger’s area management (Life on board)” area: Include devices for exchanging information (50%); Inform passengers and potential passengers about PT and other services (50%).

About the “IT Application on board management” area: Provide a good interface for the driver (62,5%); Provide integrated system architecture (75%); Provide open system architecture (75%); System architecture: integrate third parties devices, support the proper protocol

(75%); Provide a modular on board IT system (75%).

Moreover, the following FRs have a MODERATE LEVEL (2) OF RELEVANCE:

For the Functional issues management area we have;- Keep driver informed on the state of the vehicle (50%);

IT Standard Introduction in existing fleets is a topic that certainly answer to different FRs.The IT systems installation allows both a safe and controlled driving for the driver and acomfortable journey for the passenger. Indeed, the possibility to check and monitory theservice increases the efficiency and satisfy the need for continuous information needed bythe user.


TOPIC 5: Intelligent Garage and predictive maintenance



HIGHRELEVANCE

8. Maintenance management8.1 Assure maintenabilityLimit the number of builder-specificparts and admit generic sparesProvide interaction with groundstationsAllow the operator to parameterisethe busFunctional requirements USER NEED AREAS8. Maintenance management

8.1 Assure maintenability - Maintenance- Economic and operation issues


Regarding the topic 5 “Intelligent Garage and predictive maintenance”, the following FRshave been approached with a HIGH LEVEL (3) OF RELEVANCE:For the “Maintenance management” area: Limit the number of builder-specific parts and admit generic spares (50%). Provide interaction with ground stations (50%).

Moreover, the following FRs have a MODERATE LEVEL (2) OF RELEVANCE:

About the “Maintenance management” area: Allow the operator to parameterise the bus (50%).

About the topic 5 “Intelligent Garage and predictive maintenance”, it’s very important astandardization of the vehicle in order to allow an optimal management.

TOPIC 6: Urban InfrastructureUrban Infrastructure has not been considered relevant for any vehicle requirement.Summary of results and conclusionsIn total, 34 out of the 48 functional requirements have been assessed as relevant forvehicle category. The highest relevance received functional requirements that deal withthe “Driver's cabin management”, “Modularity management” and with the “ITApplication on board management”.Regarding the user need areas, “Comfort, cleanness and quality feeling/perception”,“Economic and operation issues” Service performance” and “Safety and security” aremain user need areas for the most relevant vehicle requirements.


7.5 Infrastructure requirementsThis section includes the functional infrastructure requirements specification that apply forbus systems in urban and suburban areas.Based on the key infrastructure requirements identified within EBSF Project, information inthe framework of the different needs of the major stakeholders, operators and authoritiesare collected.The main objective is to obtain the most relevant infrastructure requirements in terms ofrunning-way, lanes, stops, crossings, etc. for each of the EBSF_2 six priority topicsidentified and their correlation with the user needs areas.

Figure 14 – Structure of work for infrastructure requirements.

Within this framework, subchapter, 7.5. Infrastructure Requirements is produced, outliningthe infrastructure requirements, drawn in accordance with the pertinent stakeholders(operators, authorities and manufactures) which includes the most relevant infrastructurerequirements for the priority topics of bus systems in urban and suburban areas.Main areas for infrastructure requirementsThe main infrastructure requirements are based on the Deliverable 1.5.1. InfrastructureRequirements of EBSF1. Infrastructure requirements are 46 functional requirementsclassified under the following 10 areas for bus system infrastructure and theirrequirements.

1. Running way management (5 requirements): safety, visibility, type of surface, etc.2. Busway and lane management (3 requirements): level of segregation, reserved

lanes, etc.3. Running-way geometric management (4 requirements): curve radius, slopes, etc.4. Crossing management (2 requirements): traffic lights, bus priority and other design

factors.

1 EBSF (2009) D.1.5.1. Infrastructure Requirements.


5. Stops requirements management (10 requirements): design of shelters, posts andother support infrastructure, location, equipment, etc.

6. Manage the accessibility to stops (5 requirements): pedestrian and PRMsaccessibility, visibility, information panels, etc.

7. Interface stop-bus management (5 requirements): characteristics of the kerb andtypology, height, access for handicapped people, etc.

8. Interchange with other modes requirements management (4 requirements):connection hubs, park and ride, etc.

9. Depots and workshop management (5 requirements).10. Interface bus–city management (3 requirements): buses in calmed traffic areas,

city planning according to the bus needed, etc.Additionally, for each of the requirement, partners answered with what user need area(one or more) is related.


Energy Management Strategy and Auxiliaries has not been considered relevant for anyinfrastructure requirement. This topic is related with solutions to improve energy andthermal management of buses, efficiency of the auxiliaries and sub-systems on-board.Therefore, infrastructure requirements are not relevant to it.


For topic 2, there have been three requirement highlighted but not relevant. Regardingrunning way requirements: to allow the safe driving of the bus and to allow the circulationof the bus with any obstacles. On the other hand, the interface stop–bus management ishighlighted for driver assistance, more specifically to know exactly where to stop. The userneed areas identifies for this requirement are three: Safety and security, Serviceperformance, and Accessibility to vehicles and infrastructure.


For vehicle design, similar to driver assistance, partners considered important (but notrelevant) the interface stop–bus management of relevance. In particular, vehicle designwas highlighted to assure a safe driving and easy and secure boarding and alighting; andthe height of the kerb in order to allow deploying a ramp with a proper slope.

TOPIC 4: IT Standard introduction in existing fleet

For topic 4, partners considered running way requirement and stop requirementmanagement to be of moderate relevance, in particular related to giving priority to buscirculation and providing dynamic information. This is related with the user need area ofService Performance and Information to Passengers, respectively. Additional threerequirements were highlighted (but not relevant) .Regarding crossings management: toprovide priority systems for the bus; concerning stops requirement management: toprovide sufficient information adapted for all users at every stop; and for interchange withother modes requirements: provide sufficient, accessible for all and organized informationon the interchange to improve passenger flow.


Topic 4: IT standard introduction in existing fleet


HIGHRELEVANCE

1. Running way requirements management

1.3. Allow giving priority to bus circulation over the rest of the traffic

To provide some advantages orpriority to the circulation of buses,especially in congested roads orstreets, to improve regularity andincrease its speed.5. Stops requirements management5.3. Provide dynamic information, especially real time information on waiting time andservice disruption.Inform the passenger about the realstate of operation, especially duringdisruption. Improve the well feeling ofthe customer about waiting time at thebus stop.

Functional requirements USER NEED AREAS1. Running way requirements management1.3. Allow giving priority to buscirculation over the rest of the traffic


5. Stops requirements management5.3. Provide dynamic information,especially real time information onwaiting time and service disruption.

-Information to passenger, relational andbehavioural issues.

Table 29 – Infrastructure Requirements identified as relevant for Topic 4 and related user needs areas

Regarding the Topic 4: ʺIT Standardʺ, two FRs have approached with MODERATELEVEL (2) OF RELEVANCE.For the ʺRunning way managementʺ area: Allow giving priority to bus circulation over the rest of the traffic (50%);

For the ʺStop managementʺ area: Provide dynamic information, especially real time information on waiting time and

service disruption (50%).

TOPIC 5: Intelligent Garage and predictive maintenance

For intelligent garage and predictive maintenance, the partners considered highly relevantdepots and workshop management requirement, in particular, to provide sufficient spacein the depots and workshops (50% of the responses) and to provide interaction betweenthe bus and the ground stations (62.50% of responses). The two of these are user needsconnected to Maintenance and Service performance.




HIGHRELEVANCE

9. Depots and workshop management9.2. Allow the depots and workshops to have appropriate spaceThe depots and workshop shouldhave appropriate space andorganization for the movement ofvehicles and the needed maintenanceoperations9.4. Provide interaction between the bus and the ground stationsThe depots should have the possibilityto interact with the bus to collectdiagnosis data, functioning data, todetect system failure and anticipatebreakdowns.

Functional requirements USER NEED AREAS9. Depots and workshop management9.2. Allow the depots and workshop tohave appropriate space

- Maintenance

9.4. Provide interaction between thebus and the ground stations

- Service performance- Maintenance


TOPIC 6: Urban Infrastructure

For topic 6, Urban infrastructure, 35 out of 46 infrastructure requirements are relevantaccording to results of the partners consultation. All main infrastructure areas areconsidered, except for Depots and Workshop management. Out of 35 relevantrequirements, 15 are highly relevant for all the partners (100% responses, i.e. mostimportant). These most relevant infrastructure requirements for the deployment of bus-related urban infrastructures are: To provide width of the lane in accordance with the kind of vehicle using it and in

accordance with its speed; To ensure comfortable stop; To adapt the stop to the needs of the demand and buses; To allow the optimisation of commercial speed while designing the stops space

and location; To avoid car parking in the place where the bus has to stop; To ensure easy access to the bus stop; To ensure the access to the bus stop to all; To allow the entire platform to be clear of any obstructions; To provide physically challenged users with appropiate space at the stop for

boarding/alighting operations; To provide near stops, connection with other modes; Transport terminals and interchange points constructions; To provide walking environments and waiting areas at interchange points that

are pleasant, safe and accesssible for all;


Design on-street constructions, speed limit regulations and the width of thestreet: to assure safe, secure and comfortable bus circulation;

To provide practicable and safe pedestrian course to the stop; To integrate bus systems in city planning and its infrastructure.

Moreover, the main user need areas for the most relevant infrastructure requirements ofurban infrastructure are Service performance, Safety and security, Accessibility tovehicles and infrastructure, Modal integration, Comfort, cleanness and quality feeling, andUrban development.



HIGHRELEVANCE

1. Running way requirements management1.3. Allow giving priority to bus circulation over the rest of the trafficTo provide some advantages orpriority to the circulation of buses,especially in congested roads orstreets, to improve regularity andincrease its speed.1.4. Allow the circulation of the bus and the visibility of the driver not be hindered by anyobstacleThe depots should have the possibilityto interact with the bus to collectdiagnosis data, functioning data, todetect system failure and anticipatebreakdowns.2. Busway and lane requirements management2.1. Provide a reserved space for the bus circulationDepending on the bus systemsolution, different levels ofsegregation should be provided:BHLS, BHLS lite, Classic urban lines,local bus lines2.2. Assure the strength to bus weight and its circulation with safety conditionsDue to high frequency bus passing onthe busways and lanes theinfrastructure needs a specialreinforcement to avoid its degradation2.3. Avoid the location of utilities under busway or bus laneIt should be avoided to locate urbanutilities (water, gas, electricity…)under the busway or bus lane3. Running-way geometric requirements management3.1. Avoid steep slopesIn order to not affect safety andcomfort of the passenger3.2. Allow the drainage




HIGHRELEVANCE

The running-way must have aminimum transversal slope in order toallow the drainage and avoid thebother to the waiting passengers orpedestrians when splashing3.3. Provide width of the lane in accordance with the kind of vehicle using it & the speedAlso have into account the need ofovertaking stopped or broken-downbuses, especially on reservedplatform infrastructures.3.4. Alignment planning of the route: assure the comfort of the passengerThe vertical and horizontal transitionsshould be adapted to the vehiclesrunning on the roadway.4. Crossing management4.1. Provide priority systems for the bus (traffic lights and signaling)Priority systems for buses atcrossings can reduce delays to busesand provide greater regularity in busschedules.4.2. Allow the bus to have the circulation and turns facilitated at crossingsThe bus should get right of way byphysical or technical priority, or atleast should get its movementsfacilitated5. Stops requirements management5.1. Guarantee passengers’ security at the stop at every timeAn adapted fitting of bus stop toreduce the risks of accidentconcerning all people5.2. Provide sufficient information adapted for all users at every stopStop information shall be easily torecognize a bus stop, to providenecessary information, legibility andreliable information.5.4. Ensure comfortable stopThe waiting time at the bus stop mustbe as pleasant as possible, to avoidcustomer regrets the comfort.5.5. Adapt the stop to the needs of the demand and buses, the organization of theoperation and the maintenance of the stopThe design and characteristics of thestop should be linked to the needs ofoperation, particularly with level oftraffic of the lines which supply thestop and with particular function




HIGHRELEVANCE

(terminal, regulation…).5.6. Allow the optimization of commercial speed while design the stops space & locationStops spacing should be optimized inorder to allow operations be as fast aspossible to avoid “lost time”.5.7. Guarantee the maximizing the demand while design the stops space and locationAvoid very long distance betweenstops in order to increase theattractiveness of the bus system.5.8. Guarantee not endanger the bus and other users of the road at the stopsStop should avoid damage on busand shelter, and other users of thesame public space.5.10. Avoid car parking in the place where the bus has to stopStop must be equipped so that carscan’t park at stop.6. Manage the accessibility to stops6.1. Ensure easy access to the bus stop, with no obstacles or obstructionsThe sidewalk shall be connected tobus platforms and not separated bygrass, grades, fences, etc.6.2. Ensure access to the bus to allThe bus stop shall be design andequipped in order to meet theaccessibility requirements by any kindof users6.3. Allow the entire platform to be clear of any obstructionsThe platform area shall be clear ofany obstruction (as trees, newspaperboxes…), according to the samedesign criteria used for planning thepath to the bus stops6.4. Provide physically challenged users with appropriate space at the stop forboarding/alighting operationsFacilities for the bus stop (markets,seats, shelters…) and any otherobject nearby should be easilydetectable by visually impairedpeople.6.5. Assure easily recognition of the bus stop and where users can waitThe customers should be easily findthe place for waiting and boardingoperations.7. Interface stop-bus management7.1. Assure an easy and secure boarding and alighting




HIGHRELEVANCE

The accessibility to the bus should befacilitated. Nothing has to hamper it.7.2. Stop designed: avoid the bus modifying its trajectoryThe bus accessibility to the stop andthe getting back in the traffic shouldbe facilitated for driver, to minimizerisks, accidents, and to avoid longwaits.7.3. Assure visibility of the stop for driverThe driver should be able to seewhere he has to stop by painting onthe road or bus stops enlighten.7.4. Height of the kerb: allow deploying a ramp with a proper slopeThe height of the kerb should not betoo high (to allow a wheelchair boardthe bus easily) nor too low.8. Interchange with other modes requirements management8.1. Provide near stops, connection with other modes, bike facilities, park&ride, etc.The connection with other bus, tramlines or other modes should be easy,safe, protected from weather, with theshorter distance possible andsignaling with indications on whatdirection are the stops.8.2. Transport terminals and interchange points construction: allow passenger tochange mode in a shorter timeTo convince the users to perceive thetrip as whole units, reducing the“broken” sensation of displacementthat transfers may cause passengers.8.3. Provide sufficient, accessible for all and organized information on the interchangeto improve the passenger flow.The signs and information of thetransport interchange station have toperform: giving directions, generalinformation, specific information8.4. Provide walking environment and the waiting areas on the interchange pleasant,safe and accessible for allThe walking and waiting environmentof the interchange should be ease toaccess, safe and protected from trafficand weather, free of obstacles, clean,etc.10. Interface bus-city management10.1. On-street constructions, speed limit regulations and the width of the street: assuresafe, secure and comfortable bus circulation, “calmed traffic areas” and pedestrian




HIGHRELEVANCE

To make bus system as an integratedpart of the city and its life, coexistingwith other traffic, vehicles andcitizens. Being able to adapt itsoperation conditions when needed.10.2. Provide practicable and safe pedestrian course to the stopThe pedestrian course to the stopshall be considered by theauthority/organization responsible forthat infrastructure section to reducerisks of injures whilst approaching ormoving away from the bus stops.10.3. Integrate bus system in the city planning and its infrastructureTo enable cities to ensure a realsustainable mobility, urban plannershave to take into account bus system

Functional requirements USER NEED AREAS1. Running way requirements management1.3. Allow giving priority to buscirculation over the rest of the traffic


1.4. Allow the circulation of the busand the visibility of the driver not behindered by any obstacle


2. Busway and lane requirements management2.1. Provide a reserved space for thebus circulation


2.2. Assure the strength to bus weightand its circulation with safetyconditions

- Safety and security- Service performance

2.3. Avoid the location of utilitiesunder busway or bus lane

- Service performance- Safety and security- Maintenance

3. Running-way geometric requirements management

3.1. Avoid steep slopes- Service performance- Comfort, cleanness and quality feeling- Safety and security

3.2. Allow the drainage- Safety and security- Service performance- Comfort, cleanness and quality feeling

3.3. Provide width of the lane inaccordance with the kind of vehicleusing it & the speed


3.4. Alignment planning of the route: - Comfort, cleanness and quality feeling


Functional requirements USER NEED AREASassure the comfort of the passenger4. Crossing management4.1. Provide priority systems for thebus (traffic lights and signaling)

- Service performance- Urban development and quality of life

4.2. Allow the bus to have thecirculation and turns facilitated atcrossings

- Service performance- Urban development and quality of life- Safety and security

5. Stops requirements management5.1. Guarantee passengers’ securityat the stop at every time


5.2. Provide sufficient informationadapted for all users at every stop

- Information to passenger, relational andbehavioural issues

5.4. Ensure comfortable stop - Comfort, cleanness and quality feeling- Urban development and quality of life

5.5. Adapt the stop to the needs of thedemand and buses, the organizationof the operation and the maintenanceof the stop


5.6. Allow the optimization ofcommercial speed while design thestops space & location


5.7. Guarantee the maximizing thedemand while design the stops spaceand location

- Service performance- Urban development and quality of life- Accessibility to vehicles and infrastructure

5.8. Guarantee not endanger the busand other users of the road at thestops


5.10. Avoid car parking in the placewhere the bus has to stop

- Service performance- Accessibility to vehicles and infrastructure

6. Manage the accessibility to stops6.1. Ensure easy access to the busstop, with no obstacles or obstructions

- Accessibility to vehicles and infrastructure

6.2. Ensure access to the bus to all - Accessibility to vehicles and infrastructure6.3. Allow the entire platform to beclear of any obstructions

- Accessibility to vehicles and infrastructure- Safety and security

6.4. Provide physically challengedusers with appropriate space at thestop for boarding/alighting operations.

- Accessibility to vehicles and infrastructure

6.5. Assure easily recognition of thebus stop and where users can wait.

- Accessibility to vehicles and infrastructure- Service performance

7. Interface stop-bus management7.1. Assure an easy and secureboarding and alighting


7.2. Stop designed: avoid the busmodifying its trajectory


7.3. Assure visibility of the stop for - Safety and security


Functional requirements USER NEED AREASdriver - Service performance7.4. Height of the kerb: allowdeploying a ramp with a proper slope


8. Interchange with other modes requirements management8.1. Provide near stops, connectionwith other modes, bike facilities,park&ride, etc.

- Modal integration- Service performance- Information to passenger

8.2. Transport terminals andinterchange points construction: allowpassenger to change mode in ashorter time

- Modal integration- Accessibility to vehicles and infrastructure

8.3. Provide sufficient, accessible forall and organized information on theinterchange to improve the passengerflow.

- Information to passenger- Service performance- Modal integration

8.4. Provide walking environment andthe waiting areas on the interchangepleasant, safe and accessible for all

- Comfort, cleanness and quality feeling- Modal integration- Accessibility to vehicles and infrastructure- Safety and security

10. Interface bus-city management10.1. On-street constructions, speedlimit regulations and the width of thestreet.

- Service performance- Safety and security- Urban development and quality of life

10.2. Provide practicable and safepedestrian course to the stop

- Safety and security- Urban development and quality of life- Accessibility to vehicles and infrastructure

10.3. Integrate bus system in the cityplanning and its infrastructure

- Urban development and quality of life- Service performance


Summary of results and conclusions

The work process for identifying most innovative infrastructure requirements for eachpriority topic has recognized 35 out of 46 infrastructure requirements as relevant ones. Bypriority topic, Urban Infrastructure in the most important for infrastructure requirements.Regarding user needs, Service performance, Safety and security, and Accessibilityto vehicles and Infrastructure are main user need areas for the most relevantinfrastructure requirements.

In order to complete the amount of information included in this subchapter 7.5., the mostsignificant (100% of the answer are high relevance) infrastructure requirements thatshould be taken into account for the definition of bus system in urban and suburban areasare the following:

3. Running way requirements (4 requirements are significant of which 1RELEVANT).


3.3. To provide width of the lane in accordance with the kind ofvehicle using it and the speed (RELEVANT FOR URBANINFRASTRUCTURE & SERVICE PERFORMANCE USER NEED).

5. Stops management requirements (8 requirements are significant of which 4RELEVANT)

5.4. To ensure comfortable stop (RELEVANT FOR URBANINFRASTRUCTURE & COMFORT, CLEANNESS AND QUALITYFEELING USER NEED).5.5. To adapt the stop to the needs of the demand and buses, theorganization of the operation and the maintenance of the stop(RELEVANT FOR URBAN INFRASTRUCTURE & SERVICEPERFORMANCE USER NEED).5.6. To allow the optimization of commercial speed while design thestops space and location (RELEVANT FOR URBAN INFRASTRUCTURE& SERVICE PERFORMANCE USER NEED).5.10. To avoid car parking in the place where the bus has to stop(RELEVANT FOR URBAN INFRASTRUCTURE & SERVICEPERFOMANCE USER NEED).

6. Manage the accessibility to stops (5 requirements are significant of which 4RELEVANT).

6.1. To ensure easy access to the bus stop, with no obstacles orobstructions (RELEVANT FOR URBAN INFRASTRUCTURE &ACCESSIBILITY TO VEHICLES AND INFRASTRUCTURE USER NEED).6.2. To ensure access to the bus to all (RELEVANT FOR URBANINFRASTRUCTURE & ACCESSIBILITY TO VEHICLES ANDINFRASTRUCTURE USER NEED).6.3. To allow the entire platform to be clear of any obstruction(RELEVANT FOR URBAN INFRASTRUCTURE & ACCESSIBILITY TOVEHICLES AND INFRASTRUCTURE USER NEED).6.4. To provide physically challenged users with appropriate space atthe stop for boarding/alighting operations (RELEVANT FOR URBANINFRASTRUCTURE & ACCESSIBILITY TO VEHICLES ANDINFRASTRUCTURE USER NEED).

8. Interchange with other modes management (4 requirements are significant ofwhich 3 RELEVANT).

8.1. To provide near stops, connection with other modes, bikesfacilities, park and ride, etc. (RELEVANT FOR URBANINFRASTRUCTURE & MODAL INTEGRATION USER NEED).8.2. Construction of transport terminals and interchange points: toallow passenger to change mode in a shorter time (RELEVANT FORURBAN INFRASTRUCTURE & MODAL INTEGRATION USER NEED).8.4. To provide walking environments and waiting areas at theinterchange points that are pleasant, safe and accessible for all(RELEVANT FOR URBAN INFRASTRUCTURE & COMFORT,CLEANNESS AND QUALITY FEELING USER NEED).

10. Interface bus-city management (3 requirements are significant of which 3RELEVANT).


10.1. On street constructions, speed limit regulations and the width ofthe street: assure safe, secure and comfortable bus circulation,“calmed traffic areas” and pedestrian (RELEVANT FOR URBANINFRASTRUCTURE & SERVICE PERFORMANCE USER NEED).10.2. To provide practicable and safe pedestrian course to the stop(RELEVANT FOR URBAN INFRASTRUCTURE & SAFETY ANDSECURITY USER NEED).10.3. To integrate bus system in city planning and its infrastructure(INNOVATION FOR URBAN INFRASTRUCTURE & URBANDEVELOPMENT AND QUALITY OF LIFE USER NEED).

To summarize, around 85% of infrastructure requirements are relevant for five topics, withthe exception of Topic 1, 2 and 3: Energy Management Strategy and Auxiliaries, DriverAssistance and Vehicle Design, respectively. Only two infrastructure requirements aremoderate relevant for Topic 4: IT Standard introduction in existing fleets. These arerelated to running way requirements (giving bus priority), and dynamic information atstops. IT standards and solutions should seek to allow bus priority circulation and toprovide dynamic information at stops. Regarding Intelligent Garage and predictivemaintenance (Topic 5) system, it is of relevance to provide interaction between the busand the ground stations based on IT solutions and provide with appropriate space ofdepots. Finally, for Urban Infrastructure (Topic 6), 35 out of 46 requirements are relevantaccording to partners. All main infrastructure areas are considered, except for Depots andWorkshop management. Out of 35 relevant requirements, 15 are highly relevant for all thepartners (100% responses, i.e. most important). These highly relevant requirements arerelated to: provide appropriate width of the lane; ensure comfortable stop; adapt the stopto the demand; optimization of commercial speed; avoid car parking; ensure easy accessto the bus stop; ensure access to the bus to all; allow the platform to be clear of anyobstruction; appropriate space of the stop for physically challenged users; provideconnection with other modes; construction of transport terminals; provide walkingenvironments; speed limits regulations; practice and safe pedestrian course to the stop;integrate bus system in city planning. In addition, all these relevant requirements for thetopics are identified with different user needs areas, being the three most common:service performance, safety and security, and accessibility to vehicles and infrastructure.All in all, infrastructure requirements are important for increasing the attractiveness andimprove the image of bus systems in urban and suburban areas.


7.6 Operation requirementsThis section describes the operational requirements that apply for bus systems in urbanand suburban areas.Based on the key EBSF requirements, information on different needs of the majorstakeholders, such as operators or authorities have been collected and transformed intosystem requirements.The overall objective was to list the most relevant requirements in terms of bus operationfor each of the EBSF_2 six priority topics and their relation to user needs areas. (Figure15) Thereby, most of the operation requirements describe a typical day of operation,starting with the start of service and continuing with the management of the service, bothwith and without interruptions. They are overlain by requirements that deal with thegeneral organisation of an urban bus network. Additionally, requirements directly relatedto the bus depot management and maintenance have been looked at.

Figure 15 – Structure of work for operation requirements.

Main areas for operation requirements

In total, 59 operation requirements have been analysed. They are subdivided into six mainareas, which again are subdivided into 17 sub areas. The following list provides anoverview on the main areas and the general direction of their requirements.

1. Service preparation management (14 requirements): public transport networkdesign, intermodality, accessibility of the bus services, user friendly fare system,driver training.


2. Pre-service management (3 requirements): preparation of bus servicesimmediately before leaving the bus depot.

3. Service management (operation) (19 requirements): incident management,delay management, service flexibility, passenger information.

4. Incident management during service (7 requirements): breakdownmanagement, emergency management.

5. Maintenance management (9 requirements): efficient maintenance and repairprocedures, maintenance staff management and support.

6. Bus depot management (7 requirements): bus depot design, vehicle datamanagement.

The most important requirements and the most relevant User Need Areas for each PriorityTopic are listed in the following tables.


The functional requirements from the operation point of view are generally not seen asvery relevant for energy management strategies and auxiliaries. The average weightedrelevance was just 0.46.



HIGHRELEVANCE

2. Pre-service management2.2 On-board equipment set-up managementAllow the operator to have thepossibility to set-up the on-board bussubsystemsSet-up the on-board equipmentbefore starting the service3. Service management (operation)3.3 Assure comfort and welcomingOperator: check the quality of thedriving of drivers

Table 32 – Operation Requirements identified as relevant for Topic 1

However, the rather low relevance is not very surprising as energy managementstrategies are internal vehicle configurations which should not interfere with dailyoperation. It can be seen as a clear hint that such management strategies must be self-adapting and that operators are in most cases neither willing nor able to adapt energy andpower management strategies to a specific line.Additionally, the driving style of drivers directly influences the energy or fuel consumptionand operators seems to be keen to check this as a measure to reduce consumptions.The according User Need Areas are dominated by Service performance.


Functional requirements USER NEED AREAS2. Pre-service management2.2 On-board equipment set-up

management- Economic and operation issues- Service performance

3. Service management (operation)

3.3 Assure comfort and welcoming- Service performance- Comfort, cleanness and quality feeling /

perceptionTable 33 – Operation Requirements identified as relevant for Topic 1 and related user needs areas


With an average weighted relevance of 0.92, driver assistance systems are seen as beingmuch more important for operation issues than energy management strategies andauxiliaries.



HIGHRELEVANCE

1. Service preparation management1.4 Driver issues managementManagement tool for collecting dataand improvement of driving style(innovation)

Provide regular training for drivers

3. Service management (operation)3.1 Safety and security managementAllow the control centre to locate andcommunicate with the vehicle andthe driverAllow the driver to send a silentinstant security alert for emergencies3.2 Service managementAllow the drivers to know their delayor advanceAllow drivers to check the timebetween previous / following bus3.3 Assure comfort and welcomingOperator: check the quality of thedriving of drivers4. Incident management during service4.1 Safety and security managementProvide the driver with passiveinstant alert device for emergenciesAllow staff to know what occurredwithout asking the driver in case ofbreak-down of a bus system




HIGHRELEVANCE

Keep the drivers informed about thestatus of different bus system


A focus lies on driver assistance systems that help the driver to stabilise operation,especially to reduce delays and the so-called bunching.Similar to energy management strategies, the possibility to check the driving styles areseen as highly important. However, in many cases it will be difficult to find an agreementwith the drivers' unions. For instance in Germany, it is nearly impossible to get anysurveillance systems that check the drivers' behaviour approved by the local unions.Additionally, systems for remote-diagnostics and alert systems are seen as very relevantfor operation.The relevant User Need Areas are listed in the following table. They are dominated bySafety and security and Service performance.

Functional requirements USER NEED AREAS1. Service preparation management

1.4 Driver issues management- Economic and operation issues- Safety and security- Service performance

3. Service management (operation)3.1 Safety and security

management- Safety and security- Service performance

3.2 Service management - Service performance- Economic and operation issues


perception4. Incident management during service4.1 Safety and security

management- Safety and security- Maintenance

Table 35 – Operation Requirements identified as relevant for Topic 2 and related user needs areas


With an average weighted relevance of just 0.41, vehicle design issues are seen as beingnot very relevant for operation. However, this mirrors the definition of the functionalrequirements which more or less regard accessibility and sufficient capacity as given.




HIGHRELEVANCE

3. Service management (operation)3.2 Service managementAllow staff to fast adapt the serviceto the demand3.3 Assure comfort and welcomingAllow to adapt the capacity to theload (internal and externalmodularity)4. Incident management during service4.1 Safety and security managementGuarantee vehicle manoeuvres inbreakdown situations not toendanger other road users


Again, the most relevant User Need Areas are Safety and Security and Serviceperformance.Functional requirements USER NEED AREAS3. Service management (operation)



perception4. Incident management during service4.1 Safety and security



TOPIC 4: IT Standard introduction in existing fleets

The introduction of IT standards into bus fleets received the highest average weightedrelevance of all six Priority Topics (1.50). That does not come as a surprise as easy, fastand standardized communication and data transmission are key factors for many aspectsof modern public transport.A strong focus lies on passenger information as IT standards are a necessary prerequisitefor this very important aspect of modern and especially accessible and comfortable publictransport. Furthermore many aspects of incident management are also relevant forstandardised IT. However, the highest relevance for IT standards has been seen in termsof bus maintenance and bus depot management. Apart from remote-diagnostics the easyand fast data exchange between buses and the back office in bus depots are seen asextremely relevant for this Priority Topic.


The following table only shows the functional requirements with the highest relevance toIT standard introduction.



HIGHRELEVANCE

3. Service management (operation)3.1 Safety and security managementAllow the control centre to locate andcommunicate with the vehicle andthe driverOperator: collect and send imagesfrom inside and outside the bus incase of emergency and accidents3.2 Service managementAllow staff to fast adapt the serviceto the demand3.4 Information managementProvide visual and audioannouncements in the busAllow tools using new technologiesto be "user friendly" for all (drivers,staff, and different type of customers:elderly, disabled…)Provide information to passengersduring the regular tripProvide passengers with reliable andon time information aboutdisturbances on the bus system andalso on modes in connectedsystems: inside the bus, at stops orhubs, and everywhere on demandAllow all passengers to know wherethe bus is located on a line or on thenetwork (at stop, in the bus…)Assure the easy update of theinformation support3.5 Integration managementEnsure the exchange of informationbetween staffs of different operators(or modes)Provide passengers with informationabout connections with other modes4. Incident management during service4.1 Safety and security managementAllow staff to know what occurredwithout asking the driver in case ofbreak-down of a bus system




HIGHRELEVANCE

Keep the drivers informed about thestatus of different bus system4.2 Incident management (detection, failure, assistance, recovery, etc.)Allow treatment of break-down byremote connectionAllow prevention of a critical fault bya bi-directional communicationbetween remote assistance and busInform passengers about the break-down and alternatives for continuingthe trip5. Maintenance management5.2 Maintainability (operational procedures and organisation, infrastructures andinstruments, etc.)Allow the on-board computers tocommunicate with the bus depot tomonitor the mechanical conditions ofthe bus, standardization of thecommunication protocol6. Bus depot management6.2 Data download / upload managementStandardization of the telematiccomponents on the bus in order toallow fast and easy communicationwith the bus depotDownload the exploitation data fromthe on-board computers at theentrance of the bus depotUpload the service data for the nextday (timetable, routes, advertising,head up display etc.) on the on-board computers6.3 Operational procedure and organisation (bus depot processes control, etc.)Transmit the bus emissions datarecord to the back office


The fact that uniform IT standards are relevant for many aspects of modern bus operationis also visible in the broad range of User Need Areas as listed in the following table.

Functional requirements USER NEED AREAS3. Service management (operation)3.1 Safety and security

management- Safety and security- Service performance


Functional requirements USER NEED AREAS



perception

3.4 Information management - Information to passengers, relationaland behavioural issues

3.5 Integration management - Modal integration and additional /flexible services

4. Incident management during service4.1 Safety and security


4.2 Management of incidents(detection, failure, assistance,recovery, etc.)


- Maintenance- Safety and security- Service performance

5. Maintenance management5.2 Maintainability management

(operational procedures andorganisation, infrastructures andinstruments, etc.)

- Maintenance- Economic and operation issues

6. Bus depot management6.2 Data download / upload

management- Maintenance- Economic and operation issues

6.3 Management of operationalprocedures and organisation(depot processes control, etc.)

- Maintenance- Economic and operation issues- Environmental issues


TOPIC 5: Intelligent garage and predictive maintenance

The Priority Topic Intelligent garage received an above average relevance of 1.05 andtogether with IT standards the highest rate of evaluated functional requirements.The highest ratings have been given to the main areas Maintenance management andBus depot management. This has to be seen against the background that efficient andpredictive maintenance procedures as well as intelligent bus depot procedures have highcost saving potentials.Again, the following table only shows the functional requirements with the highestrelevance to Intelligent garage and predictive maintenance.


Topic 5: Intelligent garage and predictive maintenance


HIGHRELEVANCE

4. Incident management during service4.1 Safety and security management

Allow staff to know what occurredwithout asking the driver in case ofbreak-down of a bus system

4.2 Incident management (detection, failure, assistance, recovery, etc.)

Allow treatment of break-down byremote connectionAllow prevention of a critical fault bya bi-directional communicationbetween remote assistance and bus

5. Maintenance management5.2 Maintainability (operational procedures and organisation, infrastructures andinstruments, etc.)Allow the bus to run without failures,following the maintenanceprocedures, due to a maintenanceprocess permanently managed andmonitored

Allow the on-board computers tocommunicate with the bus depot tomonitor the mechanical conditions ofthe bus, standardization of thecommunication protocolDesign the working area to improvefast diagnosis and repair timesRecord all maintenance operationdone for each vehicle in acomprehensive database containingstructured information about previousmaintenance operations and datafrom bus diagnosis systemStandardization of the instrumentsand tools to allow their usage onmany bus types

Provide the operator with anautomated system for measuring thestock of spare partsPerform the on-conditionmaintenance on diagnostic andfunctional parameters


6. Bus depot management6.2 Data download / upload managementStandardization of the telematiccomponents on the bus in order toallow fast and easy communicationwith the bus depotDownload the exploitation data fromthe on-board computers at theentrance of the bus depotUpload the service data for the nextday (timetable, routes, advertising,etc.) on the on-board computers6.3 Operational procedure and organisation (bus depot processes control, etc.)Transmit the bus emissions datarecord to the back officeAllow the utility devices (washingmachines, fuel station, vacuumcleaner, oil refuelling system, etc.) toautomatically identify the bus,monitor the operation andcommunicate with the back office


The most important User Need Area for Priority Topic 5 is maintenance. (see the followingtable)Functional requirements USER NEED AREAS4. Incident management during service4.1 Safety and security


4.2 Management of incidents(detection, failure, assistance,recovery, etc.)



5. Maintenance management5.2 Maintainability management

(operational procedures andorganisation, infrastructures andinstruments, etc.)


6. Bus depot management6.2 Data download / upload

management- Maintenance- Economic and operation issues

6.3 Management of operationalprocedures and organisation(depot processes control, etc.)




TOPIC 6: Urban Infrastructure

With an average weighted relevance of just 0.58 the selected functional requirementshave not been seen as particularly important for the Priority Topic Urban Infrastructure ingeneral. However, functional requirements that deal with fast and easy travelling in agiven urban network and intermodality received significantly higher attention.



HIGHRELEVANCE

1. Service preparation management1.1 Service organisation managementNetwork design for minimal lineschanges

Intermodal network design

Consider the bus service needs inthe city planning (city master plan)1.3 Intermodality managementOrganisation of the bus system to becomplementary and connected withother public transport modesOrganisation of the bus system to becomplementary and connected withalternative modes of transport (car-sharing, park and ride, taxi, bikesharing, etc.)Organisation of fast and easyconnections


This is also mirrored by the selected User Need Areas for Priority Topic 6.Functional requirements USER NEED AREAS1. Service preparation management1.1 Service organisation

management- Service performance- Urban development and quality of life

1.3 Intermodality management

- Modal integration and additional /flexible services

- Information to passengers, relational andbehavioural issues

- Service performanceTable 43 – Operation Requirements identified as relevant for Topic 6 and related user needs areas


Summary of results and conclusions

In total, 44 out of the 59 pre-defined functional requirements have been assessed asrelevant for bus operation. The highest relevance received functional requirements thatdeal with: the efficient management of bus depots, maintenance procedures that use modern communication technologies, passenger information and safety and security.

The selected functional requirements once again underline the high importance of moderncommunication technologies for all aspects of passenger friendly, safe and efficient publictransport.


8 ConclusionsCoherently with the objectives of Task 2.1, this deliverable reports on the methodologydeveloped to update the database of users’ needs and functional requirements, asidentified within the EBSF and 3iBS projetcs, as well as on the outcomes achieved.Capitalizing on the partners’ knowledge and experience, a consultation which involvedPTOs, PTAs, research entities, associations of bus stakeholders and knowledgeproviders, allowed reviewing the previous database vis-à-vis the priority topics EBSF_2 iscommitted to work on for the deployment of innovative bus systems in European cities.Overall, an up-to-date set of 168 user needs has been delivered, through the selection ofneeds identified in the previous projects which are still relevant, despite the innovationsoccurred in the bus system domain (the first selection of users’ needs took place withinEBSF in 2008-2009), and the integration of 54 “new” user needs, which had not beenidentified as such in the past projects.

The updated set of users’ needs was the starting point for the review of the functionalrequirements, which represent a coherent list of features that the whole bus system has toinclude in order to satisfy the needs of the bus stakeholders. Since the bus system isdefined as the synergic superposition of vehicle, infrastructure and operation, the analysishas taken into account both the systems requirements and the requirements to be fulfilledby the three domains (or subsystems).As a result, the deliverable contains about 200 functional requirements relevant for thedeployment of innovative bus systems with respect to the 6 EBSF_2 priority topics.

The final outcome of this analysis is therefore the up-to-date database of functionalrequirements linked with the reviewed users’ needs. As a summary of the new database,the additional users’ needs and the most relevant functional requirements are reported inthe following through graphic elaborations by topic.


TOPIC 1 - ENERGY MANAGEMENT STRATEGY AND AUXILIARIES

User needs – Integration

FROMPREVIOUSPROJECT

11N. User needs

20

INTEGRATION9


- Driving smoothness

Economic and operationissues

- Low operating costs

Environmental issues- Smart E-mobility fleet

and infrastructure- Vehicle electric charge

and temporally storagein the bus terminals

Maintenance- Increase life of

insulating materials andrubber pipes in theengine room due tohigh temperatures

Service performance- Improve energy efficiency for

climatization- Electric climatization- Improve energy storage system- Increase commercial speed: inclusion

of parking control devices inside thebus, mobility service, etc.


Functional requirements


Functional requirements HIGHRELEVANCE USER NEEDS AREAS

System requirements


- Urban development and qualityof life

- Environmental issues


Vehicle requirementsAllow the bus to meet the networkperformance requirements of itsspecific service

- Environmental issues- Service performance- Economic and operation issues

TOPIC 2 - DRIVER ASSISTANCE


N. User needs17

N. FROMPREVIOUSPROJECTS

13

INTEGRATION4


- Smooth driving


- Low operating costs- Reduced energy

use

Environmental issues

- Reduction ofemissions





System requirementsGuarantee improvedcommercial speed on the entirePT-trip


Vehicle requirementsKeep driver informed on thestate of the vehicle

- Maintenance- Economic and operation

issues- Safety and security- Service performance

Allow drivers to access to allcontrols

Provide an ergonomic driver’sworkplace

- Comfort, cleanness andquality feeling/perception

- Service performance- Economic and operation

issues

Provide a good interface for thedriver


- Information to passengers,relational and behaviouralissues

- Safety and security- Service performance- Economic and operation

issues

Allow the driver to control histrajectory

- Safety and security- Service performance- Comfort, cleanness and

quality feelingHelp driver following a unique,correct and repeatabletrajectory every times

- Service performance- Comfort, cleanness and

quality feeling- Safety and security- Economic and operation

issues

Help driver to follow a drivingprofile

Help driver doing precise,regular and repeatable docking


Operation requirements

Management tool for collectingdata and improvement of drivingstyle (innovation)

- Economic and operationissues


Allow the driver to send a silentinstant security alert foremergencies





Allow the drivers to know theirdelay or advance

- Service performance- Economic and operation

issuesAllow drivers to check the timebetween previous / followingbusProvide the driver with passiveinstant alert device foremergencies

- Safety and security- Maintenance

TOPIC 3 - VEHICLE DESIGN (CAPACITY, ACCESSIBILITY, MODULARITY)


N. User needs45


31

INTEGRATION14

Accessibility to vehicles andinfrastructure s

- Bicycle rack in the bus- Full accessibility, for all

citizens independentlyfrom their physical orsocial status

Environmental issues- Smart E-mobility

fleet andinfrastructure

Maintenance- Increase life of

insulating materials andrubber pipes in theengine room due tohigh temperatures

Service performance- Improve energy efficiency

for climatization- Define occupancy levels

according to their routes- Increase commercial

speed: inclusion of parkingcontrol devices inside thebus, mobility service, etc.





System requirements

Enable customer care in allaspects (comfort, access toinformation, access to fares, etc)

Enable capacity to be adapted todemand

Enable optimal seating capacity forspecific needs



- Service performanceAllow comfortable standing andseating for passengers - Service performance

Enable the physical protection ofpassengers, staff and surroundingpeople in case of accident andattack


Pricing and commercialpolicies

- To allow the entry byall doors and ticketingmachine before andonboard the vehicle;smart technologies(NFC, QR, etc.)


- Positive absorption ofelectric busescomponents in thevehicle designs(harmonious exteriorsand interiors)

Economic and operation issues- Status upgrade for buses,

as urban objects, to beaccepted in dense urbanzones

- Improved commercialspeed






Vehicle requirements

Allow drivers to greet passengers




- Service performanceProvide an ergonomic driver’sworkplace



Design of the driver’s cabin: allowdriver to operate in comfortProvide a good view of drivers"surroundings

- Safety and security- Economic and operation issues- Comfort, cleanness and quality

feelingProtect the driver from noisepollutionProtected driver from collisions

Allow the operator to upgrade thevehicle equipment and fittings


- Maintenance

Create, maintain and customize amodern image of the bus


- Service performance- Information to passengers,

relational and behavioural issues

Allow the operator to change thevehicle equipment, fittings andlayout



- Service performance- Maintenance- Economic and operation issues

Ensure coupling/uncouplingadditional trailer to adaptsignificantly the bus capacity


- Modal integration andadditional/flexible services



Ensure coupling/uncoupling otherbuses to combine several lines ona common segmentDesign and build the bus as anassembling of elementary standardmodules


- Maintenance

Avoid injury or disturbance topassengers waiting at stops - Safety and security




Help driver following a unique,correct and repeatable trajectoryevery times

- Service performance- Safety and security- Comfort, cleanness and quality

feeling/perception- Economic and operation issues

Help driver coupling trailers orother buses

Operation requirementsAllow to adapt the capacity to theload (internal and externalmodularity).


quality feeling / perception

TOPIC 4 - IT STANDARD INTRODUCTION IN EXISTING FLEETS


N. User needs32


24

INTEGRATION8


- To allow the entryby all doors andticketing machinebefore and onboardthe vehicle; smarttechnologies (NFC,QR, etc.)





Service performance- Use of plug'n play ITS modules

compliant with ITxPT based onmodular/flexible IT architecture.

- Open data for real timeinformation of the serviceperformance

- Define occupancy levelsaccording to their routes.





System requirementsGuarantee complete andpermanent travel informationoutside the vehicle

- Information to passengers,relational and behavioural issues


Guarantee complete andpermanent travel information insidethe vehicle




- Economic and operation issues


- Economic and operation issues- Service performance

Guarantee accurate real timeinformation, mainly but not only incase of service disruption, to avoidtrip uncertainty




- Modal integration andadditional/flexible services

Vehicle requirementsInclude devices for exchanginginformation


- Safety and security- Pricing and commercial policies- Comfort, cleanness and quality

feeling/perception

Inform passengers and potentialpassengers about PT and otherservices

Provide a good interface for thedriver



Maintenance

Reduce installationtime taken to installequipment on-board bus

Information to passenger

Different apps forinformation of theservice based onopen data





- Safety and security- Economic and operation issues

Provide integrated systemarchitecture

- Maintenance- Service performance- Economic and operation issues- Modal integration and

additional/flexible servicesProvide open system architecture

System architecture: integrate thirdparties devices, support the properprotocol

Provide a modular on board ITsystemOperation requirementsAllow the control centre to locateand communicate with the vehicleand the driver - Safety and security

- Service performanceOperator: collect and send imagesfrom inside and outside the bus incase of emergency and accidentsAllow staff to fast adapt the serviceto the demand


Provide visual and audioannouncements in the bus


Allow tools using new technologiesto be "user friendly" for all (drivers,staff, and different type ofcustomers: elderly, disabled…)Provide information to passengersduring the regular tripProvide passengers with reliableand on time information aboutdisturbances on the bus systemand also on modes in connectedsystems: inside the bus, at stops orhubs, and everywhere on demandAllow all passengers to knowwhere the bus is located on a lineor on the network (at stop, in thebus…)Assure the easy update of theinformation support

Ensure the exchange ofinformation between staffs ofdifferent operators (or modes) - Modal integration and

additional / flexible servicesProvide passengers withinformation about connections withother modes




Allow staff to know what occurredwithout asking the driver in case ofbreak-down of a bus system - Safety and security

- MaintenanceKeep the drivers informed aboutthe status of different bus system

Allow treatment of break-down byremote connection



Allow prevention of a critical faultby a bi-directional communicationbetween remote assistance andbusInform passengers about thebreak-down and alternatives forcontinuing the trip

Allow the on-board computers tocommunicate with the bus depot tomonitor the mechanical conditionsof the bus, standardization of thecommunication protocol


Standardization of the telematiccomponents on the bus in order toallow fast and easy communicationwith the bus depot


Download the exploitation datafrom the on-board computers at theentrance of the bus depotUpload the service data for thenext day (timetable, routes,advertising, head up display etc.)on the on-board computers

Transmit the bus emissions datarecord to the back office



TOPIC 5 - INTELLIGENT GARAGE AND PREDICTIVE MAINTENANCE





System requirements



- Maintenance- Service performance

N. User needs19


13

INTEGRATION6





Maintenance- Reduce installation time taken to install

equipment on-board bus- Increase life of insulating materials and

rubber pipes in the engine room due tohigh temperatures

- Improve energy storage system





Vehicle requirementsLimit the number of builder-specific parts and admit genericspares




Provide interaction with groundstations

Infrastructure requirementsThe depots and workshopshould have appropriate spaceand organization for themovement of vehicles and theneeded maintenanceoperations

- Maintenance

The depots should have thepossibility to interact with thebus to collect diagnosis data,functioning data, to detectsystem failure and anticipatebreakdowns.


Operation requirementsAllow staff to know whatoccurred without asking thedriver in case of break-down ofa bus system

- Safety and security- Maintenance

Allow treatment of break-downby remote connection



Allow prevention of a criticalfault by a bi-directionalcommunication betweenremote assistance and busAllow the bus to run withoutfailures, following themaintenance procedures, dueto a maintenance processpermanently managed andmonitored


issues

Allow the on-board computersto communicate with the busdepot to monitor themechanical conditions of thebus, standardization of thecommunication protocolDesign the working area toimprove fast diagnosis andrepair times


Record all maintenanceoperation done for each vehiclein a comprehensive databasecontaining structuredinformation about previousmaintenance operations anddata from bus diagnosis systemStandardization of theinstruments and tools to allowtheir usage on many bus typesProvide the operator with anautomated system formeasuring the stock of sparepartsPerform the on-conditionmaintenance on diagnostic andfunctional parametersStandardization of the telematiccomponents on the bus in orderto allow fast and easycommunication with the busdepot - Maintenance


Download the exploitation datafrom the on-board computers atthe entrance of the bus depotUpload the service data for thenext day (timetable, routes,advertising, etc.) on the on-board computersTransmit the bus emissionsdata record to the back office


issues- Environmental issues

Allow the utility devices(washing machines, fuelstation, vacuum cleaner, oilrefuelling system, etc.) toautomatically identify the bus,monitor the operation andcommunicate with the backoffice

TOPIC 6 - URBAN INFRASTRUCTURE

N. User needs38


22

INTEGRATION16


User needs –Integration

Accessibility to vehicles andinfrastructure s

- Easier transfers- Full accessibility, for all

citizens independentlyfrom their physical orsocial status


- Innovative bus shelterconcepts: efficient(solar panels),internet, bike; VMP


- To allow the entry byall doors and ticketingmachine before andonboard the vehicle;smart technologies(NFC, QR, etc.)

Environmental issues- Smart E-mobility fleet

and infrastructure- Vehicle electric charge

and temporally storagein the bus terminals

Service performance- Open data for real time

information of the serviceperformance

- Increase commercialspeed: inclusion of parkingcontrol devices inside thebus, mobility service, etc.

- Promotion of bus lanes,busways and traffic-lightpriority for the buses, BRT


- Positive businessmodels for busterminals

- Improvedcommercial speed





System requirements


- Accessibility to vehiclesand infrastructures

- Urban development andquality of life

Allow a concept of priority for PT- Service performance- Urban development and

quality of life

Contribute to a more sustainable city- Urban development and

quality of life- Environmental issues


Enable a service safe for pedestriansor road-users - Safety and security


- Safety and security- Accessibility to vehicles

and infrastructuresInfrastructure requirementsTo provide some advantages orpriority to the circulation of buses,especially in congested roads orstreets, to improve regularity andincrease its speed.


Information to passenger- Different apps for

information of theservice based onopen data

Urban development and quality oflife

- To facilitate connection with"new modes" (carsharing)and park&ride

- Bus terminals as urbanassets included in thecityscapes (vs. as optimizedtransport hubs)

- Co-design of bus terminalswith local authorities andservice providers


The depots should have thepossibility to interact with the bus tocollect diagnosis data, functioningdata, to detect system failure andanticipate breakdowns.


Depending on the bus systemsolution, different levels ofsegregation should be provided:BHLS, BHLS lite, Classic urbanlines, local bus lines…


Due to high frequency bus passingon the busways and lanes theinfrastructure needs a specialreinforcement to avoid itsdegradation


It should be avoided to locate urbanutilities (water, gas, electricity…)under the busway or bus lane

- Service performance- Safety and security- Maintenance

In order to not affect safety andcomfort of the passenger


quality feeling- Safety and security

The running-way must have aminimum transversal slope in orderto allow the drainage and avoid thebother to the waiting passengers orpedestrians when splashing

- Safety and security- Service performance- Comfort, cleanness and

quality feeling

Also have into account the need ofovertaking stopped or broken-downbuses, especially on reservedplatform infrastructures.


The vertical and horizontaltransitions should be adapted to thevehicles running on the roadway.

- Comfort, cleanness andquality feeling

Priority systems for buses atcrossings can reduce delays tobuses and provide greater regularityin bus schedules.

- Service performance- Urban development and

quality of life

The bus should get right of way byphysical or technical priority, or atleast should get its movementsfacilitated


quality of life- Safety and security

An adapted fitting of bus stop toreduce the risks of accidentconcerning all people



Stop information shall be easily torecognize a bus stop, to providenecessary information, legibility andreliable information.

- Information topassenger, relationaland behavioural issues

The waiting time at the bus stopmust be as pleasant as possible, toavoid customer regrets the comfort.



The design and characteristics of thestop should be linked to the needs ofoperation, particularly with level oftraffic of the lines which supply thestop and with particular function(terminal, regulation…).


Stops spacing should be optimized inorder to allow operations be as fastas possible to avoid “lost time”.


Avoid very long distance betweenstops in order to increase theattractiveness of the bus system.


quality of life- Accessibility to vehicles

and infrastructureStop should avoid damage on busand shelter, and other users of thesame public space.


Stop must be equipped so that carscan’t park at stop.

- Service performance- Accessibility to vehicles

and infrastructureThe sidewalk shall be connected tobus platforms and not separated bygrass, grades, fences, etc.

- Accessibility to vehiclesand infrastructure

The bus stop shall be design andequipped in order to meet theaccessibility requirements by anykind of users


The platform area shall be clear ofany obstruction (as trees, newspaperboxes…), according to the samedesign criteria used for planning thepath to the bus stops



Facilities for the bus stop (markets,seats, shelters…) and any otherobject nearby should be easilydetectable by visually impairedpeople.


The customers should be easily findthe place for waiting and boardingoperations.




The accessibility to the bus shouldbe facilitated. Nothing has to hamperit.


- Safety and securityThe bus accessibility to the stop andthe getting back in the traffic shouldbe facilitated for driver, to minimizerisks, accidents, and to avoid longwaits.


The driver should be able to seewhere he has to stop by painting onthe road or bus stops enlighten.


The height of the kerb should not betoo high (to allow a wheelchair boardthe bus easily) nor too low.


- Safety and securityThe connection with other bus, tramlines or other modes should be easy,safe, protected from weather, withthe shorter distance possible andsignaling with indications on whatdirection are the stops.

- Modal integration- Service performance- Information to passenger

To convince the users to perceivethe trip as whole units, reducing the“broken” sensation of displacementthat transfers may causepassengers.

- Modal integration- Accessibility to vehicles

and infrastructure

The signs and information of thetransport interchange station have toperform: giving directions, generalinformation, specific information

- Information to passenger- Service performance- Modal integration

The walking and waiting environmentof the interchange should be ease toaccess, safe and protected fromtraffic and weather, free of obstacles,clean, etc.


- Modal integration- Accessibility to vehicles

and infrastructure- Safety and security

To make bus system as anintegrated part of the city and its life,coexisting with other traffic, vehiclesand citizens. Being able to adapt itsoperation conditions when needed.

- Service performance- Safety and security- Urban development and

quality of life

The pedestrian course to the stopshall be considered by theauthority/organization responsible forthat infrastructure section to reducerisks of injures whilst approaching ormoving away from the bus stops.

- Safety and security- Urban development and

quality of life- Accessibility to vehicles

and infrastructure

To enable cities to ensure a realsustainable mobility, urban plannershave to take into account bus system




Operation requirements

Intermodal network design - Service performance- Urban development and quality

of lifeConsider the bus service needsin the city planning (city masterplan)Organisation of the bus systemto be complementary andconnected with other publictransport modes

- Modal integration andadditional / flexible services



Organisation of the bus systemto be complementary andconnected with alternativemodes of transport (car-sharing,park and ride, taxi, bike sharing,etc.)Organisation of fast and easyconnections


9 AnnexesAnnex 1 – USER NEEDS UPDATING: RESULTSEnergy Management Strategy and Auxiliaries

Energy Management Strategy and Auxiliaries

ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP

USER NEEDS AREA MAIN USER NEEDS Is UN achieved? [Y/N] % Y % N

Comfort, cleanness andquality feeling/perception Comfort on bus and station N N n.a. n.a. n.a. N n.a. N 0 100



N N N n.a. n.a. N n.a. N 0 100


Possibility of monitoring thecomfort in the vehicle N N N n.a. n.a. N n.a. n.a. 0 100


Suitable heat and air conditioningsystems Y N Y n.a. Y N n.a. N 50 50


Applying new recommendedprocurement rules (warranty,vehicle"s availability, functionalspecifications, penalties of allsorts...)

Y N N n.a. n.a. Y n.a. n.a. 50 50



N N N n.a. n.a. N n.a. n.a. 0 100

Environmental issues High energy efficiency of vehicles N N Y n.a. N N n.a. N 17 83,4

Environmental issues Precise and periodic controls ofpolluting emissions N N N n.a. Y N n.a. Y 33 66,7

Environmental issues Recyclability of the vehicle and ofits parts N N N n.a. n.a. N n.a. n.a. 0 100

Environmental issues Reduce engine noise N N Y n.a. Y N n.a. n.a. 40 60

Safety and security Healthy working environment Y N Y n.a. n.a. Y n.a. n.a. 75 25


Driver Assistance

Driver assistance

ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP



Attention to ergonomics andstandardisation of driver placeand tasks

n.a. N Y n.a. n.a. N n.a. N 25 75



N N N n.a. n.a. N n.a. N 0 100



Y N Y n.a. Y N n.a. N 50 50

Economic and operationissues Standardization of components n.a. N N n.a. n.a. N n.a. N 0 100

Environmental issues High energy efficiency of vehicles N N Y n.a. n.a. N n.a. N 20 80

MaintenanceContinuous training ofmaintenance personnel also withthe support of multimedia

Y N Y n.a. n.a. N n.a. N 40 60

Safety and security Absence/minimize of obstacles onthe pathway to the bus stop Y N N n.a. n.a. Y n.a. n.a. 50 50

Safety and security Availability of instant alert devicesfor drivers Y N Y n.a. n.a. Y n.a. N 60 40


Safety and security Improved driver assistancesystem N N N n.a. n.a. N n.a. N 0 100

Safety and security Improved training for drivers Y N N n.a. Y N n.a. N 33 66,7

Safety and security On line assistance in case ofemergency Y N Y n.a. n.a. N n.a. n.a. 50 50

Safety and securityPossibility for the driver to controlthe trajectory whatever road orweather condition

Y N N n.a. Y N n.a. N 33 66,7


Vehicle Design

Vehicle Design (Capacity, Accessibility,Modularity)

ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP




Y N Y n.a. N N n.a. N 33 66,7


Easy and fast boarding/alightingof passengers N N N n.a. n.a. N n.a. N 0 100


Integration bus and shelterdesigns N N N n.a. N N n.a. N 0 100


Attention to ergonomics andstandardisation of driver placeand tasks

Y N Y n.a. Y N n.a. N 50 50

Comfort, cleanness andquality feeling/perception Cleanness (bus, stop and station) N N N n.a. N N n.a. Y 17 83,4

Comfort, cleanness andquality feeling/perception Comfort on bus and station N N n.a. n.a. n.a. N n.a. N 0 100



N N N n.a. n.a. N n.a. N 0 100


Possibility of monitoring thecomfort in the vehicle N N N n.a. n.a. N n.a. N 0 100


Reduction/elimination of internalnoise ,vibrations and ‘odours" N N N n.a. n.a. N n.a. Y 20 80


Suitable heat and airconditioning systems Y N Y n.a. n.a. N n.a. N 40 60



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP



Applying new recommendedprocurement rules (warranty,vehicle"s availability, functionalspecifications, penalties of allsorts...)

Y N N n.a. n.a. Y n.a. n.a. 50 50


Development of externalmodularity to adapt the serviceto the demand (impact onoperating costs)

N N N n.a. N N n.a. N 0 100



N N N n.a. n.a. N n.a. n.a. 0 100

Economic and operationissues Standardization of components N N N n.a. n.a. N n.a. N 0 100

Environmental issues High energy efficiency of vehicles N N Y n.a. N N n.a. N 17 83,4

Environmental issues Recyclability of the vehicle and ofits parts N N N n.a. Y N n.a. n.a. 20 80

Information to passengers,relational and behaviouralissues

Clear identification of theentrance/exit doors and ofreserved seats

Y N Y n.a. Y Y n.a. Y 83 16,7


Easy and accessible information(bus, stop and station) Y N Y n.a. Y N n.a. N 50 50


Possibility of using extra serviceslike telephone and internet (onthe bus and at the station/stop)

Y N Y n.a. n.a. N n.a. N 40 60


Reliability/availability ofpassengers information systems,especially on trip changing,traffic and "next stop"

Y N Y n.a. Y N n.a. N 50 50

Modal integration andadditional/flexible services

Bus seating capacity adaptable tothe local network and specificneeds of the operator/city

N N Y n.a. Y N n.a. Y 50 50



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP



Development of externalmodularity to adapt the serviceto the demand (impact on travelcomfort)

N N N n.a. N N n.a. N 0 100


Adaptable driver cabin when thedriver is in charge of ticket selling N N N n.a. n.a. N n.a. N 0 100


Flexible vehicle solutions forticketing and space for ticketingequipments

N N Y n.a. n.a. N n.a. n.a. 25 75


Safety and security Control of door opening/closingfree of risk for passengers Y N N n.a. Y N n.a. Y 50 50

Safety and security Fire fighting devices (enginecompartments) N N N n.a. n.a. N n.a. n.a. 0 100

Service performance Higher transport capacity N N N n.a. n.a. N n.a. N 0 100

Service performance


N N Y n.a. n.a. N n.a. N 20 80

Urban development andquality of life Intermodality PT and bike N N N n.a. n.a. N n.a. N 0 100

Urban development andquality of life

Attractive and welcoming design(bus - in particular exteriors - andstation/stop)

N n.a. n.a. n.a. n.a. N n.a. N 0 100


IT Standard introduction in existing fleets


ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP




Y N Y N n.a. N n.a. n.a. 40 60



N N N N n.a. N n.a. N 0 100


Applying new recommendedprocurement rules (warranty,vehicle"s availability,functional specifications,penalties of all sorts...)

Y N N N N Y n.a. n.a. 33 67


Efficient fleet management,also through collaboration busmanufacturers/ITS developers

Y N Y N n.a. N n.a. Y 50 50


Standardization ofcomponents N N N n.a. n.a. N n.a. N 0 100

Information to pasengers,relational and behaviouralissues

Easy and accessibleinformation (bus, stop andstation)

Y N Y N Y N n.a. N 43 57



Y N Y N N N n.a. N 29 71


Reliability/availability ofpassengers informationsystems, especially on tripchanging, traffic and "nextstop"

Y N Y N Y N n.a. Y 57 43

Maintenance

Adoption of structuralstandard: linked with systems(remote connections) andoutside devices

N N N n.a. n.a. N n.a. N 0 100



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP


Maintenance


N N Y N n.a. N n.a. N 17 83

Maintenance


N N N N n.a. N n.a. N 0 100

MaintenanceReduction of maintenancetime (duration and frequency):increase in LCC of components

N N N N n.a. N n.a. N 0 100

Maintenance

Standardisation and easyinstallation of on boardtelematic components (telediagnostic box)

N N N Y N N n.a. N 14 86

Maintenance

Standardisation ofcommunication protocolsbetween vehicles and back-office

N N N N n.a. N n.a. N 0 100


Integration between thedifferent types of networks(transport, information andticketing)

N N N N n.a. N n.a. N 0 100


Flexible vehicle solutions forticketing and space forticketing equipments

Y N Y N n.a. N n.a. n.a. 40 60

Safety and security Improved driver assistancesystem N N N N n.a. N n.a. N 0 100

Safety and security On line assistance in case ofemergency Y N Y N N N n.a. n.a. 33 67



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP


Safety and security


N N N N n.a. N n.a. N 0 100

Service performanceEasy collection of data tocontrol, evaluate and adaptthe service

Y N N N Y N n.a. N 29 71

Service performance Efficient fleet management Y N Y N n.a. N n.a. N 33 67

Service performance Knowing the passenger load inreal time N N N N N N n.a. n.a. 0 100

Service performance

Standardisation and easyinstallation of on boardtelemetric components(AVMS, ticketing, passengerinformation devices,telediagnostic box andcommunication gateway)

N N Y Y n.a. N n.a. N 33 67


Improved management oftraffic lights and priorities forPT (green wave)

Y N n.a. N n.a. N n.a. Y 40 60


Intelligent Garage and predictive maintenance


ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP



Improved overallattractivity/image of thePT system

N N n.a. N n.a. N n.a. N 0 100


Applying newrecommendedprocurement rules(warranty, vehicle"savailability, functionalspecifications, penalties ofall sorts...)

Y N N N n.a. Y n.a. n.a. 40 60


Efficient fleetmanagement, also throughcollaboration busmanufacturers/ITSdevelopers

N N n.a. N n.a. N n.a. N 0 100

Maintenance

Adoption of structuralstandard: linked withsystems (remoteconnections) and outsidedevices

N N n.a. N n.a. N n.a. N 0 100

Maintenance

Continuous training ofmaintenance personnelalso with the support ofmultimedia

N N n.a. N N N n.a. N 0 100

Maintenance

Easy, but detailed, onboard diagnosis withoutuse of external diagnosticdevice (pc, tester,diagnostic workstation,etc)

N N Y N N N n.a. N 14,3 85,7

Maintenance

Improved telediagnosticand pre-analysis ofpotential sub-systemsfailure (preventivemaintenance)

N N N n.a. n.a. N n.a. N 0 100

Maintenance

Reduction of maintenancetime (duration andfrequency): increase in LCCof components

N N N N n.a. N n.a. N 0 100

Maintenance

Standardisation ofcommunication protocolsbetween vehicles andback-office

N N N N n.a. N n.a. N 0 100



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP


Safety and security

Easy diagnosis andidentification of errors tofacilitate the role ofsystem controller

N N n.a. N n.a. Y n.a. N 20 80

Service performanceEasy collection of data tocontrol, evaluate andadapt the service

N N n.a. N n.a. N n.a. N 0 100

Service performance Efficient fleetmanagement N N n.a. N n.a. N n.a. N 0 100

Service performance

Standardisation and easyinstallation of on boardtelemetric components(AVMS, ticketing,passenger informationdevices, telediagnostic boxand communicationgateway)

N N N Y n.a. N n.a. N 16,6 83,4


Urban Infrastructure


ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP



Adoption of newtechnologies (e.g.information tech.) to notcreate barriers for certaincategories of users

N N N n.a. n.a. N N N 0 100


Easy and fastboarding/alighting ofpassengers

N N N n.a. n.a. N N N 0 100


Integration bus and shelterdesigns N N N n.a. N N N N 0 100


Platforms sized to host allwaiting passengers Y N N n.a. Y N N N 28,6 71,4


Cleanness (bus, stop andstation) N N N n.a. n.a. N N N 0 100

Comfort, cleanness andquality feeling/perception Comfort on bus and station N N n.a. n.a. n.a. N N N 0 100



N N N n.a. n.a. N N N 0 100


Optimization of timetablesand connections/transfers Y N Y n.a. Y N N N 42,9 57,1


Easy and accessibleinformation (bus, stop andstation)

Y N Y n.a. Y N N N 42,9 57,1


Possibility of using extraservices like telephone andinternet (on the bus and atthe station/stop)

Y N Y n.a. N N N N 28,6 71,4


Reliability/availability ofpassengers informationsystems, especially on tripchanging, traffic and "nextstop"

Y N Y n.a. Y N N N 42,9 57,1


Integration between thedifferent types of networks(transport, information andticketing)

N N N n.a. n.a. N N N 0 100


More bus lines feedingrailways stations Y N Y n.a. n.a. Y Y Y 83,3 16,7



ASSTRA

CRTM

DBUS

DIGIMO

BEE

FRAUN

HOFER

UTP

RATP

UITP


Safety and securityAbsence/minimize ofobstacles on the pathway tothe bus stop

Y N N n.a. N Y N N 28,6 71,4

Service performance Knowing the passenger loadin real time N N N n.a. n.a. N N n.a. 0 100

Urban development andquality of life Intermodality PT and bike N N N n.a. n.a. N N N 0 100


Pavements free from triphazards and unnecessaryobstacles - free and safemovement

Y N N n.a. N Y N N 28,6 71,4


Reduction of traffic andcongestion N N N n.a. n.a. Y N n.a. 20 80


Attractive and welcomingdesign (bus - in particularexteriors - and station/stop)

N N N n.a. n.a. N N N 0 100

Urban development andquality of life Seamless travel N N Y n.a. n.a. N N N 16,6 83,4


Improved management oftraffic lights and prioritiesfor PT (green wave)

Y N Y n.a. Y N n.a. Y 66,6 33,4


Increase of number of buscorridors Y N Y n.a. N Y n.a. N 50 50

Documents

Report on updated definition for “innovative bus system” D 2 · 2018-05-30 · Deliverable 2.1 Page 1 of 135 Version 2.0 Date of issue June 1st 2016 Nature of Deliverable External