1. Avivim TA’s Mobility management system

2. Urban Mobility Management Concept Transportation objectives often conflict  Accessibility Vs. Mobility  Efficiency Vs. policy The system is composed of humans rather then packets  Un-expected behavior  Changes over time  Stochastic in nature

3. Urban Mobility Management Concept The management system supports the engineer  Presents relevant information  Provides recommendations for appropriate actions  Sub-Network most suitable signal program  Supports data analysis processes  Historical data charts  Pattern identification

4. Urban Mobility Management Process Strategic Management Level Defining traffic management overall long-term goals Tactical Management Level Development and implementation of medium-term traffic- management principles needed to achieve long-term goals Operative Management Level Implementation of real-time traffic-management actions based on medium-term principles Central Control Transmission of operational instructions and analysis of operational data collected from input/output devices Field Control Implementation of operational instruction and collection of operational data from input/output devices Performance data Operational instruction Management Layer Operational Layer

5. Avivim History 1980s’ – 2006 : Siemens traffic control system 1995 – Eyal – a decision support system Avivim – a mobility management system  Developed in the municipality of Tel Aviv (operational since 2004)  TA Traffic wing engineers  Technion  PCS - Command & control company  Communication consultant  Monitors and controls the signalized network  VMS in Haifa

6. Development Approach ITS – Integrated Transportation Systems  4 groups  Mobility management  Communication  Control Time Team A Team B

7. Development Approach ITS – Integrated Transportation Systems  4 groups  Mobility management  Communication  Control Time Agile development methodology

8. Development Approach Exploitation of advanced technologies Independent from hardware vendors

9. Avivim Architecture Data Server INSYTE – A traffic Surveillance system EYAL – A traffic management and decision-support system STORM – A traffic Control system Management Layer Operational Layer

10. Avivim Components – Management Layer Information presentation and interpretation Decision support tool  Short term  Mid term Interface to other centers

11. On-Line Demo Congestion Level Reports Avivim Components INSYTE – traffic monitoring  Traffic Level of Service  Link based PT exclusive lanes  Geographic information System  Layer based  Junction status  LOS and congestion alerts  Historical data  Shares information with Eyal

12. Avivim Components Eyal – Decision Support System  Definition Module  Signal Program Design DB Import design parameters Download to the controller  Schedule management

13. On-Line Demo Sub Network Congestion Handling Sub Network Similar Events Avivim Components Operational Module  Congestion handling  Dedicated search module Junctions Sub-network  Similar events  Reporting  Real Time  Historical Data

14. Avivim Components Analysis Module  Identification of recurrent actions  Capacity Analysis  Traffic counts Analysis

15. Avivim Components – Operational Layer Execution of management decision  Conversion from hardware independence to hardware dependent Field data collection  Signal program related reports  Hardware integrity Maintenance analysis services

16. Avivim Components Signal Controllers  Normal Operation  Signal Program with local parameters  Instruction Synchronization Signal Program number Operation mode Blink…  Emergency Operation  Signal Program with local parameters  Local schedule

17. Avivim Components Communication routers  Driver for seamless operation  Accumulation of reports  Volume & Occupancy  Green Durations  Execution of instructions  Synchronization  Schedule backup

18. Avivim Components Control System  Citec-SCADA application  Control application generator  Acquisition of the signal controller status  Signal Group status  Synchronization status  Hardware failure  Forward management instruction  Signal programs  Downloads