Intelligent Transportation systems in Egypt : Opportunities and Challenges. INTELLIGENT TRANSPORTATION SYSTEMS IN EUROPE. Dr. Omayma ABDEL MOHSEN Switching Department Omayma.firstname.lastname@example.org April 2014. The European Commission’s Directorate- General for Mobility and Transport (MOVE).
Intelligent Transportation systems in Egypt : Opportunities and Challenges
INTELLIGENT TRANSPORTATION SYSTEMS IN EUROPE
“The European Commission’s Directorate-General for Mobility and Transport is in charge of developing transport policies for the European Union. Its remit is to ensure mobility in a single European transport Area, integrating citizen’s needs, environmental policy, and competitiveness.”
The 1992 Maastricht Treaty took a big step forward by introducing the concept of the Trans-European Transport Network (TEN-T).
This strengthened the basis for Member States to act together to provide key links in the European transport infrastructure, on which the European single market depends
TRANS-EUROPEAN TRANSPORT NETWORK (TEN-T CORE NETWORK CORRIDORS)
In the late 1980sthe EC began to invest in research in ITS for roads (the PROMETHEUS and DRIVEProgrammes, European ATIS Projects/Systems)
Starting in the 1990sthe Euro-Regional Projects funded from the Trans- European Transport Network (TEN-T) budget made significant advances in harmonised data exchange (DATEX)between European road authorities and in the use of language independent traffic messages over the Radio Data System Traffic Message Channel (RDS-TMC).
These Euro-Regional projects merged in 2007 into a single DG-MOVE project EasyWay
Two decades on from the pioneering DRIVE research programme, the EC tabled proposals designed to provide a framework for ITS applications and services connected with road transport, including their interfaces with other transport modes.
The aim is to harmonise deployment and operational use of ITS throughout Europe where possible.
The Commission’s proposals were subject to a long process of scrutiny before finally being adopted in 2010. The so-called ‘ITS Directive’ has a seven year lifespan during which time the EC is required to develop specifications for ITS systems and services in four priority areas
Action Plan for the Deployment of Intelligent Transport Systems (ITS) in Europe (2008)
Directive2010/40/EU: Framework for the Coordinated and Effective Deployment and Use of Intelligent Transport Systems
The European Commission’s ITS Action Plan is working to accelerate and coordinate the deployment of ITS in road transport, including interfaces with other transport modes.
The action plan was adopted after much preparatory work and a long consultation with stakeholders.
Its main focus is to ensure the compatibility and interoperability of systems, to facilitate the continuity of ITS services, and to do so through coordinated and concerted action at EU level.
Road Safetyand Security
Continuity ofTraffic &
for EU ITS
of road data
& Travel Data
places for trucks
for I2I, V2X
funding for ITS
toolkit for ITS
6 priority areas - 24 actions
The implementation of the ITS Action Plan represents a joint effort by several European Commission services, coordinated by the Directorate-General for Mobility and Transport with the direct and active collaboration of four other directorates general (DGs) of the Commission:
The plan is also implemented in close cooperation with ITS stakeholders, as seen for example in the staging of various workshops on action plan topics.
Framework for the Coordinated and Effective
Deployment and Use of Intelligent Transport Systems
in force since26 Aug 2010
ITS Directive Timeline
Source: ITS Policy and Funding Instruments in Multi-annualFinanacial Framework 2014-2020, PawelStelmaszczyk Head of ITS Unit,EuropeanCommission – DG MOVE
Intelligent transport systems
Vice-President Kallas welcomes deal on 112 eCall
The eCall system automatically dials 112-Europe's single emergency number - in the event of a serious accident.
Action Area 2.3 of the EU ITS Action Plan requires the use of ITS Architectures to support the European objectives of the Plan.
The European ITS Framework Architecture, also known as the FRAME Architecture, provides a suitable basis for this task.
The FRAME Architecture was produced by the EC funded project KAREN (1998-2000). It has been maintained and enhanced continuously since then with cooperative systems being added by the E-FRAME project (2008-11).
E-FRAME is funded by the EC, FP7 IST Programme (IST:Information Society Technology)
Clearly this architecture is a candidate for use by those who are implementing the ITS Action Plan.
The FRAME Architecture is quite large. When originally produced by the KAREN project it was documented in paper form, resulting in several large documents that were not easy to navigate.
As part of the work of the FRAME projects the Functional Viewpoint is now available in HTML format. This is known as the FRAME Browsing Tool and can be viewed using Internet Explorer.
A copy can be downloaded from the FRAME website at: http://www.frame-online.net/.
The FRAME Browsing Tool provides an interactive interface through which it is possible to move from one part of the FRAME Architecture to another and to follow through the relationships between all of the functional elements.
It includes the diagrams shown in Figures that follows, plus Data Flow Diagrams for all the hierarchies in each of the Functional Areas.
It also includes the descriptions of all of the elements in the functionality, i.e. Functions, Data Stores and Data Flows, the Terminator and Actor descriptions, plus the identity and description of each User Need.
The User Needs are divided up according to the areas in which the Services operate.
Hence there are User Needs for:
• Traveller Journey Assistance,
• Traffic Management,
• Public Transport Operations,
• Freight and Fleet Operations,
• Advanced Driver Assistance Systems,
• Safety and Emergency Facilities,
• Support for Law Enforcement and
• Electronic Payment
In order for the functionality in each of the Functional Areas to work, it needs to be able to collect data from the outside world and to provide either that data, or a processed version of it back to the outside world.
This is done by specific dedicated parts of the functionality in each Functional Area. The links with the outside world that this functionality needs are illustrated by what is called the "Context Diagram" which is shown in Figure.
The FRAME Selection, which contains a data base with all the elements of the FRAME Architecture does not perform any selections automatically, but it does support the architecture team in its use of the methodology in the following ways.
• The team selects those User Needs that reflect the Stakeholder Aspirations.
•The tool will then guide the architecture team to those parts of the Functional Viewpoint that help to satisfy those User Needs.
• Once a Functional Viewpoint is considered acceptable, it can be used as the basis for one or more Physical Viewpoints.
• Once a Physical Viewpoint has been completed one of the reports available from the Selection Tool can be used to provide the starting point for an analysis of the Physical Data Flows. This leads to the creation of the Communications Viewpoint, which shows the characteristics of the links required between each of the sub-systems and modules, plus those with the Terminators.