The growing use of "Intelligent Transport Systems" (ITS) or transport
telematics - i.e. applications of information and
telecommunications
technologies in the field of transport - has made it increasingly important to have
a
high level framework which helps to ensure that systems are
well-conceived and compatible at national and European level.
The
European ITS Framework Architecture was created in order to provide
guidelines and a common approach to the
planning, development and implementation of ITS throughout
Europe. The first version was created by the KAREN project and published in autumn 2000.
It focusses mainly on road-based ITS applications and covers eight major
functional areas.
The benefits of having an ITS Architecture and how to go about creating one are
explained in the brochure 'Planning
a Modern Transport System'.
History of
the Architecture
- Version 1.0 was created
by the KAREN Project (Keystone Architecture Required for
European Networks) and issued in October 2000. It was the result of
an effort to create a minimum stable framework necessary for the
deployment of working and workable ITS within the European Union
until at least 2010. The Architecture focusses mainly on road-based
applications. It is planned to extend it in the future to include
intermodal interfaces.
- Version 1.1
was issued in
March 2002 by the FRAME Projects. It consists of an update of the previous version
and corrects a number of inconsistencies found in Version 1.0.
For details of the changes made see the Update Notes (D10) in the LIBRARY.
- Version 2.0 was issued in August 2004 by the FRAME Projects.
It is an upgrade of the previous version which takes into account the use of the Selection Tool.
For details of the changes made see the Update Notes (D11) in the
LIBRARY. Note that this document also includes
details of all Update Request and Problem Reports submitted by users.
- Version 3.0 was issued
in November 2004 and incorporates further improvements based on the Update Requests and Problem Reports submitted by
users of the ITS Framework Architecture. For details of the changes made see
Update Notes (D12) in the LIBRARY
Top
Areas
covered
The following are the FUNCTIONAL
AREAS covered by the European ITS Framework Architecture
- Electronic Payment
Facilities
- Safety and Emergency
Facilities
- Traffic Management
- Public Transport Operations
- Advanced Driver Assistance
Systems (ADAS)
- Traveller Journery
Assistance
- Support for Law Enforcement
- Freight and Fleet Operations
Top
Overview
The European ITS Framework Architecture is a "tool-box"
from which other ITS Architectures and/or systems specifications can be developed. It provides a framework for the
development of:
- National, Regional or Local ITS
Architectures
- Systems for ITS deployments at
national, regional or local level
What does it consist of?
- User Needs: provide the formal definition of what
the stakeholders want an ITS deployment to provide in terms of the services they want to see delivered and any constraints they wish to place on the delivery of these services.
- Functional Viewpoint: defines the functionality needed by the ITS System to fulfil the User Needs and interface
with the outside world. It also includes a definition of the data
used by
the System as input or output. It is divided into Functional Areas, which are further divided
into Functions. All the Areas are provided with diagrams (called Data Flow
Diagrams) which show how the functions relate to each other, to Data Stores
and to the Terminators (the outside world) through the Data Flows.
- Physical Viewpoint: describes the various ways the Functional Architecture can be used
by
defining how the functionalities can be grouped into physical locations to form
implementable Systems, taking account of any User
Needs that have physical (as opposed to functional) requirements. It consists of a series of "Example Systems" and
also provides a description of the methodology for deployment and implementation.
- Communications Viewpoint: developed
from the Physical Architecture and describes the kind of communications links
needed in a System in order to support its
physical data flows. It may include some
requirements from the User Needs, where they relate to specific communication
requirements. It consists of an analysis of the communications requirements for
several of the "Example Systems" in the Physical Architecture.
It also describes the best current communication technologies and
standards.
- Deployment Study: shows how the
Systems derived from the Architecture can be deployed and describes some of the
ways in which existing systems can be
migrated to conform with the European Framework Architecture.
- Cost Benefit Study:
provides a prediction of the likely costs and benefits that can be
expected to accrue from the deployment of the Architecture.
- Organisational Viewpoint:
looks at how the organisations responsible for owning, managing or operating
sysems can work together in order to deliver the ITS services being developed.
- Risk Analysis: describes the
risks to ITS deployment and categorises them according to the seriousness of
their impact. Mitigation strategies may are provided for some of the most
severe risks.
Other background information on the
methodology can be found in the Overview Document (D3.6) in the LIBRARY.
Top
|
