Metropolitan Topeka Planning Organization

Transcription

1 TOPEKA-SHAWNEE COUNTY REGIONAL ITS ARCHITECTURE ITS COMMUNICATIONS PLAN DELIVERABLE NO.5 DRAFT Submitted to Metropolitan Topeka Planning Organization Submitted by In association with February 13, 2007

2 TABLE OF CONTENTS 1.0 INTRODUCTION PURPOSE OF THIS REPORT INVOLVED AGENCIES EXISTING AND PLANNED ITS AND COMMUNICATIONS RESOURCES CITY OF TOPEKA SHAWNEE COUNTY KANSAS DEPARTMENT OF TRANSPORTATION (KDOT) OTHER STAKEHOLDERS OTHER COMMUNICATIONS COMMUNICATIONS REQUIREMENTS PROTOCOLS AND STANDARDS COMMUNICATIONS NETWORK HIERARCHY BASELINE CONCEPT OF OPERATIONS COMMUNICATIONS NETWORK REQUIREMENTS Center-to-Center Communications Requirements Center-to-Field Communications Requirements COMMUNICATIONS ALTERNATIVE ANALYSIS NETWORK ARCHITECTURE COMMUNICATIONS APPROACH Communication Approach Type 1 Centers Communication Approach Type 2 Centers COMMUNICATIONS MEDIA AND TECHNOLOGIES ASSESSMENT LAND-LINE SOLUTIONS Fiber Optic SONET on Fiber ATM on Fiber Ethernet on fiber Leased Line ISDN DSL T-Carrier ATM Internet WIRELESS SOLUTION GPRS Wi-Fi Communcations WiMax Mesh Networks RECOMMENDATIONS FOR COMMUNICATIONS MEDIA AND TECHNOLOGY Center-to-Center Communications Backbone Center-to-Field Communications NEXT STEPS...46 Iteris, Inc. i

3 LIST OF FIGURES FIGURE 1.1: STUDY AREA FOR TOPEKA-SHAWNEE COUNTY REGIONAL ITS ARCHITECTURE...2 FIGURE 2.1: CITY OF TOPEKA TRAFFIC MANAGEMENT CENTER...4 FIGURE 2.2: TOPEKA-SHAWNEE COUNTY REGION SIGNALIZED INTERSECTIONS...5 FIGURE 2.3: CITY OF TOPEKA COMMUNICATION SYSTEM...8 FIGURE 2.4: PROPOSED 4.9 GHZ WI-FI COMMUNICATIONS NETWORK...9 FIGURE 3.1: AGENCY LEVEL COMMUNICATIONS CONCEPT...14 FIGURE 3.2: HIGH LEVEL TOPEKA-SHAWNEE COUNTY COMMUNICATIONS CONCEPT...14 FIGURE 3.3: CONCEPT OF OPERATIONS -ALTERNATIVE FIGURE 3.4: CONCEPT OF OPERATIONS -ALTERNATIVE FIGURE 4.1: STAR NETWORK (EXAMPLE)...28 FIGURE 4.2: TREE NETWORK (EXAMPLE)...29 FIGURE 4.3: UNPROTECTED RING NETWORK (EXAMPLE)...29 FIGURE 4.4: PROTECTED RING NETWORK (EXAMPLE)...30 FIGURE 4.5: MESH NETWORK (EXAMPLE)...30 FIGURE 4.6: COMMUNICATIONS APPROACH TYPE 1CENTERS...33 FIGURE 4.7: COMMUNICATIONS APPROACH TYPE 2CENTERS...34 LIST OF TABLES Table 1.1: Communication Sharing Needs for Stakeholders...3 Table 3.1: Roles, Responsibilities, and Type of Data for Stakeholders...16 Table 5.1: Summary of Preliminary Recommendation for Center to Center Communications...44 Iteris, Inc. ii

4 1.0 INTRODUCTION The Metropolitan Topeka Planning Organization (MTPO), in cooperation with the Federal Highway Administration (FHWA), the Federal Transit Administration (FTA), the Kansas Department of Transportation (KDOT), the Topeka Metropolitan Transit Authority (TMTA), Shawnee County, and the City of Topeka has sponsored the development of a Regional Intelligent Transportation System (ITS) Architecture for the Topeka-Shawnee County Region. The goal of the architecture is to answer questions such as: How can we make travel on our roadways safe, secure and more efficient? How can we make government services, such as transit and emergency response, more efficient? What can we do by working together, that we can't do as well on our own? The Topeka-Shawnee County Regional ITS Architecture will become a plan of projects for technologies, interagency collaboration, communication and technical integration in the Topeka- Shawnee County Region. The purpose of developing a Regional ITS Architecture is to illustrate and document regional integration so that planning and deployment can take place in an organized and coordinated fashion. The common thread for all agencies is the need to provide ITS solutions to transportation safety, congestion and security. This project will be conducted through 12 tasks with multiple milestones and deliverables. This deliverable presents the draft Communications Master Plan developed in support of Task 5 with the primary objective of assessing the adequacy of the existing and planned communication infrastructure in the region and contains the following primary actions: Perform communications inventory in concert with development of the overall system needs. Identify communications alternatives. Recommend communications strategies and concepts. Develop. 1.1 Purpose of this Report This report identifies and documents an ITS communications network capable of connecting the agencies Transportation Management Centers (TMC) to the ITS field elements and sharing information between transportation agencies or other stakeholders in the region. Existing and planned communication inventory, the overall system needs, communications requirements, and alternative analysis provide a framework for the recommended ITS communications plan. Please note that this communications plan considers connection to a multitude of ITS systems deployed in the field. Its intent is not to complete a detailed systems design for each element. It is high level in nature, so that it will allow for the use of various technologies. A key element of the plan is to identify some of the opportunities that may be available, but it should not be considered a substitute for future communications analysis. As additional devices or systems Iteris, Inc. 1

