Deliverable D4.3.6: Guidelines and proposals for the revision of ITS architecture in Slovenia. Robert Rijavec, Darja Šemrov

Transcription

1 Deliverable D4.3.6: Guidelines and proposals for the revision of ITS architecture in Slovenia Robert Rijavec, Darja Šemrov October, 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 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.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 1

3 DOCUMENT PROFILE Document status: Deliverable code: Deliverable title: Final version D4.3.6 Guidelines and proposals for the revision of ITS architecture in Slovenia Work Package: 4 Preparation date: 20/12/2013 Submission date: 01/04/2014 Total pages: 36 Dissemination level: Public Authors: Robert Rijavec, Darja Šemrov Contributors: Evangelos Mitsakis, Maria Chatziathanasiou, Panagiotis Iordanopoulos Abstract: The current document presents the status of the Slovenian 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.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 2

4 EXECUTIVE SUMMARY The goal of this project report is to present the existing status of ITS architecture in Slovenia. SITSA-C, Slovenian ITS Architecture, module Roads (Ceste), represents a proposed concept for the designing, planning and integration of ITS in Republic of Slovenia. In Slovenia Traffic management subsystem was successfully implemented, but other subsystems not due to lack of promotion and reorganisation of stakeholders. In this report the components and the methodology of SITSA-C are presented. SITSA-C defined physical subsystems and modules with specific functionalities. The list of subsystems, algorithm for accessing the process of elaborating physical ITS architecture aspect, the logicalfunctional processes and inter-relations between individual components and communication viewpoints are presented in this report. In this report also an example of practical implementation of SITSA-C subsystems and their function, data stores, parallel systems, organisational aspect of included subsystems and encountered problems are demonstrated in case of NCUP - National Traffic Management Centre. NCUP is set up according to appropriate national legislation. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 3

5 CONTENTS 1. Introduction Short outline of SEE-ITS project Aim of the report Contents and structure of the document 7 2. Overview of Slovenian ITS Architecture Background Components of Slovenian national ITS architecture Approaches and Methodology User needs and services Context Diagram Logical Architecture (or Functional Viewpoint) Communications Viewpoint Architecture implementation Case 1: NCUP - National Traffic Management Centre NCUP Subsystems and Their Data Stores Other Technological/Parallel Systems Organisational aspect of Subsystems included in NCUP Problems encountered Conclusions Actions towards interoperability Final concluding remarks 36 LIST OF TABLES Table 1: Existing and planned ITS in road transport 14 Table 2: SITSA-C data stores - road transportation 32 LIST OF FIGURES Figure 1: SITSA-C: Methodology and approach 11 Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 4

6 Figure 2: Algorithm of using FRAME Selection Tool for the SITSA-C development 12 Figure 3: Physical ITS Subsystems Categories Diagram 17 Figure 4: Functional diagram of Providing electronic payment area 24 Figure 5: Functional diagram of Provide Safety And Emergency Facilities area 25 Figure 6: Functional diagram of Manage Traffic area 25 Figure 7: Functional diagram of Manage PT Operations area 25 Figure 8: Functional diagram of Advanced Driver Assistance System area 26 Figure 9: Functional diagram of Provide Support For Law Enforcement area 26 Figure 10: Functional diagram of Traveler Journey Assistance area 27 Figure 11: Functional diagram of Manage Freight and Fleet Operations area 28 Figure 12: Integration of NCUP components 30 ANNEXES Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 5

7 ABBREVIATIONS AND TERMINOLOGY CUJPP CUVP DARS DRSC FCD GCNVP ITS NCUP PIC SITSA-C TERN Public Transport Management Centre Traffic management and control centre for other national roads Motorway Company in the Republic of Slovenia Slovenian Roads Agency Floating Car Data Main motorway Traffic Control Centre (in Slovenia) Intelligent Transport Systems and Services National road traffic management centre (in Slovenia) Traffic Information Centre for Public Roads (in Slovenia) Slovenian national ITS architecture, module Roads Trans European Road Network Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 6

8 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 The purpose of this report is to present the status of the existing ITS architecture in Slovenia, including the problems of its application by giving the critical assessment. This report describes the first version of Slovenian national ITS architecture (SITSA-C) with explanation why it is needed and for what propose to use it. This report also gives the methodology which was used during the preparation of the first version and which can be used for the next steps e.g. the revision of it. Managing national ITS architecture is a process which must be upgraded time to time. The first version of SITSA-C was prepared five years ago in year 2008 and there is the need for its revision Contents and structure of the document Contents and structure of the document is formatted as the SITSA-C documentation. The results of SITSA-C project (version 1.1) are documented in electronic documents and are accessible on web page in the hypertext form (navigation through documents in Slovene and FRAME architecture pseudo language): SITSA C: Guide through the project Outline scheme of ITS in road traffic - presents a guide through SITSA-C as a whole. SITSA-C: Current development of intelligent transport systems and services (ITS) - presents a detailed report on the current development (state of the art) related to ITS on the EU level and on the level of Slovenia until SITSA-C: ITS user needs in Slovenia, version presents the results of collecting the SITSA-C user needs, important for the development of the ITS architecture. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 7

