Deliverable D4.3.7: Guidelines and proposals for the revision of ITS architecture in Italy. Stefano Dondi

Transcription

1 Deliverable D4.3.7: Guidelines and proposals for the revision of ITS architecture in Italy Stefano Dondi December 2013

2 PROJECT INFORMATION Title: Acronym: EoI Reference number: Programme: Intelligent Transport Systems in South East Europe SEE-ITS SEE/D/0099/3.2/X South East Europe Transnational Cooperation Programme Starting date: September 28 th, 2012 Duration: Web site: 24 months PROJECT PARTNERS No Name Short name Country LP Centre for Research and Technology Hellas - Hellenic Institute of Transport CERTH-HIT Greece ERDF PP1 Patras Municipal Enterprise for Planning and Development S.A. ADEP S.A. Greece ERDF PP2 AustriaTech - Federal Agency for Technological Measures Ltd ATE Austria ERDF PP3 Hungarian Transport Administration HTA Hungary ERDF PP4 Bulgarian Association Intelligent Transport Systems ITS Bulgaria Bulgaria ERDF PP5 Intelligent Transport Systems Romania ITS Romania Romania ERDF PP6 University of Ljubljana UL Slovenia ERDF PP7 Institute for Transport and Logistics Foundation EU ASP1 Hellenic Intelligent Transport Systems ITS HELLAS Greece EU ASP2 ITS Hungary Association ITS Hungary Hungary 20% ASP1 Italian ITS Association TTS Italia Italy 10% PP1 Albanian Association of Urban Transport SHKTQ Albania 10% PP2 Faculty of Transport and Traffic Sciences, University of Zagreb ITL FPZ Italy Croatia Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 1

3 DOCUMENT PROFILE Document status: Final version Deliverable code: D4.3.7 Deliverable title: Guidelines and proposals for the revision of ITS architecture in Italy Work Package: 4 Preparation date: 20/12/2013 Submission date: 01/04/2014 Total pages: 25 Dissemination level: Public Author: Stefano Dondi Contributors: Evangelos Mitsakis, Maria Chatziathanasiou, Panagiotis Iordanopoulos Abstract: The current document presents the status of the Italian National ITS Architecture, giving an overview about the problems of the maintenance and operation of this Architecture and providing proposals for its revision Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 2

4 EXECUTIVE SUMMARY The current document presents the status of the Italian National ITS Architecture, giving an overview about the problems of the maintenance and operation of this Architecture and providing proposals for its revision Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 3

5 CONTENTS 1. Introduction Short outline of SEE-ITS project Aim of the report Contents and structure of the document 6 2. Overview of Italy s ITS Architecture Background Components of Italy s national ITS architecture Analysis of the current deployment of ITS User needs and services Logical Architecture (or Functional) Physical Architecture Organizational Architecture Context Diagram Navigation tool Glossary Architecture implementation Case 1: e-call Case 2: STRIM-TP Problems encountered Conclusions Actions towards interoperability Final concluding remarks 24 Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 4

6 LIST OF FIGURES Figure 1: European Framework Architecture 10 Figure 2: Italian Architecture in the international context 10 Figure 3: Symbols for Architectural Diagram 14 Figure 4: Provide Electronic Payments Facilities - Physic Architecture 15 Figure 5: ARTIST architecture 17 Figure 6: Navigation tool framework 18 Figure 7: e-call architecture 20 Figure 8: e-call organizational architecture 21 Figure 9: STRIM-TP organizational architecture 22 Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 5