5 are deployed, or as the need for data sharing and exchange between agencies progresses, each project should contain an analysis for detailed communications planning and design. 1.2 Involved Agencies The Steering Committee for the Topeka-Shawnee County Regional ITS Architecture includes representatives from Metropolitan Topeka Planning Organization (MTPO), Federal Highway Administration (FHWA), Federal Transit Administration (FTA), Kansas Department of Transportation (KDOT), Topeka Metropolitan Transit Authority (TMTA), Shawnee County, and the City of Topeka. The Topeka-Shawnee County Regional ITS Architecture will encompass all major communities and interested organizations within Shawnee County. Figure 1.1 provides a map of the Topeka-Shawnee County project study area. Figure 1.1: Study Area for Topeka-Shawnee County Regional ITS Architecture From a communication needs stand point, these Stakeholders could be grouped into following categories: 1. Stakeholders with traffic management, emergency operations or maintenance systems that will transmit and receive information through the communications network on a continuous basis 2. Stakeholders that will transmit information to other Stakeholders only 3. Stakeholders that will receive information from other Stakeholders only Iteris, Inc. 2

6 4. Stakeholders that will not transmit or receive information from other Stakeholders For the Topeka-Shawnee County Regional ITS Architecture project, the communication needs for the project Stakeholders are summarized in Table 1.1. Table 1.1: Communication Sharing Needs for Stakeholders Transmit & Receive 1. City of Topeka (Traffic Operations TMC) 2. Shawnee County 911 Dispatch Center 3. KDOT-District 1 (Topeka Office) 4. City of Topeka (Transportation Operations Maintenance Operations) 5. Shawnee County Emergency Management Center Receive Only 1. Shawnee County Public Works 2. City of Topeka (Traffic Engineering) 3. City of Topeka Fire Department 4. Shawnee County Sheriff s Office 5. Shawnee County Fire District 3 6. Topeka Metropolitan Transit Authority 7. Kansas Highway Patrol 8. Metropolitan Topeka Airport Authority 9. Washburn University 10. American Medical Response 11. St. Francis Health Center 12. Stormont-Vail Healthcare 13. Rural/Special Fire Departments Transmit Only 1. City of Topeka Police Department 2. Kansas Turnpike Authority 1. School Districts No Sharing Iteris, Inc. 3

7 2.0 EXISTING AND PLANNED ITS AND COMMUNICATIONS RESOURCES The following sections describe existing communication resources in the area and the planned communications to be implemented shortly. 2.1 City of Topeka Traffic Signal System The City of Topeka maintains and operates approximately 175 traffic signals with 90 of these signals interconnected through fiber optic cable and operating in coordinated patterns during peak periods. The City utilizes PYRAMIDS traffic signal software system, by Econolite, to operate the 90 signals that are on-line. The PYRAMIDS workstation is located at the Topeka TMC, presented in Figure 2.1, located at 927 NW Harrison. Figure 2.1: City of Topeka Traffic Management Center Most of the City s traffic signal controllers are Type 170E, operate Wapiti controller firmware, and utilize the serial data port for communications. To date, the City has installed ten (10) Model 2070 traffic signal controllers, by Econolite, that operate OASIS controller software. The City s signalized intersections are illustrated in Figure 2.2. The City also maintains five (5) Shawnee County signalized intersections and six (6) KDOT signalized intersections in the Topeka-Shawnee County region. The County and KDOT signalized intersections are also illustrated in Figure 2.2. Iteris, Inc. 4

8 Figure 2.2: Topeka-Shawnee County Region Signalized Intersections Iteris, Inc. 5

9 Some of the major arterial corridors where the signalized intersections are located include: Wanamaker Road Topeka Boulevard Washburn Avenue 6 th Avenue 10 th Avenue 21 st Street The City is planning to upgrade all traffic signal controllers to Model 2070 controllers at a rate of 6 controllers per year. Currently, the City utilizes the serial data port for communications with the 2070 controllers, with the ultimate goal to utilize Ethernet communications. The current Model 2070 controllers are equipped with only a serial port. It is recommended that future Model 2070 controllers be equipped with both a serial and an Ethernet port as a cost savings measure versus a future upgrade to the Model 2070 controllers to install the Ethernet port. The City has a total of 52 intersections that use complete or partial video detection, as noted below. Peek Video Trak at 15 intersections to operate the full intersection Econolite Autoscope Solo Pro at 25 intersections to operate the full intersection Econolite Rack Vision hardware at 12 intersections to control one or more legs of an intersection but not the entire intersection Their current specification for video detection hardware is Econolite Autoscope equipment and they are in the middle of a program to remove all of the Peek Video Trak installations. The City uses 3M Opticom Priority Control Systems, by 3M, for emergency vehicle signal pre-emption at two locations. Video Surveillance System The City of Topeka currently has two CCTV cameras installed and operational with one more planned, at the locations listed below: I-70 & Wanamaker 21 st & Wanamaker I-470 & Wanamaker (planned) The CCTV cameras are Vicon dome CCTV cameras that currently transmit analog video but are Internet Protocol (IP) upgradeable. The analog video is converted to IP video prior to transmission to the Topeka TMC and camera control is integrated into the PYRAMIDS traffic signal software system. The City has plans to implement 14 additional CCTV cameras in Most of the cameras will be located at freeway interchanges in the Topeka area and will be shared City/KDOT cameras. Fiber Optic Communications Iteris, Inc. 6

