The FRAME Architecture (originally called the European ITS Framework Architecture) was developed as a result of recommendations from the High Level Group on transport telematics, which were supported by a resolution of the Council of Ministers. It was created and first published by the EC funded project KAREN in October 2000. The underlying aim of this initiative was to promote the deployment of (mainly road-based) ITS in Europe by producing a framework which would provide a systematic basis for planning ITS implementations, facilitate their integration when multiple systems were to be deployed, and help to ensure inter-operability, including across European borders.
A distinctive feature of the FRAME Architecture is that it is designed to have sub-sets created from it, and is thus unlikely to be used in its entirety. Indeed, on occasions, it contains more than one way of performing a service and the user can select the most appropriate set of functionality to deliver it in that environment. Thus the FRAME Architecture is not so much a model of integrated ITS, as a framework from which specific models of integrated ITS can be created in a systematic and common manner.
The FRAME Architecture now covers the following areas of ITS:
- Electronic Fee Collection
- Emergency Notification and Response – Roadside and In-Vehicle Notification
- Traffic Management – Urban, Inter-Urban, Parking, Tunnels and Bridges, Maintenance and Simulation, together with the Management of Incidents, Road Vehicle Based Pollution and the Demand for Road Use
- Public Transport Management – Schedules, Fares, On-Demand Services, Fleet and Driver Management
- In-Vehicle Systems – includes some Cooperative Systems
- Traveller Assistance – Pre-Journey and On-Trip Planning, Travel Information
- Support for Law Enforcement
- Freight and Fleet Management
- Provide Support for Cooperative Systems – specific services not included elsewhere, e.g. bus lane use, freight vehicle parking
- Multi-modal interfaces – links to other modes when required, e.g. travel information, multi-modal crossing management
The FRAME Architecture should be freely available; however, privacy concerns
and business considerations also should be taken into account.
As a part of an architecture creation process a review of the privacy, safety
and security aspects should be conducted, i.e. the privacy, safety and security
aspects are the responsibility of a user of the FRAME Architecture.
The Functional View may be used by the advisors and academic users
and the Physical View should be designed for the developers and/or ITS planners.
It is worth considering expanding the FRAME Architecture tool to provide:
component descriptions/examples and best practices /solutions for a few
ITS service requirements, e.g. those included in EU ITS Directive.