7 1. INTRODUCTION 1.1. Short outline of SEE-ITS project The idea and one of the tasks of SEE-ITS project is to harmonize the existing ITS architectures with architectures in design in SEE countries and in EU. ITS (intelligent transport systems and services) architecture assumes profound knowledge about how the ITS works in the sense that innovative proposals shall be formulated, corresponding to the existing conditions and not binding for its further development. According to SEE-ITS activities a guidelines and proposals for the revision of the existing ITS architectures in SEE countries should be prepared. Then a common revision plan with included guidelines and proposals will be elaborated, in order to ensure the interoperability of the systems within and across the SEE countries, with a special attention on the standardization issues of ITS systems architecture, following the respective European standards Aim of the report Text text text text text text text text text text text text text text text text text text text text text text text text Text text text text text text text text text text text text text text text text text text text text text text text text 1.3. Contents and structure of the document Text text text text text text text text text text text text text text text text text text text text text text text text Text text text text text text text text text text text text text text text text text text text text text text text text Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 6

8 2. OVERVIEW OF ITALY S ITS ARCHITECTURE 2.1. Background Promoting the development and dissemination of ITS at national level requires the definition of a strategic framework that establishes Guidelines in order to guarantee integration, interoperability and communication among different ITS applications. In this view during the 2001, the Ministry for Transport and Infrastructure launched the ARTIST project for the definition of a Telematic Italian Architecture for the Transport System. ARTIST project has its origin in the indications of the General Plan for Transport and Logistics /PGTL), and it aims to define the national reference framework for the deployment of telematics systems for Transport in Italy. The first part of the project ended in January 2003 with the realization of a Version 1 of the ARTIST architecture. ARTIST, starting from the needs of the users, defines: the services needed for the user functional, logics and physics relations among systems information flows organizational relations among different subjects (public and private bodies) that are involved in the development and management of ITS ARTIST allows identifying the actors involved and the strategies to be adopted for the processes of collection, elaboration and management of Information, that are basic processes for the operation of ITS systems. From ARTIST it is possible to obtain recommendations for new rules, technical and legal, in order to ensure that innovative solutions are feasible, suitable with those existing and able to catch the opportunities offered by the technological developments. The objective is to facilitate interoperability between modes of transport and telematics services at national and European level. ARTIST is the product of a structured development process which was attended by the most important national actors with interests in transport telematics. In the 2001 the Ministry of Infrastructure and Transport has selected, through an international tender, an operating unit that has been entrusted for "drawing" ARTIST. The project was overseen by a Steering Committee consisting of representatives of the Ministry of Infrastructure and Transport. For the project management and monitoring of the progress, the Steering Committee has been supported by a Technical Group. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 7

9 The various development stages of the project have been validated by a Consultative Group consisting of representatives of the major national public and private organization of the transport sector. Parts of the Consultative Group are: the Ministry of Infrastructure and Transport and the Ministry of Interior the user associations trade associations local authorities (municipalities, provinces, regions) companies of the Local Public Transport mobility agencies operators of the transport infrastructure managers of mobility services vehicle manufacturers universities and research Institutes policy bodies logistics companies components manufacturers service companies consulting companies The Italian Telematics Architecture for the Transport System consists of three different architectures: 1 - Logical Architecture: the reference logical architecture is described through a structure in which are specify multiple levels of detail: The highest level is represented by the Process (also called Functional Area) understood as ITS service provided The process is divided into logical functionality that are called functions Each function, depending on its complexity, can be divided into several other features of the lower level, named sub-functions. The interaction between the logical architecture elements (processes, functions and sub-functions) is made through an exchange of data flows which are referred to as messages (input, output or consultation). 2 - Physical Architecture: the physical architecture is the allocation of the functionalities defined in the logical architecture on the different nodes involved, highlighting also the interfaces between them and proposing standard communications. 3 - Organizational Architecture: it represent, from an organization/business point of view, the functionalities described in the Logical Architecture, with the aim to define roles, Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 8