10 The City of Topeka has an extensive fiber optic network that is comprised of three communication systems, as described below. The fiber network is illustrated in Figure 2.3. KMC Telecom Fiber Network: KMC is a private telecommunications company that installed fiber optic cable in the Topeka area. In support of this effort, KMC has provided 12 fiber strands for use by the City and Shawnee County. The 12 fiber strands are completely separate from KMC s fiber and the associated communication hardware is all City- or County-owned and maintained. Currently, all 12 strands are in use with 6 strands allocated for Traffic use, which are currently supporting backbone communications. The City s fiber strands are maintained by the Topeka IT department. Topeka School District Fiber Network: The school district fiber has allocated 24 fiber strands for Traffic use. Currently, all 24 fiber strands are in use by Traffic. This fiber is managed by the Topeka IT department. Traffic Fiber Network: The City has several distribution fiber runs that branch off of the backbone fiber to support the signalized intersections. The distribution fiber consists of 24 fiber strands. Typically, 2 to 4 of the fiber strands are in use. Public Safety Wireless Communications (Future) The City of Topeka is planning to deploy a WI-FI communications network that utilizes the 4.9 GHz Public Safety frequency. The FCC-approved 4.9 GHz license gives an agency the right to use the entire MHz frequency band. However, multiple agencies may receive licenses within the same geographic area, thus the possibility for interference exists. For the Topeka-Shawnee County region, it is envisioned that the frequency will be collectively shared by Stakeholders. The system could support Ethernet communications to ITS field devices including traffic signal controllers, CCTV cameras, Dynamic Messages Signs (DMS), freeway sensors, etc., and can fill gaps in the fiber optic communications system. The envisioned coverage area provided by the wireless network is illustrated in Figure 2.4. The City also has a GDI 1200 baud wireless system throughout the downtown area. The system was abandoned when the fiber system was installed. However, several of the antennas are still mounted on the traffic signal poles. 2.2 Shawnee County Shawnee County owns 16 traffic signals, 5 of which are fully-operational signalized intersections. The remaining 11 traffic signals are flashing beacon installations. The City of Topeka maintains and operates the 5 County fully-operational signalized intersections, which are listed below and illustrated in Figure th and Croco 29 th and Westedge 45 th and Adams 57 th and Topeka 58 th and Topeka Iteris, Inc. 7

11 Figure 2.3: City of Topeka Communication System Iteris, Inc. 8

12 Figure 2.4: Proposed 4.9 GHz WI-FI Communications Network Iteris, Inc. 9

13 ITS Communication Plan These five County signalized intersections are currently not on-line and the County has no immediate plans to bring them onto the network using fiber. The locations are too remote for the installation of fiber optic cable. However, the County desires to connect to these locations in the future using wireless communications or other viable means of communications. Based on discussion with Shawnee County Staff, the two critical signalized intersections that warrant communications are noted below. 29 th and Croco 57 th and Topeka Shawnee County does not own any fiber optic network of its own. However, Shawnee County Emergency Communications currently uses 8 strands of City of Topeka fiber which extends from 215 SE 7 th Street to 1500 SW 8 th Street. Shawnee County currently has no video surveillance system but has plans to have access to the City of Topeka TMC system which could provide access to City cameras. Additionally, the County would like to see CCTV cameras installed at the two critical locations noted above. The Shawnee County emergency communications center also has plans to provide pre-emption at signals for emergency vehicles. The Shawnee County Public Works department would like to receive weather information from KDOT, the City and Surface Systems, Inc. (SSI ). The Shawnee County emergency communications center also has plans to deploy a wireless hot spot next year in its parking lot (320 S. Kansas Avenue) to be used by County staff. This can also be used/shared to bring some of the outlying signal locations online. 2.3 Kansas Department of Transportation (KDOT) KDOT owns no fiber optic communications in the Topeka-Shawnee County Region. KDOT has 12 dark (unused) fiber stands leased from Lycore (Private Entity) that runs primarily on US 24 onto US 75 going north towards I-70. Lycore allocated the fiber to KDOT which were then connected using KDOT equipment. The focus of KDOT was to develop backbone communications for statewide communications using fiber connections to major cities (Kansas City, Wichita, and Topeka) in the state of Kansas. KDOT has plans to set up a statewide Virtual Operation Center (VOC) with no existing state infrastructure on the ground. KDOT envisions that the VOCs would interface with the regional TMC s, hosted by other agencies such as City of Topeka, in which KDOT can transmit and receive traffic related data. KANROADS or 511 will be a primary component of the VOC. KDOT also has plans to install DMS at major interchanges with I-70/I-470 in the City of Topeka- Shawnee County region. Other planned programs include queue detection and congestion warning system on Wanamaker Road, DMS at Quincy viaduct for construction & maintenance, DMS on US-75, and vehicle system detection along the freeways in the Topeka-Shawnee County region. Iteris, Inc. 10

14 2.4 Other Stakeholders Below is a listing of communications systems employed by other Topeka-Shawnee County stakeholders. The City of Topeka Information Technology (IT) Department primarily maintains fiber optic and wireless communication networks for both City of Topeka and Shawnee County. City of Topeka Police Department (TPD) currently has In-vehicle radio systems, Invehicle computers and Automatic Vehicle Location (AVL) systems. TMTA utilizes two-way communications, security cameras on buses and demandresponsive trip scheduling software and plans to add AVL and mobile data terminals to demand-responsive vehicles. The City of Topeka construction and maintenance division currently has AVL, vehicle temperature probes and In-vehicle radio systems for maintenance vehicles. The City of Topeka Fire Department has a signal preemption device at Station 1 for fire vehicles. They plan to use more ITS devices in the future. The Shawnee County health agency has a surveillance system which receives reports from schools, hospitals and major employers to administer and notify the public concerning health risks. Washburn University has its own dispatch center for all campus calls. They also currently have CCTV camera surveillance in some parking lots and are working on installing cameras in all parking lots. Washburn police currently has no GPS on patrol vehicles but they do have mobile data terminals inside their patrol vehicles. Washburn University currently uses DMS for campus information and at Lee Arena for event notification, but not for traveler information. American Medical Response (AMR-Ambulance service) covers the entire region including transport for hospitals. They currently have computer aided dispatch and also use the 800 MHz system/400 MHz back up/paging system to contact other agencies during incidents. All AMR vehicles have GPS on them which are used for vehicle tracking purpose only. 2.5 Other Communications Most agencies in the Topeka-Shawnee County region are on the 800 MHz Trunked radio system. KDOT uses the radio system to communicate with maintenance and Kansas Highway Patrol (KHP). The Shawnee County Public Works Maintenance and Construction Operations (MCO) and emergency communications division also has an 800 MHz radio system and can communicate with Police and KHP. However, the City of Topeka MCO division is on a different Iteris, Inc. 11

15 radio system and currently can not communicate with agencies using the 800 MHz Trunked radio system. Iteris, Inc. 12