9 SITSA-C: Functional architecture - the document defines the components of the ITS architecture in a road traffic (functional areas, functions, data storages, terminators, data flows). It describes the logical-functional processes and presents inter-relations between individual components. SITSA-C: Physical architecture - it deals with physical units or subsystems with their functions described in the document Functional architecture and ITS user needs in Slovenia. The document deals with physical data flows connecting functions, data storages, terminators and physical subsystems into an integrated ITS, version 1.1 in Slovenia. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 8

10 2. OVERVIEW OF SLOVENIAN ITS ARCHITECTURE 2.1. Background Traffic analyses carried out in years indicated that the road transport in Slovenia will increase significantly, mainly on the motorway network. Such increase of traffic would have additional negative impact on traffic flows and level of services, due to inadequate traffic control, inadequate traffic and road information service provider system and inadequate coordination of activities in traffic informatics (international exchange of data and information on traffic conditions). Being aware of these problems, a decade ago the Slovenia initiated faster development and introduction of ITS on the Trans European Road Network (TERN), on parallel road connections and on border crossings, together with implementation of National Motorway Construction Programme. In order to solve the above mentioned problems, a proposal for first version Slovenian ITS framework architecture for road traffic on national level has been prepared. SITSA-C, Slovenian ITS Architecture, module Roads (Ceste), represents a uniform concept for the designing, planning and integration of ITS in Republic of Slovenia. When defining the national framework of the ITS architecture, ITS should not be neglected, either on the national or the international level. This applies for systems, services and standards already disseminated and used in today's practice, on the level of contemporary initiatives, as well as for the plans for the future (strategies). Traffic management system on Slovenian motorways, as part of ITS in road transportation, has already been introduced in It has hierarchical structure and is divided in four levels. At the highest level is the Main motorway traffic control centre (GCNVP), which is still in the stage of setting-up (concessioner is Motorway Company in the Republic of Slovenia - DARS d.d.). On the other hand, the Traffic management and control centre for other national roads (CUVP) has already been framed (under the jurisdiction of Slovenian Roads Agency - DRSC) but its organisational viewpoint has never been defined. The CUVP (in implementation) will be situated on the same place and in the same control room as GCNVP. Slovenia set up the National road traffic management centre (NCUP), which is based on a specific system design which is part of SITSA-C. The introduction of ITS architecture in the NCUP represents the groundwork for improved control and management of road traffic, information service provider system for the public on traffic and road conditions or on any other traffic infrastructure, as well as for the coordination of ITS infrastructure management. On the other hand both main road managers established common Traffic Information Centre for Public Roads (PIC) in 2006, which distribute the traffic information on road and traffic conditions reported by the DARS d.d. and DRSC. Other modes are not included. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 9

11 NCUP in formation cover public road network in Slovenia, i.e. all state roads and strategically important local roads. The task of NCUP is to collect, analyse and provide traffic-travelling information to the users, as well as to manage traffic in real-time on strategic level, what is one step further than PIC. The real-time and off-line data on traffic flows, special events, incidents and weather conditions are collected by external subsystems (e.g. regional centres or field teams or sensors). The database also includes information provided by the police, various contractual co-workers, road maintenance personnel and other road traffic participants. It will be strategically connected to similar centres abroad, and will have especially close links to traffic management centres in the neighbouring countries and to centres managing traffic on lower levels (region, community). We could say the Traffic Management subsystem was successfully implemented according to SITSA-C. SITSA-C defined also other subsystems, which unfortunately were not deployed and developed due to lack of promotion and reorganisation of stakeholders Components of Slovenian national ITS architecture SITSA-C represents profound knowledge of road transport system functioning in the sense that it prepares innovative proposals that are in agreement with the current conditions in Slovenia, but are not binding for their further development. Why only roads? Problems in the road sector were and are still priority. SITSA-C does not impose rules and does not include the existing systems; it does not give any binding indications how to choose solutions, nor does it propose any technologies. But it offers: Basic capacities that must be included in the planning phase and/or in the implementation phase with the intention to make sure that the ITS satisfie the basic features foreseen for ITS in Slovenia. Description of functional and logical special features for the national structure to exchange information between different transport systems (traffic means) and the participating users, and the description of interfaces that allow the system to be included in the network, in some cases by using the existing technologies. Main guidelines and common terminology to define systems and services in Slovenian language. Offers the indications regarding users and basic features, their importance and priorities in Slovenia (from 2004). Guide to standards and requirements (specifications) that the systems and services in Slovenia should satisfy. The goal of SITSA-C was also to define and describe an aggregate of functions and services as support to the road transport system in the area of Slovenia Approaches and Methodology Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 10