10 responsibilities and levers necessary for a proper provision of services based on the features described. The methodology adopted for the definition of the reference organizational structure is based on the "value chain". The architecture is described by: a macro-process or value chain roles flow of roles/activities responsibilities and levers The logical (or functional) architecture is formed by hierarchical trees of functions and data flows between them, the limitation of this structure consists in the lack of a transversal perspective that allows a vision of the functions also in view of the models organizational functions that translate into services, also the flow of information is not easily represented in standard languages (UML/XML). Overcoming this limitation is the specific objective of this work. Adopting a method of analysis of the functional type, and a representation of objects (methodology already adopted by ACTIF), would make it easier to consult and to update the documentation. In addition, the definition of talking codes, able to correlate the classes and objects of the Italian architecture as has been done in ACTIF, will ensure the exchange in the international level and specifically European Components of Italy s national ITS architecture The ARTIST Architecture is composed of seven main elements. This structure reflects the stages in which the project was elaborated and that led to the definition of the Version 1 of ARTIST Analysis of the current deployment of ITS The analysis is a first basic step that led to the design of ARTIST. It is a general survey on transport telematics: it consists of a broad overview, on national and international level, which describes the present situation on systems, services and standards that are already in use and their developments. The survey takes into account the initiatives similar to ARTIST, launched in Europe and not (KAREN, FRAME-NET, ACTIF, American ITS Architecture, etc..). Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 9

11 Figure 1: European Framework Architecture In the European context, the project of the Italian architecture is part of the initiatives for realization of national and local architectures, arising from the reference European architecture (KAREN - FRAME), with which it intends to maintain compatibility. The Italian project relates with other activities in the sector at international level, as shown in figure 1. The project has registered its association with FRAME-NET thematic network with which it is in constant contact, has also established a working relationship with the French initiative ACTIF, in order to obtain a fruitful exchange of results and constantly monitors the situation international initiatives and emerging developments in this sector. Public and Private Operators International activ. ITS Arch (US, JP,..) Standardization bodies (UNI-CEI) Reasearch projects (EU) Thematic netw. Euro-regional projects National Architecture - Italy National projects EU projects Figure 2: Italian Architecture in the international context Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 10

12 User needs and services The User Requirements represent the decisive part of the project in which are defined needs, priorities and points of view. They are, in practice, the list of objectives that the National Architecture should meet. These Objectives represent the real reason for which the architecture is born and are the minimum set of requirements (in terms of services required) to which ARTIST should provide a solution. The User Requirements, identified prior to the development of the Architecture, therefore constitute the cornerstone for all its subsequent development. User Requirements are classified as follow: General Requirements o Architecture Features o Interoperability o Adaptability o Constraints o Continuity o Costs/Benefits o Expandability o Maintainability o Quality of Data o Robustness o Security o Safety/Protection o Ease of use o Special Requirements Planning And Infrastructure o Support for transportation planning o Management of infrastructure maintenance Laws And Regulations o Application of laws and regulations on traffic and transport Electronic Payment And Financial Transactions o Electronic financial transactions o Management of transportation/transit titles Emergency o Emergency Messages o Reporting Alert o Management of stolen vehicles o Management of emergency vehicles o Dangerous goods and road accident management Information Users o Pre-travel information o Information during the journey o Warning of dangers Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 11

13 o Infrastructure Management o Sustaining Economic Growth o Demand Management o Social Services Traffic Management o Traffic Management o Road accident Management o Demand Management Driver Assistance o General requirements for driver assistance o Increased visibility o Speed Matrix o Improvements in safety o Longitudinal Anti-collision o Side Anti-collision o Platoons / Trains of Vehicles Goods And Commercial Vehicle Fleet o Control commercial vehicles o Administrative procedures for commercial vehicles o Automated surveillance security vehicle at the roadside o Monitoring of security on board commercial vehicles o Management of commercial fleets o Management traffic and at intermodal centres o Management of fleets of road vehicles o Management of vehicle, driver, equipment and load o Cargo delivery o Intermodal Interface Fleet Of Public Passenger Vehicles o Management of public transport o On call Public transportation o Management of shared transport o Information on public transport during the trip o Safety for public transport Multimodal Logistics Chain o Control and management of intermodal traffic at the interchange nodes o Transport and Logistics chain of goods o Control and management of the intermodal nodes o Management of dangerous goods in intermodal nodes Logical Architecture (or Functional) The services identified by User Needs and Services are necessarily delivered through processes, functionalities and data flows: these processes, functionality and data flows are formalized at a high level by the Logical Architecture. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 12

