2 User Needs Results

1

• 2) User Needs Results
• Jonathan Booth
• MVA

2
WP2 - User Needs and Communication Scenarios

• Achievements
• Finalised user needs requirements
• Assessment of user needs and preferred
  communications scenarios
• Prioritised areas for development
• Introduced the TRIDENT concept to users

Next
3
WP2 - User Needs and Communication Scenarios
Technology Review (D2.1)
Desk Studies
Non -Technical Obstacles Recommendations (D2.3
)
Other User Input
Questionnaire
User Forum (Results D2.4)
Final User Needs (D2.5)
System Requirements WP3
4
WP2 - User Needs and Communication Scenarios

• D2.1 - Characteristics and benefits of state of
  the art data sharing and exchange technologies
• Introduction to the TRIDENT architecture
• Existing ITS data exchange
• Messaging technologies
• EDI, EDIFACT, ASN.1
• Extensions to DATEX, new messages, functionality

Next
5
WP2 - User Needs and Communication Scenarios

• D2.1 - (continued)
• New technologies applied to the ITS domain
• Internet technologies (CGI, XML, X-HTML)
• federated and distributed databases
• object oriented technologies (state of the art,
  CORBA, JAVA, D-COM)
• Comparative assessment of different technologies

Example
6
WP2 - User Needs and Communication Scenarios

• Comparative assessment of different technologies

Deployment Skills
Deployment Costs
Deployment Time
Maintenance Costs
Portability
Extensibility
CORBA
? ? ? ?
? ?
? ?
? ? ?
? ? ? ?
?
D-COM
? ? ?
? ? ?
? ?
? ? ? ?
? ? ?
?

• Medium complexity example

Process Flowchart
7
WP2 - User Needs and Communication Scenarios

• D2.3 - Draft recommendations to overcome
  non-technical obstacles
• Identifies issues
• Suggests approaches to solutions
• Finalised version provided after evaluation of
  TRIDENT specifications

Next
8
WP2 - User Needs and Communication Scenarios

• D2.3 - (continued)
• Issues identified include
• Contracts and agreements, service level
  agreements
• Differing applications, added value to VASPs
• Competition between modes, modal shift
  agreements
• Costs
• Security and privacy, bandwidth, latency
• Integration with existing systems

Process Flowchart
9
WP2 - User Needs and Communication Scenarios

• D2.4 - Results of the User Forum
• User Forum held in Leeds, UK on 10 March 00
• 30 attendees
• Attendees included PT operators, PT Authorities,
  central government, system developers,
  consultants, broadcasters
• Focus
• to present initial concepts of TRIDENT
• to gain user input on a range of issues
• validate TRIDENT approach

Next
10
WP2 - User Needs and Communication Scenarios

• D2.4 - (continued)
• Issues discussed included
• The types of users of TRIDENT
• Types of data to be exchanged
• The use of TRIDENT to support end-user services
• Likely technological choices and their impact
• Granularity of the data exchanged
• Location referencing

Process Flowchart
11
WP2 - User Needs and Communication Scenarios

• D2.5 - Final user needs and communication
  scenarios
• Desk Studies
• Questionnaire
• User needs gathered from other sources
• High-level communication scenarios
• Derived System Requirements

Next
12
WP2 - User Needs and Communication Scenarios

• D2.5 - Desk Studies
• Desk Studies
• Stradivarius
• EU-Spirit
• DATEX-Go
• INFOTEN

Next
Process Flowchart
13
WP2 - User Needs and Communication Scenarios

• D2.5 - Questionnaire
• Questionnaire
• About the organisations
• Data sent received
• Contractual arrangements
• Technologies
• Location Referencing, maps data

Next
Process Flowchart
14
WP2 - User Needs and Communication Scenarios

• D2.5 - Other sources of user needs
• Other sources of user needs
• From the standardisation process
• TRIDENT User Forum
• CENTRICO TIC-TIC Workshop
• UK Urban Traffic Management and Control
  Programme
• Location Referencing, maps data

Next
Process Flowchart
15
WP2 - User Needs and Communication Scenarios

• D2.5 - Final user needs - System Requirements
• System Requirements
• 21 requirements, covering functionality,
  configuration, security and areas of data to be
  exchanged

Process Flowchart
WP3
16
WP2 - User Needs and Communication Scenarios

• System Requirements
• cover urban inter-urban transport
• different modes of transport
• send receive static, semi-static and dynamic
  data - support sharing remote querying
• common data model and data dictionary approach
• common location referencing rules
• alternative location referencing mechanisms
• as much as possible compatible with existing
  implementations
• easy to maintain and extend
• easily reconfigurable

Process Flowchart
Next
17
WP2 - User Needs and Communication Scenarios

• System Requirements
• cost-effective way
• near real-time
• confirmation of the reception of data
• not media specific
• privacy of data
• allow exchange of encrypted data
• support contractual arrangements on-line
• browsing through catalogues of available data
• support deployment of strategic priorities
• support mechanisms for charging for exchange
• ...

Process Flowchart
WP3
18

• 3) EDI Specifications
• Jonathan Booth
• MVA

19
WP3 - Draft EDI Specifications

• Achievements
• Specify an extension to DATEX to permit key
  public transport information to be exchanged
• Provide input to the standardisation process
  (through CEN TC278 WG8)
• Provide a basis for testing

Next
20
WP3 - Draft EDI Specifications

• What has been done
• Assessment of various data types for public
  transport information provision
• Selection of the key initial target areas based
  on user needs
• PT vehicle(s) status, delays and cancellation
• PT vehicle travel time(s)
• Identify new location referencing solution -
  extension to current ILOC specification
• Draft new EDIFACT message TRAPTI
• D3.1 corresponds to DATEX Data Dictionary

Next
21
WP3 - Draft EDI Specifications

• Extension to current ILOC specification
• ILOC considered good general solution
• Signed Longitude 01234567
• Signed Latitude 6543210
• Word order L
• Descriptor 1 name of stop point 53165
• Descriptor 2 road/street name or number 53262
• Descriptor 3 destination name blanks
• Location type 3 chars
• BUT location types for PT required (stop point)
• ALSO applying the LLOC concept (two ILOCs
  identifying a link) to public transport

22
WP3 - Draft EDI Specifications

• Public transport delays
• Public transport cancellations
• Travel times (road and public transport)
• Public transport timetables
• Public transport status
• Public transport enquiries and booking
• Fares (to include public transport and road
  tolls)
• Network description and characterisation
• Road traffic events
• Road traffic status
• Journey planners
• Points of interests
• Tourist information
• Special facilities
• Weather

23
(No Transcript)