12 In order to define the approach and consequently also the selection of the methodology for the national ITS framework architecture, approaches and methodologies used previously by colleagues in the framework of ARTIST (Italy) and ACTIF (France) projects as well as the projects FRAME, ITS America and TeamProject from the Czech Republic, were analysed. SITSA-C: Methodology and approach 1. List of user needs, SITSA-C: user needs, version Identification of functions (functional architecture) satisfying the user needs, version Definition of physical units subsystems and modules: o operative/ functional and organisational homogeneity o optimisation of information exchange flows considering current development o operative efficiency 4. Locating physical units locations 5. Identification of data flows connecting elements of functional architecture and physical subsystems and modules into integrated ITS in road traffic (proposal) 6. Presentation of physical data flows, version 1.1 Figure 1: SITSA-C: Methodology and approach In the SITSA-C project (version 1.1, depending on the priority of user needs) it has been decided to define physical subsystems and modules. Each subsystem or module has specific position regarding its location (e.g. Vehicle, Infrastructure, different traffic management centres such as CUJPP public transport management centre). Subsystems and modules have specific functionalities, i.e., functions and data storages are defined. The physical data flows based on functional data flows run among subsystems, modules and terminators/actors. The scheme in Figure 1 presents the methodology used in the framework of SITSA-C. The methodology consists of two stages: general and contextual. The first stage is a precondition for the preparation of the ITS architecture based on user needs. The second stage is specific and depends on each case individually. The proposal of the SITSA-C workgroup is to minimise cases into a uniform context. This was the main reason why this approach was used. For the design of the physical viewpoint of the ITS architecture the FRAME Selection Tool software was used. It is a part of the program environment FRAME Navigation Tool and was designed to allow the formation of subgroups of the European reference ITS architecture. The tool is available on the FRAME Architecture web page 1 and is free for use. The FRAME Selection Tool, and especially its data storage, has been adapted to the Slovenian needs with the permission of the FRAME-NET project group. The data storage is carried out in Microsoft Access format. With the help of the FRAME Selection Tool the first version (version 1.1) of the outline scheme of ITS in road traffic was designed, i.e. functional as well as physical viewpoint at the national level. Figure 2 presents the algorithm for accessing the process of elaborating physical aspect of the ITS architecture, which was used by SITSA-C project. 1 The FRAME Architecture web page: ( ) Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 11

13 Based on the physical viewpoint of the ITS architecture, the communication needs of the System can be defined. In the framework of the project only the type and sort of data are defined. In order to consider the communication viewpoint of the ITS architecture, the following still needs to be defined: physical principle of data transfer, safety specifications (protection) and necessary capacity for the data transfer, which is, regarding such fast development of telecommunications, on the national level almost impossible. List of user needs, SITSA-C: user needs, version 1.0 Identification of functions satisfying the user needs version 1.1. Functional architecture Modules Transfer functions and data storage in subsystem (locations) Identify the functional data flow between subsystems and the data flow of terminators between subsystems and terminators transfer into physical data flow Transfer functions and data storage in mudules inside subsystems Divide physical data flow into consistent physical data flow according to needs Physical architecture»subsystems, modules«identify functional data flow between modules transfer into physical data flow Communication architecture Organisation architecture Figure 2: Algorithm of using FRAME Selection Tool for the SITSA-C development Regarding the functional and physical (and communication) viewpoint of ITS architecture the allocation of physical units is prepared: subsystems and modules for individual organisations (subjects) in the system who will manage them. This distribution is called organisational ITS architecture. Fortunately, in Slovenian regulation ITS are defined from day to day better Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 12

14 and the area of organisation has more attention for future development of the national ITS. The promotion of ITS has also more attention, while ITS is a part of EU priorities User needs and services SITSA-C user needs of ITS in Slovenia presents the results of collecting the SITSA-C user needs, important for the development of the ITS architecture from the year The method of stakeholder s interviews was used. Almost 50 Slovenian organisations were involved in the research of user needs. The purpose of the questionnaire was to obtain information at a high level, which allows the distribution of the respondent (whether companies, legal entities, etc.) in the field of ITS. The purpose of the questionnaire was to identify the existing ITS and plan the deployment of ITS for the next 5 or 10 years. Table 1 shows the synthesis of the results through the "A" labelled systems and services that are current today and "P" if they are provided or planned for the next 10 years. It is also possible combination of "A/P" as the upgrading of existing ITS. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 13