14 The logical architecture has been defined after the verification and extension of the ACTIF and FRAME projects, and therefore inherits the methodology adopted by the pillar project KAREN. It is a "Process-Oriented" methodology which describes the reference Logical Architecture through a structure in which more levels of detail are defined: The highest level of aggregation is represented by the Functional Area (also named Scope or Process) intended as a delivered ITS service. Each area contains features called logical functions (which, depending on the complexity, break down into a tree of other features more detailed) and, in some cases, includes Database. External relations are represented by the Terminators, which represent a set of systems, variables, databases external from the area of expertise. The interaction between logical architecture elements (Areas, Functions, Database and Terminators) is done through an exchange of data flows, also considered as messages (input, output or consultation) Physical Architecture The physical architecture suggests hypotheses about grouping and allocating the different features described by the Logical Architecture, so as to form a system that can physically be implemented. In addition to describing the methodology to be applied in the design of the physical schema, provides also a set of schemes. The Architectural Diagram it is drawn using the symbols in figure 3. ARTIST then defines reference models of Physic Architectures for some priority fields: 1. Provide Electronic Payment Facilities (figure 4) 2. Provide Traveller Journey Assistance 3. Manage Freight & Fleet Operations Moreover, it provides a brief overview of the technologies used in the context of ITS, divided with respect to the following matters: cartographic databases and GIS automatic Identification automatic location traffic data collection and classification fixed networks mobile networks electronic data interchange EDI The original source of this list is - UNI-CEI Appendix to the standard UNI-CEI standard framework - Overview of applications, references and legislative guidelines. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 13

15 Activity or Service Provided (functions and sub-functions) Terminators directly involved (senders and receivers) Database of interest for the scope Message: that could be of consultative, or an event i.e. launch a particular service Physical node in which are localized the functions indicated in the diagram Interface between nodes, to which are associated the involved technologies Figure 3: Symbols for Architectural Diagram Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 14

16 Figure 4: Provide Electronic Payments Facilities - Physic Architecture Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 15

17 Organizational Architecture The Organisational Architecture is, compared to cross-border experiences, a peculiarity Italian Architecture. The Organisational Architecture aims to highlight those specific organizational aspects, and related business models - that can actually realize the payable services as the defined by the Logical Architecture at a functional level. Often, under this point of view services are welldesigned, then do not find effective application in the business world, since the organizational models adopted are not equally valid. In addition to suggesting a methodology for the design of the organizational model of a system, the Organisational Architecture provides some examples of application of the proposed method. The methodology adopted is based on the identification of the sequence (chain) of processes / functions, tools (methodology, technical solutions) and activities geared to the production of a result (in this case a service) (functional view of the service). The service is not guaranteed by the mere implementation of processes / functions, which can ensure the effectiveness, but must be supported by a business analysis focused on efficiency. For this reason we proceed to the analysis of value along the chain, in other words for each process chain, it is necessary to identify the levers that allow you to create value by increasing service efficiency and reducing the costs of the process (business service Vision). Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 16

18 Context Diagram Logical Architect. Std Scope Physic Architect. Organiz. Architect. Role Function Site Interface Link onemany Terminator Messages Figure 5: ARTIST architecture Navigation tool To allow the use of ARTIST by the widest range of users possible, we created a computerized tool to navigate interactively within Architecture. The tool fulfils the dual purpose of: 1. provide the support necessary to implement the architecture and dealing with future updates 2. facilitate navigation within the architecture itself by a user wishing to access, retrieve information and documents, rather than actively interact with it So you must implement two different support tools that have the characteristics necessary to meet the required targets and different features: 1. Support for the Creation / Management; 2. Support Consultation / navigation. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 17

