Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006

European ITS Framework Architecture Consequences of Integration for

and its application for Co-operative Co-operative Systems
Systems
• Integrated system (and large)
– Whole > sum of the parts
• Many stakeholders that need to co-operate
– Vehicle Owners/Drivers
– Road Operators
– Operators of Other Transport Modes
– Regulatory/Enforcement Authorities etc.
• Varying commercial interests
– Public services, commercial services
• Multi-disciplinary activities
– e.g. Software, Hardware, Traffic Engineering
Peter Jesty & Richard Bossom - FRAME Team
• Multiple manufacturers / technologies
Jan Willem Tierolf – FRAME Forum
– To build integrated systems
© European Commission

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 2

Communication between Parties Levels of Thinking

• Need a way of describing integrated ITS Multi-Authority
Multi-AuthorityInter-
Inter-
Level 3
– To identify business opportunities operability
operabilityProperties
Properties Behaviour
– For planning deployments
– To identify technical solutions
Single
SingleAuthority
Authority Technology
– To highlight critical parts Level 2
System
SystemProperties
Properties Independent
– Simple : that everyone can understand
Functional Viewpoint
Physical Viewpoint
Level 1 System
SystemStructure
Structure Communication Viewpoint
etc.

Design Level Architectures

Level 0
•Software
•Hardware Technology Dependent
•Communications
•….etc. CONVERGE
TRANSPORT TELEMATICS
SUPPORT & CONSENSUS

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 3 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 4

© European Commission 1
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006

Uses of a High-Level ITS Partial System Integration

Architecture e.g. Regional, Inter-
Urban or City Issues

e.g. National or
Regional Issues • Many people think that you only need good
Multi-Operator Inter-operability
Stakeholder Aspirations
Properties (Level 3) communications to integrate systems
Single Operator Single Operator

ITS Architecture
System Properties
(Level 2)
System Properties
(Level 2) Assumptions
Assumptions Assumptions
Assumptions
Overall System Structure
Overall System Structure
Overall System Structure

Overall System Structure

Overall System Structure
System
System A
A System
System B
B
Overall System Structure
Organistional
Issues
Risk
Analysis
Individual ITS
Deployment Cost
Benefits
Architectures
Programme Component
(Level 1)
Agreed
System
Specifications
Boundary Infrastructure
Specifications

System Design Architectures Communications

(Level 0)

Provide • Different assumptions prevent inter-operability

Inputs
Enterprise Viewpoint Carried out through
Project activities

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 5 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 6

Agreed Communications BUT Consistent System Integration

Different Assumptions/Beliefs
“Long live “Long live
King Henry!” King Edward!” Assumptions
Assumptions

System
System A
A System
System B
B

• Agreed communications AND common

assumptions produce inter-operability
• Achieved with a System Architecture
Towton
1461

7 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 8

© European Commission 2
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006

Impact on Development Costs What is a High-Level ITS

10 : 100: 1000 Rule Architecture?
• Cost of fixing problems
in System development Cost
• Top-level framework
(MEuro)

increases exponentially • Strategic plan for designs

with time – “What is needed”
• System Architectures NOT
can expose these – “How is it to be implemented”
problems early in the • Technology independent
development cycle
• Top-level assumptions
• Early fixing costs less
– Minimum necessary
– “70% of faults found
after unit testing are NOT
requirements errors” System
Requirements
System
Design
System System
Development Installation
System
Operation
– Maximum Possible
System Architectures
Jointused here
eSafety/Prime Workshop, Budapest - 4-5 September 2006 9 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 10

Simple Overview Example Application 1a

Identified from Functional Data Flow
Traffic
User Needs
Actor 1c
Analyse Traffic
Sub-System Y Data
Fn H Collect Traffic
FDFi Traffic
Function A Data
Control
Centre
Fn M Roadside
Unit Inform
Drivers
Fn D FDFj
Data Fn T Raw Traffic Data
Message – 100 Bytes
Store
Max delay – 0.5 secs
Sub-System X Physical Data Flow Message Interval – 0.1 secs
Terminator 4 Drivers
PDFq = FDFi + FDFj Min Data Rate = 200 B/s
Min Inter-Message gap = 0.1s
Functional Viewpoint Physical Viewpoint
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 11 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 12

© European Commission 3
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006

Example Application 1b Example Application 2

Traffic
Traffic Control Centre
• Intersection Safety:
Inform – Projects will produce
Collect Traffic Drivers demonstrations
Data – Provide “proof of concept”

Roadside
Unit
Drivers • The next step will be:
– Deployment throughout
Analyse Traffic European Union
Data • In time
Traffic Flow Data
Message – 100 Bytes • In space
Max delay – 5 secs • By many providers
Message Interval – 10 secs
Min Data Rate = 20 B/s
Min Inter-Message gap = 10 s
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 13 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 14

Use of a High-Level Architecture Additional Benefit to

A High-Level Architecture
Co-operative System IPs and STREPS
provides
Other ITS
• In time Technology Applications
– Technology will independence SAFESPOT
change
CVIS European
SAFESPOT

• In space High-Level CVIS

functional and ITS
– Intersections have
physical structure Framework
many configurations COOPERS Other ITS
Projects
COOPERS Other ITS Architecture
• Multiple providers Projects
High-Level
– Many designs Specifications

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 15 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 16

© European Commission 4
Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006

Why use the European FRAME –Activities being funded by the

ITS Framework Architecture? FRAME Forum
• Cost • Maintenance of
– Many similarities between nation states – the European ITS Framework Architecture
• Especially for cross-border services • Version 3 → Version 3.1
– Estimate that Framework Architecture has 80% – Maintenance of the Selection Tool
• Work does not have to be repeated • Version 1.1.5 → Version 1.1.6

• Compatibility and Communication • Review of current ITS Architectures

– A common approach – Europe and rest of the world
– A common planning “language” • Update FRAME Web Site
• Knowledge Pool • Direct support for members
– Increasing body of experience available • Open User Forum 15? November 2006
• e.g. from the FRAME Forum Team

www.frame-online.net

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 17 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 18

European ITS Framework Architecture

in Europe
VIKING

Thank you for listening

CONNECT

Countries involved with the Projects using Framework

Framework Architecture Architecture

Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 19 Joint eSafety/Prime Workshop, Budapest - 4-5 September 2006 20

© European Commission 5