15 Table 1: Existing and planned ITS in road transport Ref. number. Its systems and services Transport service providers Local governmental authorities Public entities or supervising authorities Infrastructure managers/operators Technology solution providers Associations, Research entities or universities 2 Management Activities 2.1 Transportation Planning Support A A P A P A/P A A A/P A 2.2 Infrastructure Maintenance Management A/P A/P A A/P A 3 Policing/Enforcing A A P 3.1 Policing/Enforcing Traffic Regulations A/P A A A/P A/P 4 Financial Transactions A A 4.1 Electronic Financial Transactions A/P A A A/P 4.2 Transport documents management A/P P P 5 Emergency Services A 5.1 Emergency Notification and Personal Security A/P A A A 5.2 Emergency Vehicle Management A A A A A 5.3 Hazardous Materials & Incident Notification 6 Travel Information A/P A A A A A A A 6.1 Pre-trip Information A/P A A A/P 6.2 On-trip Information P A A P 7 Traffic Management A P 7.1 Traffic Control A/P P A A A/P 7.2 Incident Management A/P P A A A/P A/P 7.3 Demand Management A/P A A/P Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 14

16 Ref. number. Its systems and services Transport service providers Local governmental authorities Public entities or supervising authorities Infrastructure managers/operators Technology solution providers Associations, Research entities or universities 7.4 Safety Enhancements for Vulnerable Road Users A/P A P A/P 7.5 Intelligent crossing and intersections A A A/P A/P 8 Intelligent Vehicle Systems P 8.1 Vision Enhancement A P 8.2 Automated Vehicle Operation A/P P 8.5 Safety Readiness P P Data about drive (»Black-box«) P P 8.6 Pre-crash Restraint Deployment A/P P A 9 Freight and Fleet Operations P 9.1 Commercial Vehicle Pre-clearance 9.2 Commercial Vehicle Administrative Processes 9.3 Automated Roadside Safety Inspection 9.4 Commercial Vehicle On-board Safety Monitoring 9.5 Commercial Fleet Management A/P A P A P A P A P A P A/P P P A/P A/P P P 9.6 Multimodal transport management A/P P P 10 Public Transport P 10.1 Public Transport Management A P P 10.2 Demand Responsive Public Transport P A/P 10.3 Shared Transport Management P 10.4 On-trip Public Transport Information A/P P Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 15

17 Ref. number. Its systems and services Transport service providers Local governmental authorities Public entities or supervising authorities Infrastructure managers/operators Technology solution providers Associations, Research entities or universities 10.5 Public Travel Security A A/P P Context Diagram Figure 3 presents the list of subsystems defined in the architecture, connected to each other. It defines also the physical location of the individual systems. Different centres for subsystem and services implementation were introduced: NCUP National Traffic Management Centre, CUP_mesto Urban Traffic Management Centre, CU_JPP Public Transport Management Centre, CU_cestnina Tolling Administration Centre, CORS Emergency and notification Centre, Police, CUN Police and Tolling control Centre. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 16

18 NCUP CUP_mesto CU_JPP CU_cestnina NCUP CUP_mesto NCUP NCUP CORS NCUP NCUP CENTRE Maintenence Management System Parking Management System Public Transport Management System Toll Administration System Inter-city Traffic Management System Urban Traffic Management System Travel Coordination System Archived Data Management System Emergency Management System Commercial Vehicle Administration System Freight Management System INFRASTRUCTURE Roadway System Parking Management System Toll Collection System Commercial Vehicle Check System FRAME architecture SITSA-C SLOVENIA VEHICLE Commercial Vehicle System Emergency Vehicle System Freight Equipment System Maintenence Vehicle System Public Transport Vehicle System Personal Vehicle System TRAVELER Personal Device System Kiosk Systems NCUP Police, CUN Information Service Provider System Law Enforcement System Figure 3: Physical ITS Subsystems Categories Diagram For each subsystem functional areas, functions, data storages, terminators and data flows are described. The logical-functional processes are described and inter-relations between individual components are presented. The definitions are the same as were introduced in FRAME ITS architecture. The functions and data stores by individual subsystems are presented below. Maintenance Management System Evaluate Short Term Maintenance Needs Evaluate Long Term Maintenance Needs Evaluate Equipment Maintenance Needs Evaluate De-icing Need Provide Operator Maintenance Operations Interface Manage Maintenance Data Store Data stores Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 17