19 Architecture Database Architecture Database Architecture Database Continuous link Not Continuous link Figure 6: Navigation tool framework Glossary Collects the words commonly used in the ITS. The glossary is defined reference for the entire project ARTIST. The glossary is integrated into the navigation tool made for version 1 of the software Mega ARTIST. The construction of the glossary is the result of a costly and careful integration of contributions coming from different sources (listed in the source field of the table Glossary), both inside the unit operates both from outside and between them we can mention: [KNET] [FV2000] progetto FV 2000 [GLSA_ATT] sorgente interna [ITSGLOSS] [SIEMENS] [IMAGE] progetto IMAGE Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 18

20 3. ARCHITECTURE IMPLEMENTATION 3.1. Case 1: e-call The project aims to define a plan for the integrated management of emergency calls on the national territory, in accordance with the work done as part of ARTIST. The pilot project will analyze in detail the management of emergencies related to the environment and vehicle caused by an accident, driver illness, robbery and fire. In accordance with the European directive that aims to establish a free Europe-wide single number for emergency calls, the work done in the project led to the creation of a center for access to the service, called PSAP (Public Safety Access Point). The functions defined in the ARTIST architecture and involved in this service are: Acquire Mayday Call on Roadside; Manage Emergency Intervention; Manage Emergency Vehicle; Provide Emergency Control on the Operator; Provide Access and Maintain Data for Emergency Provide Traffic Control; Manage Incidents; Monitor PT Fleet; Integrate Vehicle in Traffic System. The functions listed above, that in the case of use of the organizational architecture represent activities to be done in order to provide the service, can be grouped according to a set of attributes that characterize it: Professional skills required; Involved systems; Data needed; Interaction with other features. Group 1 (SP): Acquire Mayday Call on Roadside; Integrate Vehicle in Traffic System; Group 2 (PSAP): Acquire Mayday Call on Roadside; Manage Emergency Intervention; Manage Emergency Vehicle; Provide Emergency Control on the Operator; Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 19

21 Provide Access and Maintain Data for Emergency; Group 3 (External Agencies): Manage Notification Stolen vehicle; Provide Traffic Control; Manage Incidents; Monitor PT Fleet; Figure 7: e-call architecture From what has been said so far follows the flow of activities with the roles allocation, as represented in MEGA, necessary to provide the service. In particular, in the columns are represented the roles identified for the service under consideration, and represented in MEGA by the object "actor" preceded by the prefix "R-". Also note that, in case of transversal view, i.e. special analysis involving equally several scope of the architecture, all existing flows follow a nomenclature composed by the prefix "VT_" (which stands for "transverse view"), together with the "name transversal view" (vtec_ = indicates the E-Calls transversal view ) followed by the "acronym of the message". The adoption of the organizational model shown, in agreement with the findings by the working group of the pilot project, meets difficulties related to the absence of legislation defining individual roles and that gives them the right levers to operate. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 20

22 Figure 8: e-call organizational architecture Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 21

23 3.2. Case 2: STRIM-TP The project STRIM-TP (Regional Integrated Electronic System for Monitoring of Public Transport) aims to a better management of the Local Public Transport Service. Telematic technologies for transport (ITS) make available to the actors of the system a series of high value services, useful for: 1. monitor the service provided, by providing quantitative data useful to the realization of exercise programs in the planning stages; 2. collect data on the service provided by correlating the scheduled service, in order to enhance quality indicators useful for monitoring compliance with the minimum quality standards defined in the service contracts; 3. provide users of the TPL information on integrated mobility on the territory updated in real time. Figure 9: STRIM-TP organizational architecture 3.3. Problems encountered From a careful analysis of the documents produced and made available by individual projects, emerges the lack of a functional architecture structured ARTIST. This gap is revealed by the impossibility to apply the methodology devised for the preparation of the organizational architecture of the priority areas indicated by PGTL. Not be able to adopt this method makes it more difficult to find architectural consistency and for this reason the proposal from an organizational architecture, which can t be based on an Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 22