16 3.0 COMMUNICATIONS REQUIREMENTS Prior to evaluating and planning the Topeka-Shawnee County communications network, it is first necessary to identify the requirements for the communication between traffic management or operation centers and their corresponding field elements and the data transmission requirements between involved agencies. The focus of this section is to establish a set of communication requirements for the Topeka-Shawnee County communications network. 3.1 Protocols and Standards One of the primary goals for the Topeka-Shawnee County Regional is to establish common communications and infrastructure protocols for all current and future ITS projects in the Topeka-Shawnee County region. To achieve this goal, the first step is to bring Topeka-Shawnee County into compliance with some of the more broadly accepted National Transportation Communications for ITS Protocol (NTCIP) standards. NTCIP is a family of communications protocols and data definition standards that have been designed for use in all types of systems dealing with the transportation environment, including those for freeways, traffic signals, emergency management, traveler information, and data archiving. It has been adopted by Federal Highway Administration (FHWA) to meet the needs and requirements for ITS communications and to insure that inter-network connectivity is done through an open architecture and industry standard interfaces. NTCIP eliminates barriers to interagency coordination by reducing the need for reliance on specific equipment vendors and customized one-of-a-kind products. It allows a management system to communicate with a mixture of device types of the same communications channel. It also allows for the future expansion of the system to benefit from true competitive bidding, as well as allow other types of ITS elements to be added. One primary purpose of NTCIP is to handle two major ITS communications needs: (1) Centerto-Center (C2C) Communications and (2) Center-to-Field (C2F) Communications and field ITS device interconnect. The communications network requirements for Topeka-Shawnee County are mostly derived from the ITS needs/services and can be grouped into the C2C and C2F categories. A separate effort is being conducted to develop the Kansas Statewide ITS Architecture. Another requirement of the Topeka-Shawnee County ITS Communications Master Plan is to be compliant with and integrate with the Statewide Architecture. Typically, the regional ITS Architectures are rolled up into the statewide plan. In this case, the Topeka-Shawnee County Regional ITS Architecture will become a subset to the Kansas Statewide ITS Architecture. Therefore, the proposed high-level communications plan, will also become a subset of the larger center-to-center communications plan as well. 3.2 Communications Network Hierarchy The expected hierarchy of the communication network of the City of Topeka, and the Topeka- Shawnee County region could be presented as Figures 3.1 and 3.2. These figures indicate that Iteris, Inc. 13

17 the City network will eventually be integrated into the KDOT and the statewide communication system. Figure 3.1: Agency Level Communications Concept Figure 3.2: High Level Topeka-Shawnee County Communications Concept Iteris, Inc. 14

18 3.3 Baseline Concept of Operations The concept of operations defines, in more detail, the relationship between participating Topeka-Shawnee County stakeholder agencies, including their roles and responsibilities and the level of information, status, and control sharing among those agencies. It represents the vision of the system based on user needs and how the system will work to satisfy those user needs. The concept of operations is an important component of the system engineering process and has a direct effect on the C2C communications network requirements. The Topeka-Shawnee County concept of operations consists of two major components: Role and Responsibilities Based on the desire and capabilities of the agencies to transmit/receive, just transmit or just receive traffic information, the centers could be categorized into two types: - Type 1 Center In order to be classified as Type 1, a center has to both transmit and receive information to and from other centers on a continuous basis. In addition, the Type 1 centers are responsible for housing, operating, and maintaining communications equipment for data exchange and sharing with other centers. These centers usually have the most communications infrastructure and are the most ready to provide communications for the Topeka-Shawnee County region. Examples of Type 1 Centers are the City of Topeka TMC, Shawnee County 911 Dispatch Center, KDOT-District 1 (Topeka Office), City of Topeka (Transportation Operations Maintenance Operations), and Shawnee County Emergency Management Center. - Type 2 Center Type 2 centers will either transmit or receive information, or transmit and receive, but not on a continuous basis, to and from other centers, typically to one or more Type 1 Centers. Type 2 centers are not required to house, operate, and maintain regional communications equipment. An example of this would be the connection between the City of Topeka TMC and the City of Topeka Fire Department. The City of Topeka TMC may only transmit information relative to major events which the City of Topeka Fire Department would request or like to receive such as road closures. In the future, each Type 2 center may require the need to transmit and receive information on a more frequent basis, or be upgraded to a Type 1 center for continuous information exchange at a future time. Type of Information Two types of information will be involved in the Topeka-Shawnee County communications network: Video and Data. Table 3.1, on the following page, summarizes the relationships of these two components for the Topeka-Shawnee County region. Based on the roles of the Topeka-Shawnee County stakeholders, there are two alternatives for the concept of operations. Iteris, Inc. 15

19 Table 3.1: Potential Roles, Responsibilities, and Type of Data for Stakeholders Role Type 1 Center Type 2 Center Type 2 Center No Data Exchange Responsibility Transmit and Receive Information House, operate, and maintain regional communications equipment Transmit Information Stakeholder City of Topeka (Traffic Operations TMC) Shawnee County 911 Dispatch Center KDOT-District 1 (Topeka Office) City of Topeka (Transportation Operations Maintenance Operations) Shawnee County Emergency Management Center City of Topeka Police Department Kansas Turnpike Authority Receive Information Shawnee County Public Works City of Topeka (Traffic Engineering) City of Topeka Fire Department Shawnee County Sheriff s Office Shawnee County Fire District 3 Topeka Metropolitan Transit Authority Kansas Highway Patrol Metropolitan Topeka Airport Authority Washburn University American Medical Response St. Francis Health Center Stormont-Vail Healthcare Rural/Special Fire Departments These agencies currently do not Transmit or Receive Information School districts Type of Informati on Data and Video Data and Video Data and Video Not applicable Concept of Operations - Alternative 1 Under this alternative, all centers will be connected to the Topeka-Shawnee County communications network for data and video sharing. In order to communicate with the network, each center has to have similar communications equipment used to access the network. As a result, each center has to house, operate, and maintain its own regional communications equipment. However, the entire communications network can utilize more than one type of media and technologies as a hybrid network. The advantage of this alternative is uniformity because all agencies will be using the same or compatible communications equipment. The disadvantage is that Type 2 centers, as defined, might not have the space and operations and maintenance budget for the regional communications equipment. Figure 3.3 illustrates the concept of operations for Alternative 1. Concept of Operations - Alternative 2 Iteris, Inc. 16