19 D3.6 Maintenance Data Store Parking Management System Monitor Urban Car Park Occupation Data stores - Public Transport Management System Confer to Vehicles Control Vehicle Driving. Data stores D4.1 Real Time PT Vehicle Status D4.2 Historical PT Vehicle Data D4.3 PT Service Plan D4.4 PT Route Static Data Toll Administration System Create EP Contract Establish Contract Statistics Manage Service Data Load User's Account Debit User's Account Inform Users on Transactions Distribute Fees Revenue Credit Operator's Account Inform Operators on Transactions Manage Tariffs Manage Access Rights Data stores D1.5 Tariffs Store D1.1 EP Contracts Store D1.2 User's Account Store D1.4 Transactions Store D1.3 Service Information Store D1.6 Fraud Store D1.7 Access Rights Store Inter-city Traffic Management System Monitor Service Area Vehicle Occupation Provide Inter-urban Traffic Forecasts and Strategies Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 18

20 Manage Inter-urban Traffic Data Provide Inter-urban Traffic Management Provide Planned Inter-urban Traffic Management Facilities Provide Service Area Vehicle Occupancy States Provide Inter-urban Traffic Speed Management Provide Inter-urban Output Actuation Provide Inter-urban Lane Management Provide Operator Inter-urban Traffic Management Facilities Manage Inter-urban Static Traffic Data Assess Bridge Status Assess Tunnel Status Provide Bridge and Tunnel Operator Interface Output Tunnel Information Identify and Classify Incidents Assess Incidents and Determine Responses Manage Incident Data Provide Incident Management Operator Interface Predict Environmental Conditions Provide Environmental Conditions Operator Interface Data Stores D3.2 Inter-urban Traffic Data Store D3.8 Inter-urban Road Static Data Store Urban Traffic Management System Provide Urban Traffic Forecasts and Strategies Manage Urban Traffic Data Provide Urban Traffic Management Provide Planned Urban Traffic Management Facilities Provide Urban Car Park States Provide Urban Traffic Speed Management Provide Urban Output Actuation Provide Urban Traffic Lane Management Provide Operator Urban Traffic Management Facilities Detect Urban Traffic Violations Manage Urban Static Traffic Data Data Stores D3.1 Urban Traffic Data Store D3.7 Urban Road Static Data Store Travel Coordination System Receive Information on Travel Factors Implement Demand Management Strategy Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 19

21 3.3.3 Develop Demand Management Strategy Manage Demand Data Store Provide Demand Management Operator Interface Data Stores D3.3 Environmental Data Store D3.4 Incident Data Store D3.5 Demand Data Store Archived Data Management System : 9.1 Search archive 9.2 Process archive 9.3 Manage Archive Access Data Stores - Commercial Vehicle Administration System Prepare and Deliver Operational Transport Document Prepare/Process information to/from board Manage Incident Evaluate Transport Conditions Evaluate and Record Safety Status Manage Vehicle and Equipment Data stores D8.2 Resources data store Emergency Management System Acquire Mayday Call on Roadside Identify and Classify Emergencies Manage Incident and Emergency Information Plan Emergency Intervention Process Emergency Progress Reports Provide Emergency Control to the Operator Provide Access and Maintain Data for Emergency Data stores D2.2 Incident And Emergency Data Store Freight Management System Negotiate Principal Requests Administrate Freight Transactions Data Stores Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 20

22 - Information Service Provider System Inform Traveller Assess the need for Trip Plan Changes Provide Trip Planning Interface Plan Traveller Trip Collect Road Traffic Data Collect PT Data Provide Emergency Services Routes Data stores D6.4 PT Trip Planning Data D6.3 Road Trip Planning Data D6.2 Private Trip File Law Enforcement System Perform Measure Check Compliance Analyse Image Determine Violator ID Sort Fraud Notifications Establish Prosecution File Manage Rules Manage Users' Registration 7.6 Store Violations Data Data Stores D7.3 Violations Store D7.2 Users Registration Store D7.1 Rules Store Commercial Vehicle System : Monitor Transport Order Monitor Operational Task Monitor Driver Monitor Vehicle Monitor Cargo Comply with Regulation Data Stores D8.3 On board database Emergency Vehicle System Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 21

23 : Manage Emergency Vehicle Data stores: - Freight Equipment System Monitor Equipment Data stores - Maintenance Vehicle System - Data stores - Public Transport Vehicle System Estimate Vehicle Indicators Predict Vehicle Indicators Plan & Schedule Services Manage Fare Schemes Provide Maintenance Co-ordination Manage Vehicle Sharing Monitor Infrastructure Optimise Control Action Require Vehicle Priority Manage Additional Vehicles Data stores - Personal Vehicle System Provide Mayday Call Provide Vehicle ID Data stores - Commercial Vehicle Check System - Data stores - Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 22