24 structured logical architecture as the Italian architecture of reference, should be considered as an example application with no claim to absoluteness both as regards contents and logical consistency- functional. The pilot project "E- Calls" at present provides functional specifications and organizational guidelines necessary for the proper execution of organizational analysis, as shown by the deliverables produced by the project, and in particular by deliverable D6i.1, D6v.1, D7i.1 and D7v.1. Case 1 The adoption of the organizational model shown, in agreement with the findings by the working group of the pilot project, meets difficulties related to the absence of legislation defining individual roles and that gives them the right levers to operate. It highlights the need for a high degree of integration of telematic systems of different entities of public safety and emergency for the operation of the service. Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 23

25 4. CONCLUSIONS 4.1. Actions towards interoperability The Ministry of Infrastructure and Transport in 2003 published the Italian Telematics Architecture for the Transport System (ARTIST) to fix guidelines to ensure that ITS applications could be compatible, integrated and interoperable with each other and consistent with the European Architecture KAREN, albeit complex practical application. The lack of common specifications and shared procedures has slowed the market for systems and services and increased a high fragmentation of the applications. The National Architecture ARTIST was a first important step in this direction. It is a clear priority carrying out a revisions and updates of the National Architecture to make it more usable by users, as well as promoting the dissemination and training activities Final concluding remarks A lack of coordination and organization emerges from the Italian situation, and this seems true not only speaking about ARTIST but also with reference to the whole sector of ITS in Italy. The ARTIST architecture has not been successfully disseminated and then not all the projects and initiatives are interoperable and based on ARTIST. At the same time some problems seem to characterize the initial version that now has to be revised and updated. Some action can be done in order to overcome these difficulties. a) Creating a board of coordination only for ITS It would be appropriate to set up a coordination table bringing together the various ministries with expertise in various fields of application of ITS (Ministry of Infrastructure, Ministry of Transport, Ministry of Environment, Ministry of Regional Affairs, Ministry of the Interior, the Ministry of Innovation, Ministry of Economy, Ministry of Communications, Ministry of Economic Development and the Ministry of Research), and representatives of the associations of local authorities (municipalities, provinces and regions). The overall coordination of this common table should be entrusted to the Ministry of Transport, in order to ensure the necessary interaction with the management committees of Architecture National ARTIST. b) Establishment of a Technical Secretariat to support the Ministry of Transport to promote the use of ARTIST Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 24

26 The application of ARTIST Architecture to different contexts is crucial to achieve a truly integrated transport network with the ITS. To promote the knowledge and application of ARTIST is therefore an urgent necessity to promote the full development of ITS in Italy, in order to enhance the market for systems and services in the short term. With the aim to accelerate the process of diffusion the national architecture, could be considered an opportunity to delegate the management and dissemination of ARTIST to a technical support to the Ministry of Transport, which is controlled by the Ministry itself but external to it. This should take the form of a "technical secretariat", to which should be delegated some actions: ARTIST's dissemination to an audience as wide as possible communication of the results of the activities of national and/or local made on the basis of ARTIST (e.g. projects financed with funds PON) maintenance and updating of the website ARTIST with later versions, that will be carried out by an external body through special tender, technical and financial support to local governments and to the managing bodies of the services and infrastructure, for the application of ARTIST in different contexts; training of technicians and experts in the field who will have to implement the ITS Architecture schemes, in close collaboration with the university. c) Provision of financing instruments A central coordination responsible for allocating funds to public administrations plays a fundamental role to ensure, through the use of tools such as ARTIST, that investments go to the latest ITS technologies and interoperable solutions to national and European level. d) Stimulate the use of ARTIST The Ministry of Transport should consider the possibility of developing some sort of certification ARTIST for ITS applications premises. This could be an interesting incentive for local governments to adopt systems only compatible with ARTIST (for example in notices compatibility with ARTIST should be identified as a matter of preference). Deliverable D4.3.7: Guidelines/proposals for the revision of ITS architecture in Italy 25