20 ITS Communication Plan Figure 3.3: Concept of Operations - Alternative 1 Iteris, Inc. 18

21 Figure 3.4: Concept of Operations - Alternative 2 Iteris, Inc. 19

22 The City of Topeka area-wide network (Topeka IT) supports the various City facilities (Topeka City Hall, Topeka TMC, Shawnee County 911, etc.). Additionally, this network can be modified to connect the KDOT D1 office to support the future KDOT VOC. The Topeka area-wide network includes a SONET ring and a Gigabit Ethernet ring, the latter of which supports the Topeka TMC. Alternative 2 utilizes the Topeka area-wide network to support the communications between the Type 1 centers, and in some cases, the Type 2 centers. In this case, Type 1 centers will be connected to the Topeka area-wide network. Other Type 2 centers will be indirectly connected to the Topeka-Shawnee County communications network through the Topeka TMC via the Topeka-Shawnee County communications system that could include fiber optic cable, leased line communications and dial up. This approach does not require each center to install the same communications equipment used to access the network. For example, a Type 2 center can continue to use its legacy equipment to transmit data to the Type 1 center. Other centers may receive information from that particular Type 2 center via the Topeka-Shawnee County communications network. However, this does not mean that a Type 2 center cannot implement a direct connection to the Topeka-Shawnee County communications network, but they are not required to do so. Like Alternative 1, the entire communications network can utilize more than one type of media and technologies. Figure 3.4 illustrates the concept of operations for Alternative 2. The following three primary factors were considered in the selection of the most appropriate alternative for the Topeka-Shawnee County concept of operations. Cost It is assumed that the Topeka-Shawnee County communications network will be a high speed, high capacity communication backbone for the Topeka-Shawnee County region. Since some Topeka-Shawnee County agencies might not require a high speed and high capacity network, it is not cost effective to have all centers connect to the Topeka-Shawnee County communications network directly. In addition, the Type 2 centers might not have the space to house the regional communication equipment and the operations and maintenance budget for regional communication. Based on the cost fact, Alternative 1 is less desirable than Alternative 2. Ease of Deployment Since one common communication technology will be used for the Topeka-Shawnee County communications network for both alternatives, the ease of deployment will depend on the number of agencies that need to be connected to the network. While Alternative 1 requires all centers to be connected to the network, Alternative 2 requires only Type 1 centers to be connected to the network. Therefore, Alternative 2 is relatively easier to deploy than Alternative 1. Existing Infrastructure Alternative 2 is more flexible in terms of existing infrastructure. Alternative 2 makes use of the existing Topeka area-wide network, with minor modification, to support communications between centers. Additionally, the Type 2 centers may be connected to the network via their legacy communications network. Iteris, Inc. 17

23 ITS Communication Plan Based on the above analysis, it is recommended that Alternative 2 of the Concept of Operations be used for the development of communications network requirements for the Topeka-Shawnee County communications network. This alternative will make the most use of existing infrastructure and the City of Topeka area-wide network. 3.4 Communications Network Requirements The Topeka-Shawnee County Regional will focus on Center-to- Center (C2C) and Center-to-Field (C2F) communications. The following sections present the requirements for these two types of communications Center-to-Center Communications Requirements The following presents the specific C2C communications network requirements that the Topeka-Shawnee County communications network design should support. I. Protocol and Standard Requirements 1. The Topeka-Shawnee County communications network and its associated equipment should comply with NTCIP and other applicable standards, such as the IEEE standards for Ethernet. 2. The Topeka-Shawnee County communications network should allow participating centers to use the same or compatible communications protocols for data sharing and exchange. 3. Communications protocols should be independent of communications media. II. Data Requirements As discussed in the previous chapter, there are two types of centers involved in the Topeka-Shawnee County communications network. The specific data requirements for each type of center are presented below. Note that the list of data requirements is intended to be thorough but not necessarily all encompassing. City of Topeka TMC Type 1 Center It is envisioned that the Topeka TMC will serve as the Regional TMC for the Topeka- Shawnee County region. The Topeka TMC will serve as the data hub for transportation management activities in the Topeka-Shawnee County region. The Topeka TMC will serve as the communication hub to the field devices in the Topeka- Shawnee County region. The Topeka TMC will also serve as the communication hub for the Type 1 and Type 2 centers in the region. The data requirements listed below are intended to support this goal. 1. Transmit and Receive 1.1. Transmit and receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) from City of Topeka field devices. Iteris, Inc. 20

24 1.2. Transmit and receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video, CCTV camera control) from Shawnee County field devices Transmit and receive arterial or freeway traffic data (e.g. timing data, traffic demand data, congestion data, detection data) from KDOT D1 field devices Transmit and receive CCTV video and camera control from shared City of Topeka / KDOT CCTV cameras Transmit and receive other arterial event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) as needed Transmit and receive traffic event data (e.g. agency name, contact information, number of injuries and fatalities, property damages, number of vehicles involved, etc.). 2. Receive 2.1. Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, and detection data) for KDOT signalized intersections from KDOT D-1 VOC Receive freeway and highway traffic data (e.g. traffic demand data, congestion data, detection data, etc) from KDOT D-1 VOC Receive arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) from field devices and other Type 1 and Type 2 centers Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) from other Type 1 centers Receive DMS message data Receive DMS message data as information changes Receive arterial device status information continuously Receive freeway traffic data (e.g. demand data, congestion data, etc) Receive freeway incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) as needed Receive other freeway event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) Receive toll road traffic data (e.g. demand data, congestion data, etc) Receive toll road incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) as needed Receive other toll road event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) Receive roadway weather data as needed Receive transit data (e.g. position, route, stop, schedule, arrival, and departure.) Receive incident data from Shawnee County 911 Dispatch 3. Transmit 3.1. Transmit arterial traffic data, CCTV video and camera control to Shawnee County 911 Dispatch 3.2. Transmit arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) to other centers Transmit arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) to other centers. Iteris, Inc. 21