24 Toll Collection System Detect User Identify User Check User's Contract Inform and Guide User Compute Service Fee Check Advanced Payment Recover Fee Check User's rights Detect Payment Violations Detect Access violations Block Access Data stores - Parking Management System - Data stores - Roadway System Collect Urban Traffic Data Collect Inter-urban Traffic Data Detect Inter-urban Traffic Violations Detect Incidents Monitor Weather Conditions Monitor Noise Pollution Manage Environmental Conditions Data Data stores Logical Architecture (or Functional Viewpoint) Functional viewpoint of the SITSA-C (functional areas, functions, data storages, terminators, data flows) describes the logical-functional processes and presents inter-relations between individual components. Functional areas, which are defined in the context of SITSA-C include eight FRAME functional areas, to ensure compatibility and the ability to upgrade in terms of uniformity of European ITS architecture. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 23

25 Following functional areas are defined: 1. Provide Electronic Payment Facilities, 2. Provide Safety And Emergency Facilities, 3. Manage Traffic, 4. Manage Public Transport Operations, 5. Provide Advanced Driver Assistance System, 6. Provide Traveller Journey Assistance, 7. Provide Support For Law Enforcement, 8. Manage Freight And Fleet Operations. on the highest level for each functional area are presented in the figures below. that are part of the functional architecture SITSA-C, version 1.1 are yellow highlighted. 1. Zagotavljanje elektronskega plačevanja Provide Electronic Payment Facilities 1.6 Manage Tariffs and Access Rights 1.5 Access and Credit Control 1.1 Set up Contract 1.4 Manage Operators' Revenue 1.2 Manage User's Account 1.3 Perform Electronic Payment Transaction Manage Tariffs Detect Access violations Manage Service Data Distribute Fees Revenue Debit User's Account Check Advanced Payment Manage Access Rights Check User's rights Create EP Contract Credit Operator's Account Inform Users on Transactions Detect User Block Access Establish Contract Statistics Inform Operators on Transactions Load User's Account Recover Fee Detect Payment Violations Identify User Check User's Contract Inform and Guide User Compute Service Fee Figure 4: Functional diagram of Providing electronic payment area Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 24

26 2. Zagotavljanje zaščite, reševanja in pomoči Provide Safety and Emergency Facilities 2.1 Manage Emergencies 2.2 Manage stolen vehicle notification Acquire Mayday Call on Roadside Identify and Classify Emergencies Manage Incident and Emergency Information Plan Emergency Intervention Process Emergency Progress Reports Manage Emergency Vehicle Provide Emergency Control to the Operator Provide Access and Maintain Data for Emergency Figure 5: Functional diagram of Provide Safety And Emergency Facilities area 3. Upravljanje prometa Manage Traffic 3.5 Manage Road Maintenance 3.3 Manage Demand 3.1 Provide Traffic Control 3.4 Provide Environmental Information 3.2 Manage Incidents Figure 6: Functional diagram of Manage Traffic area 4. Upravljanje javnega prometa Manage Public Transport Operations 4.3 Provide PT Management 4.4 Control PT Fleet 4.2 Plan PT Service 4.1 Monitor PT fleet Manage Vehicle Sharing Require Vehicle Priority Manage Fare Schemes Confer to Vehicles Monitor Infrastructure Manage Additional Vehicles Plan Vehicle Pooling Services Estimate Vehicle Indicators Provide Maintenance Coordination Optimise Control Action Plan & Schedule Services Predict Vehicle Indicators Provide Service on Demand Control Vehicle Driving Manage PT Route Stores and Operator Interface Calculate Service Performance Manage PT Drivers Figure 7: Functional diagram of Manage PT Operations area Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 25

27 5. Zagotavljanje naprednega sistema navigacije vozila Provide Advanced Driver Assistance Systems 5.13 Provide Vehicle Data and ISA 5.11 Provide Driver Monitoring and Mayday 5.12 Provide Vehicle Communications Interfaces Provide ISA Speed Limits Record Operational Data Detect Illegal Use Provide Vehicle Position Determination Provide Mayday Call Collect Road Infrastructure Data Prepare Floating Car Data Monitor Driver Status Provide Traffic Regulations Provide Current Speed Limit Provide Operational Data Provide Vehicle to Vehicle Communications Provide ISA Facilities Provide Vehicle ID Provide Communications with In-Vehicle Systems Figure 8: Functional diagram of Advanced Driver Assistance System area 7. Zagotavljanje podpore pri uveljavljanju zakonov Provide Support for Law Enforcement 7.1 Detect Fraud 7.2 Identify Violator 7.3 Process Fraud Notifications 7.5 Manage Rules and Users' Registrations Perform Measure Check Compliance Analyse Image Determine Violator ID Sort Fraud Notifications Establish Prosecution File Manage Rules Manage Users' Registration 7.6 Store Violations Data Figure 9: Functional diagram of Provide Support For Law Enforcement area Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 26

