Israel ITS Architecture Development Rob Jaffe, Ph.D. President, ConSysTec Shenorock, NY USA

1. Israel ITS Architecture Development Rob Jaffe, Ph.D. President, ConSysTec Shenorock, NY USA

2. What is ITS? • Intelligent Transportation System Could be: • IntegratedTransportation System • One Definition: • “The application of data processing and data communications to surface transportation, to increase safety and efficiency.”

3. Systems Engineering (SE) • We practice SE to Reduce the Risk of: • Cost/Schedule Overage • Building the Wrong System • ITS Architecture is the first step of SE

4. Operations and Maintenance Changes and Upgrades Feasibility Study / Concept Exploration Regional Architecture(s) Retirement/ Replacement System Validation Plan Concept of Operations System Validation System Verification Plan (System Acceptance) Subsystem Verification Plan (Subsystem Acceptance) Unit / Device Test Plan Systems Engineering Project Lifecycle Concept of Operations System Validation System Verification/ Deployment System Requirements Subsystem Verification High-Level Design Decomposition and Definition Integration and Recomposition Unit / Device Testing Detailed Design Software / Hardware Development Field Installation Document/Approval Implementation Time Line

5. Fix It Here Cost to Correct 100x+ Phase that Defect is Created ConOps 1x Requirements 1x Design 1x Construction 1x ConOps Requirements Design Construction O&M Phase that Defect is Corrected Cost of Correcting System Defects (Adapted from McConnel, Steve, “Code Complete”)

6. ITS Architecture is a Consensus Institutional Architecture • Needs and Services to meet the needs • Stakeholders: • Their Roles and Responsibilities and • Their ITS Elements • Information Flows between ITS elements to do services • ITS Standards selected to encode the information flows • ITS Element Functional Requirements to issue and receive the information flows • Agreements required between ITS stakeholders • Technology Neutral • Must be a Consensus ITS Architecture

7. Architecture Use in Project Development • Step by Step Regional ITS Architecture Concept of Operations 2 3 System Requirements 4 High-Level Design 1 Detailed Design

8. Project Critical Success Factors- From a Standish Group Report

9. Contribution of ITS Architecture and Systems Engineering to Project Success

10. I-93 Closed at Decatur Blvd. Traffic Information Request for Traffic Information ITS Framework: A Regional Architecture Traffic Travelers Transit Emergency Service Providers

11. Framework/Regional/ProjectITS Architectures & Standards US National ITS Architecture Other National ITS Architectures (e.g. Canadian) Other ITS Standards (e.g. CEN) Logical Physical Israel ITS Architecture Selected ITS Standards Project Architectures

12. User Services Phase I & II Development 1993 1993-6 Architecture Published HRI ADUS Ver 3.0 Transportation Security Ver 5.0 MCO Ver 4.0 1996 Ver 2.0 1997 Version 6.0 1998 1999 2002 2003 2007 National ITS Architecture is a “Living Document” • Continuing evolution of the architecture over 10 years • Version 6.0 continues support for ITS technical evolution and deployment

13. Subsystem Diagram Travelers Centers Traffic Management Emergency Management Toll Administration Commercial Vehicle Administration Maintenance & Construction Management Remote Traveler Support Information Service Provider Emissions Management Transit Management Fleet and Freight Management Archived Data Management Personal Information Access Wide Area Wireless (Mobile) Communications Fixed-Point to Fixed-Point Communications Roadway Vehicle Emergency Vehicle SecurityMonitoring Vehicle to Vehicle Communications Transit Vehicle Toll Collection Dedicated Short Range Communications Commercial Vehicle Parking Management Maintenance & Construction Vehicle Commercial Vehicle Check Vehicles Field

14. Regional ITS Architecture Layers Communications Layer • How information transferred between ITS elements Communications Transportation Layer • What information is transferred between ITS elements Transportation Institutional Layer • Policy, Relationships, Strategies Institutional

15. Development Process • Top Down – MOT Leadership • Identification of customization at the Framework Level • Policy Development and Implementation • Bottom Up – ITS Israel Leadership • Work with Stakeholders to Develop their Projects using the ITS Architecture Methodology • Build Stakeholder Consensus

16. What ITS Israel Has Done With Stakeholders (So Far) • Nov 2007 and July 2008: Two 2-Day Workshops: ITS Architecture and its use in Systems Engineering • Full Stakeholder Workshops July and September: • Ayalon Highway • Haifa Municipality • Short Discussions • Driver Improvement Technology • Advanced Traveler Information (Private Sector) • Transit with Israeli Institute of Standards • Tel Aviv Projected Metropolitan TCC • METRONIT – Transit Project • Carmel Tunnels Project • Highway 6

24. Forward Plan • This is methodology is now available • Contact ITS Israel (Eran Reuveni) • To participate and • Gain the benefits: • Integration with your peers • Reduced risk of cost/schedule overrun • Produce ITS products that meet user expectations

25. Thank You! Rob Jaffe, Ph.D.President, ConSysTecShenorock, NY USAConsensus Systems Technologies (“ConSysTec”)rsj@consystec.com+1 914 248 8466www.consystec.com