25 3.4. Transmit other event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) to other centers Transmit CCTV control data as needed. KDOT District 1 Virtual Operations Center (VOC) Type 1 Center The KDOT VOC is envisioned to be connected to the Topeka TMC to transmit data between the KDOT VOC and the Topeka TMC. The data requirements listed below are intended to support this goal. Additionally, the KDOT VOC will be connected to other KDOT VOCs and TMCs throughout the State. However, the data requirements associated with that element will be addressed as part of the Statewide ITS Architecture project being conducted as part of a separate project. 1. Transmit and Receive 1.1. Transmit and receive messages from freeway DMS Transmit and receive freeway traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) to other centers Transmit and receive freeway incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) to other centers Transmit and receive freeway event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) as needed Transmit and receive traffic data from other KDOT districts Transmit and receive traffic event data (e.g. agency name, contact information, number of injuries and fatalities, property damages, number of vehicles involved, etc.). 2. Receive 2.1. Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) from City, County and KDOT field devices Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) from other Type 1 centers Receive event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) from other Type 1 centers Receive roadway weather data as needed Receive freeway device status information continuously Receive arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) from field devices and other Type 1 and Type 2 centers Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) from other Type 1 centers Receive DMS message data Receive DMS message data as information changes Receive arterial device status information continuously Receive freeway traffic data (e.g. demand data, congestion data, etc) Receive other freeway event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) Receive toll road traffic data (e.g. demand data, congestion data, etc). Iteris, Inc. 22

26 2.13. Receive toll road incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) as needed Receive other toll road event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) Receive roadway weather data as needed Receive transit data (e.g. position, route, stop, schedule, arrival, and departure.) Receive incident data from Shawnee County 911 Dispatch Receive AVL data from Shawnee County 911 Dispatch 3. Transmit 3.1. Transmit CCTV control data. Shawnee County 911 Type 1 Center The Shawnee County 911 Center is envisioned to be connected to the Topeka TMC to transmit data between the 911 Dispatch Center and the Topeka TMC. The data requirements listed below are intended to support this goal. 1. Transmit and Receive 1.1. Transmit and receive other arterial event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) as needed Transmit and receive traffic event data (e.g. agency name, contact information, number of injuries and fatalities, property damages, number of vehicles involved, etc.). 2. Receive 2.1. Receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) Receive CCTV video and camera control Receive freeway and highway traffic data (e.g. traffic demand data, congestion data, detection data, etc) Receive arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) from field devices and other Type 1 and Type 2 centers Receive freeway incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) Receive DMS message data Receive DMS message data as information changes Receive other freeway event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) 2.9. Receive toll road traffic data (e.g. demand data, congestion data, etc) Receive toll road incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) as needed Receive other toll road event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) Receive roadway weather data as needed Receive transit data (e.g. position, route, stop, schedule, arrival, and departure.). 3. Transmit Iteris, Inc. 23

27 3.1. Transmit arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) Transmit freeway incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) Transmit toll road incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) Transmit AVL data 3.5. Transmit CCTV control data as needed. Other Type 1 Centers It is envisioned that additional Type 1 centers will come on-line at a future time in the Topeka-Shawnee County region. Depending on the sponsoring stakeholder, the information to transmit and / or receive will vary. Some of the types of data requirements are listed below. 1. Transmit and Receive 1.1. Transmit and receive arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) Transmit and receive freeway traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) Transmit and receive toll road traffic data (e.g. timing data, traffic demand data, congestion data, detection data, CCTV video and camera control) Receive arterial, freeway and toll road incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) Transmit and receive other arterial, freeway and toll road event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) as needed Transmit and receive DMS messages 1.7. Transmit and receive traffic event data (e.g. agency name, contact information, number of injuries and fatalities, property damages, number of vehicles involved, etc.) Transmit and receive DMS messages 2. Receive 2.1. Receive arterial device status information continuously Receive DMS message data as information changes Receive roadway weather data as needed Receive transit data (e.g. position, route, stop, schedule, arrival, and departure.). 3. Transmit 3.1. Transmit arterial traffic data, CCTV video and camera control 3.2. Transmit CCTV control data as needed. Type 2 Centers Typical data requirements for a Type 2 center are listed below. Iteris, Inc. 24

28 1. Receive or transmit arterial traffic data (e.g. timing data, traffic demand data, congestion data, detection data, etc) from Type 1 centers at regular intervals or upon request. 2. Receive or transmit arterial incident data (e.g. data, time, location, type, blockage pattern, duration, and status of incidents) from Type 1 centers. 3. Receive or transmit freeway / toll traffic data (e.g. demand data, congestion data, etc). 4. Receive or transmit freeway / toll incident data (e.g. date, time, location, type, blockage pattern, duration, and status of incidents) as needed. 5. Receive other freeway / toll event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) 6. Receive or transmit arterial DMS message data as information changes. 7. Receive or transmit Shawnee County 911 traffic event data (e.g. agency name, contact information, number of injuries and fatalities, property damages, number of vehicles involved, etc) 8. Receive or transmit other event data (e.g. construction, scheduled maintenance, lane closure, special events, etc.) as needed. 9. Receive or transmit arterial device status information continuously. 10. Receive or transmit roadway weather data as needed. 11. Receive or transmit transit data (e.g. position, route, stop, schedule, arrival, and departure.) 12. Receive or transmit emergency information. 13. Receive or transmit bus locations (transit or school). III. Connectivity Requirements 1. The Topeka-Shawnee County communications network for centers should be continuously available to participating agencies, 24 hours per day, 7 days per week. 2. The communications interface to the Topeka-Shawnee County network should be able to make use of an open architecture and common industry standards. 3. The network should be able to recover from cable cut or hub failure automatically. IV. Bandwidth Requirements 1. The Topeka-Shawnee County communications network should provide sufficient bandwidth for traffic data transmission for all signalized intersections controlled by the Type 1 Centers simultaneously. 2. If video is transmitted in digital format, the data rate for video transmission should be adjusted dynamically based on the available bandwidth. V. Design Requirements 1. In order to avoid duplication of investments in infrastructure, the Topeka- Shawnee County communications network should utilize existing infrastructure wherever available and feasible. Iteris, Inc. 25