28 6. Zagotavljanje pomoči pri načrtovanju potovanja Provide Traveller Journey Assistance 6.1 Define Traveller's GTP 6.5 Prepare Trip Plan 6.3 Support Trip 6.4 Evaluate Trip Provide Emergency Services Routes Provide Operator Access to General Trip Preference Provide Traveller Guidance Provide Operator Access to Trip Planning Data Define Traveller Trip Preferences Inform Traveller Plan Traveller Trip Perform Bookings and Make Payments Provide Trip File Management Operator Interface Collect PT Data Provide Trip Planning Interface Assess the need for Trip Plan Changes Provide FFM Data and Routes Collect Road Traffic Data Provide Trip Plan and Trip File Figure 10: Functional diagram of Traveler Journey Assistance area Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 27

29 8. Upravljanje tovornega prometa Manage Freight and Fleet Operations 8.1 Manage Logistics and Freight 8.2 Manage Commercial Fleet 8.3 Manage vehicle/ driver/cargo/ equipment Handle Customs Declaration Manage Driver Employment Negotiate Freight Operator Requests Comply with Regulation Identify Possible Transport Optimisations Prepare and Deliver Official Transport Documents Manage Vehicle and Equipment Manage and Schedule Maintenance Activities Process on_board Payments Manage Incident Monitor Operational Task Monitor Transport Order Monitor Equipment Control Freight/ Cargo Operations Administrate Freight Transactions Book Storage Places Negotiate Principal Requests Evaluate Freight Operations Performance Choose a Fleet Supplier Evaluate and Record Safety Status Prepare/Process information to/from board Administrate Fleet Transactions Prepare and Deliver Operational Transport Document Elaborate and Store Operational trip and load plan Evaluate Transport Conditions Determine Compliant Resources Evaluate Fleet Operations Performance Monitor Driver Monitor Cargo Check Transport Order Monitor Vehicle Create New Transport Unit Handle Hazardous Goods Transport Declaration Figure 11: Functional diagram of Manage Freight and Fleet Operations area Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 28

30 Communications Viewpoint Based on the physical viewpoint of the SITSA-C the communication needs of the ITS can be defined. In the framework of the SITSA-C only the type and sort of data are defined. In order to consider the communication viewpoint of the ITS architecture, the following still needs to be defined: physical principle of data transfer safety specifications (protection) necessary capacity for the data transfer, which is, regarding such fast development of telecommunications, on the national level almost impossible Regarding the functional and physical (and communication) ITS architecture the allocation of physical units is prepared: subsystems and modules for individual organisations (subjects) in the system who will manage with them. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 29

31 3. ARCHITECTURE IMPLEMENTATION 3.1. Case 1: NCUP - National Traffic Management Centre NCUP includes public road network in Slovenia - all national roads and strategically important local roads. Within NCUP the integration of three components (Figure 12) is foreseen: Main motorway traffic control centre (GCNVP) Traffic management and control centre for other national roads (CUVP), including other national roads and strategically important community roads not managed by any local traffic management centre Traffic Information Centre (PIC Prometno-informacijski center) Within NCUP a common road-weather information centre (CVIC) is active NCUP PIC CVIC GCNVP CUVP Figure 12: Integration of NCUP components NCUP Subsystems and Their NCUP represents the highest strategic level in the traffic and road management system hierarchy on all national roads, including the strategically important community roads. The system's main task is control over the functioning of the whole national system. While the main function of the regional and local traffic control centres is to take care of everyday local (regional) traffic management and system functioning, the main centre will focus on the tasks at the national and international level. Since for the future additional regional control centres Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 30

32 are foreseen, the main centre shall allow the system to be extended by adding new regional traffic control and management centres. Similar requirements apply also due to the upgrading of the main centre as central interface between other ITS systems (main tolling centre, sources of traffic information and services, possible security centres, etc). According to expectations, their number will also grow. The functions of the centre are defined according to the needs, wishes and demands or according to the applications of the existing road managers. The following systems with specified selection of functions, defined data stores and specified physical data flows have been determined: Traffic Control Subsystem: o traffic management at the national and international level o traffic measurement data management o overview of the conditions on the national road network (including strategically important community roads) o overview of special events (incidents) o overview of weather conditions (also outside the road area) o overview of maintenance interventions at the motorway network with closed sections o assuring short-term traffic predictions and strategies for managing traffic for the whole national road network o communication and harmonisation of measures with similar traffic management systems abroad and o assuring up-to-date data on the road network intended to the final user Travel Coordination Subsystem: o control over transportation of goods and travellers: special transports o weighing of vehicles, transport of dangerous goods, transport of high vehicles, control of public transport, etc o control over carriers, support to vehicle exclusion and o support e.g. according to transport policy Maintenance Management System: o winter service, road-weather information system (environment or weather conditions) o coordination of roadblocks at the whole national road network: road works o overview of maintenance vehicles with the possibility of using Floating Car Data (FCD) Archive Data Management Subsystem: o collecting, storing and viewing data o road infrastructure databank o link to the existing data stores within the existing Office for Road System Records and Archives of the Slovenian Roads Agency Information Service Provider System: o informing road users on the conditions on the national road network or providing information to authorised media that inform Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 31

33 o collection, processing and transfer of user information with the help of Alert- C, DATEX II and TPEG protocols in Slovenia Primarily the basic functions and data flows of the NCUP subsystems are defined in the proposal of the national ITS architecture (Website of SITSA-C). In this way the possibility of connecting similar centres in the European space is assured (similar functions, similar data stores and requirements for functions) Data Stores Functional areas or NCUP subsystems include also data stores, representing stores of data potentially used by several functions of different subsystems. Table 2 presents all the current data stores designed in the FRAME-NET project, which was the groundwork for SITSA-C. Table 2: SITSA-C data stores - road transportation ID Name of Data store ID Name of Data store D1.1 EP Contracts Store D4.1 Real Time PT Vehicle Status D1.2 User's Account Store D4.2 Historical PT Vehicle Data D1.3 Service Information Store D4.3 PT Service Plan D1.4 Transactions Store D4.4 PT Route Static Data D1.5 Tariffs Store D5.1 Operational Data D1.6 Fraud Store D5.2 ISA Data D1.7 Access Rights Store D6.1 General Trip Preferences (GTP) D2.1 Common Emergency Data Store D6.2 Private Trip File D2.2 Incident And Emergency Data Store D6.3 Road Trip Planning Data D3.1 Urban Traffic Data Store D6.4 PT Trip Planning Data D3.2 Inter-urban Traffic Data Store D7.1 Rules Store D3.3 Environmental Data Store D7.2 User's Registration Store D3.4 Incident Data Store D7.3 Violations Store D3.5 Demand Data Store D8.1 Consignment D3.6 Maintenance Data Store D8.2 Resources data store D3.7 Urban Road Static Data Store D8.3 On board database D3.8 Inter-urban Road Static Data Store The highlighted data stores are those that are currently connected to NCUP. The data stores D6.1 D6.4 are also part of NCUP, but they can be established only in the second phase. The data store D8.3 on/in a vehicle shall be designed for the needs of the Maintenance Management System. Other data stores should also be implemented in other centres directly connected to NCUP or ITS in the area of Slovenia (e.g. Information Centre or Operative- Communication Centre) Other Technological/Parallel Systems In order to meet the requirements of the proposed functionality of the systems in NCUP, the existing external components for measurement, monitoring, analysis and control shall be appropriately defined or upgraded: Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 32

34 roadside equipment for traffic control and for monitoring environmental data (monitoring) system of vehicles for the maintenance and safety of roads, system of control over service areas system of control over commercial vehicles Organisational aspect of Subsystems included in NCUP The purpose of this aspect is to allocate subsystems or their functions and data stores to different organisations. The key stakeholders included in the NCUP subsystem can be identified based on their roles in the service chain and based on the concept of partakers in the traffic management system in Slovenia within NCUP. It is also important to define the principle of providing data. The proposal was as follows: Operative-Communication Centre (Police): free traffic information, Information Centre (rescue teams): free traffic information, Motorist organisations and clubs: contractual information provider services, Government or public institutions and organisations providing traffic information and monitoring road conditions (road managers, Slovenian Environment Agency): o contractual (possibly free) traffic information provider services via RDS-TMC, DATEX II, worldwide web/tpeg) and field units, o free support to traffic policy and planning and o coordination of public services in the traffic information centre (TMC, worldwide web/tpeg); Radio-diffusion operators (transmitters): providing minimum FM frequency channel with the possibility of transmitting RDS signal (TMC), transition to digital technology (TMC, worldwide web/tpeg), Manufacturers of navigation systems: development of products and sales to individual markets, Manufacturers of digital maps: development of digitalised maps and integration of location tables (TMC, DATEX II, worldwide web/tpeg) for the area of services, Providers of information-communication services: contractual service providers and coordination for commercial services TMC, worldwide web/tpeg, Traffic-information centres (road management centres) in neighbouring countries: international support to services (DATEX II) on contractual basis Problems encountered When establishing ITS services from the technical viewpoint, success depends on a great extent also on good organisational and business model. From the organisational viewpoint, as mentioned under the subject of data collection, for each communication interaction the assumed liabilities and contractual provisions shall be clearly defined through a chain of services, irrespective of its function as the base of services to the public, private or mixed business model. And, for example in Case 1 NCUP, there is still open question of business and financial model of mentioned centre. Deliverable D4.3.6: Guidelines/proposals for the revision of ITS architecture in Slovenia 33