29 2. Since the timeframe for the Topeka-Shawnee County Regional ITS Architecture is 20 years, the Topeka-Shawnee County communications network should be designed to support communications and system expansion for a minimum of 20- year period. 3. The network should have at least one alternate routing option to ensure uninterrupted operations during hub failure and maintenance downtime. 4. The latency (time between request and system response) of the communications network should be less than one second. 5. The network should support a modular design so that it can be incrementally increased or decreased in size with limited cost and risk as the need to add or remove equipment becomes necessary. 6. Communications equipment should be interchangeable and interoperable. 7. Communications equipment should be IP-addressable for ease of management Center-to-Field Communications Requirements In order to ensure that the current and future ITS projects in Topeka-Shawnee County follow the common communications and infrastructure protocol, it is important to establish some guidelines for C2F communications and interconnection requirements for each center. The following presents some specific C2F communications network requirements that Topeka- Shawnee County agencies should consider for their current and future ITS projects. I. Data Requirements There are several types of ITS devices that have been or will be deployed in the Topeka- Shawnee County. The specific data requirements for each type of devices are presented below. 1. Traffic Signals a. Support NTCIP Class B standards. b. Support once per second communications with traffic signal controllers. c. The minimum baud rate for signal communications is assumed to be 9,600 bits per second (bps) and preferably 19.2 kbps. d. Traffic signal data can be multi-dropped. e. The maximum number of traffic signal controllers on a 9.6 kbps channel should be four, and on a 19.2 kbps channel should be eight. f. In a digital system, each traffic signal controller should have its own IPaddress. 2. CCTV Cameras a. The communications network should support the transmission of National Television System Committee (NTSC) full motion video as well as camera control and status data. There should be 30 frames per second for full motion video. b. For IP NTSC full motion video, MPEG 2 or MPEG 4 compression standards should be used. c. At a minimum, CCTV camera control data should be transmitted on a 9.6 kbps channel. Iteris, Inc. 26

30 d. For analog transmission, each CCTV video should be transmitted on a dedicated communication channel. e. CCTV camera control data can be multi-dropped. f. In a digital system, each CCTV camera should have its own IP-address. g. The latency of a digital CCTV camera system should be less than one second. 3. Dynamic Message Signs (DMS) a. The communications network should support the transmission of DMS messages and control and status data. b. At a minimum, DMS signals should be transmitted on a 9.6 kbps or higher baud rate channel. c. DMS messages and control and status data can be multi-dropped. d. The maximum number of DMS on a 9.6 kbps or higher baud rate channel should be six. e. In a digital system, each DMS should have its own IP-address. 4. Other ITS Elements a. At a minimum, all other ITS elements should be transmitted on a 9.6 kbps or higher baud rate channel. II. Connectivity Requirements 1. C2F communications should be continuously available to the owner. 2. C2F communications and interface should be able to make use of an open architecture and industry standards. 3. C2F communications should be able to recover from communications failure automatically. III. Bandwidth Requirements 1. At a minimum, all data should be transmitted on 9.6 kbps baud rate channels and all video should be transmitted on Integrated Digital Service Network (ISDN) or equivalent channels. IV. Design Requirements 1. In order to avoid duplication of investments in infrastructure, all field devices should utilize as much existing communications infrastructure as possible. 2. A desired, but not required ability for each field element is to have at least one alternate routing option to ensure uninterrupted operations during communications failure or down time on one path. Iteris, Inc. 27

31 4.0 COMMUNICATIONS ALTERNATIVE ANALYSIS This analysis will discuss the various network architecture alternatives. Based on the recommended alternative, applicable communication technologies and media will be presented and analyzed. The final Topeka-Shawnee County ITS Communications Network will be presented in terms of recommended network architecture and communication technologies and media. 4.1 Network Architecture Network architecture consists of the configuration which is used to design and construct a communications network. Configuration is an arrangement of functional units of a communications network according to their number and nature and can be represented by a schematic description showing how those functional units are connected together. Network architecture can be described in both physical and logical ways. The physical architecture of a communications network shows the actual geometric layout of its elements and how those elements are connected together physically. Logical architecture describes the communications paths between elements of the network. In fact, logical links and connections can also be implemented as physical links and connections. The physical architecture of a communications network is usually based on the identification of the number and geographical locations of the connecting field elements. Such information is usually available during the conceptual or preliminary design stage. For the purpose of ITS communications in Topeka-Shawnee County, this analysis will focus on developing logical architecture alternatives for C2C communications only. Strategies for C2F communications should be developed in each Topeka-Shawnee County agency s individual communications master plan and should comply with the C2C communications requirements presented in this regional ITS communications plan. The most common types of network configuration are star, tree, ring, and mesh. A star network is designed with the communication links emanating from the central point of communications concentration, such as a center. Each communication link will be directly connected to the FIELD ELEMENTS FIELD ELEMENTS TYPE 1 CENTER TYPE 2 CENTER TYPE 1 CENTER FIELD ELEMENTS TYPE 1 CENTER TYPE 2 CENTER Figure 4.1: Star Network (Example) FIELD ELEMENTS Communication link FIELD ELEMENTS network elements, for example a device or a center. Figure 4.1 illustrates the concept of a star network. Iteris, Inc. 28

32 The tree configuration is a variation of the star network. It works similar to the star configuration except that communication links will emanate from both the center and communication hubs. In addition to the option to connect to the center directly, the tree network allows field devices to be connected to the center via a communication hub. These field devices can be Figure 4.2: Tree Network (Example) daisy-chained, multiplexed, or aggregated. Figure 4.2 illustrates the concept of a tree network. Elements of a ring network are connected together by a uni-directional communication link to form a closed loop. As a result, data will travel from one element in the loop to the next in a single direction around the loop. If any link between two elements is cut, there will be no communication between the two elements and the devices attached to those two elements. This is why this configuration is often called an unprotected-ring. Figure 4.3 illustrates the concept of an unprotected ring. TYPE 1 CENTER TYPE 1 CENTER Direction of data transmission TYPE 1 CENTER TYPE 1 CENTER Communication link Figure 4.3: Unprotected Ring Network (Example) Iteris, Inc. 29

33 An unprotected ring can be configured as a protected ring by adding another unprotected ring whereby data is able to travel in the opposite direction. During the normal operation of the network, only the primary ring will be activated. When the medium between two elements is cut or not available, the primary data flow is blocked and the secondary ring will be activated automatically. Then, data will travel in the reverse direction around the loop to its destination. This allows each element on the communications network to communicate with every other element even when the medium or the communication hub fails. Figure 4.4 illustrates the concept of a protected ring. TYPE 1 CENTER A mesh network is a configuration in which there are at least two elements with two or more communication paths between them. In the full mesh configuration, each element on the communications network is connected directly to each of the others. In the partial TYPE 1 CENTER mesh configuration, some elements are connected to all the others, and some are connected only to those other elements with which they exchange the most data. Figure 4.5 illustrates the concept of a partial mesh network. TYPE 1 CENTER Primary Direction of data transmission TYPE 1 CENTER TYPE 1 CENTER Primary Communication link Secondary Communication link Figure 4.4: Protected Ring Network (Example) TYPE 1 CENTER TYPE 1 CENTER TYPE 1 CENTER Figure 4.5: Mesh Network (Example) TYPE 1 CENTER Primary Communication link Secondary Communication link Since the recommendation for the Topeka-Shawnee County communications is to utilize the City of Topeka IT network where available, particularly for the Type 1 centers, and establish direct communications to the Topeka TMC for Type 2 centers, the network architecture for the Topeka-Shawnee County region will be a combination of Mesh Network and Star Network (point-to-point communications). The City of Topeka IT network is comprised of a Mesh Network, and the communications between the Topeka TMC and the Type 2 centers will likely be a combination of fiber optic cable, leased line, or dial up using point to point communications. The following data and video communications alternatives are based on a combination of star, tree, ring, and mesh configurations. Iteris, Inc. 30

34 4.2 Communications Approach Based on the recommendation above to utilize the City of Topeka IT network to support communications between the Type 1 centers, this section presents the detailed approach to implementing the communications network Communication Approach Type 1 Centers The development of the Topeka-Shawnee County communications system to support communications between the Type 1 centers will be based on the following list of assumptions. 1. The TMC will act as the central point of data communication concentration. 2. Each Type 1 Center will receive a regional server to perform the following functions: a. Interface with the Type 1 agency s existing system. Such systems can be a traffic control system, DMS system, CCTV camera control system, or a combination of these individual subsystems. b. Collect data from the existing system. c. Convert collected data into a standard format that will be recognized by the regional server. d. Receive data from other regional servers. 3. The City of Topeka s Pyramids signal system software will serve as the regional signal software system. a. The server application will reside on the server at the Topeka TMC. b. Each Type 1 Center will receive a client application to support a Topeka- Shawnee County ITS workstation(s) at each Type 1 Center. c. The Pyramids system will interface with the field devices including traffic signal controllers, CCTV, DMS and system detectors. 4. Each Type 1 Center will receive a network switch / router that will interface with the City of Topeka IT network. 5. The communication network will be Ethernet-based to support IP communications to the field devices. a. Ethernet communications to the traffic signal controllers, requiring 1B modules on the 2070 controllers, an Ethernet module for Type 170E controllers or a serial to Ethernet converter (SLIP) for other Type 170 controllers. b. IP video and data from CCTV cameras utilizing MPEG2 or MPEG4 compression algorithms. c. Ethernet communications to other field devices such as DMS or system detectors. The communication link between a Type 1 Center and the field devices can utilize various media and technologies, such as Ethernet on fiber, analog video and data that is converted to Ethernet-based communications at a hub, dedicated leased line, spread spectrum or broadband wireless, such at the planned Wi-Fi network to be implemented by the City of Topeka IT. Iteris, Inc. 31

35 This approach should be relatively easy and inexpensive to deploy because the Type 1 Centers will utilize the existing City of Topeka IT network and only require slight modification of the network to support the Type 1 Centers, including the installation of a regional server, workstation and network switch/router. Figure 4.6 illustrates the concept of communications approach for Type 1 Centers Communication Approach Type 2 Centers The Type 2 centers will be connected to the City of Topeka regional server to transmit or receive information. Again, the communication link between those centers and the network switch or router can utilize the same or different media and technologies as the backbone, being the City of Topeka IT network, fiber optic cable, leased line, phone drop or private internet website. The development of the Topeka-Shawnee County communications system to support communications between the Type 2 centers will be based on the following list of assumptions. 1. Type 2 centers will be connected to the regional server at the Topeka TMC. 2. The Topeka TMC will act as the central point of data communication concentration. 3. Each Type 2 Center will receive a remote workstation to perform the following functions: a. Transmit or receive information from the Topeka-Shawnee County regional server. b. View Topeka-Shawnee County regional information map. 4. The communication interface between the Type 2 Centers and the Topeka TMC will vary by center. a. Communication may be implemented via the City of Topeka IT network for Type 2 Centers with access to the network. b. Direct fiber optic cable connection can be implemented. c. Leased line or dial up communications for Type 2 Centers outside of the City of Topeka-Shawnee County region. d. Internet-based connection via private network connection. The level of complexity to complete each Type 2 Center connection will vary based on means of communication utilized as noted above. This information will need to be determined as part of this project based on discussions with the project stakeholders. Figure 4.7 illustrates the concept of communications approach for Type 2 Centers. Type 1 Centers are shown for completeness. Iteris, Inc. 32

36 ITS Communication Plan Figure 4.6: Communications Approach Type 1 Centers Iteris, Inc. 33

37 ITS Communication Plan Figure 4.7: Communications Approach Type 2 Centers Iteris, Inc. 34