19.06.2014 Views

Strategic Deployment Plan - sacog

Strategic Deployment Plan - sacog

Strategic Deployment Plan - sacog

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

EXECUTIVE SUMMARY<br />

Intelligent Transportation Systems (ITS)<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> (SDP)<br />

for the Sacramento Region<br />

Prepared for:<br />

Prepared by:<br />

September 2005<br />

097860000<br />

Copyright © 2005, Kimley­Horn and Associates, Inc.


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Executive Summary<br />

This executive summary is a high­level overview of the Intelligent Transportation Systems<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> for the Sacramento Region. For technical details and further discussion<br />

please refer to the main report and appendices, which are available at the SACOG ITS <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> website at http://www.<strong>sacog</strong>.org/websites/kimley­horn/.<br />

This executive summary contains the following sections:<br />

• Background of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> and Intelligent Transportation Systems (ITS)<br />

• Key Project Stakeholders<br />

• Goals for Regional Growth<br />

• Key Results of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

• Mainstreaming Advanced Technology into planning and project development initiatives<br />

• Outline of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

• Steps for Successful Implementation of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

What is ITS?<br />

For stakeholders who are unfamiliar with the advanced technologies of Intelligent Transportation<br />

Systems, the following is a general definition of ITS:<br />

Intelligent Transportation Systems (ITS) are a collection of roadway, transit, communications,<br />

and computer technologies that are used to improve the operation of roadway and transit<br />

systems. ITS make real­time traveler information available to the public so that better decisions can be<br />

made about when and how to travel. Freight and business services are improved with the ability to<br />

monitor roadways and re­route vehicles if necessary. ITS also improve mobility and safety for<br />

pedestrians and bicyclists using technologies that detect and adapt intersection signals for these<br />

travelers. While much of the ITS technologies are "behind the scenes," some examples that can been<br />

seen around the region include: ramp meters on highway on­ramps, message signs, video cameras,<br />

enhanced bus service, and 511.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

1 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Introduction<br />

The Intelligent Transportation Systems <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> for the Sacramento Region is a<br />

planning document that defines how advanced technologies can support the transportation and land<br />

use planning initiatives in the region to help planners to achieve the region’s planning objectives.<br />

Results of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will help determine how and when to incorporate<br />

advanced technology in transportation projects, and which technologies to use. By integrating the<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> with other regional planning initiatives such as the Sacramento Region<br />

Blueprint and the Metropolitan Transportation <strong>Plan</strong>, and by incorporating lessons learned when<br />

other agencies deploy similar technologies, the planning partners can realize the benefits from<br />

coordination, shared investments, and multimodal integration while working towards common<br />

regional goals. The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> suggests some tools and techniques for including<br />

advanced technologies in the planning and deployment stages of regional development, and key<br />

strategies for building upon the existing regional advanced technology framework.<br />

The central principle of the project is the interrelation of Intelligent Transportation Systems (ITS)<br />

with transportation and land use planning. All of these areas of development are ultimately<br />

concerned with region­wide effectiveness in achieving broad standard­of­living goals related to<br />

growth, mobility, accessibility, convenience, and safety. Considering alternate mode mobility in<br />

every development encourages developers to incorporate design elements which are more inclusive<br />

(for example, more pedestrian­friendly entrances or walkways to transit). Linking transit<br />

operations to jobs, services and housing is another key consideration in projects, affecting the<br />

planning of both (for example, modification of transit routes as need grows due to new<br />

developments, or guiding development to first take advantage of proximity to transit corridors). A<br />

useful resource considering ITS deployment strategies for sustainable and livable communities is<br />

Roads Less Traveled published by Public Technology, Incorporated (PTI) and available from<br />

FHWA at http://www.fhwa.dot.gov/tfhrc/safety/ pubs/its/generalits/rdless.pdf.<br />

Advanced technologies can take many forms including the areas of traffic monitoring, data<br />

collection and dissemination, safety, transit service, and walkability/bikeability. These<br />

technologies and solutions are meant to supplement other transportation projects to enhance the<br />

benefits being provided by the transportation system. A few examples of advanced technologies<br />

are shown in Figure 1 on the following page.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

2 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Figure 1 –Examples of ITS Technologies<br />

Bicycle and Pedestrian Solutions<br />

Pedestrian Crossing Signal Head Pedestrian Crossing Detection Bicycle Video Detection<br />

Traveler Information<br />

Sacramento Region 511<br />

Changeable Message Sign<br />

Transit<br />

Real­Time Train Arrival and<br />

Departure Times<br />

Queue Jumper Lane<br />

Electronic Fare Collection<br />

Roadway Management<br />

Bus Rapid Transit<br />

Ramp<br />

Metering<br />

CCTV Camera<br />

Transportation Management<br />

Center (TMC)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

3 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Stakeholders<br />

Throughout this project process, many stakeholders were solicited for input through a consistent<br />

outreach effort. The wide range of stakeholders included cities, counties, SACOG, Caltrans, transit<br />

agencies, environmental groups, bicycle and pedestrian coalitions, citizen groups, transportation<br />

and land use planners, engineers, consultants and concerned residents. Anyone having an interest<br />

in deployment of technology in transportation projects participated in the project. Transportation<br />

agencies and organizations in charge of planning, building and operating transportation systems in<br />

the region were especially encouraged to attend.<br />

The intent of including non­ITS stakeholders was to bring advanced technology to the forefront of<br />

consideration when other smart growth and capital improvements are being planned. This project<br />

raised the awareness among non­ITS stakeholders of the benefits that can be achieved by including<br />

advanced technology in planning and development activities as a way to achieve the smart growth<br />

objectives of the region.<br />

Principles for Regional Growth<br />

As part of the Metropolitan Transportation <strong>Plan</strong>, the region has<br />

already developed ten overarching transportation­related goals<br />

which were used as the basis for the region’s ITS Vision<br />

developed by the ITS Partnership. The goals emphasize quality<br />

of life, which in the context of transportation and advanced<br />

technologies pertains to improving air quality, enhancing transit<br />

service, improving alternate mode opportunities (bicycles,<br />

walking, transit), and improving mobility along major corridors. In addition, ITS can support<br />

Homeland Security initiatives in preparing for, preventing, and monitoring terrorist activities by<br />

creating a safer and better­equipped transportation network. Throughout the <strong>Strategic</strong> <strong>Deployment</strong><br />

<strong>Plan</strong> development, these transportation­related goals helped assess the status of the region’s current<br />

planning outlook and guided the prioritization of projects.<br />

The Sacramento Region Blueprint: Transportation and Land Use Study evaluated and created a<br />

scenario for how the region expects to grow to the year 2050. The emphasis was on Smart<br />

Growth principles such as the following, reflected throughout Blueprint and throughout numerous<br />

General <strong>Plan</strong>s, to guide future development:<br />

• Provide a variety of transportation choices<br />

• Take advantage of compact development<br />

• Use existing assets<br />

• Mixed land uses especially near transit<br />

• Encourage distinctive, attractive communities with quality design<br />

Where and how does the<br />

region expect to grow in<br />

10 years, 20 years, and<br />

beyond?<br />

The goals of these two initiatives, the MTP and Blueprint, were closely considered as the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> was prepared. The first place that these goals are discussed is with the Updated<br />

ITS Vision. Each ITS Vision goal was expanded to include a list of objectives that can help<br />

achieve those goals. This was an interim step that fed into the Gap Assessment to determine<br />

whether the ITS Vision of the region was being fulfilled.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

4 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Overarching ITS Priorities<br />

The stakeholders provided input regarding the types of ITS applications they wanted to see in the<br />

Sacramento Region and which ones they felt were more important than others. Based on the<br />

discussions, the following high level applications are guidelines for future ITS enhancement and<br />

focus in the region:<br />

• Completion of STARNET Wide Area Network –Provide communications link between<br />

agencies to allow exchange of data and video.<br />

• Expand 511 traveler information –Provide additional traveler information services to the<br />

public such as multimodal route planning and guidance.<br />

• Transit Service Enhancements (Automatic Vehicle Location/GPS systems) –Enable Bus<br />

Rapid Transit (BRT); and provide the ability to broadcast real­time vehicle location and<br />

stop arrival information.<br />

• Bicycle and pedestrian projects –Enhance safety of alternative modes for reliable<br />

mobility.<br />

• Additional SMART Corridors –Provide traffic monitoring capabilities along major<br />

arterials; enable Bus Rapid Transit (BRT).<br />

• Enhanced transportation system operation –Enhance signal operations (timing) and<br />

proactive traffic management activities.<br />

• Freight Movement –Provide coordinated operations between transportation management<br />

and freight operations to enhance goods movement through the region.<br />

• Emergency Service Coordination – Provide coordinated planning and operations of<br />

incident management between emergency services and traffic management.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

5 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Key Results of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

The strategic deployment of advanced technology will help the Sacramento region realize the<br />

objectives and goals articulated above. While advanced technologies can be deployed as standalone<br />

project, the greatest benefits can be seen when they are deployed in conjunction with other<br />

capital improvement projects. Advanced technologies are not meant to drive development. There<br />

are four key elements of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> that provide tools to assist the stakeholders<br />

in deploying advanced technologies to facilitate the smart growth initiatives of the region.<br />

ITS Solutions Toolbox<br />

How do stakeholders know how and when to deploy technologies? Which technologies should<br />

be deployed and how much will they cost? The ITS Solutions Toolbox was developed as part of<br />

the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> to be used as a quick reference tool for planning and programming<br />

decision­makers. This set of two tables offers possible technology solutions, descriptions, and<br />

deployment considerations; and planning level cost estimates for installation, operations, and<br />

maintenance for every type of advanced technology. The first table identifies the type of ITS<br />

solutions that can be considered for various types of capital improvement projects. The second<br />

table expands on those solutions to identify additional issues as an ITS solution is considered.<br />

This Toolbox provides a good starting point and high­level comparison tool for stakeholders<br />

considering the deployment of advanced technology.<br />

A sample of the Toolbox is shown in Figure 2 below; the full table appears at the end of Section<br />

6 of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

Figure 2 –Sample of ITS Solutions Toolbox (Bicycle Detection)<br />

Project Types<br />

• Bicycle Lanes<br />

• At­Grade Trail<br />

Crossings<br />

• Traffic Signals<br />

• Traffic Signal<br />

Modifications<br />

Cost Considerations<br />

Depends on technology and<br />

installation/ mounting<br />

requirements<br />

Solution Descriptions<br />

Detection device, cabling to<br />

signal cabinet, power to detect<br />

bicycles at intersections<br />

Benefits to Project or Agency<br />

(of Concurrent ITS <strong>Deployment</strong>)<br />

• If added to another project,<br />

disruption to traffic is minimized<br />

• Reliable source of traffic data<br />

<strong>Deployment</strong><br />

Considerations<br />

Unit<br />

Cost<br />

• Detection technology<br />

(in­pavement vs. nonintrusive).<br />

$3,000­<br />

$10,000<br />

per<br />

location<br />

O & M<br />

Cost Per<br />

Year<br />

$1,000 per<br />

location<br />

Benefits to Public<br />

(of ITS <strong>Deployment</strong>)<br />

• Real­time traffic flow data could be<br />

available<br />

• No privacy issues compared with other<br />

technologies<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

6 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

<br />

ITS Architecture<br />

The ITS Architecture is a process that defines how agencies and systems are interrelated or<br />

interconnected. There is a national level architecture, a California statewide architecture, and<br />

regional and local architectures throughout the state. Once an ITS Architecture is defined, it<br />

helps planners and project developers ensure that a complete system is deployed, rather than just<br />

an individual component, and it helps ensure that adjoining systems are compatible. Establishing<br />

and following an ITS architecture will increase the consideration for federal ITS funding.<br />

The diagram presented below is a simplified version of Figure 4.2 of the <strong>Strategic</strong> <strong>Deployment</strong><br />

<strong>Plan</strong>.<br />

Figure 3 –Simplified Regional ITS Architecture<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

7 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

<br />

Gap Assessment<br />

As part of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>, the prior state of ITS in Sacramento was assessed.<br />

With a focus on the ITS Vision and existing, planned, and programmed projects, there are several<br />

key observations that became the emphasis of the deployment plan based on stakeholder input.<br />

o Additional opportunities need to be identified to include ITS solutions in more<br />

bicycle and pedestrian projects.<br />

o New projects have been defined in Section 7 of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> for<br />

ITS Vision objectives that do not currently have an existing, planned, or programmed<br />

project that matches that objective including:<br />

• Improve access to and reliability of alternate modes;<br />

• Improve bicycle and pedestrian safety;<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711,<br />

audio, multi­lingual) and varying media (i.e., web, TV, in­vehicle, 511, kiosks);<br />

• Develop an ITS education program in the region;<br />

o New projects have been defined in Section 7 of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> for<br />

elements of the ITS Architecture where projects have not been defined in the<br />

Sacramento region:<br />

• Transit Maintenance (APTS06)<br />

• Emissions Monitoring and Management (ATMS11)<br />

• Standard Railroad Grade Crossing (


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Project Prioritization<br />

The Sacramento ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> includes project prioritization defined by the<br />

stakeholders. It identifies the recommended order of deployment of ITS central systems, projects,<br />

or infrastructure based on stakeholder preference according to the following categories:<br />

• Short­Term Projects (currently deployed or planned for deployment in the next 5 years);<br />

• Mid­Term Projects (considered for deployment in the 5­10 year timeframe);<br />

• Long­Term Projects (considered for deployment in the 10­20 year timeframe); and<br />

• Not planned for deployment at this time.<br />

The following is a select summary list of the types of high­priority projects for the Sacramento<br />

Region. This information was taken from Section 7.1 of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>:<br />

High­Priority Projects (Short­Term)<br />

• Develop interagency communications via STARNET<br />

• Expand existing 511 traveler information system<br />

• Expand Caltrans Traffic Operations System with ramps meters,<br />

closed­circuit television cameras, changeable message signs,<br />

and vehicle detection along strategic freeway corridors<br />

• Enhance transit safety and operations through increased<br />

surveillance and improved services by deploying queue jumper<br />

lanes, automatic vehicle locating, and transit priority<br />

• Improve pedestrian and bicycle safety and mobility by deploying<br />

equipment to raise awareness of pedestrian presence<br />

• Expand local fiber and copper communications infrastructure<br />

• Construct traffic management centers<br />

• Commercial Vehicle Operations – Goods Movement<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

9 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Mainstreaming Advanced Technologies<br />

“Mainstreaming” refers to an intentional process to systematically and strategically include<br />

advanced technologies in all aspects of transportation and land use planning whether it is being<br />

done on a local, corridor or regional level, or specifically tied to projects. The goal of<br />

mainstreaming is to ensure that technology strategies are an integral component of the metropolitan<br />

transportation planning and programming process and are incorporated into the Metropolitan<br />

Transportation <strong>Plan</strong> (MTP) and Metropolitan Transportation Improvement Program (MTIP).<br />

Strategies that assist in “mainstreaming” ITS include the use of committees with regional<br />

stakeholders; education of policymakers, staff and the public; inclusion of ITS in planning<br />

documents; a program of regional projects; and methodologies to encourage consideration of<br />

advanced technology into transportation investment alternatives.<br />

There are a number of additional steps that can be taken to raise the consideration level of advanced<br />

technologies with other transportation opportunities, including:<br />

1. Utilize the priority list presented in Section 7 of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> to program<br />

projects that will capitalize on the benefits of advancing the ITS program in the region.<br />

2. Develop an awareness and education program on the benefits of ITS in general and<br />

specifically on projects deployed in the region.<br />

3. Link ITS solutions to the Blueprint Preferred Scenario using the ITS Solutions Toolbox.<br />

4. Utilize the ITS Solutions Toolbox in all planning and programming activities.<br />

5. Incorporate components of the SDP into the main body of the next Metropolitan<br />

Transportation <strong>Plan</strong> with a focus on outcomes that benefit users of the system.<br />

6. Schedule a joint meeting of the ITS Partnership and Regional <strong>Plan</strong>ning Partnership at least<br />

annually.<br />

7. Consider separating the ITS Partnership into two groups –a technical working group and a<br />

policy steering group and identify the roles of each group.<br />

8. Create incentives for incorporating and maintaining advanced technology solutions in the<br />

MTP and MTIP projects that can demonstrate a measurable outcome.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

10 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Outline of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Many of the sections found in this <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> are consistent with the federal<br />

guidelines. There are also several sections that make this plan unique. The individual elements of<br />

the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> project are outlined below and can be found on the project website<br />

at http://www.<strong>sacog</strong>.org/websites/kimley­horn/.<br />

• Section 2: Updated ITS Vision Statement describes the updated Sacramento region’s ITS<br />

Vision (Goals and Objectives) based on input from a representative cross­section of<br />

stakeholders.<br />

• Section 3: Gap Assessment summarizes existing, planned and programmed ITS deployments<br />

and how they fit in with the ITS Vision and ITS Architecture, so that “gaps”can be identified.<br />

• Section 4: Sacramento Regional ITS Architecture completes the initial effort of the 2001<br />

Sacramento Regional ITS Architecture.<br />

• Section 5: <strong>Plan</strong> Maintenance outlines an ongoing maintenance strategy for the Sacramento<br />

ITS architecture to ensure that the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is implemented and kept up­todate.<br />

• Section 6: ITS Solutions Toolkit provides a useable decision­making tool for ITS planners<br />

and deploying agencies in the Sacramento region.<br />

• Section 7: <strong>Deployment</strong> outlines prioritized Sacramento region projects, benefits, and costs,<br />

along with a discussion of the recommended stakeholder agreements.<br />

• Section 8: Next Steps highlights recommendations and future actions for ITS deployment<br />

based on the inputs of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> process.<br />

• Appendices provide detailed results and summaries of stakeholder input and other data.<br />

o APPENDIX A: Outreach <strong>Plan</strong><br />

o APPENDIX B: Sacramento Region ITS Vision Update<br />

o APPENDIX C: Existing Conditions Summary Report<br />

o APPENDIX D: Project Inventory<br />

o APPENDIX E: Gap Assessment<br />

o APPENDIX F: Performance Criteria<br />

o APPENDIX G: Market Packages mapped to Elements<br />

o APPENDIX H: Customized Market Package Diagrams<br />

o APPENDIX I: Equipment Packages mapped to Elements<br />

o APPENDIX J: Functional Requirements by Elements<br />

The flowchart below in Figure 3 demonstrates how the SACOG Blueprint, the Metropolitan<br />

Transportation <strong>Plan</strong>, and the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> interrelate to result in a unique process that<br />

promotes integrated, coordinated planning and project development in the Sacramento region.<br />

While some plans are more oriented toward land use planning (shown in pink), others are oriented<br />

more toward transportation planning (shown in blue). Nonetheless, all of these planning<br />

documents have an impact on each other and take into account transportation and land use efforts.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

11 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Steps for Successful Implementation<br />

As with other recent regional planning documents, this report can be an active resource that builds<br />

upon other major regional planning initiatives such as the Sacramento Region Blueprint and the<br />

Metropolitan Transportation <strong>Plan</strong>. To continue making progress toward transportation­related and<br />

land use­related Goals developed in the initial stages this project, the following Next Steps are<br />

suggested:<br />

MOU: Execute a Memorandum of Understanding as soon as possible for<br />

implementing the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

Early Winners: The responsible agencies should follow up on Early Winner<br />

projects in their jurisdiction to identify opportunities to provide greater benefit<br />

and cost savings by implementing them.<br />

Commercial Vehicle Operations (CVO):<br />

As ITS mainstreaming moves<br />

forward, engage stakeholders from freight agencies and goods movement<br />

organizations (such as the Port of Sacramento).<br />

Feed into Blueprint Next Steps: The ITS Solutions Toolbox should be linked<br />

to, or be adopted as one of the “tools”in the Blueprint Toolbox.<br />

Maintenance: Execute the conditions of the ITS Maintenance <strong>Plan</strong> to ensure<br />

that the ITS Architecture will continue to be updated.<br />

Mainstreaming: As part of the ITS Partnership or other group of stakeholders,<br />

set a schedule for discussing the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> on a regular basis<br />

to ensure success.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

12 Executive Summary<br />

September 2005


INTELLIGENT TRANSPORTATION SYSTEMS<br />

STRATEGIC DEPLOYMENT PLAN<br />

Figure 3 –Interrelationships of <strong>Plan</strong>ning Documents in Sacramento Region<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

13 Executive Summary<br />

September 2005


Intelligent Transportation Systems<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

for the Sacramento Region<br />

FINAL REPORT<br />

Prepared for:<br />

Prepared by:<br />

September 2005<br />

097860000<br />

Copyright © 2005, Kimley­Horn and Associates, Inc.


TABLE OF CONTENTS<br />

LIST OF ACRONYMS ............................................................................................................................. 4<br />

LIST OF WEB RESOURCES ......................................................... 6<br />

1 INTRODUCTION.............................................................................................................................. 7<br />

1.1 <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Background .......................................................................... 7<br />

1.2 Project Overview and Deliverables .................................................................................. 7<br />

1.3 ITS and the Connection with Land Use and Transportation <strong>Plan</strong>ning........................... 8<br />

1.4 ITS and the Preferred Blueprint Scenario ..................................................................... 10<br />

1.5 ITS and Homeland Security ........................................................................................... 10<br />

1.6 USDOT Regional ITS Architecture Guidance ............................................................... 12<br />

1.7 Sacramento Region <strong>Plan</strong>ning Documents –How Do They All Fit Together?............... 12<br />

1.8 Document Overview........................................................................................................ 13<br />

2 VISION STATEMENT..................................................................................................................... 14<br />

2.1 Original Sacramento Region ITS Vision........................................................................ 14<br />

2.2 Updated Sacramento Region ITS Vision........................................................................ 14<br />

3 GAP ASSESSMENT........................................................................................................................ 18<br />

3.1 ITS Existing Conditions Summary Report .................................................................... 18<br />

3.2 Overarching ITS Priorities............................................................................................. 21<br />

3.3 Gap Assessment .............................................................................................................. 22<br />

3.4 Topics for Further Update Consideration...................................................................... 24<br />

4 SACRAMENTO REGIONAL ITS ARCHITECTURE .......................................................................... 26<br />

4.1 Scope................................................................................................................................ 26<br />

4.2 Stakeholders.................................................................................................................... 27<br />

4.3 Operational Concepts ..................................................................................................... 31<br />

4.4 Inventory......................................................................................................................... 37<br />

4.5 Market Packages and Performance Criteria Measures................................................. 54<br />

4.6 Interfaces and Information Exchanges .......................................................................... 63<br />

4.7 Functional Requirements................................................................................................ 68<br />

4.8 Standards Identification ................................................................................................. 69<br />

5 PLAN MAINTENANCE................................................................................................................... 75<br />

5.1 Introduction .................................................................................................................... 75<br />

5.2 Methodology and Analysis.............................................................................................. 76<br />

5.3 Maintenance Roles and Responsibilities......................................................................... 78<br />

5.4 Frequency of Updates ..................................................................................................... 81<br />

5.5 What Architecture Components will be Updated? ........................................................ 81<br />

5.6 Identifying and Implementing a Change........................................................................ 83<br />

5.7 Regional Adjacencies and Overlap Issues ...................................................................... 84<br />

5.8 Version Control............................................................................................................... 85<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

1 Final Report<br />

September 2005


6 ITS SOLUTIONS TOOLBOX........................................................................................................... 86<br />

6.1 SACOG ITS Solutions Toolbox ...................................................................................... 86<br />

7 DEPLOYMENT ............................................................................................................................ 117<br />

7.1 Project Prioritization .....................................................................................................117<br />

7.2 Early Winners ................................................................................................................125<br />

7.3 Gap Resolution...............................................................................................................130<br />

7.4 Stakeholder Agreements................................................................................................135<br />

7.5 Mainstreaming ...............................................................................................................138<br />

8 NEXT STEPS ............................................................................................................................... 141<br />

TABLE OF APPENDICES<br />

APPENDIX A:<br />

APPENDIX B:<br />

APPENDIX C:<br />

APPENDIX D:<br />

APPENDIX E:<br />

APPENDIX F:<br />

APPENDIX G:<br />

APPENDIX H:<br />

APPENDIX I:<br />

APPENDIX J:<br />

Outreach <strong>Plan</strong><br />

Sacramento Region ITS Vision Update<br />

Existing Conditions Summary Report<br />

Project Inventory<br />

Gap Assessment<br />

Performance Criteria<br />

Market Packages mapped to Elements<br />

Customized Market Package Diagrams<br />

Equipment Packages mapped to Elements<br />

Functional Requirements by Elements<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

2 Final Report<br />

September 2005


TABLE OF FIGURES<br />

Figure 1.1: <strong>Plan</strong>ning Process .............................................................................................................10<br />

Figure 1.2: <strong>Strategic</strong> Development Process Flow Diagram...............................................................13<br />

Figure 3.1: Gap Assessment related to ITS Vision and Projects ......................................................18<br />

Figure 4.1: Geographic Scope of Architectures ................................................................................27<br />

Figure 4.2: Sacramento Regional ITS Architecture System Interconnect Diagram........................64<br />

Figure 4.3: Example Customized Market Package...........................................................................65<br />

Figure 4.4: Example of Architecture Flows between Elements ........................................................67<br />

TABLE OF FIGURES<br />

Table 3.1: Background Documents for this SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> ....................19<br />

Table 4.1: Stakeholders......................................................................................................................28<br />

Table 4.2: Roles and Responsibilities ................................................................................................32<br />

Table 4.3: Inventory by Stakeholder.................................................................................................38<br />

Table 4.4: Inventory Sorted by Entity...............................................................................................48<br />

Table 4.5: Market Package Prioritization.........................................................................................54<br />

Table 4.6: Performance Measures.....................................................................................................58<br />

Table 4.7: Applicable ITS Standards ................................................................................................71<br />

Table 4.8: Individual Standards within each Group.........................................................................72<br />

Table 5.1: Project Stakeholders.........................................................................................................80<br />

Table 5.2: List of Architecture Elements to be Updated...................................................................82<br />

Table 5.3: Interregional Adjacencies and Overlap by Region..........................................................84<br />

Table 6.1: MTP Sample Projects that can benefit from Project Example #1...................................87<br />

Table 6.2: MTP Sample Projects that can benefit from Project Example #2...................................88<br />

Table 6.3: MTP Sample Projects that can benefit from Project Example #3...................................89<br />

Table 6.4: MTP Sample Projects that can benefit from Project Example #4...................................89<br />

Table 7.1: Project Sequencing ­ Short Term Projects (0­5 years) ..................................................118<br />

Table 7.2: Project Sequencing ­ Medium Term Projects (5­10 years)............................................121<br />

Table 7.3: Project Sequencing ­ Long Term Projects (10­20 years) ...............................................123<br />

Table 7.4: Early Winner Projects....................................................................................................125<br />

Table 7.5: Projects for Regional Architecture Gaps .......................................................................130<br />

Table 7.6: Projects for ITS Vision Gaps..........................................................................................134<br />

Table 7.7: Potential Agreements for the Sacramento Region.........................................................136<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

3 Final Report<br />

September 2005


LIST OF ACRONYMS<br />

AASHTO<br />

ASTM<br />

ATIS<br />

ATMS<br />

AVL<br />

BART<br />

CAD<br />

CCTV<br />

CHP<br />

CMS<br />

CV<br />

CVO<br />

DARC<br />

DMS<br />

DMV<br />

DPS<br />

DPW<br />

DSRC<br />

EMC<br />

EMS<br />

EOC<br />

ETMCC<br />

EV<br />

EVP<br />

FC<br />

FHWA<br />

FTP<br />

HAR<br />

HAZMAT<br />

HCRS<br />

HOT<br />

HOV<br />

HRI<br />

I/F<br />

IEEE<br />

IM<br />

IMMS<br />

ITS<br />

ISP<br />

ITE<br />

ITS<br />

LRT<br />

MCM<br />

MCV<br />

MDT<br />

American Association of State Highway and Transportation Officials<br />

American Society for Testing and Materials<br />

Advanced Travel Information System<br />

Advanced Traffic Management System<br />

Automated Vehicle Location<br />

Bay Area Rapid Transit<br />

Computer Aided Dispatch<br />

Closed­Circuit Television<br />

California Highway Patrol<br />

Changeable Message Signs<br />

Commercial Vehicle<br />

Commercial Vehicle Operations<br />

Data Radio Channel<br />

Dynamic Message Sign<br />

Department of Motor Vehicles<br />

Department of Public Safety<br />

Department of Public Works<br />

Dedicated Short Range Communications<br />

Emergency Management Center<br />

Emergency Medical Services<br />

Emergency Operations Center<br />

External TMC Communication<br />

Emergency Vehicle<br />

Emergency Vehicle Preemption<br />

Fare Collection<br />

Federal Highway Administration<br />

File Transfer Protocol<br />

Highway Advisory Radio<br />

Hazardous Materials<br />

Highway Condition Reporting System<br />

High Occupancy Toll<br />

High Occupancy Vehicle<br />

Highway­Rail Intersections<br />

Interface<br />

Institute of Electrical and Electronics Engineers<br />

Incident Management<br />

Incident Management Message Sets<br />

Intelligent Transportation Systems<br />

Information Service Provider<br />

Institute of Transportation Engineers<br />

Intelligent Transportation System<br />

Light Rapid Transit<br />

Maintenance and Construction Management<br />

Maintenance and Construction Vehicle<br />

Mobile Data Terminal<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

4 Final Report<br />

September 2005


MOU<br />

MS<br />

MTP<br />

NEMA<br />

NTCIP<br />

OB<br />

PI<br />

PSAP<br />

PTMS<br />

PWD<br />

RT<br />

RWIS<br />

SACOG<br />

SAE<br />

SDO<br />

SDP<br />

SIC<br />

STARNET<br />

STIC<br />

TCIP<br />

TEA­21<br />

TM<br />

TMC<br />

TMDD<br />

TOC<br />

TSP<br />

USDOT<br />

VID<br />

WIM<br />

Memorandum of Understanding<br />

Message Sets<br />

Metropolitan Transportation <strong>Plan</strong><br />

National Electrical Manufacturers Association<br />

National Transportation Communications for ITS Protocol<br />

On­board<br />

Passenger Information<br />

Public Safety Answering Point<br />

Public Transportation Management System<br />

Public Works Department<br />

Regional Transit<br />

Road Weather Information System<br />

Sacramento Area Council of Governments<br />

Society of Automotive Engineers<br />

Standards Development Organization<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Signal Interconnect Cable<br />

Sacramento Transportation Area NETwork<br />

Subcarrier Traffic Information Channel<br />

Transit Communication Interface Protocol<br />

Transportation Equity Act for the 21st Century<br />

Traffic Management or Transportation Management<br />

Traffic Management Center or Transportation Management Center<br />

Traffic Management Data Directory<br />

Traffic Operations Center<br />

Transit Signal Priority<br />

United States Department of Transportation<br />

Video Image Detection<br />

Weigh­in­Motion<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

5 Final Report<br />

September 2005


LIST OF WEB RESOURCES<br />

This ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is a living document. Throughout this report, the symbol<br />

will direct the reader to websites containing related reports and more detailed information.<br />

Although this ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is designed to be useful on its own electronically or in<br />

printed format, stakeholders are encouraged to make active and frequent reference to the major planning<br />

documents for the Sacramento region, and to use this document in tandem with those documents and<br />

related updates on the websites below.<br />

• ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> –The project website for this report<br />

http://www.<strong>sacog</strong>.org/websites/kimley­horn/<br />

This SDP was developed to compliment these existing Sacramento region documents:<br />

• Blueprint ­ The Sacramento Region Blueprint: Transportation/Land Use Study<br />

http://www.sacregionblueprint.org<br />

• The Metropolitan Transportation <strong>Plan</strong><br />

http://www.<strong>sacog</strong>.org/mtp/<br />

The following is a list of the website references which appear throughout this report:<br />

• USDOT ITS Program: http://www.its.dot.gov/<br />

• ITS America: http://www.itsa.org/<br />

• National Transportation Operations Coalition: http://www.ntoctalks.com/<br />

• California PATH: http://www.path.berkeley.edu/<br />

• ITS DECISION Gateway: http://www.calccit.org/itsdecision/<br />

• National ITS Architecture: http://itsarch.iteris.com/itsarch/<br />

• California Statewide ITS Architecture: http://www.kimley­horn.com/CAArchitecture/<br />

• FHWA Toolbox for Regional Policy Analysis:<br />

http://www.fhwa.dot.gov/planning/toolbox/sacramento_overview.htm<br />

• Phase 1 of the California Goods Movement Action <strong>Plan</strong>:<br />

http://www.arb.ca.gov/gmp/docs/draftreport031805.pdf<br />

• Sacramento Regional ITS Architecture website:<br />

http://www.consystec.com/sacramento/web/_regionhome.htm<br />

• Guidance for Regional ITS Maintenance <strong>Plan</strong>s: www.kimley­horn.com/regionalguidance<br />

• Sacramento Region 511: http://www.sacregion511.org/<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

6 Final Report<br />

September 2005


1 INTRODUCTION<br />

1.1 <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Background<br />

This Intelligent Transportation Systems <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> replaces the 1996 “Early<br />

<strong>Deployment</strong> <strong>Plan</strong>” and updates the Sacramento “ITS Regional Architecture” which was completed<br />

in 2001. This <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will update work completed since the Early <strong>Deployment</strong><br />

<strong>Plan</strong> was released. This project addresses 23 CFR 940 of the Federal Highway Administration and<br />

Federal Transit Administration Policy for National ITS Architecture, and provides additional detail<br />

in the following areas: new subsystems, operational concept, system functional requirements,<br />

system interfaces, project sequencing, and agency operational agreements. The <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> will bring the Sacramento region into full compliance with National ITS<br />

Architecture requirements; provide a vision for ITS; outline a program prioritized projects; identify<br />

planning level probable costs; and establish a plan for managing, integrating and operating the ITS<br />

elements in the region that are to be implemented over a designated planning period.<br />

The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will also incorporate and build upon recent efforts by various local<br />

agencies and SACOG which demonstrate the importance of land use in planning for future<br />

transportation improvements, and the interrelation between land use and circulation. This <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> will represent a first effort to integrate ITS planning and ITS project deployment<br />

strategies within the broader transportation and land use planning efforts. The <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> will also address ways in which advanced technologies can improve mobility and<br />

air quality in the region. The link between land use and transportation is particularly emphasized<br />

in the wake of Blueprint (the Sacramento Region Blueprint: Transportation/Land Use Study), and<br />

it will be shown in this report how ITS deployment “fits into”and is consistent with Blueprint.<br />

1.2 Project Overview and Deliverables<br />

The individual elements of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> project are shown below. Throughout<br />

the project, many sections have been completed as separate deliverables. This document is the<br />

culmination of intermediate project tasks to present a comprehensive, usable document to guide<br />

future ITS deployment in the region.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

7 Final Report<br />

September 2005


SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Project<br />

TASK 1: DEVELOP OUTREACH PROGRAM<br />

• TASK 1.1: EXISTING CONDITIONS SUMMARY REPORT<br />

• TASK 1.2: DEVELOP OUTREACH PLAN<br />

TASK 2: PLANNING PROCESS<br />

• TASK 2.1: GAP ASSESSMENT<br />

• TASK 2.2: REFINE ITS VISION<br />

• TASK 2.3: MARKET PACKAGES<br />

• TASK 2.4: UPDATE REGIONAL ITS ARCHITECTURE<br />

TASK 3: STRATEGIC DEPLOYMENT PLAN<br />

• TASK 3.1: PROJECT SEQUENCING<br />

• TASK 3.2: AGREEMENTS<br />

• TASK 3.3: STRATEGIC DEPLOYMENT PLAN REPORT<br />

• TASK 3.4: EXECUTIVE SUMMARY<br />

TASK 4: MAINTENANCE PLAN<br />

• TASK 4.1: MAINTENANCE PLAN<br />

This and other deliverables can also be found on the<br />

SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> website:<br />

http://www.<strong>sacog</strong>.org/websites/kimley­horn/<br />

Throughout this report, the symbol will direct the reader to websites containing more detailed<br />

information and related reports. In this way stakeholders are encouraged to make active and<br />

frequent reference to the main planning documents for the Sacramento region.<br />

1.3 ITS and the Connection with Land Use and Transportation <strong>Plan</strong>ning<br />

Stakeholders in the SACOG region are in various stages of understanding, deploying and<br />

eventually mainstreaming ITS into the planning process. For stakeholders who are new to this<br />

advanced technology, ITS devices are a collection of roadway, transit, communications, and<br />

computer technologies that are used to improve the operation of roadway and transit systems.<br />

ITS make real­time traveler information available to the public so that better decisions can be made<br />

about when and how to travel. Freight and business services are improved with the ability to<br />

monitor roadways and re­route vehicles if necessary. ITS also improve mobility and safety for<br />

pedestrians and bicyclists using technologies that detect and adapt intersection signals for these<br />

travelers. While much of the ITS technologies are "behind the scenes," some examples that can<br />

been seen around the region include: ramp meters on highway on­ramps, message signs, video<br />

cameras, enhanced bus service, and 511.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

8 Final Report<br />

September 2005


Several resources are available which can provide a comprehensive introduction into ITS concepts,<br />

solutions, sample deployments, benefits and costs including the following:<br />

• USDOT ITS Program: http://www.its.dot.gov/<br />

• ITS America: http://www.itsa.org/<br />

• National Transportation Operations Coalition: http://www.ntoctalks.com/<br />

• California PATH: http://www.path.berkeley.edu/<br />

• ITS DECISION Gateway: http://www.calccit.org/itsdecision/<br />

• National ITS Architecture: http://itsarch.iteris.com/itsarch/<br />

• California Statewide ITS Architecture: http://www.kimley­horn.com/CAArchitecture/<br />

• Roads Less Traveled:<br />

http://www.fhwa.dot.gov/tfhrc/safety/ pubs/its/generalits/rdless.pdf<br />

• National ITS Program <strong>Plan</strong> (Homeland Security Supplement):<br />

http://www.itsa.org/resources.nsf/Files/PPRA_Security_Final/$file/PPRA_Security_Final.pdf<br />

The last document, Roads Less Traveled, is a thorough resource published by Public<br />

Technology, Inc. (PTI) that offers an additional overview of ITS, deployment strategies for<br />

sustainable communities, and case studies of technology deployment across the country.<br />

The ITS Architecture is a framework by which ITS infrastructure and activities can be integrated,<br />

shared and coordinated. It maps out how various systems and elements are interrelated. To qualify<br />

for funding on different levels, ITS deployments typically have to demonstrate conformance to the<br />

National ITS Architecture (and by extension, compatibility with any existing statewide and<br />

regional architectures).<br />

As ITS becomes more understood and deployed throughout the Sacramento region, it is important<br />

for planners and other stakeholders to understand and to leverage the synergies between land use<br />

and transportation. This importance is supported by the Smart Growth principles defined in the<br />

Sacramento Region Blueprint: Transportation/Land Use Study, of which the Preferred Blueprint<br />

Scenario was adopted in December 2004.<br />

This ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> builds upon the following Smart Growth<br />

principles reflected throughout Blueprint and throughout numerous local General <strong>Plan</strong>s:<br />

• Provide a variety of transportation choices<br />

• Take advantage of compact development<br />

• Use existing assets<br />

• Mixed land uses especially near transit<br />

• Encourage distinctive, attractive communities with quality design<br />

Details about Blueprint are available on the website http://www.sacregionblueprint.org.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

9 Final Report<br />

September 2005


Land use planning, transportation planning, and ITS planning activities should all be interrelated<br />

since all are ultimately concerned with system­wide effectiveness in achieving broad standard­ofliving<br />

goals such as mobility, accessibility, convenience, and safety. Land use planning is served<br />

by the guidelines of transportation planning; transportation planning is optimized by ITS planning.<br />

This is illustrated in Figure 1.1 below.<br />

Figure 1.1: <strong>Plan</strong>ning Process<br />

Land Use<br />

<strong>Plan</strong>ning<br />

… is driven by…<br />

Transportation<br />

<strong>Plan</strong>ning<br />

… which is<br />

influenced by…<br />

ITS<br />

<strong>Plan</strong>ning<br />

SACOG recognizes a need to have a strong relationship between ITS deployment and planning, so<br />

the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> focuses on how ITS solutions can be integrated, or mainstreamed,<br />

into the land use and transportation planning activities across the region.<br />

Distinctions between planning and ITS include the following characteristics:<br />

• <strong>Plan</strong>ning:<br />

o typically broad, goal­oriented<br />

o more tied to funding constraints due to longer­term considerations<br />

o incorporating longer­term growth and demand patterns<br />

• ITS:<br />

o typically shorter­term and even real­time<br />

o incorporating latest and emerging technologies<br />

1.4 ITS and the Preferred Blueprint Scenario<br />

The Blueprint 2050 Preferred Alternative land use scenario, approved by the SACOG Board of<br />

Directors in December 2004, is a smart growth vision for the Sacramento region that promotes<br />

higher densities, mixing land uses, and reinvesting in existing urban areas to create urban<br />

environments where walking, bicycling, and transit become more viable options to the automobile.<br />

Even though the Preferred Alternative will likely increase non­automobile travel, there will<br />

undoubtedly also be increases in automobile congestion in many of the activity centers and<br />

corridors where densities rise. There are a number of ITS applications that will help minimize this<br />

impact while at the same time maximize the viability of the non­auto options. These applications<br />

include:<br />

• Deploying cameras to monitor roadway and transit systems in real­time enabling operators to<br />

react more quickly to incidents or changing conditions;<br />

• Installing signals that can be controlled from a remote operations center in order to modify<br />

timing to improve flow as traffic volumes increase;<br />

• Integrating bus, roadway, and signal technologies to improve service reliability and make<br />

possible Bus Rapid Transit;<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

10 Final Report<br />

September 2005


• Adapting signal operations and detection to improve mobility and safety for pedestrians and<br />

bicyclist; and<br />

• Collecting and disseminating roadway and transit information via the 511 Traveler<br />

Information system and kiosks in public areas and at transit stops.<br />

These examples and many other ITS applications will support the implementation of Blueprint, as<br />

well as, improve current roadway and transit operations.<br />

1.5 ITS and Homeland Security<br />

Since September 11, 2001, the United States has had a major focus on Homeland Security.<br />

Through this evolution, ITS has become an integral factor in preparing, preventing, and monitoring<br />

terrorist activity by utilizing video surveillance, integrating traffic management with emergency<br />

operations, and route guidance for drivers during evacuations or following destruction. For ITS to<br />

integrate effectively, there must be coordinated management, compatible communications systems,<br />

and real­time information feedback. There must also be up­to­date information made available to<br />

the public.<br />

There are five key areas that the National ITS Program <strong>Plan</strong> focuses on as it relates to Homeland<br />

Security. These include the following:<br />

• Preparedness is having transportation system data collection for analysis of<br />

vulnerabilities, and communications and coordination technologies between agencies and<br />

to the public;<br />

• Prevention not only involves video surveillance to monitor the transportation system, but<br />

sensors to detect misuse of commercial vehicles or other transportation infrastructure (rail,<br />

stations, communications);<br />

• Protection is tools and technology for maintaining the integrity of the transportation and<br />

communications facilities and systems; and route guidance for route guidance of<br />

emergency response personnel and escapees/evacuees;<br />

• Response is having the tools and technologies that collect, process, and disseminate up­todate,<br />

accurate information to emergency responders and the general public; and having a<br />

durable communications framework with the ability to maintain communications during<br />

emergencies; and<br />

• Recovery is having the ability to reconfigure a transportation system to meet the needs of<br />

an emergency, being able to utilize alternate modes due to emergency situations.<br />

In all of these areas, ITS can help provide a transportation system that is more secure, better able to<br />

respond to crises, and well­equipped to aid and support the many agencies that must be involved<br />

with protecting the region.<br />

The National ITS Program <strong>Plan</strong> offers additional discussion and perspective on the five key areas<br />

above, with additional discussion about opportunities and approaches for enhancing security using<br />

ITS.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

11 Final Report<br />

September 2005


1.6 USDOT Regional ITS Architecture Guidance<br />

The FHWA final rule for obtaining ITS earmarks requires that ITS projects funded through the<br />

Highway Trust Fund conform to the National ITS Architecture and applicable standards. The rule<br />

suggests that the National ITS Architecture be used to develop a localized implementation strategy<br />

of the National ITS Architecture, which is referred to as a “Regional ITS Architecture.” This<br />

becomes a mapping of the applicable aspects of the National ITS Architecture, identifying which<br />

components are relevant to the Sacramento Region.<br />

The Sacramento Regional ITS Architecture was originally developed in June 2001. A major<br />

component of this <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is Section 4 which includes an update to that<br />

Regional ITS Architecture based on recent stakeholder input.<br />

1.7 Sacramento Region <strong>Plan</strong>ning Documents – How Do They All Fit Together?<br />

Stakeholders in the Sacramento and adjacent regions are encouraged to use the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> in tandem with other regional documents and planning updates to help<br />

implement the Preferred Blueprint Scenario. The flowchart in Figure 1.2 demonstrates how the<br />

ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> compliments existing planning processes in the Sacramento region.<br />

Relevant information from existing local and regional documents, along with input from agency<br />

and stakeholder representatives, were inputs to the following SACOG documents illustrated in the<br />

flowchart:<br />

• Blueprint ­ This document focuses on smart growth principles for land use and<br />

transportation planning decisions. Updated local plans and input are the basis for<br />

“supportive actions”called for in Blueprint Next Steps.<br />

• Metropolitan Transportation <strong>Plan</strong> ­ This document focuses on interjurisdictional and<br />

multimodal coordination. Local General <strong>Plan</strong>s and stakeholder input were used to<br />

develop the MTP. The MTP Goals are the basis for the ITS Vision Goals.<br />

• ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> (this report) ­ This document focuses on the selection<br />

and deployment of suitable technologies to help achieve the goals and principles<br />

defined in the other regional documents. Local General <strong>Plan</strong>s and existing ITS Master<br />

<strong>Plan</strong>s were used as input into the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. In addition, statewide and<br />

national ITS architectures guided the development of the Sacramento regional ITS<br />

architecture.<br />

The Blueprint Smart Growth principles and the 10 MTP goals feed in to the <strong>Strategic</strong> <strong>Deployment</strong><br />

<strong>Plan</strong> by laying out guidelines for regional growth. The output of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

impacts future updates to local General <strong>Plan</strong>s and ITS Master <strong>Plan</strong>s, as well as the implementation<br />

strategies of the MTP and Capital Improvements Projects. Several <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

objectives are consistent with the Next Steps outlined in Blueprint that pertain to performance<br />

measures, air emissions, and formulation of a Best Practices toolbox. Since SACOG does not have<br />

the authority to require amendments or updates to Blueprint on the local level, those decisions are<br />

left to the local governments to implement.<br />

It is important to note that city and county policymakers are not bound by decisions in regional<br />

level planning documents. Although consensus over priorities and content has been achieved in<br />

many areas of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>, varying needs at the jurisdictional level may cause<br />

differences in the way those goals are achieved. The intent of regional planning guidance is to<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

12 Final Report<br />

September 2005


provide a useful, applicable framework to promote integrated, coordinated, smart growth in the<br />

Sacramento region.<br />

Figure 1.2: <strong>Strategic</strong> Development Process Flow Diagram<br />

1.8 Document Overview<br />

The remainder of this report is organized as follows.<br />

• Section 2, Vision Statement, presents the Sacramento region’s updated ITS Vision based on<br />

input from a representative cross­section of stakeholders.<br />

• Section 3, Gap Assessment, summarizes existing, planned and programmed ITS projects and<br />

how they address, or do not address, the ITS Vision developed in Section 2.<br />

• Section 4, Sacramento Regional ITS Architecture, updates the previous Sacramento<br />

Regional ITS Architecture completed in 2001.<br />

• Section 5, <strong>Plan</strong> Maintenance, outlines an ongoing maintenance strategy to keep the<br />

Sacramento Regional ITS architecture up­to­date.<br />

• Section 6, ITS Solutions Toolkit, provides a useable decision­making tool for ITS planners<br />

and project developers in the Sacramento region.<br />

• Section 7, <strong>Deployment</strong>, outlines specific Sacramento region projects, benefits, and costs,<br />

along with recommended stakeholder agreements needed for successful deployment.<br />

• Section 8, Recommendations/Next Steps, highlights recommendations and future actions<br />

for ITS deployment based on the inputs of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> process.<br />

• Appendices provide detailed results and summaries of stakeholder input and other data.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

13 Final Report<br />

September 2005


2 VISION STATEMENT<br />

2.1 Original Sacramento Region ITS Vision<br />

In 2002, the Sacramento ITS Partnership developed and approved an ITS Vision for the<br />

Sacramento Region. The document outlined the ITS needs for the region and presented a vision<br />

that paralleled a set of overarching goals defined by the SACOG Metropolitan Transportation <strong>Plan</strong><br />

(MTP). The ITS Vision represents a high level view of the stakeholders’desired objectives for<br />

advanced technologies in the region. This ITS Vision was updated as part of this <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> with specific objectives intended to describe how technologies can help the<br />

Region achieve the ten goals stated in the Metropolitan Transportation <strong>Plan</strong>. It does not identify<br />

any specific project solutions; rather it describes guiding principles for consideration as ITS<br />

solutions are defined in capital improvement programs and other deployment initiatives. During<br />

the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>ning process, these principles were prioritized so deployment can<br />

focus on addressing the services and objectives that are important to the stakeholders.<br />

2.2 Updated Sacramento Region ITS Vision<br />

The original ITS Vision was based on the MTP Goals. During this SDP process, stakeholder input<br />

was compiled and integrated into the Vision document. Goals and objectives from existing<br />

Sacramento region planning documents were used as guiding principles during the update process.<br />

The current version of the Sacramento Region ITS Vision, as of March 2005 is repeated below,<br />

and is included in Appendix B as a stand­alone document. A correlation of ITS Vision objectives<br />

to prioritized projects is shown in Table 7.1 on Page 114. This vision document should continue<br />

to be revisited at least as often as the ITS Architecture and SDP are updated, currently scheduled<br />

for every three years in advance of the MTP update.<br />

1. OVERARCHING GOAL: QUALITY OF LIFE<br />

Develop a fully integrated, multi­modal transportation system to serve as a catalyst to<br />

enhance the quality of life enjoyed by the current and future residents of the Sacramento<br />

region.<br />

ITS is the technology needed to develop a fully integrated, multi­modal transportation<br />

system. With the ability of ITS to enhance and integrate transit services, improve safety and<br />

mobility for pedestrians and bicyclist, smooth traffic flow, and provide traveler information<br />

via 511 or other service; the region can achieve this goal by employing technologies that<br />

help improve operations and safety for every mode of travel.<br />

2. ACCESS AND MOBILITY<br />

Improve access to goods, jobs, services, housing, and other destinations; provide mobility for<br />

people and goods throughout the region, in a safe, affordable, efficient and convenient<br />

manner.<br />

ITS will be a critical component in achieving this goal. ITS provides the technology needed<br />

to integrate various transit services, improve transit timeliness, create new Bus Rapid<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

14 Final Report<br />

September 2005


Transit (BRT) trunk lines, allow for multi­modal transit transfers, and eventually makes<br />

possible neighborhood­scale paratransit services that provide virtual door­to­door access<br />

either as a stand­alone service or as a feeder service to transit trunk lines. ITS can also help<br />

to provide online bicycle route planning, electronic bicycle lockers, automated bicycle<br />

enforcement, and bicycle counts (through video or in­pavement detection). Traffic<br />

Operations Centers (TOC) will be able to leverage this ITS infrastructure investment to<br />

increase traveler mobility using applications that will allow engineers to remotely monitor<br />

the roadway system, offer signal priority to transit vehicles, and coordinate operations and<br />

management of traffic flow across jurisdictions. These technologies can also be used to<br />

reduce conflicts between non­motorized modes and vehicles. Traveler information made<br />

available via 511 will be more reliable and will help residents choose modes and routes that<br />

best meet their needs given conditions on the region’s roadways and the availability of<br />

transit.<br />

3. AIR QUALITY<br />

Develop a transportation system and related strategies that contribute to achieving healthy air<br />

in the region.<br />

ITS will help reduce vehicle emissions using enhancements for all modes – transit, nonmotorized,<br />

and auto. For transit trips, improvements mentioned above will make bus and<br />

light rail service a more convenient and viable option for travelers in the region. With even<br />

a modest number of trips shifting from auto to transit, cold starts and VMT will be reduced<br />

thereby reducing emissions. For non­motorized trips, increasing safety of bicycle and<br />

pedestrian facilities will likely increase these types of trips, again shifting trips from auto to<br />

an alternate mode. For auto trips, ITS will improve traffic operations and management to<br />

smooth traffic flow or reduce congestion. This will reduce stop­and­go conditions, which<br />

tend to have higher rates of emissions on a per mile basis.<br />

4. TRAVEL CHOICES<br />

Provide affordable, convenient, safe, and integrated travel choices.<br />

As mentioned above, ITS is the technology needed to integrate the various modes of transit in<br />

the region. Not only can ITS integrate modes of transit (paratransit, bus, and rail), it can<br />

integrate service between transit districts creating a seamless system that will enable<br />

travelers to access most parts of the region with transit service. With the deployment of ITSenhanced<br />

paratransit service, transit can become a virtual door­to­door service making it a<br />

convenient alternative to the automobile. On­board cameras and cameras at transit stops<br />

will improve the security of the transit system by making surveillance easier and<br />

uninterrupted. Advances in signal operations have the potential to help reduce vehicle<br />

conflicts with bicyclists and pedestrians making these modes more viable. Additionally,<br />

traveler information made available via 511 will help people make better decisions about<br />

mode, route, and time of travel.<br />

5. ECONOMIC VITALITY<br />

Enhance the economic vitality of our region by efficiently and effectively connecting people<br />

to jobs, goods, and services, and by moving goods within our region and beyond with an<br />

integrated multi­modal freight system.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

15 Final Report<br />

September 2005


ITS is the technology that businesses will use to improve the efficiency of moving goods and<br />

services throughout the region and beyond. Improvements in freight movement are already<br />

being seen from weigh­in­motion sensors in the roadway to reduce delay that commercial<br />

vehicles experience at weigh stations. Real­time roadway condition information, made<br />

available via STARNET and 511, will enable businesses to re­route or re­schedule<br />

commercial vehicles according to changing conditions on the system. Not only will<br />

businesses benefit from improved freight movement and expedited deliveries, but also<br />

employees and customers will have better access to jobs by focusing initial ITS<br />

improvements on corridors that feed job centers. Access improvement will come in the form<br />

of improved transit service, as well as in the ability of TOCs to integrate operations across<br />

jurisdictional boundaries. These interconnected TOCs will be able to maintain roadway<br />

capacity during peak periods by facilitating faster accident clearing, adjusting signals to<br />

smooth traffic flow, and providing alternate routes when needed.<br />

6. EQUITY<br />

Pursue a transportation system that addresses the needs of all people in all parts of the region<br />

and assure that impacts of transportation projects don’t adversely affect particular<br />

communities disproportionately.<br />

Focusing ITS improvements on transit, bicycling, and walking not only addresses unmet<br />

needs, but also helps balance investments made in roadway improvements. While initial ITS<br />

deployments will be in select priority corridors; they will nonetheless help expand and<br />

improve the transportation system making alternate modes more attractive for travelers,<br />

providing greater reliability, access, safety, and mobility. For those who are unable or<br />

unwilling to drive, ITS transit applications will noticeably improve the level of service in<br />

existing and new transit corridors, providing greater frequency, timeliness, and easier<br />

transfers. These ITS improvements will also help traffic engineers relieve congestion in<br />

many of the same corridors by adding functionality that will reduce stop­and­go traffic<br />

conditions. Consideration for bike and pedestrian movement can also be included making<br />

for a comprehensive corridor improvement effort.<br />

7. TRANSPORTATION AND LAND USE<br />

Influence land use policies to improve access to jobs, services and housing to everyone in the<br />

region by using market forces and the regulatory process.<br />

With the adoption of the Blueprint Preferred Alternative, the region will likely see an<br />

increase in higher density mixed­use developments. Such urban form fosters walking,<br />

bicycling, and transit use and ITS can be used to the increase the viability of these modes.<br />

ITS solutions for Bus Rapid Transit (BRT) and paratransit, improve the operations and<br />

integration of these modes and help expand transit trunk lines into areas without light rail<br />

service. BRT trunk lines can be targeted for Transit­Oriented Development as stops become<br />

activity centers similar to those envisioned for many of the light rail stations in the region.<br />

Safety and mobility for pedestrians and bicyclist in denser mixed­use areas will be improved<br />

by ITS through the use of detection and signal timing technologies that cater to these nonmotorized<br />

travelers.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

16 Final Report<br />

September 2005


8. FUNDING AND REVENUE<br />

In order to adequately fund the <strong>Plan</strong>, develop appropriate, innovative, equitable, and stable<br />

funding sources (both short­ and long­term) and identify cost­reduction measures.<br />

While ITS will have to compete with other projects in the Transportation Improvement<br />

Program for funding, there is anticipation that federal transportation bills will have some<br />

form of discretionary funding for ITS integration. In an effort to mainstream ITS in the<br />

planning and funding process, many capital improvement projects will be encouraged to<br />

included ITS technologies where applicable. Beyond specific ITS funding, other funding<br />

sources such as Homeland Security, Bicycle Transportation Account, Safe Routes to School,<br />

and Federal Transit Authority could provide opportunities to include ITS as part of other<br />

non­ITS projects.<br />

9. HEALTH AND SAFETY<br />

Improve the health of our residents by developing systems that would encourage walking<br />

and biking, and improve the safety and security of people on all modes in all areas.<br />

An outcome of increasing transit service and improving safety and mobility for pedestrians<br />

and bicyclists will likely be an increase in walking and biking activities. Transit­oriented<br />

development and other forms of high density mixed­use also create urban designs conducive<br />

to walking and biking. Such land use designs coupled with signal timing that accommodates<br />

pedestrian and bike movement and possibly bicycle enforcement along the roadway will<br />

create a much safer environment for non­motorized modes and encourage people to<br />

consider these as viable and safe alternates.<br />

Improvements in transit safety will result from monitoring technologies at transit stops and on<br />

vehicles. Cameras on roadways, emergency vehicle signal preemption, and other<br />

improvements that coordinate traffic management and emergency services will accelerate<br />

the detection of emergencies and reduce the response time of fire, police, and ambulance<br />

personnel. Additionally, an ITS enhanced transportation system can help reduce vehicle<br />

emissions and resultant respiratory distress by encouraging alternate modes and by<br />

smoothing traffic flow.<br />

10. ENVIRONMENTAL SUSTAINABILITY<br />

Develop the transportation system to promote and enhance environmental quality for present<br />

and future generations.<br />

An ITS­enhanced transportation network will support smart growth land use designs, which<br />

reduce pressure to convert agriculture and other open space for future development. Smart<br />

growth developments also promote the use of transit, walking, bicycling, which, when<br />

enhanced with ITS, become more viable options and help reduce automobile emissions.<br />

Real­time information on ride­sharing and transit trip planning will provide people with<br />

information that can lead to the use of alternate transportation modes, again helping to<br />

reduce emissions from automobile use.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

17 Final Report<br />

September 2005


3 GAP ASSESSMENT<br />

Up to this point, the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> process has focused on the Sacramento region’s<br />

ITS Vision. This section evaluates how well the region’s existing, planned and programmed<br />

projects identified in existing planning documents achieve the goals and objectives of the ITS<br />

Vision. In simplified form, the Gap Assessment can be illustrated in Figure 3.1.<br />

Figure 3.1: Gap Assessment related to ITS Vision and Projects<br />

Projects<br />

matching<br />

to Vision<br />

objective<br />

s<br />

3.1 ITS Existing Conditions Summary Report<br />

In order to map out future regional ITS deployment, it necessary to understand current project<br />

deployment status throughout the region. This is accomplished in the Existing Conditions<br />

Summary Report which is included in Appendix C. It contains an evaluation summary of<br />

numerous existing plans and studies of local and regional agencies in the Sacramento Region. The<br />

existing plans and studies often contain valuable recommendations and strategies for growth that<br />

could benefit from the addition of advanced technology. It also contains a summary of key<br />

recommendations from each plan or study that pertain to land use and circulation (transportation)<br />

growth issues.<br />

Forty­one documents were reviewed to provide background for the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> and<br />

to introduce and mainstream a connection of ITS to land use and transportation planning. The<br />

documents are listed in Table 3.1 below, along with their dates of publication. In the Existing<br />

Conditions Summary Report, each document is summarized by its agency, main purpose, and<br />

recommendations. Depending on the type of publication (for example, a General <strong>Plan</strong> vs. an ITS<br />

Master <strong>Plan</strong>), the documents also contain differing levels of granularity and detail depending on<br />

the document’s purpose. Documents for areas adjacent to SACOG’s jurisdiction but deemed to<br />

have or potentially have effects on this SDP are also included (for example, the Bay Area Regional<br />

ITS <strong>Plan</strong>). As elements of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> are being implemented or updated, other<br />

related documents in the list below should be considered in parallel, and vice versa.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

18 Final Report<br />

September 2005


An ITS Project Inventory was conducted as part of the existing conditions document review. This<br />

ITS Project Inventory appears in Appendix D. The projects are arranged into three categories:<br />

Existing, Programmed (projects with allocated funding awaiting implementation), and <strong>Plan</strong>ned<br />

(potential projects recommended for implementation).<br />

Table 3.1: Background Documents for this SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Report<br />

Date<br />

General Category<br />

Land<br />

Development Transportation<br />

SACOG Blueprint Transportation/Land Use Study Dec 2004 • •<br />

SACOG Metropolitan Transportation <strong>Plan</strong> May 2002 • •<br />

City and County General <strong>Plan</strong>s<br />

City of Citrus Heights General <strong>Plan</strong> Nov 2000 • •<br />

City of Davis General <strong>Plan</strong> May 2001 • •<br />

City of Elk Grove General <strong>Plan</strong> Jan 2005 • •<br />

City of Isleton Comprehensive General <strong>Plan</strong> and<br />

Environmental Impact Report<br />

City of Lincoln General <strong>Plan</strong> – Goals and Policies<br />

Report<br />

Sept 2000 • •<br />

Sept 2003 • •<br />

Town of Loomis General <strong>Plan</strong> 2001 • •<br />

City of Placerville General <strong>Plan</strong> Policy Document Jan 1989 • •<br />

City of Rancho Cordova General <strong>Plan</strong> Aug 2004 • •<br />

City of Rocklin General <strong>Plan</strong> Apr 1991 • •<br />

City of Roseville General <strong>Plan</strong> (Technical Update) 2003 • •<br />

City of Sacramento General <strong>Plan</strong> 2004 • •<br />

City of South Lake Tahoe General <strong>Plan</strong> Apr 1999 • •<br />

City of West Sacramento General <strong>Plan</strong> 2000 • •<br />

City of Woodland General <strong>Plan</strong> 2002 • •<br />

Yuba City General <strong>Plan</strong> Apr 2004 • •<br />

El Dorado County General <strong>Plan</strong> Jul 2004 • •<br />

Placer County General <strong>Plan</strong> Update Aug 1994 • •<br />

Sacramento County General <strong>Plan</strong> Dec 1993 • •<br />

Sutter County General <strong>Plan</strong> Nov 1996 • •<br />

Yolo County General <strong>Plan</strong> Jul 1993 • •<br />

Yuba County General <strong>Plan</strong> Dec 1996 • •<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

19 Final Report<br />

September 2005


Table 3.1: Background Documents for this SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

(cont’d.)<br />

Report<br />

Transportation and ITS <strong>Plan</strong>s<br />

Date<br />

General Category<br />

Land<br />

Development Transportation<br />

Sacramento Transportation ARea NETwork<br />

(STARNET) Needs Assessment<br />

Nov 2001<br />

Mobility Strategies for County Corridors Sept 2004 •<br />

City of Elk Grove ITS Master <strong>Plan</strong> Nov 2004 •<br />

City of Citrus Heights ITS Master <strong>Plan</strong> Nov 2004 •<br />

City of Roseville ITS Master <strong>Plan</strong> Feb 2005 •<br />

Sacramento Regional ITS Architecture Jun 2001 •<br />

Placer Parkway Interconnect Project Jan 2000 • •<br />

Elk Grove – Rancho Cordova – El Dorado<br />

Connector Concept <strong>Plan</strong><br />

Aug 2004 • •<br />

Sacramento Exploratory Process 1998 • •<br />

San Joaquin Valley ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Sept 2001 •<br />

Tahoe Gateway ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> 2002 •<br />

Tahoe Basin ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Mar 2003 •<br />

Bay Area Regional ITS <strong>Plan</strong> Jun 2004 •<br />

Regional Street Network and Address Database<br />

System Architecture and Design<br />

Regional Transit Multi­Corridor Study – System<br />

Expansion and Phasing Strategy<br />

California Statewide ITS Architecture and System<br />

<strong>Plan</strong><br />

Feb 2002<br />

Jun 2001<br />

Oct 2004<br />

•<br />

•<br />

•<br />

•<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

20 Final Report<br />

September 2005


Among the reports above, prevalent general themes for regional growth include the following:<br />

• Encourage mixed use developments, “village concept” developments, transit­oriented<br />

developments. Encourage land use plans that support public transit.<br />

• Enhance the accessibility and attractiveness of existing and planned employment areas.<br />

• Focus growth inward (infill development, using existing assets).<br />

• Facilitate integration among different technologies, applications, and jurisdictions (for<br />

example, through Transportation Management Centers or agreements between neighboring<br />

and overlapping jurisdictions). Investigate different ITS solutions.<br />

• Provide intermodal choices –Encourage and facilitate transit, bicycle, and pedestrian modes<br />

of transportation. Reduce automobile use by improving transit service. Encourage carpools<br />

and vanpools.<br />

• Improve emergency response capabilities.<br />

• Ensure safety (for example, minimizing cut­through traffic in residential areas).<br />

• Decrease noise and air pollution.<br />

• Provide or improve traffic signals and control. Use signal pre­emption where beneficial.<br />

• Revitalize existing downtown areas. Transform and revitalize existing commercial<br />

corridors.<br />

• Designate truck routes and facilitate improved goods movement.<br />

• Standardize data types and nomenclature (for example, as described in the Regional Street<br />

Network and Address Database System Architecture and Design).<br />

• In particular, the Mobility Strategies for County Corridors offers strategic guidance for<br />

implementation of ITS along strategic corridors.<br />

3.2 Overarching ITS Priorities<br />

Input was solicited from the stakeholders regarding the types of ITS applications they wished to<br />

see in the Sacramento Region and which ones they felt were more important than others. Based on<br />

the discussions, the following high level applications are guidelines for ITS enhancement and focus<br />

in the region:<br />

• Completion of STARNET Wide Area Network –Provide communications link between<br />

agencies to allow exchange of data and video.<br />

• Expand 511 traveler information –Provide additional traveler information services to the<br />

public such as multimodal route planning and guidance.<br />

• Transit Service Enhancements (Automatic Vehicle Location/GPS systems) –Enable<br />

Bus Rapid Transit (BRT); and provide the ability to broadcast real­time vehicle location<br />

and stop arrival information.<br />

• Bicycle and pedestrian projects –Enhance safety of alternative modes for reliable<br />

mobility.<br />

• Additional SMART Corridors –Provide traffic monitoring capabilities along major<br />

arterials; enable Bus Rapid Transit (BRT).<br />

• Enhanced transportation system operation –Enhance signal operations (timing) and<br />

proactive traffic management activities.<br />

• Freight Movement –Provide coordinated operations between transportation management<br />

and freight operations to enhance goods movement through the region.<br />

• Emergency Service Coordination – Provide coordinated planning and operations of<br />

incident management between emergency services and traffic management.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

21 Final Report<br />

September 2005


3.3 Gap Assessment<br />

Gap Assessment Process<br />

The Gap Assessment can be explained through the following steps:<br />

Step 1: Map the ITS Vision to Market Packages. The Sacramento region’s ITS Vision or<br />

“wish list”was presented in Section 2. To begin the analysis of the “gaps”between the ITS<br />

Vision and the existing, programmed and planned ITS deployments, the ITS Vision<br />

objectives were first cross­checked against services that ITS technologies can provide.<br />

These services are defined in the National ITS Architecture as Market Packages. There are<br />

85 Market Packages that represent components of the architecture that address specific areas<br />

of service (for example, emergency routing, surface street control, or transit vehicle<br />

tracking). They help to define information flows, interconnects, and subsystems of various<br />

elements of ITS deployment. Mapping the Vision to Market Packages is important because<br />

the ITS architecture is the framework which allows different systems to operate together.<br />

Understanding how SACOG’s ITS Vision fits into this standardized framework will help<br />

ensure that ITS deployment and system­wide INTEGRATION is successful and that the<br />

necessary INTEROPERABILITY is achieved in the Sacramento Region.<br />

Step 2: Map Projects to ITS Vision and Market Packages. Mapping the existing, planned<br />

and programmed SACOG projects to the Market Packages identified in Step 1 identifies the<br />

ITS solutions that are being deployed through particular projects. The projects are also<br />

mapped to the ITS Vision objectives to identify which objectives are already being met and<br />

which objectives are not being satisfied by projects. Projects in the project inventory<br />

(described in Section 3.2) are developed and recommended at the regional and local levels,<br />

either by agencies within the Sacramento region, or by agencies adjacent to or overlapping<br />

the Sacramento region.<br />

Step 3: Identify Gaps. The gaps identify the Vision objectives that have not been satisfied<br />

by current or future projects? The Sacramento region and stakeholders can focus on “closing<br />

these gaps” and addressing these objectives with future projects, so that ultimately the<br />

region’s ITS Vision is achieved. The gaps represent areas that should have associated<br />

projects identified to satisfy the gap.<br />

This process is detailed in Appendix E, Gap Assessment. Results are summarized below.<br />

Gap Assessment Results<br />

As the ITS Vision and existing, planned, and programmed projects were mapped to the National<br />

ITS Architecture Market Packages, there were several observations:<br />

o Several objectives of the ITS Vision are not part of a specific National ITS Architecture<br />

Market Package. This includes objectives related to bicycle, pedestrian, and other alternative<br />

transportation modes. Since the stakeholders identified these objectives in the ITS Vision,<br />

they are included as part of the Gap Assessment, but will not have a market package<br />

associated with them. These Vision objectives are presented below.<br />

o Several of the 85 Market Packages do not have a Vision objective that can be mapped to it.<br />

The stakeholders were asked to determine if these are relevant to the Sacramento Region and<br />

to prioritize the market packages. From those results it was determined that the following<br />

Market Packages are not relevant or important to the Sacramento Region stakeholders at this<br />

time:<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

22 Final Report<br />

September 2005


• Drawbridge Management (ATMS20)<br />

• Vehicle Safety Monitoring(AVSS01)<br />

• Advanced Vehicle Longitudinal Control (AVSS08)<br />

• Advanced Vehicle Lateral Control (AVSS09)<br />

• Automated Highway System (AVSS11)<br />

• CV Administrative Processes (CVO04)<br />

• International Border Electronic Clearance (CVO05)<br />

o Not all of the market packages that were matched with one of the Vision objectives had a<br />

project associated with them. These market packages which are needed to meet the ITS<br />

Vision objectives and for which there are no plans for deployment, represent “gaps”in the<br />

current ITS program and are listed below:<br />

• Transit Maintenance (APTS06)<br />

• Probe Surveillance (ATMS02)<br />

• Electronic Toll Collection (ATMS10)<br />

• Emissions Monitoring and Management (ATMS11)<br />

• Standard Railroad Grade Crossing (80 mph) (ATMS14)<br />

• Railroad Operations Coordination (ATMS15)<br />

• Roadway Closure Management (ATMS21)<br />

• Driver Safety Monitoring (AVSS02)<br />

• Longitudinal Safety Warning (AVSS03)<br />

• Intersection Collision Avoidance (AVSS10)<br />

• Freight Administration (cargo) (CVO02)<br />

• Electronic Clearance (CVO03)<br />

• Weigh­In­Motion (CVO06)<br />

• Roadside CVO Safety (CVO07)<br />

• On­Board CVO and Freight Safety and Security (CVO08)<br />

• CVO Fleet Maintenance (CVO09)<br />

• HAZMAT Management (CVO10)<br />

• Roadside HAZMAT Security Detection and Mitigation (CVO11)<br />

• CV Driver Security Detection and Mitigation (CVO12)<br />

• Freight Assignment Tracking (CVO13)<br />

• Transportation Infrastructure Protection (EM05)<br />

• Evacuation and Reentry Management (EM09)<br />

• Work Zone Management (MC08)<br />

• Work Zone Safety Monitoring (MC09)<br />

The stakeholders categorized each market package as having high, medium, or low priority<br />

as it pertains to the needs of the Sacramento Region. For the gaps that occur between the<br />

high and medium priority market packages and the projects, new projects will be defined that<br />

will accommodate the market packages. This is conducted later in Section 7. The gaps that<br />

occur in the low priority category will not be addressed in the current strategic deployment<br />

plan.<br />

o In the Sacramento Region ITS Vision in Section 2, there were several objectives that were<br />

defined that do not relate to any market package and for which there is no project already<br />

identified that will fulfill that Vision objective. These represent other gaps in the current list<br />

of projects that do not satisfy the ITS Vision objectives.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

23 Final Report<br />

September 2005


• Improve mobility and reliability for pedestrians and bicycles;<br />

• Improve bicycle and pedestrian safety;<br />

• Provide traveler information in accessible formats (i.e., large print, Braille,<br />

audio, multi­lingual) and varying media (i.e., web, TV, in­vehicle, 511, kiosks);<br />

• Develop an ITS education program in the region;<br />

Projects that could address these areas are defined in Section 7.<br />

3.4 Topics for Further Update Consideration<br />

The following additional points are based on feedback from project workshops that were not<br />

completely addressed through this <strong>Plan</strong> and warrant further discussion:<br />

• Electronic Toll Collection: There have been discussions of High Occupancy Vehicle<br />

(HOV) and High Occupancy Toll (HOT) lanes in the Sacramento area. The<br />

administration of HOT lanes can be facilitated with Electronic Toll Collection, and<br />

thus stakeholders discussed the need for continuing to include the Electronic Toll<br />

Collection market package in the list of gaps even though it may be many years away.<br />

In FHWA’s “Toolbox for Regional Policy Analysis 1 ”, transportation­land use models<br />

were applied to several case studies to measure the effects of transportation<br />

investments and policies on land use, and to consider the consequent impact of land<br />

use policies and patterns on the transportation system. The case study for the<br />

Sacramento region stated that “HOV and HOT policies were found to be much more<br />

effective when applied in conjunction with land use and/or pricing policies”.<br />

• Goods Movement: Several of the gaps above pertain to Commercial Vehicle<br />

Operations (CVO) and goods movement. Stakeholders reiterated that the goods<br />

movement industry is a key part of the intermodal transportation system in the<br />

Sacramento region. The Sacramento ITS Vision includes the goal of Economic<br />

Vitality, which is to “enhance the economic vitality of our region by efficiently and<br />

effectively connecting people to jobs, goods, and services, and by moving goods<br />

within our region and beyond with an integrated multimodal freight system.” So as<br />

ITS deployment moves forward in the region, stakeholders from freight agencies and<br />

goods movement organizations (such as the Port of Sacramento) should be identified<br />

and engaged more actively in future discussions.<br />

In January 2005, a California Goods Movement Action <strong>Plan</strong> was completed. The <strong>Plan</strong><br />

articulates goals which parallel those included in the ITS Vision and MTP for the<br />

Sacramento region (shown in brackets below), including:<br />

o Generate jobs (Economic Vitality)<br />

o Increase mobility and relieve traffic congestion (Access and Mobility)<br />

o Improve air quality and protect public health (Air Quality)<br />

o Enhance public and port safety (Health and Safety)<br />

o Improve California’s quality of life (Quality of Life)<br />

Additional information can be found at:<br />

1 http://www.fhwa.dot.gov/planning/toolbox/sacramento_overview.htm<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

24 Final Report<br />

September 2005


http://www.arb.ca.gov/gmp/docs/draftreport031805.pdf<br />

Goods movement is directly affected by land use policies and planning, and vice<br />

versa. For example, the Preferred Blueprint Scenario from the Sacramento Region<br />

Blueprint emphasizes dense development to promote shorter driving distances. If<br />

local land parcels in strategic locations (near freeways, for example) are developed for<br />

warehouse and goods­related uses within the framework provided by Blueprint, truck<br />

miles driven will decrease, along with truck emissions and goods distribution costs.<br />

ITS can strengthen this interaction between land use and goods movement by<br />

providing tools (such as weigh­in­motion systems, electronic credentialing, and truckspecific<br />

traveler information) which further facilitate truck movement through the<br />

region between different land uses in a safe fashion which promotes decreased air<br />

emissions.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

25 Final Report<br />

September 2005


4 SACRAMENTO REGIONAL ITS ARCHITECTURE<br />

The Sacramento Regional ITS Architecture is a roadmap for transportation systems integration in<br />

the Sacramento region over the next 20 years. The architecture was originally developed in 2001<br />

through a cooperative effort by the region’s transportation agencies. It has been extensively<br />

updated as part of this current effort. The architecture represents a shared vision of how each<br />

agency’s systems will work together in the future, sharing information and resources to provide a<br />

safer, more efficient, and more effective transportation system for travelers in the region.<br />

The architecture is an important new tool that will be used by:<br />

• Operating Agencies to recognize and plan for transportation integration opportunities in<br />

the region.<br />

• <strong>Plan</strong>ning Agencies to better reflect integration opportunities and operational needs into<br />

the transportation planning process.<br />

• Other organizations and individuals that use the transportation system in the region.<br />

The architecture provides an overarching framework that spans all of these organizations and<br />

individual transportation projects. Using the architecture, each transportation project can be<br />

viewed as an element of the overall transportation system, providing visibility into the relationship<br />

between individual transportation projects and ways to cost­effectively build an integrated<br />

transportation system over time.<br />

Architecture updates for the Sacramento Region described in the following sections can also be<br />

found on the<br />

Sacramento Regional ITS Architecture website:<br />

http://www.consystec.com/sacramento/web/_regionhome.htm<br />

4.1 Scope<br />

The scope of a regional ITS architecture is defined by three attributes:<br />

• Geographic scope<br />

• Timeframe<br />

• Scope of services covered by the architecture<br />

For the Sacramento Regional ITS Architecture the geographic scope has been updated to include<br />

the counties of Sacramento, Yolo, Yuba, Sutter, and the western halves of Placer and El Dorado.<br />

Figure 4.1 provides a representation of the geographic coverage of the architecture.<br />

The geographic scope of the Sacramento Regional ITS Architecture borders on the geographic<br />

scope of several other architectures. There is an overlap with the Tahoe Gateway ITS Architecture,<br />

which covers the eastern halves of Placer and El Dorado counties (as well as several other<br />

counties). There is some relationship as well with the Tahoe Basin ITS Architecture, which<br />

focuses on the region around Lake Tahoe. The geographic extent of these two architectures is also<br />

shown in the Figure below. In addition, the Bay Area ITS Architecture borders the SACOG<br />

architecture to the southwest. Finally, the California Statewide ITS Architecture, which focuses on<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

26 Final Report<br />

September 2005


statewide and interregional services, relates to the Sacramento Regional ITS Architecture in a<br />

hierarchical manner, defining key interfaces in a general way that are further customized and<br />

defined at the regional level.<br />

Figure 4.1: Geographic Scope of Architectures<br />

Tahoe Gateway Regional ITS<br />

Architecture Geographic Scope<br />

Tahoe Basin Regional ITS<br />

Architecture Geographic Scope<br />

Sacramento Regional ITS<br />

Architecture Geographic Scope<br />

The timeframe over which the regional ITS architecture is concerned is 20 years. This aligns with<br />

the regional transportation plan timeframe.<br />

The architecture covers services across a broad range of ITS including traffic management, transit<br />

management, traveler information, emergency services, archived data management, and<br />

maintenance and construction operations services.<br />

4.2 Stakeholders<br />

Stakeholder coordination and involvement is one of the key elements of the development of a<br />

regional ITS architecture. Because ITS often transcends traditional transportation infrastructure, it<br />

is important to consider a range of stakeholders beyond the traditional traffic, transit, and<br />

maintenance areas. In addition, it is important to consider stakeholders at a regional level and<br />

stakeholders in adjoining regions.<br />

If an agency is not called out specifically in this table, they are accounted for in one of the “Other”<br />

categories. The stakeholders represent a mix of specific agencies or organizations and generic<br />

names used to represent a variety of stakeholders. Examples of specific agency or organizations<br />

would be City of Citrus Heights. An example of a generic stakeholder name would be Local Fire<br />

Districts, which represents the local fire departments in each city, municipality, or locality that<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

27 Final Report<br />

September 2005


esponds/dispatches emergency vehicles to an incident within the region (as well as many other<br />

roles). Table 4.1 identifies the stakeholders that own or operate elements within the Regional<br />

ITS Architecture. The table provides a name and description of the agency, department, active<br />

participation in the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>, and organization represented by the stakeholder.<br />

This table represents all of the stakeholders who have responsibility for one or more elements in<br />

the architecture.<br />

If an agency is not called out specifically in this table, they are accounted for in one of the “Other”<br />

categories. The stakeholders represent a mix of specific agencies or organizations and generic<br />

names used to represent a variety of stakeholders. Examples of specific agency or organizations<br />

would be City of Citrus Heights. An example of a generic stakeholder name would be Local Fire<br />

Districts, which represents the local fire departments in each city, municipality, or locality that<br />

responds/dispatches emergency vehicles to an incident within the region (as well as many other<br />

roles).<br />

Table 4.1: Stakeholders<br />

Indicates active participation in <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

Stakeholder Name Active Stakeholder Description<br />

Ambulance Operators<br />

Operators of public ambulance services within the Sacramento region.<br />

Archive Data Users<br />

Users (and their systems) of general archive data within the region.<br />

California Department of<br />

Motor Vehicles<br />

The California Department of Motor Vehicles (DMV) section associated with<br />

licensing and registrations for the State of California.<br />

Caltrans Districts<br />

Other Caltrans Districts outside of the Sacramento region.<br />

Caltrans District 3 * District 3 of the California Department of Transportation. District Counties ­<br />

Butte, Colusa, El Dorado, Glenn, Nevada, Placer, Sacramento. Sierra, Sutter,<br />

Yolo and Yuba<br />

Caltrans HQ<br />

Caltrans Headquarters departments and sections.<br />

Capitol Corridor JPA<br />

The Capitol Corridor Joint Powers Authority (CCJPA) is a partnership among<br />

the six local transit agencies in the eight county service area which shares the<br />

administration and management of the Capitol Corridor. The San Francisco<br />

Bay Area Rapid Transit District (BART) provides day­to­day management<br />

support to the CCJPA. The CCJPA consists of PCTPA, Sacramento RT,<br />

BART, Santa Clara Valley Transportation Authority, Solano Transportation<br />

Authority, and Yolo County Transportation District. The Capitol Corridor route<br />

operates on tracks primarily owned and dispatched by the Union Pacific RR<br />

and Caltrain.<br />

Chemtrec<br />

CHEMTREC serves as a round­the­clock resource for obtaining immediate<br />

emergency response information for accidental chemical releases. It is linked<br />

to the largest network of chemical and hazardous material experts in the world<br />

including chemicals and response specialists within the ACC membership,<br />

response specialists within the carrier community, public emergency services,<br />

and private contractors.<br />

CHP<br />

California Highway Patrol. The regions dispatch center is the Sacramento<br />

Communications Center.<br />

City of Citrus Heights * Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Citrus Heights.<br />

City of Davis<br />

Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Davis.<br />

City of Elk Grove * Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Elk Grove.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

28 Final Report<br />

September 2005


Table 4.1: Stakeholders<br />

Stakeholder Name Active Stakeholder Description<br />

City of Folsom * Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Folsom.<br />

City of Rancho Cordova * Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Rancho Cordova.<br />

City of Roseville * Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Roseville.<br />

City of Sacramento DPW * The City of Sacramento Public Works Department ­ responsible for the overall<br />

management and control of vehicular and pedestrian traffic within the City as<br />

well as maintenance operations for the City of Sacramento.<br />

City of Sacramento Fire<br />

Department<br />

Provides fire, rescue and emergency medical services to the City of<br />

Sacramento.<br />

City of Sacramento Police<br />

City of West Sacramento<br />

Engineering Division<br />

City of Woodland<br />

City of Yuba City<br />

Commercial Vehicle<br />

Operators<br />

County Government<br />

County/Municipal<br />

Government<br />

El Dorado County Transit<br />

Authority<br />

Financial Institution<br />

Independent School<br />

Districts<br />

Local Fire Districts<br />

Local Government<br />

Local News Media<br />

Local Police Departments<br />

Local Traffic Agencies<br />

NOAA<br />

Other Law Enforcement<br />

Other Local Transit<br />

Operators<br />

Paratransit, Inc.<br />

Placer County Transit<br />

Law enforcement provider for the City of Sacramento.<br />

* Division responsible for the overall management and control of vehicular and<br />

pedestrian traffic within the City of West Sacramento. Includes design,<br />

construction, operation and maintenance of traffic control systems.<br />

Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Woodland.<br />

Represents overall the municipal government, department of public works, and<br />

miscellaneous departments for the City of Yuba City.<br />

Companies operating fleets of commercial vehicles within the region.<br />

Represents the County Governments within the Sacramento region.<br />

Represents a general stakeholder that is municipal or county government.<br />

* The El Dorado County Transit Authority provides fixed route and paratransit<br />

services for the county, as well as commuter services to Sacramento.<br />

Banks involved in the transfer of funds for toll and fare collection as well as for<br />

other fee based transportation services.<br />

The public schools systems throughout the Sacramento region.<br />

Represents the local fire departments/districts within the Sacramento region<br />

that are not specifically called out in the architecture.<br />

Represents the Local Governments (cities and towns) within the Sacramento<br />

region that are not specifically called out within the architecture.<br />

Includes both print (newspaper) and broadcast (TV, radio) news media.<br />

Represents the local police, sheriff or public safety departments within the<br />

Sacramento region that are not specifically called out in the architecture.<br />

Represents the local traffic departments/agencies within the Sacramento<br />

region that are not specifically called out in the architecture.<br />

National Oceanic and Atmospheric Administration (National Weather Service).<br />

Represents other law enforcement agencies (public and/or private) within the<br />

Sacramento region that are not specifically called out in the architecture.<br />

Represents other public transit agencies within the Sacramento region that are<br />

not specifically called out in the architecture. Includes the UniTrans system.<br />

Private company that subcontracts but also receives CTSA funds to provide<br />

social service transportation.<br />

Provides fixed route service for Placer County, as well as commuter services<br />

to Sacramento.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

29 Final Report<br />

September 2005


Table 4.1: Stakeholders<br />

Stakeholder Name Active Stakeholder Description<br />

Private Sector ISP<br />

Local, regional and national information service providers that provide travel<br />

information, including Internet sites, service bureaus, concierge services, etc.<br />

Private Taxi Companies<br />

Companies that have private Taxi operations in the region.<br />

Private Transit Providers<br />

Represents private transit agencies within the Sacramento region that are not<br />

specifically called out in the architecture.<br />

Private/Public Utilities<br />

Public or private utility companies within the Sacramento region.<br />

Regional Event Promoters Event promoters in the Sacramento Region<br />

Regional Hospitals<br />

Hospital/trauma centers in the region.<br />

Regional Rail Providers<br />

Providers of regional heavy rail operations to the Sacramento region.<br />

Roseville Transit<br />

Provides fixed route service for Roseville, as well as commuter services to<br />

Sacramento.<br />

SACOG * Sacramento Area Council of Governments is the Metropolitan <strong>Plan</strong>ning<br />

Organization for the region.<br />

Sacramento County<br />

Represent the Sacramento County government and misc. departments.<br />

Sacramento County<br />

Airport System<br />

The Sacramento County department that operates, maintains, and develops<br />

the County Airport System in a safe, convenient, and economical manner<br />

Sacramento County<br />

County law enforcement for Sacramento County.<br />

Sheriff<br />

Sacramento County<br />

Transportation Department<br />

* County agency responsible for traffic signal control and coordination as well as<br />

maintaining county roads and bridges in Sacramento County.<br />

Sacramento Fire JPA<br />

Sacramento Fire Joint Powers Authority ­ California Office of Emergency<br />

Services that serves as a joint partnership between the fire/ems agencies in<br />

California that provide training and educations services to 17 agencies in the<br />

Sacramento region.<br />

Sacramento Metropolitan<br />

Air Quality Management<br />

District (SMAQMD)<br />

The Sacramento Metropolitan Air Quality Management District (AQMD) has<br />

monitoring, enforcement, and permitting roles to help to achieve and maintain<br />

healthy air quality for Sacramento.<br />

Sacramento Region<br />

This is a Server that will connect center­to­center for all TMCs and TOCs in<br />

(Partnership)<br />

Sacramento Regional<br />

Transit District<br />

State Office of Emergency<br />

Services<br />

Travelers ­ The Public<br />

UC Berkeley<br />

UC Davis<br />

the region.<br />

* The Sacramento Regional Transit District (RT) operates natural gas powered<br />

fixed route buses, light rail and shuttle vans. Buses operate daily from 5:00<br />

a.m. to 11:30 p.m., light rail trains operate from 4:30 a.m. to 1:00 a.m.<br />

Demand response services are contracted through Paratransit, Inc. Other RT<br />

amenities include 41 light rail stops or stations, 21 bus and light rail transfer<br />

centers and 14 free park­and­ride lots. RT also serves more than 3,800 bus<br />

stops throughout Sacramento County.<br />

California Governor's Office of Emergency Services coordinates overall state<br />

agency response to major disasters in support of local government. The office<br />

is responsible for assuring the state's readiness to respond to and recover<br />

from natural, manmade, and war­caused emergencies, and for assisting local<br />

governments in their emergency preparedness, response and recovery efforts.<br />

Traveling public accessing various modes of transportation, including surface<br />

street, air, rail/transit, and non­motorized modes of transportation.<br />

California University that hosts the Performance Monitoring System.<br />

California University that owns and operates Unitrans.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

30 Final Report<br />

September 2005


Table 4.1: Stakeholders<br />

Stakeholder Name Active Stakeholder Description<br />

Yolo County<br />

Transportation District<br />

Yuba­Sutter Transit<br />

* The District that administers YOLOBUS, which operates local and inter­city<br />

bus services in Yolo County and neighboring areas. YOLOBUS serves Davis,<br />

West Sacramento, Winters, Woodland, downtown Sacramento, Sacramento<br />

International Airport, Cache Creek Casino, Esparto, Madison and Knights<br />

Landing. Yolobus also makes connections with other local public<br />

transportation systems (Unitrans and Citylink Amtrak in Davis, and Regional<br />

Transit and Light Rail in Sacramento).<br />

The transit agency that services Yuba City, Marysville, Sacramento and the<br />

surrounding rural communities. The Yuba­Sutter Transit Agency provides<br />

fixed route operations (local and to Sacramento), rural operations, and "dial­aride"<br />

(demand response) operations.<br />

4.3 Operational Concepts<br />

An Operational Concept documents each stakeholder’s current and future roles and responsibilities<br />

in the operation of the regional ITS systems. The operational concept documents these roles and<br />

responsibilities across a range of transportation services. The services covered are:<br />

• Traffic Signal Control: the development of signaling systems that react to changing traffic<br />

conditions and provide coordinated intersection timing over a corridor, an area, or multiple<br />

jurisdictions.<br />

• Highway Management: the development of systems to monitor freeway (or tollway) traffic<br />

flow and roadway conditions, and provide strategies such as ramp metering or lane access<br />

control to improve the flow of traffic on the freeway. Includes systems to provide information<br />

to travelers on the roadway.<br />

• Incident Management: the development of systems to provide rapid and effective response to<br />

incidents. Includes systems to detect and verify incidents, along with coordinated agency<br />

response to the incidents.<br />

• Transit Management: the development of systems to more efficiently manage fleets of transit<br />

vehicles or transit rail. Includes systems to provide transit traveler information both pre­trip<br />

and during the trip.<br />

• Traveler Information: the development of systems to provide static and real time<br />

transportation information to travelers.<br />

• Emergency Management: the development of systems to provide emergency call taking,<br />

public safety dispatch, and emergency operations center operations.<br />

• Maintenance and Construction Management: the development of systems to manage the<br />

maintenance of roadways in the region, including winter snow and ice clearance. Includes the<br />

managing of construction operations.<br />

• Archive Data Management: the development of systems to collect transportation data for use<br />

in non­operational purposes (e.g. planning and research).<br />

• Electronic Payment: the development of electronic fare payment systems for use by transit<br />

and other agencies (e.g. parking).<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

31 Final Report<br />

September 2005


Table 4.2 identifies the roles and responsibilities of key stakeholders for a range of transportation<br />

services.<br />

Table 4.2: Roles and Responsibilities<br />

Stakeholder<br />

Roles/Responsibilities<br />

Traffic Signal Control<br />

Caltrans District 3 • Operate traffic signal systems on state owned arterials<br />

• Interconnect with signal systems operated by counties or municipalities adjoining the<br />

Caltrans systems.<br />

• Provide signal preemption for emergency vehicles<br />

City of Sacramento DPW • Operate traffic signal systems for City of Sacramento.<br />

• Interconnect with signal systems operated by Caltrans and Sacramento County<br />

adjoining the city (future).<br />

• Provide signal preemption for emergency vehicles<br />

• Provide signal priority for transit vehicles (future).<br />

Sacramento County<br />

Transportation Department<br />

• Operate traffic signal systems for Sacramento County, Caltrans, Citrus Heights, and<br />

Rancho Cordova.<br />

• Interconnect with signal systems operated by Caltrans and municipalities adjoining the<br />

Sacramento County systems.<br />

• Provide signal preemption for emergency vehicles.<br />

• Provide signal priority for transit vehicles.<br />

Municipal PWD • Operate traffic signal systems for municipality owned arterials.<br />

• Interconnect with signal systems in adjacent jurisdictions (future).<br />

• Provide signal preemption for emergency vehicles<br />

City of Citrus Heights • Operate traffic signal systems for City of Citrus Heights.<br />

• Interconnect with signal systems operated by Caltrans and Sacramento County<br />

adjoining the city (future).<br />

City of Davis • Operate traffic signal systems for City of Davis.<br />

• Interconnect with signal systems operated by Caltrans or county adjoining the city<br />

(future).<br />

• Provide signal preemption for emergency vehicles (future).<br />

• Provide signal priority for transit vehicles (future).<br />

City of Elk Grove • Operate traffic signal systems for City of Elk Grove.<br />

• Interconnect with signal systems operated by City of Sacramento adjoining the city<br />

(future).<br />

• Provide signal preemption for emergency vehicles.<br />

City of Folsom • Operate traffic signal systems for City of Folsom.<br />

• Interconnect with signal systems operated by municipalities adjoining the city (future)<br />

• Provide signal preemption for emergency vehicles (future).<br />

City of Rancho Cordova • Operate traffic signal systems for City of Rancho Cordova.<br />

• Interconnect with signal systems operated by municipalities adjoining the city (future)<br />

• Provide signal preemption for emergency vehicles (future).<br />

City of Roseville • Operate traffic signal systems for City of Roseville.<br />

• Interconnect with signal systems operated by Caltrans adjoining the city (future).<br />

• Provide signal preemption for emergency vehicles<br />

• Provide signal priority for transit vehicles (future).<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

32 Final Report<br />

September 2005


Table 4.2: Roles and Responsibilities<br />

Stakeholder<br />

Roles/Responsibilities<br />

City of West Sacramento<br />

Engineering Division<br />

• Operate traffic signal systems for City of West Sacramento.<br />

• Interconnect with signal systems operated by Caltrans, Sacramento County, and City of<br />

Sacramento adjoining the city (future).<br />

• Provide signal preemption for emergency vehicles.<br />

City of Woodland • Operate traffic signal systems for City of Woodland.<br />

• Interconnect with signal systems operated by Yolo County adjoining the city (future).<br />

• Provide signal preemption for emergency vehicles (future).<br />

City of Yuba City • Operate traffic signal systems for City of Yuba City.<br />

• Interconnect with signal systems operated by the county adjoining the city (future).<br />

• Provide signal preemption for emergency vehicles (future).<br />

Highway Management<br />

Caltrans District 3 • Monitor traffic sensors on highways.<br />

• Determine travel times for highways.<br />

• Collect road weather information.<br />

• Operate traffic information devices on freeway (e.g. DMS and Highway Advisory Radio)<br />

• Provide traffic information reports to other agencies (future).<br />

Incident Management<br />

Caltrans District 3 • Perform network surveillance for detection and verification of incidents.<br />

• Provide incident information to travelers via traffic information devices on freeways (e.g.<br />

DMS and Highway Advisory Radios­ HAR).<br />

• Coordinate maintenance resource response to incidents with state police and county<br />

public safety.<br />

• Coordinate operations with City and County of Sacramento during scheduled events.<br />

City of Sacramento DPW • Perform incident detection and verification for arterial streets in the City of Sacramento<br />

through video surveillance.<br />

• Adjust signal timing patterns in response to incidents.<br />

• Coordinate incident response with City of Sacramento Public Safety (Police, Fire, and<br />

EMS).<br />

• Operate Dynamic Message Signs on City of Sacramento arterials to inform travelers of<br />

incidents (future).<br />

• Coordinate maintenance resources for incident response with Caltrans and county.<br />

• Coordinate operations with Caltrans and County during scheduled events.<br />

Sacramento Fire JPA • Receive emergency calls for incidents within the City of Sacramento and Sacramento<br />

County.<br />

• Dispatch Police, Fire, and EMS to incidents within the City and Sheriff, Fire, and EMS<br />

to incidents within Sacramento County.<br />

• Provide incident information to traffic and other public safety agencies.<br />

• Coordinate incident response between Sacramento County public safety and City of<br />

Sacramento public safety.<br />

• Coordinate incident response with public safety in surrounding counties.<br />

City of Sacramento Fire • Respond to Hazmat incidents with City of Sacramento.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

33 Final Report<br />

September 2005


Table 4.2: Roles and Responsibilities<br />

Stakeholder<br />

Roles/Responsibilities<br />

CHP • Receive emergency calls from cell phones for incidents within the region.<br />

• Dispatch State Police vehicles for incidents on freeways.<br />

• Dispatch Freeway Service Vehicles.<br />

• Coordinate incident response with Caltrans, county and municipal public safety.<br />

• Provide incident information to traffic and public safety agencies.<br />

Sacramento County<br />

Transportation Department<br />

Municipalities (including cities of<br />

Citrus Heights, Davis, Elk Grove,<br />

Folsom, Rancho Cordova,<br />

Roseville, West Sacramento,<br />

Woodland, Yuba City)<br />

• Perform network surveillance for detection and verification of incidents.<br />

• Provide incident information to travelers via traffic information devices on highways and<br />

arterials (e.g. DMS).<br />

• Coordinate maintenance resource response to incidents with state police and county<br />

public safety.<br />

• Adjust signal timing patterns in response to incidents.<br />

• Coordinate operations with City of Sacramento during scheduled events.<br />

• Perform incident detection and verification for arterial streets within municipalities in the<br />

region.<br />

• Dispatch Police, Fire, and EMS to incidents within the municipalities.<br />

• Coordinate incident response for incidents within the municipality.<br />

Regional event promoters • Provide event information to traffic, maintenance and public safety agencies.<br />

Transit Management<br />

Sacramento Regional Transit<br />

District<br />

• Provide fixed route bus service for City of Sacramento.<br />

• Operate light rail system.<br />

• Provide paratransit service for City of Sacramento.<br />

Roseville Transit • Provide commuter service to downtown Sacramento and Yolo Bus connection.<br />

Roseville Transit • Provide fixed route and paratransit bus service for Roseville.<br />

Caltrans • Operate Commuter Rail (future)<br />

Yolo County Transportation • Provide fixed route bus service for Yolo County.<br />

District<br />

School Districts • Provide fixed route school bus services to the region.<br />

Paratransit, Inc. • Operate paratransit services for region.<br />

El Dorado County Transit<br />

Authority<br />

• Provide fixed route bus service for El Dorado County.<br />

• Provide paratransit service for El Dorado County<br />

Placer County Transit • Provide downtown Sacramento commuter service.<br />

• Provide fixed route to RT’s light rail station @ I­80/Watt Ave.<br />

• Provide Dial­a­Ride to Granite Bay and Rocklin.<br />

City of Elk Grove • Provide fixed route bus service and paratransit for City of Elk Grove with connections to<br />

City of Sacramento<br />

• Provide paratransit service for City of Elk Grove.<br />

City of Folsom • Provide fixed route, commuter, and dial­a­ride service for City of Folsom.<br />

City of Davis/UC Davis • Provide fixed route bus service for the City of Davis.<br />

Yuba­Sutter Transit • Provide fixed route bus service to Yuba City, Marysville, Linda and Olivehurst.<br />

• Provide commuter bus service to Sacramento<br />

• Provide paratransit services to the area,<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

34 Final Report<br />

September 2005


Table 4.2: Roles and Responsibilities<br />

Stakeholder<br />

Roles/Responsibilities<br />

Traveler Information<br />

Sacramento Region<br />

• Provide traffic and transit information from the region by website (future)<br />

(Partnership)­ STARNET<br />

Stakeholder<br />

Caltrans District 3 • Provide traffic and maintenance information for region<br />

• Provide traveler information directly to drivers via DMS and HAR.<br />

• Provide traveler information to the local print and broadcast media and websites<br />

(through Public Information Office).<br />

City of Sacramento • Provide traffic and maintenance information for City of Sacramento to the public via<br />

website. (future)<br />

• Provide traffic and maintenance information for City of Sacramento to the local media.<br />

• Provide traveler information directly to drivers via DMS and other technologies. (future)<br />

Sacramento Regional Transit<br />

District<br />

• Provide transit information for Sacramento Services the public via website<br />

• Provide on­line reservation capability for paratransit services (future)<br />

Sacramento County • Provide traffic and maintenance information for Sacramento County to the public via<br />

website.<br />

• Provide traveler information directly to drivers via DMS.<br />

Tahoe Gateway • Coordinate traveler information between Sacramento and Tahoe regions.<br />

Municipalities • Provide traffic and maintenance information for municipality to the public via website.<br />

Emergency Management<br />

Sacramento Fire JPA • Provide emergency call taking (9­1­1) for unincorporated areas of Sacramento County<br />

and for the City of Sacramento.<br />

• Dispatch Sacramento County sheriff, fire, and EMS.<br />

• Dispatch City of Sacramento police, fire, and EMS.<br />

• Coordinate emergency operations with State Police, county, and municipal public<br />

safety.<br />

City of Sacramento Police and<br />

Fire<br />

• Develop city emergency preparedness plan.<br />

• Provide Emergency Operations Center for city responsible for directing emergency<br />

operations during major emergencies and disasters (jointly with Sacramento County).<br />

CHP • Receive emergency calls from cell phones for incidents within the region.<br />

• Dispatch State Police vehicles for emergencies on freeway and other state owned<br />

roads.<br />

• Coordinate emergency response with Caltrans, Sacramento County sheriff, City of<br />

Sacramento Police, and other municipal public safety.<br />

County Sheriff • Develop county emergency preparedness plan.<br />

• Provide Emergency Operations Center for County of Sacramento responsible for<br />

directing emergency operations during major emergencies and disasters (jointly with<br />

City of Sacramento).<br />

Tahoe Gateway • Coordinate regional emergency management between Sacramento and Tahoe regions.<br />

Municipalities • Provide emergency call taking (9­1­1) for municipalities and townships in the region.<br />

• Dispatch police, fire and EMS for municipalities in the region.<br />

• Coordinate emergency response with State Police and county sheriff.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

35 Final Report<br />

September 2005


Table 4.2: Roles and Responsibilities<br />

Stakeholder<br />

Roles/Responsibilities<br />

Maintenance Management<br />

Caltrans District 3 • Provide maintenance of state highways in the region including snow and ice control and<br />

pavement maintenance.<br />

• Manage work zones on state owned roads.<br />

• Collect road weather information.<br />

• Maintain signalized intersection and other ITS equipment.<br />

City of Sacramento Public Works • Provide maintenance of arterials in the city including snow and ice control and<br />

pavement maintenance.<br />

• Maintain signalized intersection and other ITS equipment.<br />

• Manage work zones in the City of Sacramento.<br />

• Collect road weather information.<br />

Sacramento County Public<br />

Works<br />

Municipalities (including cities of<br />

Citrus Heights, Davis, Elk Grove,<br />

Folsom, Rancho Cordova,<br />

Roseville, West Sacramento,<br />

Woodland, Yuba City)<br />

Archived Data Management<br />

• Provide maintenance of County roads including snow and ice control and pavement<br />

maintenance.<br />

• Maintain signalized intersection equipment and other ITS equipment.<br />

• Manage work zones in Sacramento County.<br />

• Collect road weather information.<br />

• Provide maintenance of municipal roads including snow and ice control and pavement<br />

maintenance.<br />

• Maintains signalized intersection equipment.<br />

SACOG • Collect and archive transportation data for region, including traffic count and crash data.<br />

City of Sacramento • Collect and archive traffic count data for the City of Sacramento.<br />

• Collect and archive accident data for the City of Sacramento.<br />

Sacramento County<br />

• Collect and archive asset information<br />

Transportation Department • Collect and archive traffic count data for county owned roads.<br />

• Collect and archive crash records for all roads in the county.<br />

Caltrans • Collect and archive asset information.<br />

• Collect and archive traffic count data for state owned roads.<br />

• Collect and archive crash records for all roads in the state.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

36 Final Report<br />

September 2005


4.4 Inventory<br />

Each stakeholder agency, company, or group owns, operates, or maintains ITS systems (or will do<br />

so in the future) in the region. The Regional ITS Architecture inventory is a list of “elements”that<br />

represent all existing and planned ITS systems in a region as well as non­ITS systems that provide<br />

information to or get information from the ITS systems. The focus of the inventory is on those<br />

systems that support, or may support, interfaces that cross stakeholder boundaries (e.g., interagency<br />

interfaces, public/private interfaces).<br />

The vast majority of the inventory represents ITS systems in the region, but the inventory does<br />

contain some elements that represent systems in adjoining regions. An example of an element in<br />

an adjoining region would be the Other Caltrans District TMCs, which represents the traffic<br />

management centers that Caltrans operates in adjoining regions. These centers are outside the<br />

geographic scope of the Sacramento Regional ITS Architecture but will interface with traffic<br />

elements inside the region, and so must be considered in the architecture.<br />

Each element in the inventory is described by a name, the associated stakeholder, a description,<br />

general status (e.g. existing or planned), and the associated subsystems or terminators from the<br />

National ITS Architecture that best represent the function of the element.<br />

Systems by Stakeholder<br />

Table 4.3 presents the inventory sorted by stakeholder so that each stakeholder can easily identify<br />

all the relevant elements that are defined in the architecture. For each element in the inventory the<br />

table provides an element description and an indication of whether the element exists or is planned.<br />

The majority of elements in the inventory represent a specific existing or planned system. Some<br />

examples of specific systems are the Caltrans District 3 Data Server and City of Davis<br />

Maintenance Dispatch.<br />

Some of the elements represent sets of devices, rather than a single specific system or device. An<br />

example of this type of element is the element “Sacramento City Roadside Equipment”. This<br />

element represents all of the ITS field equipment that are or will be operated by the City of<br />

Sacramento. The element describes field devices, not the specific type of device (i.e. CCTV,<br />

coordinated signals, etc.), or the specific number of devices.<br />

A third type of element in the inventory is a “generic”element that represents all of the systems of<br />

a certain type in the region. An example of this type of element is Local Police Dispatch, which<br />

represents the local police or sheriff dispatch functions at the local level. These generic elements<br />

have been created for two primary reasons. First, they represent elements with similar types of<br />

interfaces, so from a standardization standpoint, describing how one of the major elements in the<br />

region (e.g. the Sacramento County Traffic Operations Center) interfaces with various public<br />

safety dispatch functions would be the same. Second, describing many systems with a single<br />

element helps keep the architecture from growing too large.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

37 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

Ambulance Operators Private/Public Ambulance Responsible for dispatching private ambulance services throughout the Sacramento region. Existing<br />

Dispatch<br />

Ambulance Operators Private/Public Ambulance Represents ITS equipment in public/private ambulances.<br />

Existing<br />

Vehicles<br />

Archive Data Users Archive Data User Systems Represents systems that make use of various archive data collected in the region. <strong>Plan</strong>ned<br />

California Department of Motor California DMV Licensing and Provides vehicle owner information for violation determination (enforcement by others), and Existing<br />

Vehicles<br />

Registration Division<br />

planning. Included in California CVISN Program <strong>Plan</strong>.<br />

Caltrans Districts<br />

Other Caltrans District<br />

This element is used to create an interface from Caltrans District 3 Maintenance to another Existing<br />

Maintenance<br />

District Maintenance.<br />

Caltrans Districts Other Caltrans District TMCs This element represents transportation management centers at other Caltrans Districts that Existing<br />

might interface with the District 3 RTMC.<br />

Caltrans District 3 Caltrans D3 Data Server District 3 Server that holds real time and archived traffic data. Existing<br />

Caltrans District 3<br />

Caltrans D3 Maintenance Monitor and maintain area freeways, including Interstates 5 and 80, the US Federal Highway Existing<br />

Dispatch<br />

50, and the California State Highway 99. Collocated with the RTMC­D3 ­ Traffic Operations<br />

Caltrans District 3<br />

Caltrans D3 Maintenance This element represents the ITS equipment in Caltrans maintenance vehicles.<br />

Existing<br />

Vehicles<br />

Caltrans District 3<br />

Caltrans D3 Pavement<br />

District pavement condition and asset management system.<br />

Existing<br />

Management System<br />

Caltrans District 3 Caltrans D3 Storage Facility Facilities that store materials for road treatment. Existing<br />

Caltrans District 3 Caltrans D3 Website The website for RTMC­D3. Existing<br />

Caltrans District 3 Caltrans District Shop The Caltrans equipment repair facility. Existing<br />

Caltrans District 3 Caltrans Roadside Equipment This element includes, CMS, CCTV, sensors, HAR, RWIS, fog detection (using RWIS), ramp<br />

meters, traffic signals.<br />

Caltrans District 3<br />

Regional Emergency<br />

The disaster information system run by Caltrans in the event of a natural or man­made<br />

Communications Network disaster.<br />

Caltrans District 3 RTMC­D3 ­ Traffic Operations This element represents the traffic operations center of Caltrans District 3. The center also<br />

contains CHP dispatch. This system monitors and controls the area freeways, including US<br />

Interstates 5 and 80, US Federal Highway 50, and the California Highway 99.<br />

Caltrans HQ California HPMS The Highway Performance Monitoring System (HPMS) is a federally mandated inventory<br />

system and planning study designed to assess the nation’s highway system.<br />

<strong>Plan</strong>ned<br />

Existing<br />

Existing<br />

Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

38 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

Caltrans HQ<br />

Capitol Corridor JPA<br />

Traffic Accident and Surveillance<br />

Analysis System (TASAS)<br />

Capitol Corridor Train Operations<br />

Center<br />

TASAS is a sophisticated version of an EDP traffic records system. It has an accident data<br />

base (AXDB), linked to a highway data base (HDB) which contains description elements of<br />

highway segments, intersections and ramps, access control, and traffic volumes<br />

The Capitol Corridor Train Operations Center is the operations center for this intercity<br />

passenger train system that provides intercity rail service to 16 stations in 7 Northern<br />

California counties: Placer, Sacramento, Yolo, Solano, Contra Costa, Alameda, San<br />

Francisco, and Santa Clara<br />

Capitol Corridor JPA Capitol Corridor Trains Trains operated by Capital Corridor JPA Existing<br />

Capitol Corridor JPA Capitol Corridor Train Stations This element represents ITS systems in the Train Stations. Existing<br />

Chemtrec<br />

ChemTrec Information System ChemTrec Information System provides information on Hazmat loads.<br />

Existing<br />

(Terminator)<br />

CHP CHP Vehicles This element represents ITS systems inside CHP vehicles. Existing<br />

CHP CHP Website Website operated by CHP. Amber Alerts are provided on the website. Existing<br />

CHP Freeway Service Patrol Vehicles This element represents the ITS equipment in freeway service patrol vehicles. Existing<br />

CHP RTMC­CHP This does the CHP dispatch function. Does Cellular 911 (PSAP). Dispatch Freeway Service<br />

Patrol.<br />

CHP<br />

Statewide Integrated Reporting The Statewide Integrated Reporting System (SWITRS) consists of two components working<br />

System (SWITRS)<br />

in conjunction to record and manage accident/crash reporting data. The server component<br />

resides on a central database server, which hosts numerous other applications.<br />

City of Citrus Heights Citrus Heights Maintenance The dispatch function for Citrus Heights maintenance and construction vehicles.<br />

Existing<br />

Dispatch<br />

City of Citrus Heights Citrus Heights Roadside ITS field equipment owned or operated by Citrus Heights.<br />

<strong>Plan</strong>ned<br />

Equipment<br />

City of Citrus Heights Citrus Heights Traffic Operations Proposed project L2 form From MMA study: "Transportation <strong>Plan</strong>ning Guidelines for the City <strong>Plan</strong>ned<br />

Center<br />

of Citrus Heights Traffic Control System… ”<br />

City of Citrus Heights City of Citrus Heights Website Website for the City of Citrus Heights. Existing<br />

City of Davis City of Davis Field Equipment ITS field equipment owned and operated by City of Davis. <strong>Plan</strong>ned<br />

City of Davis<br />

City of Davis Maintenance The dispatch function for City of Davis maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Davis City of Davis TOC The traffic operations center for the City of Davis. <strong>Plan</strong>ned<br />

City of Davis/UC Davis Unitrans Transit Dispatch Dispatch function for Unitrans fixed route system. Existing<br />

City of Davis/UC Davis Unitrans Transit Vehicles Fixed Route transit vehicles operated by Unitrans Existing<br />

City of Davis City of Davis Website Website for the City of Davis. Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

39 Final Report<br />

September 2005<br />

Existing<br />

<strong>Plan</strong>ned<br />

Existing<br />

Existing


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

City of Elk Grove City of Elk Grove Field Equipment ITS Field equipment owned and operated by City of Elk Grove. <strong>Plan</strong>ned<br />

City of Elk Grove<br />

City of Elk Grove Maintenance The dispatch function for City of Elk Grove maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Elk Grove City of Elk Grove TOC The Traffic Operations Center for the City of Elk Grove <strong>Plan</strong>ned<br />

City of Elk Grove e­tran Transit Center The Transit Operations Center for the e­tran system, which is operated by City of Elk Grove <strong>Plan</strong>ned<br />

and provides fixed route and paratransit services between Elk Grove, Laguna and Sacramento<br />

City of Elk Grove e­tran Transit Vehicles Fixed route and paratransit buses operated by e­tran. Existing<br />

City of Folsom City of Folsom Field Equipment ITS Field equipment owned and operated by City of Folsom <strong>Plan</strong>ned<br />

City of Folsom<br />

City of Folsom Maintenance The dispatch function for the City of Folsom maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Folsom City of Folsom TOC The traffic operations center for the City of Folsom. <strong>Plan</strong>ned<br />

City of Folsom Folsom Stage Line Vehicles Fixed route and paratransit vehicles of Folsom Stage Lines. Existing<br />

City of Folsom<br />

Folsom Stage Lines Transit Transit dispatch function for Folsom Stage Lines fixed route, commuter, and dial­a­ride <strong>Plan</strong>ned<br />

Dispatch<br />

operations.<br />

City of Rancho Cordova City of Rancho Cordova Field ITS field equipment owned and operated by City of Rancho Cordova.<br />

<strong>Plan</strong>ned<br />

Equipment<br />

City of Rancho Cordova City of Rancho Cordova<br />

The dispatch function for the City of Rancho Cordova maintenance vehicles.<br />

Existing<br />

Maintenance Dispatch<br />

City of Rancho Cordova City of Rancho Cordova TOC The traffic operations center for the City of Rancho Cordova. <strong>Plan</strong>ned<br />

City of Roseville<br />

City of Roseville Maintenance The dispatch function for the City of Roseville maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Roseville<br />

City of Roseville Police and Fire Dispatch function for City of Roseville Police and Fire.<br />

Existing<br />

Dispatch<br />

City of Roseville<br />

City of Roseville Roadside ITS Equipment owned and operated by City of Roseville.<br />

Existing<br />

Equipment<br />

City of Roseville City of Roseville TOC Acceding to SACOG report (Project 6), this is actually just a centralized server. The data <strong>Plan</strong>ned<br />

archiving function is a future capability.<br />

City of Roseville City of Roseville Website The website operated by the City of Roseville. <strong>Plan</strong>ned<br />

City of Roseville<br />

Roseville Transit Management Represents dispatch function of Roseville Transit. AVL/AVI capability will be added in the Existing<br />

Center (Dispatch)<br />

future.<br />

City of Roseville Roseville Transit Vehicles This element represents the ITS equipment in Roseville Transit vehicles. Existing<br />

City of Sacramento DPW City of Sacramento Equipment<br />

Shop<br />

Equipment repair facility for City of Sacramento<br />

Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

40 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

City of Sacramento DPW City of Sacramento Maintenance The dispatch function for the City of Sacramento maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Sacramento DPW City of Sacramento Maintenance This element represents the ITS equipment in City of Sacramento maintenance vehicles. Existing<br />

Vehicles<br />

City of Sacramento DPW City of Sacramento TOC The traffic operations center for the City of Sacramento. Existing<br />

City of Sacramento DPW City of Sacramento Website The website for the City of Sacramento. Existing<br />

City of Sacramento DPW Sacramento City Roadside This element represents ITS field equipment owned and operated by Sacramento City. Existing<br />

Equipment<br />

City of Sacramento Fire Sacramento City Fire Vehicles This element represents the ITS equipment in Sacramento City fire vehicles. Existing<br />

Department<br />

City of Sacramento Police Sacramento City Police<br />

This element represents the dispatch function of Sacramento City Police.<br />

Existing<br />

Department Communications<br />

City of Sacramento Police Sacramento City Police Vehicles This element represents the ITS equipment in Sacramento City police vehicles. Existing<br />

City of West Sacramento City of West Sacramento The dispatch function for the City of West Sacramento maintenance and construction Existing<br />

Engineering Division<br />

Maintenance Dispatch<br />

vehicles.<br />

City of West Sacramento City of West Sacramento ITS field equipment owned and operated by City of West Sacramento.<br />

Existing<br />

Engineering Division<br />

Roadside Equipment<br />

City of West Sacramento City of West Sacramento TOC The traffic operations center for the city of West Sacramento. <strong>Plan</strong>ned<br />

Engineering Division<br />

City of West Sacramento City of West Sacramento Website The website for the City of West Sacramento. <strong>Plan</strong>ned<br />

Engineering Division<br />

City of Woodland<br />

City of Woodland Field<br />

ITS field equipment owned and operated by City of Woodland.<br />

<strong>Plan</strong>ned<br />

Equipment<br />

City of Woodland<br />

City of Woodland Maintenance The dispatch function for the City of Woodland maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Woodland City of Woodland TOC The traffic operations center for the City of Woodland. <strong>Plan</strong>ned<br />

City of Yuba City City of Yuba City Field Equipment ITS Field equipment owned and operated by Yuba City. <strong>Plan</strong>ned<br />

City of Yuba City<br />

City of Yuba City Maintenance The dispatch function for the Yuba City maintenance vehicles.<br />

Existing<br />

Dispatch<br />

City of Yuba City City of Yuba City TOC The traffic operations center for the city of Yuba City. <strong>Plan</strong>ned<br />

Commercial Vehicle Operators Commercial Vehicle Fleet Fleet dispatch systems for private commercial vehicle firms.<br />

Existing<br />

Dispatch Systems<br />

Commercial Vehicle Operators Commercial Vehicles Represents ITS equipment on commercial vehicles. Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

41 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

County Government County AQMD County Air Quality Management District represents counties in the region other than<br />

Existing<br />

Sacramento (e.g. El Dorado, Placer, Solano and Yolo).<br />

County Government County EOC Represents Emergency Operations Centers at the County Level. Existing<br />

County Government County Maintenance Dispatch Maintenance dispatch function for counties other than Sacramento. Existing<br />

County Government County Maintenance Vehicles This element represents the ITS equipment in county maintenance vehicles Existing<br />

County Government County Roadside Equipment ITS equipment used by County maintenance organizations. <strong>Plan</strong>ned<br />

County Government<br />

County Sheriff Communications Represents sheriff dispatch function in counties in the region outside of Sacramento County. Existing<br />

Centers<br />

County Government Other County TOC Represents traffic operations centers for counties in the region other than Sacramento. <strong>Plan</strong>ned<br />

County/Municipal Government City/County Animal Control Dispatch function for municipal or county animal control. Existing<br />

El Dorado County Transit El Dorado Transit Dispatch Dispatch function for El Dorado Transit fixed route and paratransit services. <strong>Plan</strong>ned<br />

Authority<br />

El Dorado County Transit El Dorado Transit Vehicles Fixed route and paratransit vehicles operated by El Dorado Transit. Existing<br />

Authority<br />

Financial Institution Financial Institutions Represents the financial institutions the regional transit agencies will use as part of electronic Existing<br />

fare payment systems.<br />

Independent School Districts School Bus Dispatch This element represents the dispatch function for any of the region's school districts. Existing<br />

Independent School Districts School Buses This element represents the ITS equipment in school buses. Existing<br />

Local Fire Districts Local Fire/EMS Dispatch Centers Municipal dispatch of fire and EMS vehicles, often connected with a PSAP. Existing<br />

Local Fire Districts Local Fire/EMS Vehicles This element represents the ITS equipment in fire and EMS vehicles that are dispatched by Existing<br />

the Local Fire/EMS Dispatch.<br />

Local Government Municipal EOC Represents EOCs at the municipal level (e.g. Sacramento, Citrus Heights). Existing<br />

Local Government<br />

Municipal Equipment Repair Equipment repair facility operated by a municipality.<br />

Existing<br />

Facility<br />

Local Government Municipal Maintenance Vehicles Maintenance vehicles operated by municipalities in the region. Existing<br />

Local Government Regional EOC City, County, and some municipalities (Citrus Heights, Rancho Cordova, Elk Grove). Existing<br />

Local News Media Local Print and Broadcast Media Local TV (including cable TV), radio (e.g. 560KLVI), and newspapers. Existing<br />

Local Police Departments Local Law Enforcement Vehicles This element represents the ITS equipment in local (municipal) police vehicles. Existing<br />

Local Police Departments Local Police Dispatch This element represents local (municipal) dispatch of police vehicles. The function may Existing<br />

include the PSAP for municipalities.<br />

Local Traffic Agencies Municipal Field Equipment Folsom, Elk Grove and any other cities identified at a later time whose field equipment is<br />

managed by City of Sac, or County of Sac. Also include Yolo County Roadside and Placer<br />

County Roadside Equipment.<br />

<strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

42 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

Local Traffic Agencies Municipal Maintenance Dispatch The dispatch function for other municipalities within the Sacramento region's maintenance Existing<br />

and construction vehicles.<br />

Local Traffic Agencies Municipal TOCs The traffic operations center for municipalities within the region not called out with specific Existing<br />

elements. Would include cities such as Rocklin, Loomis, Lincoln, Woodland, Winters, Yuba<br />

City, Colfax, Galt, Auburn, and Placerville.<br />

Local Traffic Agencies Municipal Websites The website that is operated by local municipalities. <strong>Plan</strong>ned<br />

NOAA Weather Information Providers Represents private and public (National Weather Service) systems providing weather info. Existing<br />

Other Law Enforcement Other Law Enforcement Dispatch The element represents a law enforcement dispatch center and is used to identify interfaces Existing<br />

Center<br />

from one law enforcement dispatch element to another.<br />

Other Local Transit Operators Local Transit Dispatch Centers Represents transit systems not covered by specific elements. Such as Placer county (fixed Existing<br />

and paratransit), City of Lincoln, Davis Community Transit (paratransit), UC Med Center<br />

Shuttle (TAPS ­ UCD Transportation and Parking Sys), Hornet (Sac State).<br />

Other Local Transit Operators Local Transit Vehicles This element represents the ITS equipment in transit vehicles dispatched by those transit Existing<br />

systems included in the Local Transit Dispatch Centers element.<br />

Paratransit, Inc. Paratransit Vehicle This element represents the ITS equipment in the Paratransit vehicles. Existing<br />

Paratransit, Inc. Paratransit, Inc. Paratransit service for disabled and elderly. They also subcontract to various communities Existing<br />

and social services, including subcontracting to RT to provide their required paratransit<br />

services. Also do elderly and disabled service to Sacramento County.<br />

Placer County Transit Placer County Transit Dispatch Dispatch function for Placer County Transit fixed route service. Existing<br />

Placer County Transit Placer County Transit Vehicles Fixed route, dial­a­ride, and commuter vehicles operated by Placer County Transit. Existing<br />

Private Sector ISP<br />

Private Traveler Information Information service providers that provide traffic information, weather conditions, transit <strong>Plan</strong>ned<br />

Service Providers<br />

information, and general broadcast information to the traveling public.<br />

Private Taxi Companies Taxi Dispatch Dispatch function of private Taxi companies. Existing<br />

Private Transit Providers Private Transit Provider Dispatch Represents dispatch function of any private transit providers (e.g. Supershuttle). Existing<br />

Private/Public Utilities Utilities Dispatch Represents the dispatch function of private or public utilities in the region. Existing<br />

Regional Event Promoters Regional Event Promoters The event promoters that are in the Sacramento region. Existing<br />

Regional Hospitals Regional Medical Centers This element represents the Medical Centers in the region. Existing<br />

Regional Rail Providers Heavy Rail Wayside Equipment This element represents the railroad operated equipment (gates, flashers, and the controller Existing<br />

that operates them).<br />

Regional Rail Providers Regional Railroad Operations Represents the operations center(s) of private freight railroads. Existing<br />

Roseville Transit Roseville Transit Dispatch Dispatch function for Roseville Transit fixed route service. Existing<br />

Roseville Transit Roseville Transit Vehicles Fixed route, dial­a­ride, and commuter vehicles operated by Roseville Transit. Existing<br />

SACOG Regional Traffic Count Archive Data Collection and storage system(s) for regional traffic counts. <strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

43 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

SACOG SACOG Data Repository Add ITS elements from cities and counties to existing geo system. Also bus­stops. Primary <strong>Plan</strong>ned<br />

interest is in location of elements. Asset tracking.<br />

SACOG Sacramento Region 511 Website The Sacramento Region 511 website (http://www.sacregion511.org/) provides regional traffic Existing<br />

and transit information.<br />

Sacramento County<br />

Sacramento County<br />

Dispatch County Hazmat and maintenance vehicles (after hours).<br />

Existing<br />

Telecommunications Center<br />

Sacramento County Sacramento County Website The website for Sacramento County. Existing<br />

Sacramento County Airport Airport Dispatch Center Dispatch of airport fire personnel. Existing<br />

System<br />

Sacramento County Airport Sacramento International Airport The maintenance and construction dispatch function for the Sacramento International Airport. <strong>Plan</strong>ned<br />

System<br />

Maintenance Dispatch<br />

Sacramento County Airport Sacramento International Airport ITS Field equipment owned and operated by Sacramento International Airport.<br />

Existing<br />

System<br />

Roadside Equipment<br />

Sacramento County Airport Sacramento International Airport This element is assumed to be present, but no one was present at the workshop who could Existing<br />

System<br />

TMC<br />

specifically speak for the center.<br />

Sacramento County Airport Sacramento International Airport The website operated by the Sacramento international Airport that provides road conditions, <strong>Plan</strong>ned<br />

System<br />

Website<br />

transit information, and other traveler information to the traveling public.<br />

Sacramento County Sheriff Sacramento County Sheriff Dept. This element represents the dispatch function of Sacramento County Sheriff.<br />

Existing<br />

Communications<br />

Sacramento County Sheriff Sacramento County Sheriff Vehicle This element represents the ITS equipment in Sacramento County Sheriff vehicles. Existing<br />

Sacramento County<br />

Sacramento County Equipment County shop with responsibility for vehicle and equipment repair.<br />

Existing<br />

Transportation Department Repair Facility<br />

Sacramento County<br />

Sacramento County Maintenance The maintenance and construction dispatch function for Sacramento County.<br />

Existing<br />

Transportation Department Service Center<br />

Sacramento County<br />

Sacramento County Maintenance This element represents the ITS equipment in Sacramento County maintenance vehicles. Existing<br />

Transportation Department Vehicles<br />

Sacramento County<br />

Sacramento County Roadside ITS Field equipment owned and operated by Sacramento County.<br />

Existing<br />

Transportation Department Equipment<br />

Sacramento County<br />

Sacramento County Traffic Currently, the County has centralized control. Staff dial into VMS masters. The Center has Existing<br />

Transportation Department Operations Center<br />

been completed. Monitoring DMS, CCTV, sensors, weigh in motion.<br />

Sacramento Fire JPA Sacramento Regional Fire/ EMS This system also does data archiving, as does all emergency management centers in the Existing<br />

Comm. Center<br />

region. City and County. PSAP for City and County.<br />

Sacramento Metropolitan Air<br />

Quality Management District<br />

Air Quality Website www.airquality.org Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

44 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

Sacramento Metropolitan Air Sacramento Metro AQMD Office of Sacramento Metro Air Quality Management District. Existing<br />

Quality Management District<br />

Sacramento Region<br />

STARNET ISP<br />

This covers both web site, dynamic ride sharing, regional transit trip planning sometime in the <strong>Plan</strong>ned<br />

(Partnership)<br />

future.<br />

Sacramento Region<br />

STARNET Server<br />

This element covers the server functions of data collection and archiving. Also facilitates data <strong>Plan</strong>ned<br />

(Partnership)<br />

sharing and sharing of control between centers.<br />

Sacramento Regional Transit Light Rail Station Parking Mgmt. This element represents the ITS equipment used in the operation of the Light Rail Station <strong>Plan</strong>ned<br />

parking lot.<br />

Sacramento Regional Transit Light Rail Transit Management Light Rail Metro Control Center. The existing transit control center will evolve to have Existing<br />

Center<br />

Automated Train Control capabilities.<br />

Sacramento Regional Transit Regional Fare Card Used in conjunction with automated fare payment machines on transit buses, and can be <strong>Plan</strong>ned<br />

purchased at transit kiosks throughout the region.<br />

Sacramento Regional Transit Regional Transit Bus Vehicle This element represents the ITS equipment on Regional Transit buses. Existing<br />

Sacramento Regional Transit Regional Transit LRT Vehicle Light Rail Vehicles Existing<br />

Sacramento Regional Transit RT Passenger Information Signs This element represents the passenger information signs planned for deployment by RT. <strong>Plan</strong>ned<br />

Sacramento Regional Transit RT Police Services This element represents the dispatch function for RT Police. Existing<br />

Sacramento Regional Transit RT Security Monitoring Equipment Equipment such as cameras that RT uses to monitor tracks and check for broken gates. Existing<br />

Sacramento Regional Transit RT Transit Kiosks Existing static signs will evolve into interactive kiosks. True of all local transit agencies. <strong>Plan</strong>ned<br />

Sacramento Regional Transit RT Transit Management Center Sacramento Regional Transit District (RT) Bus Dispatch Center. It is noted that signal priority Existing<br />

is in the planning phase. However, it is not known in which jurisdictions this applies. It is<br />

assumed that priority will be provided in those areas which will provide the biggest<br />

improvement to transit flow.<br />

Sacramento Regional Transit RT Transit Monitors This element represents planned monitors to display transit information. <strong>Plan</strong>ned<br />

Sacramento Regional Transit RT Wayside Equipment This element represents the wayside equipment for the Light Rail system. Existing<br />

Sacramento Regional Transit RT Website This element represents the RT website, which displays information about RT schedules, etc. Existing<br />

State Office of Emergency California Office of Emergency The OES Warning Center is staffed 24 hours a day, 365 days a year. From this center, Existing<br />

Services<br />

Services Operations Centers warning controllers speak with county OESs and the National Warning Center in Berryville,<br />

Virginia on a daily basis. OES also maintains a 24­hour toll­free toxic release.<br />

Travelers ­ The Public Driver Drivers that use the transportation system. Existing<br />

Travelers ­ The Public Pedestrian Users of the transportation system. Existing<br />

Travelers ­ The Public User Personal Computing<br />

Existing<br />

Devices<br />

User Personal Computing Devices refers to equipment an individual owns and can<br />

personalize with their choices for information about transportation networks. An Internetconnected<br />

PC is an example.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

45 Final Report<br />

September 2005


Table 4.3: Inventory by Stakeholder<br />

Stakeholder Name Element Name Element Description Status<br />

Travelers ­ The Public Vehicles This element represents vehicles that are used as probes in the future. It also represents Existing<br />

vehicles that receive HAR broadcasts and other traveler information.<br />

UC Berkeley<br />

Caltrans Performance Monitoring The Caltrans Performance Measurement System (PeMS) is an Internet­based tool that can Existing<br />

System (PeMS)<br />

be used to monitor conditions on urban freeways. PeMS allows users to produce congestion<br />

monitoring reports using automatically collected data from sensors statewide.<br />

Yolo County Transportation Yolo Bus Dispatch Center This element represents the transit dispatch function of Yolo Bus. Existing<br />

District<br />

Yolo County Transportation Yolo County Bus Website Website providing information on Yolo County Transit Existing<br />

District<br />

Yolo County Transportation Yolo County Buses This element represents the ITS equipment in Yolo County buses. Existing<br />

District<br />

Yuba­Sutter Transit Yuba­Sutter Transit Center Transit operations center for Yuba­Sutter Transit. It operates five fixed routes providing Existing<br />

service to Yuba City, Marysville, Linda and Olivehurst. Also commuter service to Sacramento<br />

and paratransit services to the area.<br />

Yuba­Sutter Transit Yuba­Sutter Transit Vehicles Fixed route and paratransit vehicles of Yuba­Sutter Transit. Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

46 Final Report<br />

September 2005


Systems by Architecture Entity<br />

Each element in the regional architecture inventory is mapped to one or more entities from the<br />

National ITS Architecture. In version 5.0 of the National ITS Architecture (on which this<br />

architecture is based) there are 95 entities defined. These 22 subsystems and 73 terminators<br />

describe a wide array of systems that provide ITS services, or interface with systems that provide<br />

ITS services. The mapping of regional architecture elements to National ITS Architecture<br />

entities has two primary benefits. First it allows the full set of information flows contained in the<br />

National ITS Architecture to be used in the description of the regional ITS architecture<br />

interfaces, and second, it allows the elements of the regional architecture to be grouped by like<br />

entity.<br />

Table 4.4 provides just such a sorting of inventory elements by entity. This table allows the<br />

users of the architecture to immediately identify all the elements that have functions relating to<br />

the subsystems defined in the National ITS Architecture Version 5.0 (e.g. transit management).<br />

The Sacramento Regional ITS Architecture inventory contains the following number of elements<br />

mapped to different types of entities:<br />

• Archived Data Management: 13<br />

• Emergency Management: 30<br />

• Information Service Providers: 22<br />

• Maintenance and Construction Management: 22<br />

• Traffic Management: 18<br />

• Transit Management: 16<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

47 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Archived Data Management California HPMS Caltrans HQ Existing<br />

Archived Data Management Caltrans Performance Monitoring UC Berkeley<br />

Existing<br />

System (PeMS)<br />

Archived Data Management City of Roseville TOC City of Roseville <strong>Plan</strong>ned<br />

Archived Data Management City of Sacramento TOC City of Sacramento DPW Existing<br />

Archived Data Management Regional Traffic Count Archive SACOG <strong>Plan</strong>ned<br />

Archived Data Management RT Transit Management Center Sacramento Regional Transit Existing<br />

Archived Data Management RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Archived Data Management SACOG Data Repository SACOG <strong>Plan</strong>ned<br />

Archived Data Management Sacramento County Traffic Sacramento County Transportation Existing<br />

Operations Center<br />

Department<br />

Archived Data Management STARNET ISP Sacramento Region (Partnership) <strong>Plan</strong>ned<br />

Archived Data Management STARNET Server Sacramento Region (Partnership) <strong>Plan</strong>ned<br />

Archived Data Management Statewide Integrated Reporting CHP<br />

Existing<br />

System (SWITRS)<br />

Archived Data Management Traffic Accident and Surveillance Caltrans HQ<br />

Existing<br />

Analysis System (TASAS)<br />

Archived Data User Systems Archive Data User Systems Archive Data Users <strong>Plan</strong>ned<br />

Asset Management<br />

Caltrans D3 Pavement<br />

Caltrans District 3<br />

Existing<br />

Management System<br />

Basic Vehicle Vehicles Travelers ­ The Public Existing<br />

Care Facility Regional Medical Centers Regional Hospitals Existing<br />

Commercial Vehicle Subsystem Commercial Vehicles Commercial Vehicle Operators Existing<br />

DMV<br />

California DMV Licensing and California Department of Motor Existing<br />

Registration Division<br />

Vehicles<br />

Driver Driver Travelers ­ The Public Existing<br />

Emergency Management Airport Dispatch Center Sacramento County Airport System Existing<br />

Emergency Management California Office of Emergency State Office of Emergency Services Existing<br />

Services Operations Centers<br />

Emergency Management City of Roseville Police and Fire City of Roseville<br />

Existing<br />

Dispatch<br />

Emergency Management City of West Sacramento TOC City of West Sacramento<br />

<strong>Plan</strong>ned<br />

Engineering Division<br />

Emergency Management County EOC County Government Existing<br />

Emergency Management County Sheriff Communications County Government<br />

Existing<br />

Centers<br />

Emergency Management El Dorado Transit Dispatch El Dorado County Transit Authority <strong>Plan</strong>ned<br />

Emergency Management e­tran Transit Center City of Elk Grove <strong>Plan</strong>ned<br />

Emergency Management Folsom Stage Lines Transit City of Folsom<br />

<strong>Plan</strong>ned<br />

Dispatch<br />

Emergency Management Light Rail Transit Management Sacramento Regional Transit Existing<br />

Center<br />

Emergency Management Local Fire/EMS Dispatch Centers Local Fire Districts Existing<br />

Emergency Management Local Police Dispatch Local Police Departments Existing<br />

Emergency Management Local Transit Dispatch Centers Other Local Transit Operators Existing<br />

Emergency Management Municipal EOC Local Government Existing<br />

Emergency Management Other Law Enforcement Dispatch<br />

Center<br />

Other Law Enforcement<br />

Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

48 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Emergency Management Placer County Transit Dispatch Placer County Transit Existing<br />

Emergency Management Private/Public Ambulance Dispatch Ambulance Operators Existing<br />

Emergency Management Regional Emergency Operations Local Government<br />

Existing<br />

Center<br />

Emergency Management Roseville Transit Management City of Roseville<br />

Existing<br />

Center (Dispatch)<br />

Emergency Management RT Police Services Sacramento Regional Transit Existing<br />

Emergency Management RT Transit Management Center Sacramento Regional Transit Existing<br />

Emergency Management RTMC­CHP CHP Existing<br />

Emergency Management RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Emergency Management Sacramento City Police<br />

City of Sacramento Police<br />

Existing<br />

Department Communications<br />

Emergency Management Sacramento County Sheriff Dept. Sacramento County Sheriff Existing<br />

Communications<br />

Emergency Management Sacramento County<br />

Sacramento County<br />

Existing<br />

Telecommunications Center<br />

(DISPATCH)<br />

Emergency Management Sacramento Regional Fire/ EMS Sacramento Fire JPA<br />

Existing<br />

Comm. Center<br />

Emergency Management School Bus Dispatch Independent School Districts Existing<br />

Emergency Management Unitrans Transit Dispatch City of Davis Existing<br />

Emergency Management Yolo Bus Dispatch Center Yolo County Transportation District Existing<br />

Emergency Management Yuba­Sutter Transit Center Yuba­Sutter Transit Existing<br />

Emergency Vehicle Subsystem CHP Vehicles CHP Existing<br />

Emergency Vehicle Subsystem Freeway Service Patrol Vehicles CHP Existing<br />

Emergency Vehicle Subsystem Local Fire/EMS Vehicles Local Fire Districts Existing<br />

Emergency Vehicle Subsystem Local Law Enforcement Vehicles Local Police Departments Existing<br />

Emergency Vehicle Subsystem Private/Public Ambulance Vehicles Ambulance Operators Existing<br />

Emergency Vehicle Subsystem Sacramento City Fire Vehicles City of Sacramento Fire Department Existing<br />

Emergency Vehicle Subsystem Sacramento City Police Vehicles City of Sacramento Police Existing<br />

Emergency Vehicle Subsystem Sacramento County Sheriff Vehicle Sacramento County Sheriff Existing<br />

Emissions Management City of Roseville TOC City of Roseville <strong>Plan</strong>ned<br />

Emissions Management County AQMD County Government Existing<br />

Emissions Management Municipal TOCs Local Traffic Agencies Existing<br />

Emissions Management RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Emissions Management Sacramento County Traffic Sacramento County Transportation Existing<br />

Operations Center<br />

Department<br />

Emissions Management Sacramento International Airport Sacramento County Airport System Existing<br />

TMC<br />

Emissions Management Sacramento Metro AQMD Sacramento Metropolitan Air Quality Existing<br />

Management District (AQMD)<br />

Enforcement Agency RT Police Services Sacramento Regional Transit Existing<br />

Equipment Repair Facility Caltrans District Shop Caltrans District 3 Existing<br />

Equipment Repair Facility City of Sacramento Equipment City of Sacramento DPW<br />

Existing<br />

Shop<br />

Equipment Repair Facility Municipal Equipment Repair Local Government<br />

Existing<br />

Facility<br />

Equipment Repair Facility Sacramento County Equipment<br />

Repair Facility<br />

Sacramento County Transportation<br />

Department<br />

Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

49 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Event Promoters Regional Event Promoters Regional Event Promoters Existing<br />

Financial Institution Financial Institutions Financial Institution Existing<br />

Fleet and Freight Management Commercial Vehicle Fleet Dispatch Commercial Vehicle Operators Existing<br />

Systems<br />

Hazardous Materials<br />

ChemTrec Information System Chemtrec<br />

Existing<br />

Information Subsystem (Terminator)<br />

Information Service Provider Air Quality Website Sacramento Metropolitan Air Quality Existing<br />

Management District (AQMD)<br />

Information Service Provider Caltrans D3 Data Server Caltrans District 3 Existing<br />

Information Service Provider Caltrans D3 Website Caltrans District 3 Existing<br />

Information Service Provider Caltrans Performance Monitoring UC Berkeley<br />

Existing<br />

System (PeMS)<br />

Information Service Provider CHP Website CHP Existing<br />

Information Service Provider City of Citrus Heights Website City of Citrus Heights Existing<br />

Information Service Provider City of Roseville Website City of Roseville <strong>Plan</strong>ned<br />

Information Service Provider City of Sacramento Website City of Sacramento DPW Existing<br />

Information Service Provider City of West Sacramento Website City of West Sacramento<br />

<strong>Plan</strong>ned<br />

Engineering Division<br />

Information Service Provider Light Rail Transit Management Sacramento Regional Transit Existing<br />

Center<br />

Information Service Provider Municipal Websites Local Traffic Agencies <strong>Plan</strong>ned<br />

Information Service Provider Private Traveler Information Private Sector ISP<br />

<strong>Plan</strong>ned<br />

Service Providers<br />

Information Service Provider RT Transit Management Center Sacramento Regional Transit Existing<br />

Information Service Provider RT Website Sacramento Regional Transit Existing<br />

Information Service Provider RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Information Service Provider Sacramento County Traffic Sacramento County Transportation Existing<br />

Operations Center<br />

Department<br />

Information Service Provider Sacramento County Website Sacramento County Existing<br />

Information Service Provider Sacramento International Airport Sacramento County Airport System Existing<br />

TMC<br />

Information Service Provider Sacramento International Airport Sacramento County Airport System <strong>Plan</strong>ned<br />

Website<br />

Information Service Provider Sacramento Region 511 Website SACOG Existing<br />

Information Service Provider STARNET ISP Sacramento Region (Partnership) <strong>Plan</strong>ned<br />

Information Service Provider Yolo County Bus Website Yolo County Transportation District Existing<br />

Maintenance and Construction Caltrans D3 Maintenance Dispatch Caltrans District 3 Existing<br />

Management<br />

Maintenance and Construction Citrus Heights Maintenance City of Citrus Heights<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of Davis Maintenance City of Davis<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of Elk Grove Maintenance City of Elk Grove<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of Folsom Maintenance City of Folsom<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction<br />

Management<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

City of Rancho Cordova<br />

Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

50 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Maintenance and Construction City of Roseville Maintenance City of Roseville<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of Roseville TOC City of Roseville <strong>Plan</strong>ned<br />

Management<br />

Maintenance and Construction City of Sacramento Maintenance City of Sacramento DPW<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of West Sacramento<br />

City of West Sacramento<br />

Existing<br />

Management<br />

Maintenance Dispatch<br />

Engineering Division<br />

Maintenance and Construction City of Woodland Maintenance City of Woodland<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City of Yuba City Maintenance City of Yuba City<br />

Existing<br />

Management<br />

Dispatch<br />

Maintenance and Construction City/County Animal Control County/Municipal Government Existing<br />

Management<br />

Maintenance and Construction County Maintenance Dispatch County Government Existing<br />

Management<br />

Maintenance and Construction Municipal Maintenance Dispatch Local Traffic Agencies Existing<br />

Management<br />

Maintenance and Construction Other Caltrans District<br />

Caltrans Districts<br />

Existing<br />

Management<br />

Maintenance<br />

Maintenance and Construction RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Management<br />

Maintenance and Construction Sacramento County Maintenance Sacramento County Transportation Existing<br />

Management<br />

Service Center<br />

Department<br />

Maintenance and Construction Sacramento County<br />

Sacramento County<br />

Existing<br />

Management<br />

Telecommunications Center<br />

Maintenance and Construction Sacramento County Traffic Sacramento County Transportation Existing<br />

Management<br />

Operations Center<br />

Department<br />

Maintenance and Construction Sacramento International Airport Sacramento County Airport System <strong>Plan</strong>ned<br />

Management<br />

Maintenance Dispatch<br />

Maintenance and Construction Utilities Dispatch Private/Public Utilities Existing<br />

Management<br />

Maintenance and Construction Caltrans D3 Maintenance Vehicles Caltrans Distrist 3 Existing<br />

Vehicle<br />

Maintenance and Construction City of Sacramento Maintenance City of Sacramento DPW<br />

Existing<br />

Vehicle<br />

Vehicles<br />

Maintenance and Construction County Maintenance Vehicles County Government Existing<br />

Vehicle<br />

Maintenance and Construction Municipal Maintenance Vehicles Local Government Existing<br />

Vehicle<br />

Maintenance and Construction Sacramento County Maintenance Sacramento County Transportation Existing<br />

Vehicle<br />

Vehicles<br />

Department<br />

Media Local Print and Broadcast Media Local News Media Existing<br />

Multimodal Transportation Sacramento International Airport Sacramento County Airport System Existing<br />

Service Provider<br />

TMC<br />

Parking Management Light Rail Station Parking Mgmt. Sacramento Regional Transit <strong>Plan</strong>ned<br />

Pedestrians Pedestrian Travelers ­ The Public Existing<br />

Personal Information Access User Personal Computing Devices Travelers ­ The Public Existing<br />

Rail Operations Regional Railroad Operations Regional Rail Providers Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

51 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Remote Traveler Support RT Passenger Information Signs Sacramento Regional Transit <strong>Plan</strong>ned<br />

Remote Traveler Support RT Transit Kiosks Sacramento Regional Transit <strong>Plan</strong>ned<br />

Remote Traveler Support RT Transit Monitors Sacramento Regional Transit <strong>Plan</strong>ned<br />

Roadway Subsystem Caltrans Roadside Equipment Caltrans District 3 <strong>Plan</strong>ned<br />

Roadway Subsystem<br />

Citrus Heights Roadside<br />

City of Citrus Heights<br />

<strong>Plan</strong>ned<br />

Equipment<br />

Roadway Subsystem City of Davis Field Equipment City of Davis <strong>Plan</strong>ned<br />

Roadway Subsystem City of Elk Grove Field Equipment City of Elk Grove <strong>Plan</strong>ned<br />

Roadway Subsystem City of Folsom Field Equipment City of Folsom <strong>Plan</strong>ned<br />

Roadway Subsystem<br />

City of Rancho Cordova Field City of Rancho Cordova<br />

<strong>Plan</strong>ned<br />

Equipment<br />

Roadway Subsystem<br />

City of Roseville Roadside City of Roseville<br />

Existing<br />

Equipment<br />

Roadway Subsystem<br />

City of West Sacramento Roadside City of West Sacramento<br />

Existing<br />

Equipment<br />

Engineering Division<br />

Roadway Subsystem City of Woodland Field Equipment City of Woodland <strong>Plan</strong>ned<br />

Roadway Subsystem City of Yuba City Field Equipment City of Yuba City <strong>Plan</strong>ned<br />

Roadway Subsystem County Roadside Equipment County Government <strong>Plan</strong>ned<br />

Roadway Subsystem Municipal Field Equipment Local Traffic Agencies <strong>Plan</strong>ned<br />

Roadway Subsystem<br />

Sacramento City Roadside City of Sacramento DPW<br />

Existing<br />

Equipment<br />

Roadway Subsystem<br />

Sacramento County Roadside Sacramento County Transportation Existing<br />

Equipment<br />

Department<br />

Roadway Subsystem<br />

Sacramento International Airport Sacramento County Airport System Existing<br />

Roadside Equipment<br />

Security Monitoring Subsystem RT Security Monitoring Equipment Sacramento Regional Transit Existing<br />

Storage Facility Caltrans D3 Storage Facility Caltrans District 3 Existing<br />

Traffic Management<br />

Citrus Heights Traffic Operations City of Citrus Heights<br />

<strong>Plan</strong>ned<br />

Center<br />

Traffic Management City of Davis TOC City of Davis <strong>Plan</strong>ned<br />

Traffic Management City of Elk Grove TOC City of Elk Grove <strong>Plan</strong>ned<br />

Traffic Management City of Folsom TOC City of Folsom <strong>Plan</strong>ned<br />

Traffic Management City of Rancho Cordova TOC City of Rancho Cordova <strong>Plan</strong>ned<br />

Traffic Management City of Roseville TOC City of Roseville <strong>Plan</strong>ned<br />

Traffic Management City of Sacramento TOC City of Sacramento DPW Existing<br />

Traffic Management City of West Sacramento TOC City of West Sacramento<br />

<strong>Plan</strong>ned<br />

Engineering Division<br />

Traffic Management City of Woodland TOC City of Woodland <strong>Plan</strong>ned<br />

Traffic Management City of Yuba City TOC City of Yuba City <strong>Plan</strong>ned<br />

Traffic Management Municipal TOCs Local Traffic Agencies Existing<br />

Traffic Management Other County TOC County Government <strong>Plan</strong>ned<br />

Traffic Management Other Caltrans District TMCs Caltrans Districts Existing<br />

Traffic Management RTMC­CHP CHP Existing<br />

Traffic Management RTMC­D3 ­ Traffic Operations Caltrans District 3 Existing<br />

Traffic Management<br />

Sacramento County Traffic Sacramento County Transportation Existing<br />

Operations Center<br />

Department<br />

Traffic Management<br />

Sacramento International Airport Sacramento County Airport System Existing<br />

TMC<br />

Traffic Management STARNET Server Sacramento Region (Partnership) <strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

52 Final Report<br />

September 2005


Table 4.4: Inventory Sorted by Entity<br />

Entity Element Stakeholder Status<br />

Transit Management<br />

Capitol Corridor Train Operations Capitol Corridor JPA<br />

Existing<br />

Center<br />

Transit Management Capitol Corridor Train Stations Capitol Corridor JPA Existing<br />

Transit Management El Dorado Transit Dispatch El Dorado County Transit Authority <strong>Plan</strong>ned<br />

Transit Management e­tran Transit Center City of Elk Grove <strong>Plan</strong>ned<br />

Transit Management<br />

Folsom Stage Lines Transit City of Folsom<br />

<strong>Plan</strong>ned<br />

Dispatch<br />

Transit Management<br />

Light Rail Transit Management Sacramento Regional Transit Existing<br />

Center<br />

Transit Management Local Transit Dispatch Centers Other Local Transit Operators Existing<br />

Transit Management Paratransit, Inc. Paratransit, Inc. Existing<br />

Transit Management Placer County Transit Dispatch Placer County Existing<br />

Transit Management Private Transit Provider Dispatch Private Transit Providers Existing<br />

Transit Management<br />

Roseville Transit Management City of Roseville<br />

Existing<br />

Center (Dispatch)<br />

Transit Management RT Transit Management Center Sacramento Regional Transit Existing<br />

Transit Management School Bus Dispatch Independent School Districts Existing<br />

Transit Management Taxi Dispatch Private Taxi Companies Existing<br />

Transit Management Unitrans Transit Dispatch City of Davis Existing<br />

Transit Management Yolo Bus Dispatch Center Yolo County Transportation District Existing<br />

Transit Management Yuba­Sutter Transit Center Yuba­Sutter Transit Existing<br />

Transit Vehicle Subsystem Capital Corridor Trains Capitol Corridor JPA Existing<br />

Transit Vehicle Subsystem El Dorado Transit Vehicles El Dorado County Transit Authority Existing<br />

Transit Vehicle Subsystem e­tran Transit Vehicles City of Elk Grove Existing<br />

Transit Vehicle Subsystem Folsom Stage Line Vehicles City of Folsom Existing<br />

Transit Vehicle Subsystem Local Transit Vehicles Other Local Transit Operators Existing<br />

Transit Vehicle Subsystem Paratransit Vehicle Paratransit, Inc. Existing<br />

Transit Vehicle Subsystem Placer County Transit Vehicles Placer County Transit Authority Existing<br />

Transit Vehicle Subsystem Regional Transit Bus Vehicle Sacramento Regional Transit Existing<br />

Transit Vehicle Subsystem Regional Transit LRT Vehicle Sacramento Regional Transit Existing<br />

Transit Vehicle Subsystem Roseville Transit Vehicles City of Roseville Existing<br />

Transit Vehicle Subsystem School Buses Independent School Districts Existing<br />

Transit Vehicle Subsystem Unitrans Transit Vehicles City of Davis Existing<br />

Transit Vehicle Subsystem Yolo County Buses Yolo County Transportation District Existing<br />

Transit Vehicle Subsystem Yuba­Sutter Transit Vehicles Yuba­Sutter Transit Existing<br />

Traveler Card Regional Fare Card Sacramento Regional Transit <strong>Plan</strong>ned<br />

Vehicle Vehicles Travelers ­ The Public Existing<br />

Wayside Equipment Heavy Rail Wayside Equipment Regional Rail Providers Existing<br />

Wayside Equipment RT Wayside Equipment Sacramento Regional Transit Existing<br />

Weather Service Weather Information Providers NOAA Existing<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

53 Final Report<br />

September 2005


4.5 Market Packages and Performance Criteria Measures<br />

The ITS systems in the region currently provide a wide array of transportation services and that<br />

list will grow as more systems are developed or upgraded. The services can be described by the<br />

set of market packages that are shown in Table 4.5, prioritized by the stakeholders. A high<br />

priority means it is planned for deployment in the next 5 years, a medium priority means it would<br />

be considered for deployment in 5­10 years, a low priority means it would be considered for<br />

deployment in 10­20 years, or the market package was not planned for deployment at all in the<br />

timeframe of the architecture. The table also contains an indication of whether the market<br />

package is currently defined in the regional ITS architecture or whether it is not planned for<br />

deployment at all.<br />

Table 4.5: Market Package Prioritization<br />

Market Package<br />

In<br />

Arch<br />

High<br />

APTS01 Transit Vehicle Tracking x x<br />

APTS02 Transit Fixed­Route Ops x x<br />

APTS04 Transit Passenger and Fare Management x x<br />

APTS05 Transit Security x x<br />

APTS07 Multi­modal Coordination x x<br />

APTS08 Transit Traveler Information x x<br />

ATIS01 Broadcast Traveler Information x x<br />

ATMS01 Network Surveillance x x<br />

ATMS03 Surface Street Control x x<br />

ATMS04 Freeway Control x x<br />

ATMS06 Traffic Information Dissemination x x<br />

ATMS07 Regional Traffic Control x x<br />

ATMS08 Traffic Incident Management System x x<br />

EM01 Emergency Call­Taking and Dispatch x x<br />

EM08 Disaster Response and Recovery x x<br />

EM10 Disaster Traveler Information x x<br />

MC08 Work Zone Management x x<br />

MC10<br />

Maintenance and Construction Activity<br />

Coordination x x<br />

AD01 ITS Data Mart x x<br />

AD02 ITS Data Warehouse x x<br />

AD03 ITS Virtual Data Warehouse x x<br />

APTS03 Demand Response Transit Ops x x<br />

APTS06 Transit Maintenance x x<br />

ATIS02 Interactive Traveler Information x x<br />

ATIS04 Dynamic Route Guidance x<br />

ATIS06<br />

Integrated Transportation Mgmt/Route<br />

Guidance<br />

x<br />

ATMS05 HOV Lane Management x<br />

ATMS09 Traffic Forecast and Demand Management x<br />

ATMS11 Emissions Monitoring and Management x x<br />

ATMS13 Standard Railroad Grade Crossing x x<br />

ATMS19 Speed Monitoring x<br />

CVO10 HAZMAT Management x x<br />

EM02 Emergency Routing x x<br />

Medium Low<br />

Not<br />

<strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

54 Final Report<br />

September 2005


Table 4.5: Market Package Prioritization<br />

Market Package<br />

In<br />

Arch<br />

High<br />

EM04 Roadway Service Patrols x x<br />

EM05 Transportation Infrastructure Protection x x<br />

EM06 Wide­Area Alert x x<br />

EM07 Early Warning System x x<br />

EM09 Evacuation and Reentry Management x x<br />

MC03 Road Weather Data Collection x x<br />

Weather Information Processing and<br />

Distribution x x<br />

Medium Low<br />

MC04<br />

MC07 Roadway Maintenance and Construction x x<br />

MC09 Work Zone Safety Monitoring x x<br />

ATIS03 Autonomous Route Guidance x x<br />

ATIS05 ISP Base Route Guidance x x<br />

ATIS07 Yellow Pages and Reservation x<br />

ATIS08 Dynamic Ridesharing x x<br />

ATIS09 In­Vehicle Signing x<br />

ATMS02 Probe Surveillance x x<br />

ATMS10 Electronic Toll Collection x<br />

ATMS12 Virtual TMC and Smart Probe Data x<br />

ATMS14 Advanced Railroad Grade Crossing x x<br />

ATMS15 Railroad Operations Coordination x x<br />

ATMS16 Parking Facility Management x x<br />

ATMS17 Regional Parking Management x<br />

ATMS18 Reversible Lane Management x<br />

ATMS21 Roadway Closure Management x<br />

AVSS02 Driver Safety Monitoring x<br />

AVSS03 Longitudinal Safety Warning x<br />

AVSS04 Lateral Safety Warning x<br />

AVSS05 Intersection Safety Warning x<br />

AVSS06 Pre­Crash Restraint <strong>Deployment</strong> x<br />

AVSS07 Driver Visibility Improvement x<br />

AVSS10 Intersection Collision Avoidance x<br />

CVO01 Fleet Administration x<br />

CVO02 Freight Administration x<br />

CVO03 Electronic Clearance x<br />

CVO06 Weigh­In­Motion x<br />

CVO07 Roadside CVO Safety x<br />

CVO08<br />

On­Board CVO and Freight Safety and<br />

Security<br />

x<br />

CVO09 CVO Fleet Maintenance x<br />

CVO11<br />

Roadside HAZMAT Security Detection and<br />

Mitigation<br />

x<br />

CVO12 CV Driver Security Detection and Mitigation x<br />

CVO13 Freight Assignment Tracking x<br />

EM03 Mayday Support x<br />

MC01<br />

Maintenance and Construction Vehicle and<br />

Equipment Tracking x x<br />

Not<br />

<strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

55 Final Report<br />

September 2005


Market Package<br />

Table 4.5: Market Package Prioritization<br />

In<br />

Arch<br />

High<br />

Medium Low<br />

Not<br />

<strong>Plan</strong>ned<br />

MC02<br />

Maintenance and Construction Vehicle<br />

Maintenance x x<br />

MC05 Roadway Automated Treatment x x<br />

MC06 Winter Maintenance x x<br />

ATMS20 Drawbridge Management x<br />

AVSS01 Vehicle Safety Monitoring x<br />

AVSS08 Advanced Vehicle Longitudinal Control x<br />

AVSS09 Advanced Vehicle Lateral Control x<br />

AVSS11 Automated Highway System x<br />

CVO04 CV Administrative Processes x<br />

CVO05 International Border Electronic Clearance x<br />

Ideally, all the market packages that were considered for deployment would be defined in the<br />

architecture, but in this first draft of the revision that is not the case. The following market<br />

packages have been indicated to be planned, but are not currently defined in the architecture:<br />

• ATIS04 Dynamic Route Guidance<br />

• ATIS06 Integrated Transportation Mgmt/Route Guidance<br />

• ATMS05 HOV Lane Management<br />

• ATMS09 Traffic Forecast and Demand Management<br />

• ATMS19 Speed Monitoring<br />

• ATIS07 Yellow Pages and Reservation<br />

• ATIS09 In­Vehicle Signing<br />

• ATMS10 Electronic Toll Collection<br />

• ATMS12 Virtual TMC and Smart Probe Data<br />

• ATMS17 Regional Parking Management<br />

• ATMS18 Reversible Lane Management<br />

• ATMS21 Roadway Closure Management<br />

• AVSS02 Driver Safety Monitoring<br />

• AVSS03 Longitudinal Safety Warning<br />

• AVSS04 Lateral Safety Warning<br />

• AVSS05 Intersection Safety Warning<br />

• AVSS06 Pre­Crash Restraint <strong>Deployment</strong><br />

• AVSS07 Driver Visibility Improvement<br />

• AVSS10 Intersection Collision Avoidance<br />

• CVO01 Fleet Administration<br />

• CVO02 Freight Administration<br />

• CVO03 Electronic Clearance<br />

• CVO06 Weigh­In­Motion<br />

• CVO07 Roadside CVO Safety<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

56 Final Report<br />

September 2005


• CVO08<br />

• CVO09<br />

• CVO11<br />

• CVO12<br />

• CVO13<br />

• EM03<br />

On­Board CVO and Freight Safety and Security<br />

CVO Fleet Maintenance<br />

Roadside HAZMAT Security Detection and Mitigation<br />

CV Driver Security Detection and Mitigation<br />

Freight Assignment Tracking<br />

Mayday Support<br />

The first five market packages in the list were assigned a medium priority, so these in particular<br />

should be reviewed to consider whether they need to be added to the architecture.<br />

While the Table above indicates the stakeholder’s assessment of priority of the market packages,<br />

it does not address which elements do (or will) participate in each market package. This<br />

information is contained in the Turbo Architecture database, and is summarized in a table in<br />

Appendix A. This table provides for each market package the status (existing or planned) and<br />

the primary elements associated with the market package. Where the service is currently<br />

provided by some of the elements (but not others) there is a mix of existing and planned status<br />

within a single market package. A service is considered to exist if some interfaces to provide the<br />

service are currently provided via electronic communications.<br />

Performance Measures<br />

Performance measurement is an integral part of transportation system management. It provides a<br />

means of accountability to the public, improved communication between operators and users of<br />

the transportation system, and provides assistance in the region’s delivery of transportation<br />

services. In addition, some performance measures can be used to set policy, allocate resources,<br />

and report on results (before and after ITS improvement projects).<br />

Usually performance measures are addressed from a “system­wide”view. The Federal Highway<br />

Administration’s (FHWA) Office of Operations has indicated that travel time and travel time<br />

reliability are the most effective measures of the performance of the transportation system from<br />

the user’s perspective, and is championing more detailed levels of data collection and analysis in<br />

order to more accurately calculate these measures across the entire transportation network. 2<br />

This section examines the issue of performance measures from the standpoint of ITS­related<br />

services, attempting to identify performance measures that would be appropriate for evaluating<br />

each of the services (or market packages) that have been identified in the architecture in order to<br />

better convey and quantify (where feasible) the expected benefits of ITS deployments. If a<br />

project is being considered for deployment or has been deployed, these performance measures<br />

can be used to demonstrate the benefits that that particular project provides to the region.<br />

When identifying performance measures, the following overarching criteria should be especially<br />

noted:<br />

• Air Quality: Improvements to air quality, and reduction of air emissions, are directly linked<br />

to other performance measures such as reductions in travel times, congestion, stop­and­go<br />

conditions, increased public transit, and rideshare use. Since the Sacramento region is<br />

classified as a non­attainment area, the issue of addressing air quality is most crucial. Every<br />

project must have some form of air quality measure to demonstrate the potential or measured<br />

improvement in air quality. The best way to model this is to use the Sacramento Travel<br />

2 “Operations Performance Measurement”, FHWA­OP­04­039, April 2004.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

57 Final Report<br />

September 2005


Demand Model (SACMET) to simulate ITS elements, then use that data in Sacramento’s<br />

emissions model (EMFAC) to demonstrate how ITS elements can help reduce vehicles<br />

emissions and improve air quality.<br />

• Costs: Cost is not identified as a separate performance measure since it is incorporated into<br />

the cost/benefit analysis which precedes deployment of most projects. Capital and<br />

operating/maintenance costs, for example, can be compared with benefits from services<br />

which use this data in their applications, such as the percentage decrease in travel times<br />

under surface street or freeway control.<br />

• Land Use and Transportation: Many market packages facilitate the interaction between<br />

land use and transportation. For example, data collected through data archiving, transit<br />

vehicle tracking, surface street control, or freeway control projects can be applied to the<br />

PLACE3S model used in the Sacramento Region Blueprint. The model demonstrates how<br />

different land use decisions affect traffic congestion, mode choice, air pollution and other<br />

issues in the future.<br />

• Travel Time: Travel time is possibly the most tangible performance measure for the public.<br />

Travel time is important for general traffic as drivers anticipate pockets of congestion and<br />

alter their rout and mode choice largely based on expected travel time or delay. For transit<br />

vehicles, travel time is important for arrival time prediction and schedule adherence. This<br />

improves transit reliability.<br />

The initial assessment of possible performance measures is given in Table 4.6.<br />

Market<br />

Package<br />

Market Package<br />

Name<br />

Table 4.6: Performance Measures<br />

Performance Measures<br />

AD01 ITS Data Mart • Data accuracy. Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

transit travel times must have 90% accuracy).<br />

AD02 ITS Data Warehouse • Data accuracy. Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

transit travel times must have 90% accuracy).<br />

AD03<br />

ITS Virtual Data<br />

Warehouse<br />

• Data accuracy. Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

transit travel times must have 90% accuracy).<br />

APTS01 Transit Vehicle Tracking • On­Time Performance. Percentage of runs with on­time performance.<br />

• Response times to bus operator calls for assistance. Measured in<br />

minutes from call to arrival of assistance.<br />

• Passenger trips per day per vehicle. Ridership levels reflect customer<br />

satisfaction in system performance. Such a measure must be<br />

interpreted carefully because it is subjective and other factors may<br />

affect changes in ridership levels.<br />

APTS02<br />

Transit Fixed­Route<br />

Operations<br />

• On­Time Performance. Percentage of runs with on­time performance.<br />

• Response times to bus operator calls for assistance. Measured in<br />

minutes from call to arrival of assistance.<br />

• Passenger trips per day per vehicle. Ridership levels reflect customer<br />

satisfaction in system performance. Such a measure must be<br />

interpreted carefully because it is subjective and other factors may<br />

affect changes in ridership levels.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

58 Final Report<br />

September 2005


Market<br />

Package<br />

APTS03<br />

APTS04<br />

Market Package<br />

Name<br />

Demand Response Transit<br />

Operations<br />

Transit Passenger and<br />

Fare Management<br />

Table 4.6: Performance Measures<br />

Performance Measures<br />

• Passenger trips per day per vehicle. Having an automated dispatch<br />

system should improve the efficiency of pickups per vehicle.<br />

• Data collection accuracy. Measured as uncertainty of data collection<br />

statistics. Improvement in the accuracy of data collection is expected.<br />

• Reduction in fare evasion. Estimated through data collection<br />

information.<br />

APTS05 Transit Security • Response times to bus operator calls for assistance. Measured in<br />

minutes from call to arrival of assistance.<br />

• Response times to traveler calls for assistance. Measured in minutes<br />

from call to arrival of assistance.<br />

APTS06 Transit Maintenance • Maintenance actions per vehicle.<br />

APTS07 Multi­modal Coordination • On­Time Performance. Percentage of runs with on­time performance<br />

for those routes that have transit signal priority.<br />

APTS08 Transit Traveler Information • Data Accuracy: Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

transit travel times must have 90% accuracy).<br />

• System Reliability: Quantitative thresholds for mean­time between<br />

failure (MTBF) for both the phone and web systems. Internal linkages<br />

must also be monitored (for example, does the system always link<br />

properly from the main menu or main Web page to the appropriate<br />

nested menus or pages).<br />

• Use of transit information by travelers. Measured as number of calls<br />

to 511 phone system, or number of page views on transit website.<br />

• Customer Satisfaction. Measured as a customer satisfaction rating<br />

based on (subjective) criteria. Such a measure must be interpreted<br />

carefully because it is subjective and affected by the sample size, etc.<br />

ATIS01<br />

Broadcast Traveler<br />

Information<br />

• Data Accuracy: Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

travel times must have 90% accuracy).<br />

• System Reliability: Quantitative thresholds for mean­time between<br />

failure (MTBF) for both the phone and web systems. Internal linkages<br />

must also be monitored (for example, does the system always link<br />

properly from the main menu or main Web page to the appropriate<br />

nested menus or pages).<br />

• Use of transit information by travelers. Measured as number of calls<br />

to 511 phone system, or number of page views on transit website.<br />

• Customer Satisfaction. Measured as a customer satisfaction rating<br />

based on (subjective) criteria. Such a measure must be interpreted<br />

carefully because it is subjective and affected by the sample size, etc.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

59 Final Report<br />

September 2005


Market<br />

Package<br />

ATIS02<br />

Market Package<br />

Name<br />

Interactive Traveler<br />

Information<br />

Table 4.6: Performance Measures<br />

Performance Measures<br />

• Data Accuracy: Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

travel times must have 90% accuracy).<br />

• System Reliability: Quantitative thresholds for mean­time between<br />

failure (MTBF) for both the phone and web systems. Internal linkages<br />

must also be monitored (for example, does the system always link<br />

properly from the main menu or main Web page to the appropriate<br />

nested menus or pages).<br />

• Use of transit information by travelers. Measured as number of calls<br />

to 511 phone system, or number of page views on transit website.<br />

• Customer Satisfaction. Measured as a customer satisfaction rating<br />

based on (subjective) criteria. Such a measure must be interpreted<br />

carefully because it is subjective and affected by the sample size, etc.<br />

ATIS08 Dynamic Ridesharing • Number of rider requests.<br />

ATMS01 Network Surveillance • Data Accuracy: Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

travel times must have 90% accuracy).<br />

• Sensor coverage. Measured in miles of highway or arterials covered<br />

by surveillance.<br />

• Sensor functionality. Measured as availability of sensor information<br />

from highways or arterials (hours operational vs. total number of hours<br />

in measurement period).<br />

ATMS02 Probe Surveillance • Data Accuracy. Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

travel times must have 90% accuracy).<br />

• Probe system coverage. Measured in miles of highway or arterials<br />

covered by probe surveillance.<br />

ATMS03 Surface Street Control • Traffic flow. Measured at intersections with signal systems.<br />

• Travel time along a corridor (that contains coordinated signals)<br />

• Traffic signal system failure rates.<br />

• Air Emissions. Measured as proportional to travel times and vehicle<br />

classifications, and stop­and­go conditions.<br />

ATMS04 Freeway Control • Traffic flow. Measured at on ramps and on highway.<br />

• Travel Time along freeway segments.<br />

• Air Emissions. Measured as proportional to travel times and vehicle<br />

classifications, and stop­and­go conditions.<br />

ATMS06<br />

Traffic Information<br />

Dissemination<br />

• Number (or frequency) of advisory messages per DMS.<br />

• Data Accuracy. Measured as amount of data meeting a given<br />

accuracy threshold appropriate to the measurement (for example,<br />

travel times must have 90% accuracy).<br />

ATMS07 Regional Traffic Control • Traffic flow. Measured at intersections with interconnected signals<br />

across jurisdictions.<br />

• Travel Time along roadway segments.<br />

• Air Emissions. Measured as proportional to travel times and vehicle<br />

classifications, and stop­and­go conditions.<br />

ATMS08<br />

Traffic Incident<br />

Management System<br />

• Accident rates<br />

• Number of incidents detected or verified<br />

• Incident response times<br />

• Incident clearance times<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

60 Final Report<br />

September 2005


Market<br />

Package<br />

ATMS11<br />

ATMS13<br />

ATMS14<br />

Market Package<br />

Name<br />

Emissions Monitoring and<br />

Management<br />

Standard Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Table 4.6: Performance Measures<br />

Performance Measures<br />

• Number of vehicles tested.<br />

• Rate of compliance with emission standards.<br />

• Number of train/vehicle collsions at Highway­Rail Intersections (HRIs)<br />

interconnected with Traffic Signal System<br />

• Number of train/ vehicle collisions at Highway­Rail Intersections<br />

(HRIs) with advanced surveillance capabilities<br />

• Number of blocked intersection occurrences recognized by system.<br />

• Number of times coordination with rail operations occurs.<br />

ATMS15 Railroad Operations<br />

Coordination<br />

ATMS16 Parking Facility<br />

• Parking lot queues.<br />

Management<br />

CVO10 HAZMAT Management • Occurrences of HAZMAT incidents where assistance is requested.<br />

• HAZMAT Incident response times<br />

• HAZMAT Incident clearance times<br />

EM01<br />

Emergency Call­Taking<br />

and Dispatch<br />

• Call answering delay. Measured as time callers to 911 are on hold.<br />

• Average time to respond to emergency. Measured as the average<br />

time from receipt of call to arrival of emergency services at call site.<br />

EM02 Emergency Routing • Average time to respond to emergency. Measured as the average<br />

time from receipt of call to arrival of emergency services at call site.<br />

EM04 Roadway Service Patrols • Wait time for stranded motorists. Measured as time from receipt of<br />

call for assistance to arrival of freeway service patrol or other public<br />

safety vehicle.<br />

EM05<br />

Transportation<br />

Infrastructure Protection<br />

• Infrastructure coverage. Measured in transportation assets covered<br />

by surveillance.<br />

• Incidents detected. Measured as percentage of detectable incidents<br />

(under coverage area of those surveillance devices or methods)<br />

actually detected.<br />

EM06 Wide­Area Alert • Usage of alert system. Measured as percentage of appropriate alerts<br />

actually activated per situations which require usage of the system.<br />

• Evacuation or Response Time: Depending on the scenario, measured<br />

as response time for the appropriate response outlined in an<br />

agency/region’s emergency procedures.<br />

EM07 Early Warning System • Usage of warning system. Measured as percentage of appropriate<br />

warnings actually activated per situations which require usage of the<br />

system.<br />

• Evacuation or Response Time: Depending on the scenario, measured<br />

as response time for the appropriate response outlined in an<br />

agency/region’s emergency procedures.<br />

EM08<br />

EM09<br />

EM10<br />

Disaster Response and<br />

Recovery<br />

Evacuation and Reentry<br />

Management<br />

Disaster Traveler<br />

Information<br />

• Average time to respond to emergency. Measured as the average<br />

time from receipt of call to arrival of emergency services at call site.<br />

• Evacuation or Response Time: Depending on the disaster scenario,<br />

measured as response time for the appropriate response outlined in<br />

an agency/region’s emergency procedures.<br />

• Evacuation performance. Measured as time to evacuate x number of<br />

people or y area.<br />

• Usage of disaster traveler information system. Measured as<br />

percentage of times that disaster information is propagated via the<br />

system per situations which require usage of the system.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

61 Final Report<br />

September 2005


Market<br />

Package<br />

MC01<br />

MC02<br />

MC03<br />

MC04<br />

MC05<br />

Market Package<br />

Name<br />

Maintenance and<br />

Construction Vehicle and<br />

Equipment Tracking<br />

Maintenance and<br />

Construction Vehicle<br />

Maintenance<br />

Road Weather Data<br />

Collection<br />

Weather Information<br />

Processing and Distribution<br />

Roadway Automated<br />

Table 4.6: Performance Measures<br />

Performance Measures<br />

• Average response time of maintenance crews. Measured as time<br />

from request for maintenance action to arrival of maintenance vehicle<br />

on scene.<br />

• Maintenance actions per vehicle.<br />

• Number of hazardous conditions identified by the devices.<br />

• Amount of road treatment materials used<br />

• Response time of crews to treat hazardous road conditions.<br />

• Amount of road treatment materials used<br />

• Response time of crews to treat hazardous road conditions.<br />

• Number of times hazardous conditions treated by the devices.<br />

Treatment<br />

MC06 Winter Maintenance • Amount of road treatment materials used<br />

• Average response time of maintenance crews to treat hazardous road<br />

conditions. Measured as time from request for maintenance action to<br />

arrival of maintenance vehicle on scene.<br />

MC07<br />

Roadway Maintenance and<br />

Construction<br />

• Average response time of maintenance crews. Measured as time<br />

from request for maintenance action to arrival of maintenance vehicle<br />

on scene.<br />

MC08 Work Zone Management • Number of accidents (or incidents) at work zones that have ITS<br />

elements. Measurement could include comparison of similar criteria<br />

for work zones without ITS elements.<br />

• Traffic flow in area of workzones. Again measurement could be<br />

compared with a similar measure calculated for workzones without ITS<br />

elements.<br />

MC09<br />

MC10<br />

Work Zone Safety<br />

Monitoring<br />

Maintenance and<br />

Construction Activity<br />

Coordination<br />

• Number of times safety monitoring equipment activated<br />

• Number of accidents (or incidents) at work zones with safety<br />

monitoring equipment.<br />

• Frequency of activity updates<br />

• Number of agencies receiving updates.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

62 Final Report<br />

September 2005


4.6 Interfaces and Information Exchanges<br />

Top Level Regional System Interconnect Diagram<br />

A system interconnect diagram, or sausage diagram, shows the systems and primary types of<br />

interconnections in the region. The National ITS Architecture interconnect diagram has been<br />

customized for Sacramento based on the information gathered from the stakeholders and system<br />

inventory. Figure 4.2 summarizes the existing and planned ITS elements for the regions in the<br />

context of a physical interconnect. Elements (and their primary associated National ITS<br />

Architecture entity) are called out in the boxes surrounding the main interconnect diagram. In<br />

the center of the figure the rectangles represent the subsystems of the National ITS Architecture.<br />

The Sacramento Regional ITS architecture has elements that map to 18 of the 21 subsystems of<br />

the National ITS Architecture. In addition, the regional ITS architecture has elements that map<br />

to 19 terminators of the National ITS Architecture. These terminators are shown on the right<br />

side of the diagram and include entities such as Care Facilities (which maps to Regional<br />

Hospitals).<br />

The diagram also identifies the three basic types of communications used to interconnect the<br />

elements of the architecture. These communications types are defined as:<br />

• Fixed­point to Fixed­point Communications: A communications link serving stationary<br />

sources. It may be implemented using a variety of public or private communications<br />

networks that may physically include wireless (e.g., microwave) as well as wireline<br />

infrastructure. Both dedicated and shared communications resources may be used.<br />

• Wide Area Wireless Communications: A communications link that provides<br />

communications via a wireless device between a user and an infrastructure­based system.<br />

Both broadcast (one­way) and interactive (two­way) communications services are grouped<br />

into wide­area wireless communications. These links support a range of services including<br />

real­time traveler information and various forms of fleet communications.<br />

• Dedicated Short Range Communications: A wireless communications channel used for<br />

close­proximity communications between vehicles and the immediate infrastructure. It<br />

supports location­specific communications for ITS capabilities such as toll collection, transit<br />

vehicle management, driver information, and automated commercial vehicle operations.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

63 Final Report<br />

September 2005


Figure 4.2: Sacramento Regional ITS Architecture System Interconnect Diagram<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

64 Final Report<br />

September 2005


Customized Market Packages<br />

The market packages of the National ITS Architecture were customized with input from the<br />

stakeholders to reflect the unique systems and connections of the state. Each market package is<br />

shown graphically with the market package name, the entity from the National ITS Architecture,<br />

and the specific Sacramento elements associated with the entity. In addition, the market<br />

packages show the information flows that move between elements.<br />

Figure 4.3 is an example of an ATMS market package for Surface Street Control that has been<br />

customized for the City of Sacramento. This market package shows three subsystems,<br />

Maintenance and Construction Management, Traffic Management and Roadway, and the<br />

associated elements. Information flows (called “architecture flows” in the National ITS<br />

Architecture) between the subsystems indicate what information is being shared.<br />

Figure 4.3: Example Customized Market Package<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

65 Final Report<br />

September 2005


The market packages that were customized for the Sacramento Region can be found on the<br />

architecture webpage<br />

http://www.consystec.com/sacramento/web/_regionhome.htm<br />

by selecting the “Market Packages”button, or in the attached Appendix H. Market packages are<br />

grouped by stakeholder and by functional areas (e.g. Traffic Management, Maintenance and<br />

Construction, and Public Transportation) and each set of customized market packages can be<br />

viewed by clicking on the Market Package Diagram icon under each area heading. It is<br />

important to note that while the market package table on the web page shows all of the market<br />

packages from the National ITS Architecture, only those selected for the state are included in the<br />

diagrams. The selected market packages on the web page also are highlighted in the web page<br />

table with bold print and are indicated as existing or planned.<br />

Regional Architecture Information Flows<br />

While it is important to identify the various systems and stakeholders as part of a regional ITS<br />

architecture, a primary purpose of the architecture is to identify the connectivity between<br />

transportation systems in the region. The customized market packages represent services that can<br />

be deployed as an integrated capability, and the market package diagrams show the information<br />

flows between the subsystems and terminators that are most important to the operation of the<br />

market packages. The systems interface with each element is an integral part of the overall<br />

architecture.<br />

There are 163 different elements identified as part of the Sacramento Regional ITS Architecture.<br />

These elements include city and region traffic operations centers, transit centers, transit vehicles,<br />

public safety dispatch centers, media outlets, and others— essentially all of the existing and<br />

planned physical components that contribute to the region’s and state’s intelligent transportation<br />

system. Interfaces have been defined for each element in the architecture. For example, the<br />

Caltrans District 3 Maintenance Dispatch has planned or existing interfaces with 30 other<br />

elements in the region ranging from field equipment to weather service providers to transit<br />

centers. Some of the interfaces are far less complex. For example the Sacramento City Roadside<br />

Equipment has interfaces with only five other elements in the architecture.<br />

Elements and their interfaces are accessible via the Sacramento Regional ITS Architecture web<br />

page by clicking on the “Inventory by Stakeholder”button. Selecting an element from the right<br />

hand column takes you to an element detail page that shows each interface to the element in the<br />

architecture.<br />

Architecture flows between the elements define specific information that is exchanged by the<br />

elements. Each architecture flow has a direction, name and definition. Most of the architecture<br />

flows match ones from the National ITS Architecture (the mapping of elements to National ITS<br />

Architecture entities allowed the developers to match the architecture flows to the appropriate<br />

interfaces.) In some cases new user defined flows have been created for interfaces or<br />

connectivities that are not expressed in the National ITS Architecture (Note these flows have a<br />

“_ud”at the end of the name to indicate they are user defined.). These architecture flows define<br />

the interface requirements between the various elements in the regional architecture.<br />

An example of the architecture flows between two elements is shown in Figure 4.4. In this<br />

interface diagram, the flows that go between the City of Woodland’s TOC and the City of<br />

Woodland’s Field Equipment are shown. Since both of these elements exist today, there are<br />

existing flows (information is currently passing between the elements). This information<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

66 Final Report<br />

September 2005


includes a request for right­of­way for pedestrian crossing and signal control status, or the status<br />

of the signal at the roadside, that flow from the roadside field equipment to the City’s TOC. In<br />

addition to the existing flows between these elements, there are also flows that are show as future<br />

flows (e.g. traffic flows and traffic images) for future ITS deployment projects. It is important to<br />

note that there is a legend for each interface diagram that relates the color and the line type of<br />

each flow to existing information sharing, or a future connection.<br />

Each of the individual element interfaces can be accessed on the Sacramento Regional ITS<br />

Architecture web page by clicking on the “Inventory by Stakeholder”or “Inventory by Entity”<br />

buttons. Selecting any of the elements from the column on the right will display the set of<br />

interfaces to that element similar to the diagram shown below. Selecting any of the architecture<br />

flows will provide a definition, and any standards associated with that architecture flow are<br />

noted.<br />

Figure 4.4: Example of Architecture Flows between Elements<br />

City of Woodland<br />

City of Woodland TOC<br />

request for right­of­way<br />

roadway information system status<br />

signal control status<br />

traffic flow<br />

traffic images<br />

roadway information system data<br />

signal control data<br />

traffic sensor control<br />

video surveillance control<br />

City of Woodland<br />

City of Woodland Field Equipment<br />

Existing<br />

<strong>Plan</strong>ned<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

67 Final Report<br />

September 2005


4.7 Functional Requirements<br />

Functional requirements are a description of the functions or activities that are performed by the<br />

equipment packages of the National ITS Architecture. For the Sacramento Regional ITS<br />

Architecture, these functions have been developed by using the mapping from transportation<br />

services to elements shown in Appendix G and the mapping of equipment packages to each<br />

element shown in Appendix I.<br />

In the National ITS Architecture, market packages are defined by subsystems, equipment<br />

packages, and architecture flows, all of which operate together to perform a particular<br />

transportation service reflected in the Market Packages. Equipment Packages represent pieces of<br />

a subsystem that perform a single function. These functions comprise the overall functional<br />

requirements.<br />

To illustrate an example, the Surface Street Control market package is composed of the two<br />

Traffic Management Subsystem equipment packages (TMC Signal Control and Traffic<br />

Maintenance) and two Roadway Subsystem equipment packages (Roadway Signal Control and<br />

Roadway Equipment Coordination). The definitions of these four equipment packages,<br />

referenced from version 5.0 of the National ITS Architecture, are described below. It is the<br />

description of each equipment package that defines the functional requirements of the market<br />

package; in this case, the functional requirements of Surface Street Control.<br />

• TMC Signal Control: This equipment package provides the capability for traffic managers<br />

to monitor and manage the traffic flow at signalized intersections. This capability includes<br />

analyzing and reducing the collected data from traffic surveillance equipment and<br />

developing and implementing control plans for signalized intersections. Control plans may<br />

be developed and implemented that coordinate signals at many intersections under the<br />

domain of a single traffic management subsystem. In advanced implementations, this<br />

package collects route planning information and integrates and uses this information in<br />

predicting future traffic conditions and optimizing the traffic control strategy for these<br />

conditions. These capabilities are achieved through real­time communication of logged<br />

routes from an Information Service Provider. The planned control strategies can be passed<br />

back to the Information Service Provider so that the intended strategies can be reflected in<br />

future route planning.<br />

• Traffic Maintenance: This equipment package provides monitoring and remote diagnostics<br />

of field equipment to detect field equipment failures, issues problem reports, and tracks the<br />

repair or replacement of the failed equipment.<br />

• Roadway Signal Controls: This equipment package provides the capabilities to control<br />

traffic signals at major intersections and on main highways for urban areas. This equipment<br />

package is generally constrained to a single jurisdiction.<br />

• Roadway Equipment Coordination: This equipment package coordinates field equipment<br />

that is distributed along the roadway by supporting direct communications between field<br />

equipment. This includes coordination between remote sensors and field devices (e.g.,<br />

Dynamic Message Signs) and coordination between the field devices themselves (e.g.,<br />

coordination between traffic controllers that are controlling adjacent intersections.).<br />

The approach used to define the functional requirements in the Sacramento Regional ITS<br />

Architecture begins with the mapping of equipment packages to elements (based on the market<br />

package mapping in Appendix G) as an initial definition of the functions being performed by<br />

each element. This mapping is then tailored in the Turbo Architecture tool to provide a more<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

68 Final Report<br />

September 2005


accurate picture of the functions performed by the element. The Turbo Architecture tool also<br />

contains a detailed mapping of functional requirements (written as “shall”statements) to each<br />

equipment package. This mapping to functional requirements will be customized for each<br />

element, selecting only those requirements that are appropriate given the definition and<br />

connectivity of the element.<br />

The mapping of elements to the basic functions (equipment packages) is provided on the<br />

hyperlinked web site version of the architecture, as well as Appendix J. The detail page for each<br />

element (which is accessed through the Inventory by Stakeholder or Inventory by Entity tabs)<br />

has a list of the equipment packages assigned to the element.<br />

As an example, the Municipal TOCs element has the following equipment packages assigned to<br />

it:<br />

• Emissions Data Management<br />

• Emissions Data Collection<br />

• Collect Traffic Surveillance<br />

• HRI Traffic Management<br />

• TMC Probe Information Collection<br />

• TMC Freeway Management<br />

• TMC Incident Detection<br />

• TMC Incident Dispatch Coordination/Communication<br />

• TMC Regional Traffic Control<br />

• TMC Evacuation Support<br />

• TMC Signal Control<br />

• TMC Traffic Information Dissemination<br />

• Rail Operations Coordination<br />

• Traffic Maintenance<br />

• TMC Work Zone Traffic Management<br />

• Traffic Data Collection<br />

This represents the detail that can be obtained in the hyperlinked web site in connection with<br />

functional requirements. The functional requirements are defined by the description of each<br />

equipment package.<br />

4.8 Standards Identification<br />

ITS standards establish a common way in which devices<br />

connect and communicate with one another. This allows Use of ITS standards is<br />

transportation agencies to implement systems that costeffectively<br />

exchange pertinent data and accommodate project development in<br />

very important to<br />

equipment replacement, system upgrades, and system the Sacramento region<br />

expansion. Standards benefit the traveling public by providing<br />

products that will function consistently and reliably throughout the region. ITS standards<br />

contribute to a safer and more efficient transportation system, facilitate regional interoperability,<br />

and promote an innovative and competitive market for transportation products and services.<br />

The Table below identifies the ITS standards that are potentially applicable to the region. This<br />

table was created by taking the standards information available in the Turbo Architecture<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

69 Final Report<br />

September 2005


database (which identifies standards applicable to each architecture flow) and taking the total set<br />

of standards that result from all of the selected flows. The table provides the status of the<br />

standards effort as of April 2005 (the most recent update of the information).<br />

The following section explains how to identify the specific applicable standards for an individual<br />

interface. Table 4.7 lists the name of the Standards Development Organization (SDO) in the<br />

first column, the Standards Title in the second column, and the Document ID that is used to<br />

describe the standard in the third column. Some of the Standards ID columns have the indication<br />

“(see Footnote)”. These entries represent a group of standards rather than a single standard. The<br />

listing of the individual standards that make up each group is shown in Table 4.8. The SDOs<br />

listed in the table include:<br />

• American Association of State Highway and Transportation Officials (AASHTO)<br />

• American National Standards Institute (ANSI)<br />

• American Public Transportation Association (APTA)<br />

• American Society for Testing and Materials (ASTM)<br />

• Institute of Electrical and Electronics Engineers (IEEE)<br />

• Institute of Transportation Engineers (ITE)<br />

• National Equipment Manufacturers Association (NEMA)<br />

• Society of Automotive Engineers (SAE)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

70 Final Report<br />

September 2005


Table 4.7: Applicable ITS Standards<br />

SDO Standard Title Standard Doc ID<br />

AASHTO/ITE/NEMA NTCIP Center­to­Center Standards Group Being Developed<br />

AASHTO/ITE/NEMA NTCIP Center­to­Field Standards Group Being Developed<br />

AASHTO/ITE/NEMA Global Object Definitions NTCIP 1201<br />

AASHTO/ITE/NEMA Object Definitions for Actuated Traffic Signal Controller NTCIP 1202<br />

Units<br />

AASHTO/ITE/NEMA Object Definitions for Dynamic Message Signs NTCIP 1203<br />

AASHTO/ITE/NEMA Object Definitions for Environmental Sensor Stations & NTCIP 1204<br />

Roadside Weather Information System<br />

AASHTO/ITE/NEMA Data Dictionary for Closed Circuit Television (CCTV) NTCIP 1205<br />

AASHTO/ITE/NEMA Data Collection & Monitoring Devices NTCIP 1206<br />

AASHTO/ITE/NEMA Ramp Meter Controller Objects NTCIP 1207<br />

AASHTO/ITE/NEMA Object Definitions for Video Switches NTCIP 1208<br />

AASHTO/ITE/NEMA Transportation System Sensor Objects NTCIP 1209<br />

AASHTO/ITE/NEMA Objects for Signal Systems Master NTCIP 1210<br />

AASHTO/ITE/NEMA Objects for Signal Control Priority NTCIP 1211<br />

APTA TCIP Being Developed<br />

ASTM<br />

Dedicated Short Range Communication at 915 MHz Being Developed<br />

Standards Group<br />

ASTM<br />

Standard Specification for Archiving ITS Generated Traffic ASTM E2259­xx<br />

Monitoring Data<br />

IEEE Incident Management Standards Group Being Developed<br />

IEEE<br />

Standard for Interface Between the Rail Subsystem and IEEE 1570­2002<br />

the Highway Subsystem at a Highway Rail Intersection<br />

IEEE<br />

Standard for Message Sets for Vehicle/Roadside<br />

IEEE Std 1455­1999<br />

Communications<br />

ITE<br />

Standard for Functional Level Traffic Management Data ITE TM 1.03<br />

Dictionary (TMDD)<br />

ITE<br />

Message Sets for External TMC Communication<br />

ITE TM 2.01<br />

(MS/ETMCC)<br />

SAE<br />

Advanced Traveler Information Systems (ATIS) Bandwidth Being Developed<br />

Limited Standards Group<br />

SAE<br />

Advanced Traveler Information Systems (ATIS) General Being Developed<br />

Use Standards Group<br />

SAE/IEEE<br />

Dedicated Short Range Communication at 5.9 GHz<br />

Standards Group<br />

Being Developed<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

71 Final Report<br />

September 2005


The previous tables provide general information about the standards environment in the region.<br />

The architecture actually contains a far more detailed standards view, one that maps applicable<br />

standards to the individual information flow that goes from one element to another. This<br />

additional detail can be found on the project architecture website.<br />

To access the information on the web page, each element description page (Market Package<br />

Diagram) has a set of links that describe the information flowing to and from the element to other<br />

elements of the architecture. Selecting any of these interface links brings the user an interface<br />

page. Selecting one of the information flows leads to an Architecture Flow page that contains<br />

the definition of the architecture flow and the list of standards that could be applied to that<br />

particular flow.<br />

Note that the detailed standards information can also be obtained from the Turbo Architecture<br />

database for the Architecture. For those users that have access to this application, the Standards<br />

tab provides a place where standards mapping can be customized, and the Standards reports<br />

provide a variety of detailed outputs.<br />

Table 4.8: Individual Standards within each Group<br />

Advanced Traveler Information Systems (ATIS) Bandwidth Limited Standards<br />

Group<br />

SDO Standard Name Document ID<br />

SAE Location Referencing Message Specification (LRMS) SAE J2266<br />

SAE Message Set for Advanced Traveler Information System (ATIS) SAE J2354<br />

SAE<br />

Standard for ATIS Message Sets Delivered Over Bandwidth Restricted SAE J2369<br />

Media<br />

SAE Rules for Standardizing Street Names and Route IDs SAE J2529<br />

SAE Messages for Handling Strings and Look­Up Tables in ATIS Standards SAE J2540<br />

SAE RDS (Radio Data System) Phrase List SAE J2540­1<br />

SAE ITIS (International Traveler Information Systems) Phrase Lists SAE J2540­2<br />

SAE National Names Phrase List SAE J2540­3<br />

SAE Converting ATIS Message Standards from ASN.1 to XML SAE J2630<br />

Advanced Traveler Information Systems (ATIS) General Use Standards Group<br />

SDO Standard Name Document ID<br />

SAE Location Referencing Message Specification (LRMS) SAE J2266<br />

SAE Message Set for Advanced Traveler Information System (ATIS) SAE J2354<br />

SAE Rules for Standardizing Street Names and Route IDs SAE J2529<br />

SAE Messages for Handling Strings and Look­Up Tables in ATIS Standards SAE J2540<br />

SAE RDS (Radio Data System) Phrase List SAE J2540­1<br />

SAE ITIS (International Traveler Information Systems) Phrase Lists SAE J2540­2<br />

SAE National Names Phrase List SAE J2540­3<br />

SAE Converting ATIS Message Standards from ASN.1 to XML SAE J2630<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

72 Final Report<br />

September 2005


Table 4.8: Individual Standards within each Group<br />

Dedicated Short Range Communication at 5.9 GHz Standards Group<br />

SDO Standard Name Document ID<br />

IEEE Resource Manager for DSRC 5.9 GHz IEEE 1609.1<br />

IEEE Application Services (Layers 6,7) for DSRC 5.9 GHz IEEE 1609.2<br />

IEEE<br />

Communications Services (Layers 4,5) for DSRC 5.9 GHz (Future IEEE 1609.3<br />

Standard)<br />

IEEE<br />

Medium Access Control (MAC) Extension & the MAC Extension<br />

IEEE 1609.4<br />

Management Entity for DSRC 5.9 GHz<br />

IEEE<br />

Standard Specification for Telecommunications and Information Exchange IEEE 802.11<br />

Between Roadside and Vehicle Systems ­ 5 GHz Band Dedicated Short<br />

Range Communications (DSRC) Medium Access Control (MAC) and<br />

Physical Layer (PHY) Specifications<br />

IEEE Logical Link (Layer 2) for DSRC 5.9 GHz IEEE 802.2<br />

ISO Networking Services (Layer 3) for DSRC 5.9 GHz ISO 21210<br />

ASTM<br />

ASTM<br />

Dedicated Short Range Communication at 915 MHz Standards Group<br />

SDO Standard Name Document ID<br />

Standard Specification for Dedicated Short Range Communication (DSRC)<br />

Physical Layer using Microwave in the 902­928 MHz Band<br />

Standard Provisional Specification for Dedicated Short Range<br />

Communication (DSRC) Data Link Layer<br />

Incident Management Standards Group<br />

ASTM E2158­01<br />

ASTM PS 105­99<br />

SDO Standard Name Document ID<br />

IEEE Standard for Traffic Incident Management Message Sets for Use by EMCs IEEE 1512.1­2003<br />

IEEE Standard for Hazardous Material IMMS for use by EMCs IEEE 1512.3­2002<br />

IEEE<br />

Standard for Common Incident Management Message Sets (IMMS) for use IEEE 1512­2000<br />

by EMCs<br />

IEEE Standard for Public Safety IMMS for use by EMCs IEEE P1512.2<br />

NTCIP Center­to­Center Standards Group<br />

SDO Standard Name Document ID<br />

AASHTO/ITE/NEMA Base Standard: Octet Encoding Rules (OER) NTCIP 1102<br />

AASHTO/ITE/NEMA CORBA Naming Convention NTCIP 1104<br />

AASHTO/ITE/NEMA CORBA Security Service NTCIP 1105<br />

AASHTO/ITE/NEMA CORBA Near­Real Time Data Service NTCIP 1106<br />

AASHTO/ITE/NEMA Subnet Profile for Ethernet NTCIP 2104<br />

AASHTO/ITE/NEMA Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202<br />

AASHTO/ITE/NEMA Application Profile for File Transfer Protocol (FTP) NTCIP 2303<br />

AASHTO/ITE/NEMA Application Profile for Data Exchange ASN.1 (DATEX) NTCIP 2304<br />

AASHTO/ITE/NEMA Application Profile for Common Object Request Broker Architecture NTCIP 2305<br />

(CORBA)<br />

AASHTO/ITE/NEMA Information Profile for DATEX NTCIP 2501<br />

AASHTO/ITE/NEMA Information Profile for CORBA NTCIP 2502<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

73 Final Report<br />

September 2005


Table 4.8: Individual Standards within each Group<br />

NTCIP Center­to­Field Standards Group<br />

SDO Standard Name Document ID<br />

AASHTO/ITE/NEMA Simple Transportation Management Framework (STMF) NTCIP 1101<br />

AASHTO/ITE/NEMA Base Standard: Octet Encoding Rules (OER) NTCIP 1102<br />

AASHTO/ITE/NEMA Simple Transportation Management Protocol (STMP) NTCIP 1103<br />

AASHTO/ITE/NEMA Point to Multi­Point Protocol Using RS­232 Subnetwork Profile NTCIP 2101<br />

AASHTO/ITE/NEMA Subnet Profile for PMPP Over FSK modems NTCIP 2102<br />

AASHTO/ITE/NEMA Subnet Profile for Point­to­Point Protocol using RS NTCIP 2103<br />

AASHTO/ITE/NEMA Subnet Profile for Ethernet NTCIP 2104<br />

AASHTO/ITE/NEMA Transportation Transport Profile NTCIP 2201<br />

AASHTO/ITE/NEMA Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202<br />

AASHTO/ITE/NEMA Application Profile for Simple Transportation Management Framework NTCIP 2301<br />

(STMF)<br />

AASHTO/ITE/NEMA Application Profile for Trivial File Transfer Protocol NTCIP 2302<br />

AASHTO/ITE/NEMA Application Profile for File Transfer Protocol (FTP) NTCIP 2303<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

74 Final Report<br />

September 2005


5 PLAN MAINTENANCE<br />

5.1 Introduction<br />

The maintenance plan documents the procedures for updating the Sacramento Regional ITS<br />

Architecture, and defines the roles and responsibilities of each stakeholder. As projects are<br />

implemented or expanded, as agency priorities change, or as other changes occur that impact ITS<br />

in the Sacramento Area, they will need be documented through an update to the Sacramento<br />

Regional ITS Architecture.<br />

The maintenance plan is a very important component of the regional ITS architecture that acts as<br />

a control mechanism for maintaining order in the process of keeping the architecture up to date<br />

over time. It also acts as a guideline for keeping a set of complex, interrelated actions and<br />

documents on course over time.<br />

This plan is laid out in two parts, both of which act as an instruction manual for changes to the<br />

regional ITS architecture. The first portion of this document is presented for the user or regional<br />

stakeholder. It provides some background information along with recommended procedures for<br />

how a change should be initiated by the user. The second portion of this document is presented<br />

for the maintainer of the regional ITS architecture. It identifies how the change is handled after<br />

it is submitted by the user. This organization allows each party to focus on the information that<br />

primarily pertains to them.<br />

This ITS Maintenance <strong>Plan</strong> also applies to the responsibilities to maintain the existing Tahoe<br />

Gateway ITS Regional Architecture. All roles, responsibilities, policies, and procedures defined<br />

for the Sacramento Area ITS Maintenance <strong>Plan</strong> also apply to maintaining the Tahoe Gateway<br />

Regional ITS Architecture at the same time. This also means that the Tahoe Gateway Regional<br />

ITS Architecture should be updated each time the Sacramento Area Regional ITS Architecture is<br />

updated.<br />

Documentation of the plan to keep the regional architecture up to date is a requirement of the<br />

Federal Rule 940/Policy 655 for ITS, which states that, “Regional ITS Architectures be<br />

developed to guide the development of ITS projects and programs”and requires each MPO and<br />

jurisdiction with an ITS Architecture (and ITS projects) to have a plan in place to maintain and<br />

update those regional ITS architectures. More specifically, Rule 940.9f states:<br />

“The agencies and other stakeholders participating in the development of the<br />

Regional ITS Architecture shall develop and implement procedures and<br />

responsibilities for maintaining it, as needs evolve within the region.”<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

75 Final Report<br />

September 2005


5.2 Methodology and Analysis<br />

The following section outlines the decisions of the Sacramento Area in relation to stakeholder<br />

responsibilities.<br />

5.2.1 Definition of a Stakeholder<br />

Stakeholders are an important part of the Sacramento Regional ITS Architecture. They<br />

provide regional input which is used in the creation of the regional ITS architecture. A<br />

stakeholder is a public agency or private organization with a vested interest, or a "stake"<br />

in one or more transportation elements within a Regional ITS Architecture. Stakeholders<br />

are responsible for reviewing the regional ITS architecture prior to deploying new ITS<br />

projects in order to assure that the projects are consistent with the needs and goals of the<br />

region.<br />

5.2.2 Updates to the Regional ITS Architecture<br />

The Sacramento Regional ITS Architecture is a dynamic document that is subject to<br />

change as ITS evolves in the region. As changes occur, portions of the architecture, if not<br />

the whole document will need to be updated accordingly. These changes should be<br />

initiated by the stakeholders as the need arises. The following list includes events<br />

identified by the “Regional ITS Architecture Maintenance White Paper”as events that<br />

may require change to a regional ITS architecture:<br />

• Changes in Regional Needs. Regional ITS Architectures are created to support<br />

transportation planning in addressing regional needs. Over time these needs can<br />

change and the corresponding aspects of the regional ITS architecture that<br />

addresses these needs may need to be updated. These changes in needs should be<br />

expressed in updates to planning documents such as the Regional Transportation<br />

<strong>Plan</strong> (RTP).<br />

• New Stakeholders. New stakeholders who become active in ITS and the regional<br />

ITS architecture should be updated to reflect their place in the regional view of<br />

ITS elements, interfaces, and information flows. Why might new stakeholders<br />

emerge? The stakeholders might represent new organizations that were not in<br />

place during the original development of the regional ITS architecture. Or maybe<br />

the geographic scope of the architecture is being expanded, bringing in new<br />

stakeholders. Or maybe additional transportation modes or transportation services<br />

are being considered that touch the systems of additional stakeholders.<br />

• Changes in Scope of Services Considered. The range of services considered by<br />

the regional ITS architecture expands. This might happen because the National<br />

ITS Architecture has been expanded and updated to include new user services or to<br />

better define how existing elements satisfy the user services. A regional ITS<br />

architecture based on an earlier version of the National ITS Architecture should<br />

take into consideration these changes as the regional ITS architecture is updated.<br />

The National ITS Architecture may have expanded to include a user service that<br />

has been discussed in a region, but not included in the regional ITS architecture, or<br />

was included in only a very cursory manner. Changes in the National ITS<br />

Architecture are not of themselves a reason to update a regional ITS architecture,<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

76 Final Report<br />

September 2005


ut a region may want to consider any new services in the context of their regional<br />

needs.<br />

• Changes in Stakeholder or Element Names. An agency’s name or the name<br />

used to describe their element(s) undergoes change. Transportation agencies<br />

occasionally merge, split, or just rename themselves. In addition element names<br />

may evolve as projects are defined. The regional ITS architecture should be<br />

updated to use the currently correct names for both stakeholders and elements.<br />

• Changes in Other Architectures. A regional ITS architecture covers not only<br />

elements and interfaces within a region, but also interfaces to elements in<br />

adjoining regions. Changes in the regional ITS architecture in one region may<br />

necessitate changes in the architecture in an adjoining region to maintain<br />

consistency between the two. Architectures may also overlap (e.g. a statewide ITS<br />

architecture and a regional ITS architecture for a region within the state) and a<br />

change in one might necessitate a change in the other. For further information on<br />

overlap and adjacencies, please see Section 7.0 of this document.<br />

• Changes due to Project Definition or Implementation. When actually defined<br />

or implemented, a project may add, subtract or modify elements, interfaces, or<br />

information flows from the regional ITS architecture. Because the regional ITS<br />

architecture is meant to describe the currently (as well as future) regional<br />

implementation of ITS, it must be updated to correctly reflect how the developed<br />

projects integrate into the region.<br />

• Changes due to Project Addition/Deletion. Occasionally a project will be added<br />

or deleted through the planning process or through project delivery and some<br />

aspects of the regional ITS architecture that are associated with the project may be<br />

expanded, changed or removed.<br />

• Changes in Project Priority. Due to funding constraints, or other considerations,<br />

the planned project sequencing may change. Delaying a project may have a ripple<br />

effect on other projects that depend on it. Raising the priority for a project's<br />

implementation may impact other projects that are related to it.<br />

The above reasons for possible changes to the regional ITS architecture may happen<br />

frequently or infrequently, depending upon the region and the specifics of the original<br />

regional ITS architecture development effort. When a stakeholder identifies a potential<br />

update to the regional ITS architecture, the stakeholder should request a change using the<br />

procedure described below.<br />

5.2.3 Process for Requesting Updates<br />

When a possible change to the architecture has been identified, a Change Form should be<br />

completed by the initiator(s) of the change and the form should be submitted to David<br />

Shabazian of Sacramento Area Council of Governments (SACOG).<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

77 Final Report<br />

September 2005


At a minimum, the Change Form requires the following inputs:<br />

• Contact information of individual proposing change: name, title, agency, email,<br />

fax number and phone number<br />

• Date<br />

• Short description of proposed change (a title up to 25 characters)<br />

• Detailed description of proposed change. (What is to be added, deleted, or<br />

modified?)<br />

• Type of change proposed (e.g. new project, new stakeholder, etc.)<br />

• Name of system(s) or project(s) being implemented or modified (if applicable)<br />

• Status:<br />

o Proposed (the agency wants to implement but has not yet secured funding<br />

for the proposed project)<br />

o <strong>Plan</strong>ned (the agency has secured funding for the project)<br />

o Under Construction (the agency is currently deploying the system)<br />

o Existing (the agency has deployed the system(s) and it is currently<br />

operational)<br />

A sample form is included in Figure 5.1. A copy of the form can be sent via regular mail,<br />

e­mail, or fax to David Shabazian of Sacramento Area Council of Governments<br />

(SACOG) at the following address:<br />

Sacramento Area Council of Governments<br />

1415 L Street, Suite 300<br />

Sacramento, CA 95816<br />

Tel: (916) 340­6231<br />

Fax: (916) 457­3299<br />

E­mail: dshabazian@<strong>sacog</strong>.org<br />

5.3 Maintenance Roles and Responsibilities<br />

Maintenance of a regional ITS architecture can be taxing on agency resources; therefore,<br />

resources must be identified that have the willingness to accept this responsibility. The<br />

following section outlines the choices of the Sacramento Area in deciding who will be<br />

responsible for the maintenance of the regional ITS architecture.<br />

5.3.1 Maintainer Responsibilities<br />

At a minimum the regional ITS architecture maintainer shall be responsible for the<br />

following:<br />

• keeping the electronic and/or paper copies of the architecture of the latest version<br />

of the architecture;<br />

• maintaining a list of changes to be included in the next update to the Sacramento<br />

Regional ITS Architecture;<br />

• soliciting changes from stakeholders before major updates;<br />

• keeping the stakeholder contact and distribution list up to date;<br />

• initiating updates to the architecture;<br />

• implementing changes to the architecture (or overseeing the update process if done<br />

by an outside consultant); and<br />

• keeping a disposition of comments to proposed changes to the Architecture.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

78 Final Report<br />

September 2005


097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

79 Final Report<br />

September 2005


These responsibilities may be assigned to a single agency or shared by a number of<br />

agencies within a region. For the Sacramento Area, David Shabazian for the Sacramento<br />

Area Council of Governments (SACOG) is taking on the coordination role within the<br />

region, but the resources to complete the updates (either identifying in­house staff for<br />

future updates, or contracting future updates to consultants) will be provided by the<br />

agency(ies) shown in Table 5.1:<br />

Table 5.1: Project Stakeholders<br />

Current active participant<br />

Agency<br />

Sacramento County<br />

Caltrans District 3<br />

Federal Highway Administration<br />

SACOG<br />

City of Sacramento<br />

City of Roseville<br />

City of Citrus Heights<br />

City of Elk Grove<br />

City of West Sacramento<br />

City of Rancho Cordova<br />

City of Folsom<br />

City of Lincoln<br />

Town of Loomis<br />

City of Galt<br />

City of Isleton<br />

City of Davis<br />

City of Winters<br />

City of Woodland<br />

City of Live Oak<br />

Yuba City<br />

City of Marysville<br />

City of Wheatland (Raney <strong>Plan</strong>ning & Management)<br />

City of Auburn<br />

City of Colfax<br />

City of Rocklin<br />

City of Placerville<br />

Yolo County<br />

Yuba County<br />

Sutter County<br />

Placer County Transportation <strong>Plan</strong>ning Agency (PCTPA)<br />

Tahoe Gateway Counties<br />

El Dorado County Transportation Commission (EDCTC)<br />

El Dorado County Transit Authority<br />

Sacramento Regional Transit<br />

South County Transit<br />

Yuba­Sutter Transit Authority<br />

Placer County Transit<br />

Roseville Transit<br />

California Highway Patrol (CHP)<br />

Sacramento Metropolitan AQMD<br />

Yolo County Transportation District<br />

Contact<br />

Doug Maas<br />

Markus Heiman<br />

Frank Cechini<br />

David Shabazian<br />

JD Bamfield<br />

Susanna Aaltonen<br />

Stuart Hodgkins<br />

Dave Yatabe<br />

Ray Santiago<br />

Kathy Garcia<br />

Mark Rackovan<br />

John Pedri<br />

Brian Fragaio<br />

Curt Campion<br />

Jim Miller<br />

Patrick Fitzsimmons<br />

Charles Simpson<br />

Brent Meyer<br />

Rob Hickey<br />

Dennis Cook<br />

David Lamon<br />

Tim Raney<br />

Dennis Dowdy<br />

David Woodward<br />

Larry Wing<br />

Gary Valladao<br />

Rick Moore<br />

Kevin Mallen<br />

George Musallam<br />

Stan Tidman<br />

Stan Tidman<br />

Mike Higgins<br />

Katherine Cathey<br />

Mike Mattos<br />

June Gilmore<br />

Keith Martin<br />

Will Garner<br />

Mike Wixon<br />

Brian Hagler<br />

Art Smith<br />

Erik Reitz<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

80 Final Report<br />

September 2005


5.3.2 Other Committees Involved<br />

Other committees are also in place to further aid in the maintenance process. The<br />

committee names and responsibilities are listed below:<br />

• ITS Partnership –Guide the direction and development of ITS deployment in<br />

the Sacramento Region.<br />

• Regional <strong>Plan</strong>ning Partnership – Ensure consistency of architecture with<br />

planning objectives.<br />

5.4 Frequency of Updates<br />

It is important that the Sacramento Regional ITS Architecture be kept up to date in order to guide<br />

ITS planning and deployment in the region and to keep within the intent of federal requirements.<br />

The most effective way to ensure that a regional ITS architecture stays up to date is to establish a<br />

regular schedule for updates. For this reason, the Sacramento Regional ITS Architecture will be<br />

updated at regularly scheduled intervals, in coordination with the Metropolitan Transportation<br />

<strong>Plan</strong>. The Metropolitan Transportation <strong>Plan</strong> is updated every three years. The Sacramento<br />

Regional ITS Architecture (including the Tahoe Regional ITS Architecture) will be updated six<br />

months in advance of the Metropolitan Transportation <strong>Plan</strong>.<br />

It is also noted that the updates of the Sacramento Regional ITS Architecture will require<br />

resources, whether the intention is to perform the updates in­house or contract them out. These<br />

resources should be programmed in the overall work program. Currently, the stakeholders have<br />

agreed that updates to the architecture will be done using an outside consultant. Cost sharing of<br />

the updates will be established by the stakeholders prior to selecting a consultant.<br />

5.5 What Architecture Components will be Updated?<br />

The Sacramento Regional ITS Architecture consists of several lists and documents in various<br />

formats, including reports, databases, and graphics. As events occur that may result in changes<br />

to the architecture, the various components of the architecture should be updated accordingly in a<br />

systematic fashion. A change to one of the architecture components (for example, the addition of<br />

a project or a stakeholder) often requires other components of the architecture to be updated as<br />

well. This is known as dependencies between architecture components.<br />

To ensure that updates are made in all the necessary locations, Table 5.2 has been developed to<br />

assist the architecture maintainer. This table may be consulted by the maintainer to track key<br />

components of the Sacramento Regional ITS Architecture and to ensure that all parts of the<br />

Sacramento Regional ITS Architecture are updated appropriately. The table describes the<br />

different components of the Sacramento Regional ITS Architecture, their status, their location<br />

(name of the file, document or database where the component can be found), the file format (e.g.<br />

Word, Turbo, Visio Drawing, etc.) and their common dependencies. This will help the<br />

maintainer organize the architecture prior to updating and make sure that all of the necessary<br />

components are updated.<br />

All outputs in the architecture need to be reviewed to ensure that any dependencies which are not<br />

documented in the above table are followed through. For example, a change made to the list of<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

81 Final Report<br />

September 2005


stakeholders may necessitate updating all stakeholder references in other sections of the<br />

architecture. Those dependencies should then be added to the dependency matrix (or list) so that<br />

future updates to the architecture reflect that dependency.<br />

Table 5.2: List of Architecture Elements to be Updated<br />

Architecture<br />

Component<br />

Status of<br />

Component<br />

Location<br />

(Filename)<br />

Format(s)<br />

Dependencies<br />

Description of Region<br />

List of Stakeholders<br />

Operational Concept<br />

List of ITS<br />

Components/Inventory<br />

List of Agreements<br />

Interfaces between<br />

Components<br />

(Interconnects/<br />

Information Flows)<br />

System Functional<br />

Requirements<br />

Applicable ITS<br />

Standards<br />

Project Sequencing<br />

Currently in<br />

Architecture<br />

Currently in<br />

Architecture<br />

Currently in<br />

Architecture<br />

Currently in<br />

Architecture<br />

To be added to<br />

Architecture<br />

Currently in<br />

Architecture<br />

To be added to<br />

Architecture<br />

To be added to<br />

Architecture<br />

To be added to<br />

Architecture<br />

KHA:<br />

Sacramento<br />

Regional ITS<br />

Architecture.doc<br />

KHA:<br />

Sacramento<br />

Regional ITS<br />

Architecture.doc<br />

KHA:<br />

Sacramento<br />

Regional ITS<br />

Architecture.doc<br />

KHA:<br />

Sacramento<br />

Regional ITS<br />

Architecture.doc<br />

KHA:<br />

Sacramento<br />

Regional ITS<br />

Architecture.doc<br />

Word<br />

Document<br />

Word<br />

Document<br />

Word<br />

Document<br />

Word<br />

Document<br />

Word<br />

Document<br />

List of Stakeholders, Operational<br />

Concept, List of ITS<br />

Components/Inventory, List of<br />

Agreements, Interfaces between<br />

Components, System Functional<br />

Requirements, Applicable ITS Standards,<br />

Project Sequencing,<br />

Description of Region, Operational<br />

Concept, List of ITS<br />

Components/Inventory, List of<br />

Agreements, Interfaces between<br />

Components, System Functional<br />

Requirements, Applicable ITS Standards,<br />

Project Sequencing<br />

List of Agreements, Project Sequencing<br />

Interfaces between Components, System<br />

Functional Requirements, Applicable ITS<br />

Standards<br />

List of Agreements, System Functional<br />

Requirements, Applicable ITS Standards<br />

List of Agreements<br />

Interfaces between Components<br />

List of Stakeholders, List of Agreements,<br />

System Functional Requirements,<br />

Applicable ITS Standards<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

82 Final Report<br />

September 2005


5.6 Identifying and Implementing a Change<br />

5.6.1 Change Log<br />

Sacramento Area Council of Governments (SACOG) will be contracting future updates to<br />

Consultants. It will be the responsibility of the Consultant to determine and document an<br />

appropriate and systematic logging procedure for all Change Forms received. SACOG<br />

will be responsible for keeping a log of all Change Forms; these forms will be forwarded<br />

to the Consultant during the update process.<br />

5.6.2 Evaluation of Change/Impact on Region<br />

Sacramento Area Council of Governments (SACOG) will be contracting future updates to<br />

Consultants. It will be the responsibility of the Consultant to determine and document an<br />

appropriate evaluation procedure for all Change Forms received.<br />

5.6.3 Approval of Change<br />

Approval of the change will be required from:<br />

• Affected agencies when the change is minor<br />

• All project stakeholders for major changes<br />

The approval procedure for minor changes will be as follows. When minor changes are<br />

necessary, the affected agencies should convene to discuss the necessary changes and<br />

complete a Change Form. The completed form should be forwarded to the maintainer.<br />

The maintainer will keep the Change Forms on file until a formal update is made to the<br />

ITS Architecture.<br />

The approval procedure for major changes will be as follows. When changes are<br />

necessary or an update is scheduled, the maintainer should solicit input from each<br />

stakeholder for modifications. This can be through electronic means or as a discussion in<br />

a stakeholder meeting. The maintainer will then consolidate all comments into a single<br />

version for distribution, with all proposed changes clearly denoted in the document. The<br />

draft architecture with the proposed changes should be distributed to all stakeholders for<br />

review. Upon receipt of all comments and/or approval of the proposed changes, the<br />

maintainer will incorporate the comments and distribute a final version of the updated<br />

architecture to all stakeholders.<br />

If other stakeholders will be impacted by the change, they will be contacted by<br />

Sacramento Area Council of Governments (SACOG) to ascertain their agreement with<br />

the proposed change. Stakeholder comments will be incorporated into the Change Log as<br />

part of the Disposition of Comments. The term “Approval”pertains only to changes in<br />

the Architecture documentation.<br />

5.6.4 Implementation – Update Baseline and Notify Stakeholders<br />

Sacramento Area Council of Governments (SACOG) will be contracting future updates<br />

out to Consultants. It will be the responsibility of the Consultant to determine and<br />

document an appropriate Implementation and Notification Procedure for all changes,<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

83 Final Report<br />

September 2005


including keeping a baseline Architecture. Update cost sharing will be defined by the<br />

stakeholders prior to conducting update.<br />

5.7 Regional Adjacencies and Overlap Issues<br />

5.7.1 Background<br />

Within the State of California, there are currently 19 “ITS planning regions”(including<br />

the “Statewide”region), which create a challenge when trying to coordinate interregional<br />

and statewide ITS services and projects. Each regional ITS architecture is focused on<br />

defining an integrated plan for deployment of ITS projects and services within that region,<br />

serving the needs and institutional climate for that region. Due to the timing of these<br />

regional ITS architectures and the recent release of the Federal Final Rule/Policy, all of<br />

the architectures vary in detail and complexity. Many of these architectures are currently<br />

undergoing revision to bring them up to federal compliance.<br />

5.7.2 Interregional <strong>Plan</strong>ning<br />

To address the issues of overlap and adjacencies between regions, it is recommended that<br />

the most updated version of the regional ITS architecture for all adjacent/overlapping<br />

regions be obtained by the Sacramento Area Council of Governments (SACOG) prior to<br />

the update of the Sacramento Regional ITS Architecture. The adjacent regions potentially<br />

affecting the Sacramento Area are listed in the table below. SACOG will arrange a<br />

meeting twice a year with the adjacent regions to discuss and coordinate overlapping<br />

issues. By obtaining and coordinating the Sacramento Regional ITS Architecture with all<br />

adjoining and overlapping regions, interregional planning and project implementation<br />

should become more coordinated within the regions. Funding procurement for such<br />

projects should be easier to obtain since the project is covered by the regional ITS<br />

architectures of the surrounding regions. Also, by coordinating the regional ITS<br />

architectures with the statewide ITS architecture, large scale interregional and state level<br />

projects should be easier to accommodate.<br />

Previous discussions between the Sacramento region and the Tahoe Gateway region have<br />

resulted in SACOG agreeing to maintain and update the Tahoe Gateway Regional ITS<br />

Architecture whenever the Sacramento region is maintained and updated.<br />

Table 5.3: Interregional Adjacencies and Overlap by Region<br />

Adjacent Regions Overlap Subregions<br />

Bay Area (including Solano County),<br />

Tahoe Gateway, Tahoe Basin, San<br />

Joaquin Valley, Butte County, Sutter<br />

County<br />

Statewide<br />

None<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

84 Final Report<br />

September 2005


5.8 Version Control<br />

Due to the dynamics of the Sacramento Regional ITS Architecture, a version control system<br />

needs to be implemented. The version control system for the Sacramento Regional ITS<br />

Architecture should include a date on the cover sheet of any document that is part of the<br />

architecture. On an update, the new publication date should be inserted so that the current<br />

version may be identified. The maintainer should be responsible for keeping the version control<br />

accurate.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

85 Final Report<br />

September 2005


6 ITS SOLUTIONS TOOLBOX<br />

The previous sections laid the groundwork for integrated ITS deployment for the Sacramento region.<br />

Once a need is established for a particular project type, the responsible or leading agency may have<br />

different options for filling this need through the application of technology. This section presents the<br />

ITS Solutions Toolbox developed specifically for this project.<br />

6.1 SACOG ITS Solutions Toolbox<br />

The ITS Solutions Toolbox is a quick reference guide to considering ITS solutions for any<br />

capital improvement project. A planner or project developer can consult this toolbox to identify<br />

possible ITS solutions that can enhance a capital improvement project or the ITS solution could<br />

be a stand­alone project. The Toolbox is a resource containing the following “tools”for different<br />

project types:<br />

• Possible ITS solutions and descriptions<br />

• <strong>Deployment</strong> considerations<br />

• Unit Costs<br />

• Operations and Maintenance costs annually<br />

• Cost considerations<br />

To identify potential solutions, determine the type of project that is being considered. Look up<br />

that project type in the first table of the Toolbox. Mapped to each project type is a list of<br />

potential ITS solutions that could be added to a project that would provide some additional<br />

benefit (i.e., cost savings, streamlined process). Take that list of solutions and go to the second<br />

table that expands on those potential solutions including a description of the solution,<br />

deployment considerations, benefits, and costs. This table will provide the necessary information<br />

to go to the next step of mainstreaming ITS into the planning process.<br />

Several examples are provided below to illustrate how advanced technologies could be included<br />

in capital improvement projects. The projects identified in each table represent actual projects<br />

identified in the most recent MTP. Each example also has a series of benefits to agencies for<br />

including this technology in another project. Benefits to the public of these technologies can be<br />

found in the ITS Solutions Toolbox.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

86 Final Report<br />

September 2005


Example #1 –Install communications infrastructure and cable<br />

Description –Install a minimum 3” conduit, pull boxes, and possibly cable to provide a<br />

communications infrastructure network that meet the needs of an existing plan.<br />

There are numerous construction projects identified in the MTP or other documents that<br />

offer the opportunity to include communications infrastructure at a lower cost than<br />

constructing the infrastructure as a separate project. Table 6.1 contains examples of<br />

projects that could benefit from the addition of conduit and cable.<br />

Benefits<br />

• Cost savings of installing infrastructure during a reconstruction project or<br />

new roadway project is substantial compared to a project that only includes<br />

communications infrastructure.<br />

• Major cost savings by eliminating traffic control needed for a separate<br />

project.<br />

• Contracting process is streamlined by combining elements rather than<br />

separate projects.<br />

Table 6.1: MTP Sample Projects that can benefit from Project Example #1<br />

Project Agency Description<br />

Elk Grove Boulevard<br />

Enhancements<br />

City of Elk Grove Design and development of enhancements<br />

between Walnut Avenue and School Street.<br />

Folsom Road Rehabilitation City of Folsom Various major arterial roadways.<br />

SR 65 Signal Coordination Project City of Lincoln Analysis, design, and construction of traffic<br />

signal modifications, signage, and striping<br />

improvements from Ferrari Ranch Road to 7 th<br />

Street.<br />

Folsom Boulevard Enhancements City of Rancho<br />

Cordova<br />

Install landscaping and streetscaping between<br />

Rod Beaudry Drive and Sunrise Blvd.<br />

65 th Street Improvements City of Sacramento Construct sidewalk, curb, gutter, and bike<br />

lanes.<br />

Fruitridge Road City of Sacramento Streetscape and traffic improvements between<br />

65 th Street Expwy and Power In Road.<br />

Industrial Boulevard and Enterprise City of West Overlay and slurry seal<br />

Blvd<br />

Sacramento<br />

Florin Road Enhancements Sacramento County Construct sidewalks, bikeways, medians,<br />

lighting, landscaping and streetscaping from<br />

Stockton Blvd. to Elk Grove­Florin Rd.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

87 Final Report<br />

September 2005


Example #2 –Install CCTV Camera<br />

Description –Install a CCTV camera at an intersection that will be included with other<br />

traffic signal modifications.<br />

There are several projects identified in the MTP or other documents that offer the<br />

opportunity to include a CCTV camera as part of the construction to upgrade or install a<br />

new intersection. Table 6.2 contains examples of projects that could benefit from the<br />

addition of a CCTV camera.<br />

Benefits<br />

• Major cost savings by eliminating traffic control needed for a separate<br />

project.<br />

• Contracting process is streamlined by combining elements rather than<br />

separate projects.<br />

Table 6.2: MTP Sample Projects that can benefit from Project Example #2<br />

Project Agency Description<br />

West Stockton Blvd/Laguna Creek<br />

Bridge<br />

US 50 at Mather Field Rod<br />

Interchange<br />

City of Elk Grove<br />

City of Rancho<br />

Cordova<br />

Replace existing bridge with new structure.<br />

Design, install, and maintain landscape,<br />

streetscape, lighting and other enhancements<br />

within the existing freeway interchange.<br />

Construct curb, gutters, sidewalk, crosswalks,<br />

etc.<br />

Install new traffic signal.<br />

Broadway/MLK Jr. Intersection City of Sacramento<br />

Enhancements<br />

Florin Road and Woodbine Traffic City of Sacramento<br />

Signal<br />

SR 160 at Richards City of Sacramento Install signalized intersection.<br />

Cambridge/Merrychase at US 50 El Dorado County Signalized ramps and intersection<br />

improvements.<br />

47 th Avenue Station Traffic Signal Sacramento<br />

Regional Transit<br />

Construct traffic signal.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

88 Final Report<br />

September 2005


Example #3 –Install Pedestrian ITS Solutions<br />

Description – Install equipment at traffic signals that enhances pedestrian/driver<br />

awareness.<br />

There are several projects identified in the MTP or other documents that offer the<br />

opportunity to include pedestrian ITS solutions as part of the construction to upgrade a or<br />

install a new intersection. This could include solutions like lighted crosswalks, pedestrian<br />

countdown timers, or animated pedestrian heads. All of the projects identified above for<br />

the inclusion of a CCTV camera would also be appropriate for the consideration of<br />

pedestrian ITS solutions. Table 6.3 contains examples of projects that could benefit from<br />

the addition of pedestrian ITS solutions.<br />

Benefits<br />

• Cost savings if equipment can be installed with other traffic signal<br />

modifications as opposed to changing the equipment out later on a<br />

subsequent project.<br />

Table 6.3: MTP Sample Projects that can benefit from Project Example #3<br />

Project Agency Description<br />

Broadway/MLK Jr. Intersection<br />

Enhancements<br />

City of Sacramento Construct curb, gutters, sidewalk, crosswalks,<br />

etc.<br />

South Midtown Traffic Calming City of Sacramento Implement traffic signal modifications from L to<br />

Q and 16 th to 29 th .<br />

Taylor Street School Pedestrian<br />

Safety<br />

City of Sacramento Install curb, gutter, sidewalk on Taylor Street.<br />

Example #4 –Install Traveler Information Kiosks<br />

Description –Install a kiosk that would provide pedestrians access to Sacramento 511 or<br />

other traveler and transit information.<br />

There are a couple of projects that have plans to develop for the benefit of pedestrians.<br />

For these projects, a kiosk could be installed that provides traveler information and transit<br />

information. Table 6.4 contains examples of projects that could benefit from the addition<br />

of a kiosk.<br />

Benefits<br />

• Low cost solution to providing traveler information with easy access.<br />

Table 6.4: MTP Sample Projects that can benefit from Project Example #4<br />

Project Agency Description<br />

Loomis Rail Station Enhancements City of Loomis Design and construct pedestrian and<br />

landscaping improvements at the multimodal<br />

center.<br />

Rancho Cordova City Center<br />

City of Rancho<br />

Cordova<br />

Develop a city center across from the existing<br />

light rail station at Folsom Blvd/La Loma Drive.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

89 Final Report<br />

September 2005


SACOG<br />

ITS SOLUTIONS TOOLBOX<br />

FOR MAINSTREAMING ITS<br />

Project Types and ITS Solutions<br />

Project Type<br />

Arterial<br />

Traffic Calming<br />

Roadway Widening<br />

Roadway Construction<br />

Streetscaping<br />

Utility Work<br />

Traffic Signal<br />

Pavement Overlay<br />

Traffic Signal Interconnect<br />

Grade Separation<br />

Possible ITS Enhancements<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Pedestrian Improvements (in­pavement lighting, countdown<br />

pedestrian heads, animated pedestrian heads)<br />

Closed Circuit Television (CCTV) Camera<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Vehicle Detection<br />

Closed Circuit Television (CCTV) Camera<br />

Changeable Message Sign (CMS)<br />

Highway Advisory Radio (HAR)<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Vehicle Detection<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Vehicle Detection<br />

Pedestrian Improvements (in­pavement lighting, countdown<br />

pedestrian heads, animated pedestrian heads)<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Closed Circuit Television (CCTV) Camera<br />

Emergency Vehicle Preemption/Transit Signal Priority<br />

(EVP/TSP)<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Vehicle Detection<br />

Wireless Hot Spots for Field Crews<br />

Pedestrian Improvements (in­pavement lighting, countdown<br />

pedestrian heads, animated pedestrian heads)<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Vehicle Detection<br />

Closed Circuit Television (CCTV) Camera<br />

Closed Circuit Television (CCTV) Camera<br />

Ramp Meter<br />

Traffic Signal Interconnect Conduit<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

90 Final Report<br />

September 2005


SACOG<br />

ITS SOLUTIONS TOOLBOX<br />

FOR MAINSTREAMING ITS<br />

Project Types and ITS Solutions<br />

Project Type<br />

Transit<br />

Transit Stop Installation or<br />

Improvement<br />

Light Rail Extension<br />

Transit Village<br />

Livable Community<br />

Transit Fleet Addition or<br />

Upgrade<br />

Dispatch­related (software,<br />

hardware)<br />

At­grade Railroad Crossing<br />

Grade Separation<br />

Paratransit<br />

Possible ITS Enhancements<br />

Power for future equipment<br />

Transit Arrival Signs<br />

Traveler Information Kiosk<br />

Closed Circuit Television (CCTV) Camera<br />

Communications for future equipment<br />

Power for future equipment (i.e., kiosk, surveillance, signs)<br />

Transit Arrival Signs<br />

Traveler Information Kiosk<br />

Closed Circuit Television (CCTV) Camera<br />

Automatic Vehicle Location (AVL) System<br />

Transit Signal Priority (TSP)<br />

Bus Rapid Transit (BRT) Technology/Queue Jump Lanes<br />

Electronic Payment<br />

Railroad Collision Avoidance System<br />

Communications for future equipment<br />

Transit Arrival Signs<br />

Traveler Information Kiosk<br />

Closed Circuit Television (CCTV) Camera<br />

Transit Arrival Signs<br />

Traveler Information Kiosk<br />

Closed Circuit Television (CCTV) Camera<br />

Closed Circuit Television (CCTV) Camera (on­board)<br />

Automatic Vehicle Location (AVL) System<br />

Transit Signal Priority (TSP)<br />

Electronic Payment<br />

Railroad Collision Avoidance System<br />

Communications for future equipment<br />

Automatic Vehicle Location (AVL) System<br />

Communications for future equipment<br />

Automatic Vehicle Location (AVL) System<br />

Railroad Collision Avoidance System Communications for<br />

future equipment<br />

Communications for future equipment<br />

Automatic Vehicle Location (AVL) System<br />

Communications for future equipment<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

91 Final Report<br />

September 2005


SACOG<br />

ITS SOLUTIONS TOOLBOX<br />

FOR MAINSTREAMING ITS<br />

Project Types and ITS Solutions<br />

Project Type<br />

Possible ITS Enhancements<br />

Emergency Management Systems<br />

Emergency Vehicles – Fleet<br />

Addition or Upgrade<br />

Communication System<br />

Installation or Upgrade,<br />

including servers, towers,<br />

dispatch<br />

Emergency Operations Center<br />

Emergency Vehicle Preemption (EVP)<br />

Automatic Vehicle Location (AVL) System<br />

Integrate with Public Broadcasting<br />

Dynamic Route Guidance<br />

Automatic Vehicle Location (AVL) System<br />

Integration with Traffic Management Center (TMC)<br />

Integration with 511<br />

Integrate with Public Broadcasting<br />

Dynamic Route Guidance<br />

Automatic Vehicle Location (AVL) System<br />

Integration with Traffic Management Center (TMC)<br />

Collocate with Traffic Management Center (TMC)<br />

Integration with 511<br />

Commercial Vehicle Operations<br />

Truck Scales – Installation or<br />

Upgrade<br />

Rest Areas<br />

Weigh­In­Motion<br />

Electronic Credentials<br />

Transponder/Reader<br />

Closed Circuit Television (CCTV) Camera<br />

Traveler Information Kiosk<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

92 Final Report<br />

September 2005


SACOG<br />

ITS SOLUTIONS TOOLBOX<br />

FOR MAINSTREAMING ITS<br />

Project Types and ITS Solutions<br />

Project Type<br />

Bicycle<br />

Bicycle Lane<br />

At­Grade Trail Crossing<br />

Bike Storage<br />

Pedestrian<br />

Pedestrian Crossing<br />

Sidewalk<br />

Pedestrian Mall<br />

Livable Community<br />

Ports<br />

Port access and circulation<br />

projects<br />

Other<br />

Parking facility or structure<br />

Rideshare or carpool program<br />

Possible ITS Enhancements<br />

Bicycle Detection<br />

Signal Retiming<br />

Automated Enforcement<br />

Bicycle Detection<br />

Signal Retiming<br />

Automated Enforcement<br />

Surveillance (Closed Circuit Television Camera)<br />

Smart Parking<br />

In­pavement lighting<br />

Signalization<br />

Pedestrian Detection<br />

Enhanced pedestrian heads<br />

Wireless Hot Spot (only if signalized)<br />

Traffic Signal Interconnect Conduit<br />

Traffic Signal Interconnect Cable (SIC)<br />

Traveler Information Kiosk<br />

Wireless Hot Spots<br />

Traveler Information Kiosk<br />

Wireless Hot Spots<br />

Automatic Vehicle Location (AVL) System<br />

Dynamic Route Guidance<br />

Parking Reservation System<br />

Parking Guidance Information System<br />

Ridesharing software/website (see www.sacregion511.org)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

93 Final Report<br />

September 2005


SACOG<br />

ITS SOLUTIONS TOOLBOX<br />

FOR MAINSTREAMING ITS<br />

Project Types and ITS Solutions<br />

Project Type<br />

Freeway<br />

HOV Lane and/or HOT Lane<br />

Freeway Widening<br />

Freeway Construction<br />

Interchange Reconfiguration or<br />

Construction<br />

Auxiliary Lane<br />

Grade Separation (Bridge<br />

Structure)<br />

Possible ITS Enhancements<br />

Transponder/Reader (for HOT Lanes)<br />

Closed Circuit Television (CCTV) Camera<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

Vehicle Detection<br />

Portable Traffic Management Devices<br />

Closed Circuit Television (CCTV) Camera<br />

Changeable Message Sign (CMS)<br />

Highway Advisory Radio (HAR)<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

Vehicle Detection<br />

Roadway Weather Information System (RWIS)<br />

Portable Traffic Management Devices<br />

Closed Circuit Television (CCTV) Camera<br />

Changeable Message Sign (CMS)<br />

Ramp Meter<br />

Highway Advisory Radio (HAR)<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

Detection<br />

Roadway Weather Information System (RWIS)<br />

Portable Traffic Management Devices<br />

Closed Circuit Television (CCTV) Camera<br />

Ramp Meters<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

Vehicle Detection<br />

Closed Circuit Television (CCTV) Camera<br />

Changeable Message Sign (CMS)<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

Vehicle Detection<br />

Closed Circuit Television (CCTV) Camera<br />

Communications Conduit<br />

Communications Cable (or wireless)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

94 Final Report<br />

September 2005


ITS<br />

Solutions<br />

CCTV<br />

cameras<br />

Changeable<br />

Message Sign<br />

(CMS)<br />

Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

Project<br />

Types<br />

• Roadway<br />

Construction<br />

• Roadway<br />

Widening<br />

• Traffic Signal<br />

• Traffic Signal<br />

Interconnect<br />

Cable<br />

• Roadway<br />

Construction<br />

Solution<br />

Descriptions<br />

Includes pan­tiltzoom<br />

(PTZ) or fixed<br />

camera, enclosure,<br />

cabling,<br />

pole/mounting,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for traffic<br />

surveillance<br />

Sign, structure,<br />

foundation, power,<br />

communications<br />

infrastructure,<br />

communications<br />

device for<br />

displaying traveler<br />

information<br />

<strong>Deployment</strong><br />

Considerations<br />

• Pan­tilt­zoom (PTZ)<br />

or fixed camera?<br />

• New or existing<br />

structure?<br />

• Is there an existing<br />

video system?<br />

• Leased line or<br />

agency­owned<br />

communications?<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

communications<br />

infrastructure?<br />

• Structure needs to<br />

support a camera<br />

• Where to draw<br />

power for the camera<br />

and any associated<br />

electronics?<br />

• Size of the sign.<br />

• Sign technology.<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

central system or will<br />

this be stand­alone?<br />

• Were to draw<br />

power?<br />

Cost<br />

Arterial<br />

$8,000­40,000<br />

each<br />

O&M Cost<br />

$2,000­3,000<br />

per camera per<br />

year<br />

$75,000­<br />

250,000 each<br />

O&M Cost<br />

$3,000­6,000<br />

per sign per<br />

year<br />

Cost<br />

Considerations<br />

Cost depends on<br />

installation on<br />

existing or new<br />

structure and other<br />

design<br />

considerations, and<br />

includes equipment<br />

and installation.<br />

Does not include<br />

communications and<br />

power installation.<br />

Depends on<br />

technology, size of<br />

sign, type of<br />

structure. Does not<br />

include<br />

communications and<br />

power installation.<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Camera provides faster identification<br />

and response to incidents<br />

• Improve performance of traffic signal<br />

system by monitoring conditions<br />

remotely<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Improved staff efficiency when<br />

troubleshooting or verifying field<br />

issues<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• With CMS, have ability to<br />

disseminate traffic condition<br />

information<br />

• Cost savings could lead to additional<br />

transportation projects<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

from proactive use of<br />

cameras<br />

• Improved information<br />

for travel planning<br />

using real­time<br />

images<br />

• Minimize disruption to<br />

traffic<br />

• Travel information<br />

made available to<br />

public<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

95 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Arterial<br />

Highway<br />

Advisory<br />

Radio (HAR)<br />

Emergency<br />

Vehicle<br />

Preemption<br />

(EVP)/Transit<br />

Signal Priority<br />

(TSP)<br />

Traffic Signal<br />

Interconnect<br />

Conduit<br />

• Roadway<br />

Construction<br />

• Traffic Signal<br />

• Roadway<br />

Construction<br />

• Traffic<br />

Calming<br />

• Roadway<br />

Widening<br />

• Streetscaping<br />

• Utility Work<br />

• Traffic Signal<br />

Antenna, pole, sign,<br />

power, broadcast<br />

equipment for<br />

broadcasting<br />

traveler advisories<br />

Device on existing<br />

structure, cabling to<br />

signal cabinet,<br />

emitter on vehicle to<br />

allow emergency<br />

preemption or<br />

transit vehicle<br />

priority<br />

Minimum 3”<br />

conduit, pull boxes,<br />

splice vault at key<br />

locations for future<br />

interconnect cable<br />

to coordinate traffic<br />

signal timing<br />

• Need to do a<br />

frequency<br />

evaluation.<br />

• Consider the area of<br />

coverage.<br />

• If for Transit Signal<br />

Priority (TSP), can<br />

existing controller<br />

support the function?<br />

• Which approaches<br />

are required?<br />

• Adequate conduit<br />

sweeps if fiber is<br />

used<br />

• Other design<br />

elements may be<br />

different depending<br />

on medium.<br />

• Placement in<br />

roadway or behind<br />

curb?<br />

• Are multiple conduits<br />

needed?<br />

$25,000­50,000<br />

per location<br />

O&M Cost<br />

$1,500­2,000<br />

per location per<br />

year<br />

$6,000­18,000<br />

per intersection<br />

O&M Cost<br />

$1,000 per<br />

intersection per<br />

year<br />

$65,000 per<br />

mile<br />

O&M Cost<br />

Minimal<br />

Depends primarily on<br />

signal strength.<br />

Does not include<br />

communications and<br />

power installation.<br />

Includes on­board<br />

equipment<br />

Costs vary<br />

depending on<br />

number of conduit<br />

and frequency of pull<br />

boxes<br />

• Resource for disseminating traveler<br />

information<br />

• Can easily broadcast traffic advisories<br />

• Low construction and maintenance<br />

costs<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Provide ability to improve response<br />

time of emergency vehicles to incidents<br />

• Provide opportunity to offer enhanced<br />

transit service<br />

• Improved travel time for transit vehicles<br />

• Potential to reduce fleet size<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with<br />

the ability to coordinate traffic signals<br />

to improve traffic flow along a corridor<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings<br />

could lead to additional transportation<br />

projects<br />

• Little to no recurring costs<br />

• Real­time traveler<br />

information made<br />

available to public<br />

• Can receive<br />

localized travel<br />

information with a<br />

standard radio<br />

• Faster response to<br />

incidents<br />

• Enhance reliability of<br />

transit schedules<br />

• Minimize disruption<br />

to traffic<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

96 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Arterial<br />

Traffic Signal<br />

Interconnect<br />

Cable<br />

Mid­block<br />

Vehicle<br />

Detection<br />

• Roadway<br />

Construction<br />

• Traffic<br />

Calming<br />

• Roadway<br />

Widening<br />

• Streetscaping<br />

• Utility Work<br />

• Traffic Signal<br />

• Roadway<br />

Construction<br />

• Roadway<br />

Widening<br />

• Streetscaping<br />

• Traffic Signal<br />

Copper twisted pair<br />

cable, fiber optic<br />

cable, or wireless<br />

antennas;<br />

communications<br />

transmitter/receiver;<br />

termination panels<br />

to coordinate traffic<br />

signal timing<br />

Detection device,<br />

cabling to signal<br />

cabinet, power to<br />

measure traffic<br />

volume and flow<br />

along corridors<br />

• Communications<br />

medium (copper,<br />

fiber, wireless,<br />

Ethernet… )<br />

• Tie to existing<br />

system?<br />

• Ability of end<br />

equipment to use<br />

the technology.<br />

• Detection<br />

technology (inpavement<br />

vs. nonintrusive).<br />

$9,000­20,000<br />

per mile<br />

O&M Cost<br />

$1,000 per mile<br />

per year<br />

$3,000­20,000<br />

per location<br />

O&M Cost<br />

$1,000­2,000<br />

per location<br />

Depends on<br />

communications<br />

medium, does not<br />

include conduit (see<br />

above)<br />

Additional O&M costs<br />

if leased lines are<br />

used<br />

Depends on<br />

technology and<br />

installation/ mounting<br />

requirements<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with<br />

the ability to coordinate traffic signals<br />

to improve traffic flow along a corridor<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings could<br />

lead to additional transportation projects<br />

• Little to no recurring costs<br />

• If added to another project, disruption<br />

to traffic is minimized<br />

• Reliable source of traffic data<br />

• Improved traffic flow<br />

along a corridor<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

along corridor<br />

• Real­time traffic flow<br />

data could be<br />

available<br />

• No privacy issues<br />

compared with other<br />

technologies<br />

Wireless<br />

Hotspots at<br />

traffic signals<br />

• Traffic Signal<br />

Equipment in signal<br />

cabinet to allow city<br />

staff (field<br />

personnel) to<br />

access city network<br />

• Is there adequate<br />

space in the cabinet?<br />

• Is solution desirable?<br />

• Proximity to other<br />

hotspots<br />

• Place exterior<br />

equipment to avoid<br />

vandalism.<br />

$1,000­2,000<br />

per installation<br />

O&M Cost<br />

$500 per year<br />

• Cost effective method of providing<br />

communications<br />

• Can be either public (leased) or<br />

private (owned)<br />

• Opportunities for shared infrastructure<br />

with multiple agencies<br />

• Public/Private<br />

partnerships can<br />

result in added<br />

coverage for wireless<br />

access to the Internet<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

97 Final Report<br />

September 2005


ITS<br />

Solutions<br />

Pedestrian<br />

Improvements<br />

Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

Project<br />

Types<br />

• Traffic<br />

Calming<br />

• Streetscaping<br />

• Traffic Signal<br />

Solution<br />

Descriptions<br />

Raised crosswalks,<br />

countdown<br />

pedestrian heads,<br />

animated<br />

pedestrian heads,<br />

in­pavement<br />

lighting to raise<br />

awareness of<br />

pedestrians<br />

<strong>Deployment</strong><br />

Considerations<br />

• Americans with<br />

Disabilities Act<br />

(ADA) compliance.<br />

Cost<br />

Arterial<br />

$500­15,000<br />

O&M Cost<br />

$500­1,000 per<br />

year<br />

Cost<br />

Considerations<br />

Depends on extent<br />

of improvements, but<br />

typically more cost<br />

effective if part of a<br />

larger project<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

• Reduces the cost of installing<br />

advanced technology at a later date.<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• Improves visibility of<br />

pedestrians<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

98 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Transit<br />

Power<br />

Real­Time<br />

Information<br />

Signs<br />

Traveler<br />

Information<br />

Kiosks<br />

Bus Rapid<br />

Transit /<br />

Queue Jump<br />

• Bus Stop<br />

Improvements<br />

or Installations<br />

• Light Rail<br />

Extension<br />

• Bus Stop<br />

Improvements<br />

or Installations<br />

• Light Rail<br />

Extension<br />

• Transit<br />

Villages<br />

• Bus Stop<br />

Improvements<br />

or Installations<br />

• Light Rail<br />

Extension<br />

• Transit Villages<br />

• Light Rail<br />

Extension<br />

Identify service<br />

point, install service<br />

conduit for future<br />

equipment<br />

installation<br />

Sign, post, power,<br />

communications<br />

cabling for<br />

displaying vehicle<br />

arrival times or<br />

other information<br />

Kiosk equipment,<br />

power,<br />

communications for<br />

displaying traveler<br />

information<br />

Device on existing<br />

structure, cabling to<br />

signal cabinet,<br />

emitter on vehicle,<br />

signal heads, signs<br />

for enhanced bus<br />

service<br />

• 120/240V power<br />

available?<br />

• Will solar power be<br />

adequate for<br />

anticipated usage?<br />

• Is there an existing<br />

system to disseminate<br />

information to signs?<br />

• How many signs are<br />

needed?<br />

• Is there power near<br />

the locations of the<br />

signs?<br />

• What information<br />

will be displayed?<br />

• Most effective<br />

location to place the<br />

signs<br />

• Can existing<br />

controllers support<br />

the function?<br />

• Will the geometry<br />

support a queue<br />

jump lane?<br />

$8,000­15,000<br />

per location<br />

O&M Cost<br />

$0­500 per<br />

location<br />

$12,000­<br />

25,000 per<br />

sign<br />

O&M Cost<br />

$500­1,000<br />

per sign per<br />

year<br />

$10,000­<br />

50,000 per<br />

kiosk<br />

O&M Cost<br />

$1,000 per<br />

kiosk per year<br />

$10,000­<br />

25,000 per<br />

intersection<br />

O&M Cost<br />

$1,000 per<br />

intersection<br />

Depends on distance<br />

to service, does not<br />

include PG&E costs or<br />

cost of solar<br />

equipment<br />

Depends on sign<br />

technology, size,<br />

quantity, power and<br />

communications. Does<br />

not include the real­time<br />

information system<br />

(hardware and<br />

software).<br />

Depends on how<br />

much information is<br />

made available,<br />

interface development<br />

requirements.<br />

Includes on­board<br />

equipment, does not<br />

include integration or<br />

upgrade of existing<br />

equipment, does not<br />

include geometric<br />

improvements<br />

• Reduces cost of installing power at a<br />

later date<br />

• Provides a mechanism to inform<br />

passengers of arrivals/departures<br />

• Improves system reliability<br />

• Better integration with other facilities<br />

versus a stand­alone installation<br />

• Enhances performance of transit<br />

• Reduces disruption to<br />

traffic<br />

• Reduces passenger<br />

frustration<br />

• Provides a mechanism<br />

for passengers to gain<br />

information and plan<br />

their trips accordingly<br />

• Enhance reliability and<br />

performance of transit<br />

operations<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

99 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Transit<br />

Electronic<br />

Payment<br />

CCTV<br />

cameras<br />

• Light Rail<br />

Extension<br />

• New Fleet<br />

• Bus Stop<br />

Improvement<br />

s or<br />

Installations<br />

• Light Rail<br />

Extension<br />

• Transit<br />

Villages<br />

• New Fleet<br />

• At­Grade<br />

Railroad<br />

Crossings<br />

• Grade<br />

Separations<br />

• Livable<br />

Communities<br />

Fare cards, fare<br />

reader equipment,<br />

power for expedited<br />

fare collection<br />

Includes pan­tiltzoom<br />

(PTZ) or fixed<br />

camera, enclosure,<br />

cabling,<br />

pole/mounting,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for vehicle<br />

surveillance<br />

• Will relevant transit<br />

agencies<br />

participate?<br />

• PTZ or fixed<br />

camera?<br />

• New or existing<br />

structure?<br />

• Is there an existing<br />

video system?<br />

• Leased line or<br />

agency­owned<br />

communications?<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

communications<br />

infrastructure?<br />

• Structure needs to<br />

support a camera<br />

• Consider power for<br />

the camera and any<br />

associated<br />

electronics?<br />

$250,000­<br />

600,000<br />

O&M Cost<br />

$1,000­2,000<br />

$8,000­40,000<br />

each<br />

O&M Cost<br />

$2,000­3,000<br />

per camera<br />

per year<br />

Depends on extent of<br />

integration and<br />

deployment<br />

Cost depends on<br />

installation on existing<br />

or new structure and<br />

other design<br />

considerations, and<br />

includes equipment<br />

and installation. Does<br />

not include<br />

communications.<br />

• Equipment on vehicles can be done<br />

during initial vehicle production rather<br />

than after­market<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Camera provides faster identification<br />

and response to incidents<br />

• Improve performance of traffic signal<br />

system by monitoring conditions<br />

remotely<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Improved staff efficiency when<br />

troubleshooting or verifying field<br />

issues<br />

• Improves coordination<br />

across multiple modes<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

from proactive use of<br />

cameras<br />

• Improved information<br />

for travel planning<br />

using real­time images<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

100 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Transit<br />

Transit Signal<br />

Priority<br />

Automated<br />

Vehicle<br />

Location<br />

(AVL)<br />

• Light Rail<br />

Extension<br />

• New Fleet<br />

• Light Rail<br />

Extension<br />

• New Fleet<br />

• Dispatch<br />

• Paratransit<br />

Device on existing<br />

structure, cabling to<br />

signal cabinet,<br />

emitter on vehicle to<br />

allow transit<br />

vehicles priority<br />

phasing (not<br />

preemption) in the<br />

event the vehicle is<br />

not on schedule<br />

AVL unit on<br />

vehicles, central<br />

equipment to<br />

identify location of<br />

vehicles for realtime<br />

arrival or<br />

location status<br />

• Can existing<br />

controllers support<br />

the function?<br />

• Integration with an<br />

existing transit<br />

management/scheduli<br />

ng system.<br />

• Is there an existing<br />

system to support<br />

the collection and<br />

distribution of data?<br />

• Communications<br />

network available?<br />

$6,000­18,000<br />

per intersection<br />

O&M Cost<br />

$1,000 per<br />

intersection per<br />

year<br />

$300,000 per<br />

system<br />

O&M Cost<br />

$20,000 per<br />

year<br />

Includes on­board<br />

equipment, does not<br />

include integration or<br />

upgrade of existing<br />

equipment, nor does it<br />

include<br />

communications to a<br />

central system.<br />

Will vary depending<br />

on the number of<br />

transit vehicles. Cost<br />

does not include a<br />

comprehensive<br />

communications<br />

infrastructure.<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Provide opportunity to offer enhanced<br />

transit service<br />

• Improved travel time for transit<br />

vehicles<br />

• Potential to reduce fleet size<br />

• Provides an automated mechanism<br />

to track vehicles, on­time<br />

performance and data for schedule<br />

adjustments<br />

• Can process real­time monitoring<br />

data on status of transit vehicle<br />

elements for operations and<br />

maintenance<br />

• Provides efficient use of<br />

communications system (voice and<br />

data)<br />

• Enables greater degree of security for<br />

drivers/passengers with emergency<br />

alarms<br />

• Provides a mechanism for schedulebased<br />

transit priority<br />

• Enhance reliability and<br />

performance of transit<br />

operations<br />

• Provides an accurate<br />

means for real­time<br />

information<br />

• Improved security with<br />

emergency alarm<br />

capabilities<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

101 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to<br />

Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Transit<br />

Communications<br />

Infrastructure<br />

Railroad<br />

Collision<br />

Avoidance<br />

• Bus Stop<br />

Improvements<br />

or Installations<br />

• Light Rail<br />

Extension<br />

• New Fleet<br />

• At­Grade<br />

Railroad<br />

Crossings<br />

• Grade<br />

Separations<br />

• Livable<br />

Communities<br />

• Para­transit<br />

• Light Rail<br />

Extension<br />

• New Fleet<br />

• At­Grade<br />

Railroad<br />

Crossings<br />

• Grade<br />

Separations<br />

• Livable<br />

Communities<br />

Copper, fiber, or<br />

wireless<br />

communications<br />

link, end equipment<br />

In­vehicle and onboard<br />

equipment,<br />

crossing equipment<br />

for collision<br />

avoidance<br />

• Is there an existing<br />

system to interface<br />

with?<br />

• Is conduit<br />

infrastructure<br />

needed?<br />

• If conduit exists and<br />

fiber is used, will the<br />

conduit<br />

accommodate fiber?<br />

• What is the desired<br />

topology (i.e.,<br />

Ethernet, ring)<br />

• Ability of end<br />

equipment to use the<br />

technology.<br />

• Lease or own?<br />

• What detection<br />

technology will be<br />

used?<br />

$65,000 per<br />

mile for<br />

conduit<br />

O&M Cost<br />

$9,000­20,000<br />

per mile for<br />

communications<br />

per year<br />

Minimal for<br />

conduit<br />

$100,000­<br />

150,000 per<br />

crossing<br />

O&M Cost<br />

$2,000­3,000<br />

per crossing<br />

per year<br />

Depends on<br />

communications<br />

medium, does not<br />

include conduit.<br />

Additional O&M costs if<br />

leased lines are used<br />

Includes equipment at<br />

crossing and on<br />

vehicles. Does not<br />

include<br />

communications to a<br />

central facility<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with<br />

the ability to communicate with field<br />

equipment<br />

• Savings could lead to additional<br />

transportation projects<br />

• Little to no recurring costs compared<br />

to leasing communications<br />

• Equipment on vehicles can be<br />

installed during initial vehicle<br />

production rather than after­market<br />

• Operate safer crossings<br />

• Reduces disruption to<br />

traffic over<br />

communications being<br />

installed at a later date<br />

• Safer railroad crossings<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

102 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Emergency<br />

Vehicle<br />

Preemption<br />

Media<br />

Integration<br />

(for example<br />

with Public<br />

Broadcasting)<br />

TMC Colocation<br />

and<br />

Integration<br />

511<br />

Integration<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Emergency Management Systems<br />

• New<br />

Emergency<br />

Vehicles<br />

• Communications<br />

System<br />

Upgrades<br />

• Emergency<br />

Operations<br />

Center<br />

• Emergency<br />

Operations<br />

Center<br />

• Communications<br />

System<br />

Upgrades<br />

• Emergency<br />

Operations<br />

Center<br />

Device on existing<br />

structure, cabling to<br />

signal cabinet,<br />

emitter on vehicle to<br />

allow emergency<br />

vehicles to preempt<br />

a traffic signal for a<br />

green phase<br />

Identification of<br />

communications<br />

link, end equipment<br />

to allow public<br />

broadcasting of<br />

traveler information<br />

Physical cabling,<br />

end equipment,<br />

software<br />

development to<br />

enhance sharing of<br />

information<br />

Software<br />

development to allow<br />

incidents and<br />

emergency services<br />

to access and provide<br />

information to 511 to<br />

enhance information<br />

available through 511<br />

• Which approaches<br />

are required?<br />

• Which vehicles are to<br />

be equipped?<br />

• Utilize encoding to<br />

prevent unauthorized<br />

use?<br />

• Need to establish<br />

agreements with<br />

media companies?<br />

• What are the<br />

limitations of access<br />

(viewing only)?<br />

• Where will the<br />

combined center<br />

reside?<br />

• Need to establish<br />

agreements between<br />

agencies involved.<br />

• What is the extent of<br />

information<br />

disseminated?<br />

• To what extent will<br />

the systems be<br />

integrated?<br />

$6,000­18,000<br />

per<br />

intersection<br />

O&M Cost<br />

$1,000 per<br />

intersection<br />

per year<br />

$100,000­<br />

150,000<br />

O&M Cost<br />

$5,000 per<br />

year<br />

$20,0000­<br />

1,000,000<br />

O&M Cost<br />

$100,000 per<br />

year<br />

$100,000­<br />

500,000<br />

O&M Cost<br />

$0<br />

Includes on­board<br />

equipment<br />

Depending on extent of<br />

integration, number of<br />

connections, and<br />

information made<br />

available<br />

Depending on extent of<br />

integration, assumes<br />

use of existing facility.<br />

Assumes that labor is<br />

already accounted for.<br />

Depending on extent of<br />

integration to existing<br />

emergency operations<br />

databases. O&M costs<br />

are already accounted<br />

for through existing<br />

511 Program.<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Provide ability to improve response<br />

time of emergency vehicles to<br />

incidents<br />

• Traveler information can be<br />

disseminated to public via radio or<br />

television<br />

• Potential for substantial savings of<br />

equipment costs by requiring less<br />

equipment<br />

• Recurring facility costs are reduced<br />

• Better coordination during emergency<br />

situations<br />

• Able to adjust 511 information<br />

dynamically to account for emergency<br />

situations<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• Improved emergency<br />

response<br />

• Easier access to<br />

traveler information<br />

• Overall quantity and<br />

quality of traveler<br />

information is improved<br />

• Improved emergency<br />

response<br />

• Enhanced traveler<br />

information services by<br />

including impacts of<br />

emergency situations<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

103 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Dynamic<br />

Route<br />

Guidance<br />

Automatic<br />

Vehicle<br />

Location<br />

(AVL)<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Emergency Management Systems<br />

• Communication<br />

s System<br />

Upgrades<br />

• Emergency<br />

Operations<br />

Center<br />

• New<br />

Emergency<br />

Vehicles<br />

• Communication<br />

s System<br />

Upgrades<br />

• Emergency<br />

Operations<br />

Center<br />

Integrated system of<br />

field equipment and<br />

information<br />

dissemination to<br />

provide alternate<br />

real­time<br />

information in<br />

response to traffic<br />

flow impacts<br />

AVL unit on<br />

vehicles, central<br />

equipment to<br />

identify location of<br />

vehicles for realtime<br />

arrival or<br />

location status<br />

• Is there an existing<br />

system to interface<br />

with?<br />

• What physical means<br />

of providing the<br />

information is<br />

desired?<br />

• Is there an existing<br />

system to support the<br />

collection and<br />

distribution of data?<br />

• Communications<br />

network available?<br />

$100,000­<br />

150,000<br />

O&M Cost<br />

$1,000­5,000<br />

per year<br />

$300,000 per<br />

system<br />

O&M Cost<br />

$20,000 per<br />

year<br />

Depending on extent of<br />

integration<br />

Will vary depending on<br />

the number of vehicles.<br />

Cost does not include<br />

a comprehensive<br />

communications<br />

infrastructure.<br />

• Enhanced use of traveler information<br />

by public<br />

• Provides an automated mechanism<br />

to track vehicles, on­time performance<br />

and data for schedule adjustments<br />

• Can process real­time monitoring data<br />

on status of transit vehicle elements<br />

for operations and maintenance<br />

• Provides efficient use of<br />

communications system (voice and<br />

data)<br />

• Enables greater degree of security for<br />

drivers/passengers with emergency<br />

alarms<br />

• Provides a mechanism for schedulebased<br />

transit priority<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• Dynamic traveler<br />

information that<br />

responds to current<br />

conditions<br />

• Provides an accurate<br />

means for real­time<br />

information<br />

• Improved security with<br />

emergency alarm<br />

capabilities<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

104 Final Report<br />

September 2005


ITS<br />

Solutions<br />

Weigh­inmotion<br />

Electronic<br />

Credentialing<br />

(with<br />

transponders<br />

or tags)<br />

Traveler<br />

Information<br />

Kiosks<br />

Commercial<br />

Vehicle<br />

Operations<br />

(CVO) –<br />

specific info<br />

for 511<br />

Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Commercial Vehicle Operations<br />

• Truck Scales<br />

• Truck Scales<br />

• Rest Areas<br />

• Truck<br />

information<br />

In­pavement<br />

equipment,<br />

transponder, invehicle<br />

equipment,<br />

central equipment to<br />

allow CV to be<br />

weighed in motion<br />

without stopping at<br />

the truck scales<br />

Transponder, invehicle<br />

equipment,<br />

central equipment<br />

for certifying<br />

permitting of CV<br />

Kiosk equipment,<br />

power,<br />

communications for<br />

displaying traveler<br />

information<br />

Software<br />

development and<br />

integration to<br />

interface with 511 to<br />

provide traveler<br />

information or route<br />

guidance<br />

information for CVO<br />

• Is there an existing<br />

system that will<br />

support the collection<br />

of this data?<br />

• Is there an existing<br />

system that will<br />

support the collection<br />

of this data?<br />

• What information will<br />

be displayed?<br />

• Where to draw<br />

power?<br />

• Americans with<br />

Disabilities Act (ADA)<br />

requirements<br />

• What is the extent of<br />

information<br />

disseminated?<br />

• Is there any<br />

integration into an<br />

existing system?<br />

$15,000­<br />

25,000<br />

O&M Cost<br />

$1,500­2,500<br />

per year<br />

$60,000­<br />

140,000<br />

O&M Cost<br />

$1,000­3,000<br />

per year<br />

$10,000­<br />

50,000 per<br />

kiosk<br />

O&M Cost<br />

$1,000 per<br />

kiosk per year<br />

$100,000­<br />

300,000<br />

O&M Cost<br />

$0<br />

Depending on distance<br />

from facility<br />

Costs do not include<br />

any integration into an<br />

existing system<br />

Depends on how much<br />

information is made<br />

available, interface<br />

development<br />

requirements.<br />

Depending on extent of<br />

integration. O&M<br />

costs are already<br />

accounted for.<br />

• Improved efficiency at truck scales<br />

• Improved efficiency at truck scales<br />

• Better integration with other facilities<br />

versus a stand­alone installation<br />

• Create a full service 511 system<br />

• Ability to impact and improve goods<br />

movement<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• For truck drivers,<br />

reduced delay at truck<br />

scales<br />

• For truck drivers,<br />

reduced delay at truck<br />

scales<br />

• Provides a mechanism<br />

for passengers to gain<br />

information and plan<br />

their trips accordingly<br />

• Give truck drivers the<br />

opportunity to change<br />

routes in response to an<br />

incident<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

105 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Commercial Vehicle Operations<br />

CCTV Camera • Truck Scales Includes pan­tiltzoom<br />

(PTZ) or fixed<br />

camera, enclosure,<br />

cabling,<br />

pole/mounting,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for<br />

surveillance<br />

• PTZ or fixed camera?<br />

• New or existing<br />

structure?<br />

• Is there an existing<br />

video system?<br />

• Leased line or<br />

agency­owned<br />

communications?<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

communications<br />

infrastructure?<br />

• Structure needs to<br />

support a camera<br />

• Where to draw power<br />

for the camera and<br />

any associated<br />

electronics?<br />

$8,000­<br />

40,000 each<br />

O&M Cost<br />

$2,000­3,000<br />

per camera<br />

per year<br />

Cost depends on<br />

installation on existing<br />

or new structure and<br />

other design<br />

considerations, and<br />

includes equipment<br />

and installation. Does<br />

not include<br />

communications and<br />

power installation.<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Camera provides faster identification<br />

and response to incidents<br />

• Improve performance of traffic signal<br />

system by monitoring conditions<br />

remotely<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Improved staff efficiency when<br />

troubleshooting or verifying field<br />

issues<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

from proactive use of<br />

cameras<br />

• Improved information<br />

for travel planning using<br />

real­time images<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

106 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Bicycle<br />

Surveillance<br />

(Closed<br />

Circuit<br />

Television<br />

cameras)<br />

Bicycle<br />

Parking<br />

(lockers,<br />

storage)<br />

Bicycle<br />

Detection<br />

• Bicycle<br />

storage<br />

• Bicycle<br />

storage<br />

• Bicycle Lanes<br />

• At­Grade Trail<br />

Crossings<br />

Includes pan­tiltzoom<br />

(PTZ) or fixed<br />

camera, enclosure,<br />

cabling,<br />

pole/mounting,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for vehicle<br />

surveillance<br />

Advanced<br />

technology to<br />

increase security of<br />

bicycle parking<br />

Detection device,<br />

cabling to signal<br />

cabinet, power to<br />

detect bicycles at<br />

intersections<br />

• PTZ or fixed camera?<br />

• New or existing<br />

structure?<br />

• Is there an existing<br />

video system?<br />

• Leased line or agencyowned<br />

communications?<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

communications<br />

infrastructure?<br />

• Structure needs to<br />

support a camera<br />

• Where to draw power<br />

for the camera and<br />

any associated<br />

electronics?<br />

• What technology is<br />

desired?<br />

• Detection technology<br />

(in­pavement vs.<br />

non­intrusive).<br />

$8,000­40,000<br />

each<br />

O&M Cost<br />

$2,000­3,000<br />

per camera<br />

per year<br />

$10,000­50,000<br />

per site<br />

O&M Cost<br />

$1,000­5,000<br />

per location<br />

$3,000­10,000<br />

per location<br />

O&M Cost<br />

$1,000 per<br />

location<br />

Cost depends on<br />

installation on existing<br />

or new structure and<br />

other design<br />

considerations, and<br />

includes equipment<br />

and installation. Does<br />

not include<br />

communications and<br />

power installation.<br />

Depending on<br />

technology and extent<br />

of deployment<br />

Depends on<br />

technology and<br />

installation/ mounting<br />

requirements<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Camera provides faster identification<br />

and response to incidents<br />

• Improve performance of traffic signal<br />

system by monitoring conditions<br />

remotely<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Improved staff efficiency when<br />

troubleshooting or verifying field<br />

issues<br />

• Promotes bicycling<br />

• Improves safety of leaving bicycles in<br />

a secured location<br />

• Encourages a greater use of bicycles<br />

• If added to another project, disruption<br />

to traffic is minimized<br />

• Reliable source of traffic data<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

from proactive use of<br />

cameras<br />

• Improved information<br />

for travel planning using<br />

real­time images<br />

• Greater feeling of safety<br />

when parking bicycles<br />

• Convenience<br />

• Cost effective<br />

• Real­time traffic flow<br />

data could be available<br />

• No privacy issues<br />

compared with other<br />

technologies<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

107 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Bicycle<br />

Signal<br />

Retiming<br />

Automated<br />

Enforcement<br />

• Bicycle Lane<br />

• At­Grade Trail<br />

Crossing<br />

• Bicycle Lane<br />

• At­Grade Trail<br />

Crossing<br />

Signal timing will<br />

need to be modified<br />

to accommodate the<br />

increase in bicyclist<br />

at the intersection or<br />

crossing<br />

Install red­light<br />

running cameras,<br />

speed sensors,<br />

emissions<br />

monitoring or noise<br />

equipment to<br />

automatically<br />

enforce violations<br />

• Should utilize bicycle<br />

detection<br />

• Need to provide more<br />

green time for<br />

bicyclists<br />

• What locations are<br />

the bets candidates?<br />

• Will this be a leased<br />

service or agency<br />

owned and<br />

maintained?<br />

• Need to define<br />

processing format.<br />

$8,000 Includes retiming using<br />

an analytical or<br />

simulation tool, and<br />

detection on two<br />

approaches for<br />

bicycles<br />

$20,000 ­<br />

$40,000<br />

Annual<br />

leasing costs<br />

vary<br />

depending on<br />

service<br />

Depends on<br />

installation and<br />

equipment at each<br />

location<br />

• Minimize disruption to traffic if bicycle<br />

detection is installed in conjunction<br />

with another project.<br />

• Minimize disruption to traffic if bicycle<br />

detection is installed in conjunction<br />

with another project.<br />

• Improved safety for<br />

bicycles<br />

• Improved safety for<br />

bicycles<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

108 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Pedestrian<br />

Pedestrian<br />

Detection<br />

New Signal or<br />

Existing Signal<br />

Modification<br />

including<br />

Pedestrian<br />

Signal Heads<br />

In­Pavement<br />

Lighting<br />

Traveler<br />

Information<br />

Kiosk<br />

• Pedestrian<br />

Crossing<br />

• Pedestrian<br />

Crossing<br />

• Pedestrian<br />

Crossing<br />

• Pedestrian<br />

Mall<br />

• Livable<br />

Communities<br />

Detection device,<br />

cabling to signal<br />

cabinet, power to<br />

detect pedestrians<br />

at intersections<br />

Traffic signal<br />

equipment, civil<br />

modifications (ADA<br />

ramps, curb/gutter<br />

to allow for<br />

treatment of<br />

pedestrians and<br />

bicycles)<br />

To enhance the<br />

driver’s ability to<br />

see pedestrians or<br />

bicycles crossing a<br />

roadway<br />

Kiosk equipment,<br />

power,<br />

communications for<br />

displaying traveler<br />

information<br />

• Is a signal<br />

warranted?<br />

• Is or will a developer<br />

be required to<br />

pay/construct?<br />

• What is the condition<br />

of the pavement to<br />

support these<br />

devices?<br />

• What information will<br />

be displayed?<br />

• Detection technology<br />

(in­pavement vs. nonintrusive).<br />

$3,000­10,000<br />

per location<br />

O&M Cost<br />

$1,000 per<br />

location<br />

$50,000­<br />

200,000<br />

O&M Cost<br />

$2,000­4,000<br />

per intersection;<br />

$500 for existing<br />

signals<br />

$25,000­45,000<br />

O&M Cost<br />

$3,000­5,000<br />

per year<br />

$10,000­50,000<br />

per kiosk<br />

O&M Cost<br />

$1,000 per<br />

kiosk per year<br />

Depends on<br />

technology and<br />

installation/ mounting<br />

requirements<br />

Depends on extent of<br />

improvements<br />

Does not include new<br />

service. Does not<br />

include street<br />

improvements (striping<br />

or decorative crosswalk)<br />

Depends on how much<br />

information is made<br />

available, interface<br />

development<br />

requirements.<br />

• Improved coordination by only<br />

servicing pedestrians when present<br />

• Improve safety at intersections<br />

• Improved coordination by only<br />

servicing pedestrians when present<br />

• Improve safety at intersections<br />

• Improve safety at intersections<br />

• Better integration with other facilities<br />

versus a stand­alone installation<br />

• Information to<br />

pedestrians on safe<br />

crossing time<br />

• Raise awareness of<br />

pedestrians to drivers<br />

• Information to<br />

pedestrians on safe<br />

crossing time<br />

• Raise awareness of<br />

pedestrians to drivers<br />

• Improve safety at<br />

pedestrian crossings<br />

• Provides a mechanism<br />

for passengers to gain<br />

information and plan<br />

their trips accordingly<br />

Wireless<br />

Hotspot (only<br />

if signalized)<br />

• Pedestrian<br />

Crossing<br />

• Livable<br />

Communities<br />

Equipment in signal<br />

cabinet to allow city<br />

staff (field<br />

personnel) to<br />

access city network<br />

• Is there adequate<br />

space in the cabinet?<br />

• Is this a desirable<br />

solution?<br />

$1,000­2,000<br />

per<br />

installation<br />

O&M Cost<br />

$500 per year<br />

Does not include<br />

central equipment for<br />

integration<br />

• Cost effective method of providing<br />

communications<br />

• Can be either public (leased) or<br />

private (owned)<br />

• Opportunities for shared infrastructure<br />

with multiple agencies<br />

• Public/Private<br />

partnerships can result<br />

in added coverage for<br />

wireless access to the<br />

Internet<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

109 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Pedestrian<br />

Traffic Signal<br />

Interconnect<br />

Conduit<br />

Traffic Signal<br />

Interconnect<br />

Cable<br />

• Sidewalk<br />

• Sidewalk<br />

Minimum 3” conduit,<br />

pull boxes, splice<br />

vault at key locations<br />

for future<br />

interconnect cable to<br />

coordinate traffic<br />

signal timing<br />

Copper twisted pair<br />

cable, fiber optic<br />

cable, or wireless<br />

antennas;<br />

communications<br />

transmitter/receiver;<br />

termination panels to<br />

coordinate traffic<br />

signal timing<br />

• Adequate conduit<br />

sweeps if fiber is<br />

used<br />

• Other design<br />

elements may be<br />

different depending<br />

on medium.<br />

• Placement in<br />

roadway or behind<br />

curb?<br />

• Are multiple conduits<br />

needed?<br />

• Communications<br />

medium (copper,<br />

fiber, wireless,<br />

Ethernet… )<br />

• Tie to existing<br />

system?<br />

$65,000 per<br />

mile<br />

O&M Cost<br />

Minimal<br />

$9,000­<br />

20,000 per<br />

mile<br />

O&M Cost<br />

$500­1,000<br />

per mile per<br />

year<br />

Costs vary depending<br />

on number of conduit<br />

and frequency of pull<br />

boxes<br />

Depends on<br />

communications<br />

medium, does not<br />

include conduit (see<br />

above).<br />

Additional costs if<br />

leased lines are used<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with<br />

the ability to coordinate traffic signals<br />

to improve traffic flow along a corridor<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings could<br />

lead to additional transportation<br />

projects<br />

• Little to no recurring costs<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with<br />

the ability to coordinate traffic signals<br />

to improve traffic flow along a corridor<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings could<br />

lead to additional transportation<br />

projects<br />

• Little to no recurring costs<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

along a corridor<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

along corridor<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

110 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Ports<br />

Automatic<br />

Vehicle<br />

Location<br />

(AVL)<br />

Dynamic<br />

Route<br />

Guidance<br />

• Port Access<br />

and<br />

Circulation<br />

Projects<br />

• Port Access<br />

and<br />

Circulation<br />

Projects<br />

AVL unit on vehicles,<br />

central<br />

equipment to<br />

identify location of<br />

vehicles for realtime<br />

arrival or<br />

location status<br />

Integrated system of<br />

field equipment and<br />

information<br />

dissemination to<br />

provide alternate<br />

real­time information<br />

in response to traffic<br />

flow impacts<br />

• Is there an existing<br />

system to support the<br />

collection and<br />

distribution of data?<br />

• Is the necessary<br />

equipment available<br />

to support analyzing<br />

alternate routes?<br />

$300,000 per<br />

system<br />

O&M Cost<br />

$20,000 per<br />

year<br />

$100,000­<br />

150,000<br />

O&M Cost<br />

$1,000­5,000<br />

per year<br />

Will vary depending on<br />

the number of<br />

vehicles. Cost does<br />

not include a<br />

comprehensive<br />

communications<br />

infrastructure.<br />

Depending on extent<br />

of integration<br />

• Provides an automated mechanism<br />

to track vehicles, on­time performance<br />

and data for schedule adjustments<br />

• Can process real­time monitoring data<br />

on status of transit vehicle elements<br />

for operations and maintenance<br />

• Provides efficient use of<br />

communications system (voice and<br />

data)<br />

• Enables greater degree of security for<br />

drivers/passengers with emergency<br />

alarms<br />

• Provides a mechanism for schedulebased<br />

transit priority<br />

• Enhanced use of traveler information<br />

by public<br />

• Provides an accurate<br />

means for real­time<br />

information<br />

• Improved security with<br />

emergency alarm<br />

capabilities<br />

• Dynamic traveler<br />

information that<br />

responds to current<br />

conditions<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

111 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Other<br />

Parking<br />

reservation<br />

systems<br />

Ridesharing<br />

software/<br />

website (see<br />

sacregion511.org)<br />

• Parking<br />

Facility or<br />

structure<br />

• Rideshare or<br />

Carpool<br />

program<br />

Allow drivers to<br />

reserve a parking<br />

space at a specific<br />

location<br />

System designed to<br />

coordinate<br />

ridesharing<br />

opportunities<br />

•Is there an existing<br />

parking management<br />

or guidance system to<br />

integrate with?<br />

• What is the extent of<br />

services and routes<br />

being offered?<br />

$15,000­<br />

100,000<br />

O&M Cost<br />

$5,000­<br />

10,000 per<br />

year<br />

$100,000­<br />

200,000<br />

O&M Cost<br />

$5,000­<br />

10,000 per<br />

year<br />

Costs could vary<br />

significantly depending<br />

on level of integration<br />

and number of parking<br />

facilities participating<br />

Major software<br />

development is not<br />

included<br />

• Potential to raise revenue by utilizing<br />

more parking spaces<br />

• Provide more efficiency for finding<br />

parking<br />

• Provides for additional service to 511.<br />

• Reduce the amount of<br />

time driving around<br />

looking for parking<br />

• Ability to coordinate<br />

rides to reduce the<br />

number of vehicles on<br />

the road<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

112 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Freeway<br />

Transponders/<br />

Transponder<br />

Readers<br />

CCTV<br />

Cameras<br />

• High<br />

Occupancy<br />

Vehicle<br />

(HOV) Lanes<br />

• Freeway<br />

Construction<br />

• High Occupancy<br />

Vehicle (HOV)<br />

Lanes<br />

• Freeway<br />

Widening<br />

• Interchange<br />

Reconfiguration<br />

• Auxiliary Lanes<br />

• Grade<br />

Separation<br />

(Bridge<br />

Structure)<br />

In­vehicle<br />

equipment,<br />

transponder, central<br />

equipment to allow<br />

HOV lanes to<br />

assess a toll for<br />

SOV that desire to<br />

use the HOV lane<br />

Includes pan­tiltzoom<br />

(PTZ) or fixed<br />

camera, enclosure,<br />

cabling,<br />

pole/mounting,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for vehicle<br />

surveillance<br />

• What is the location<br />

and frequency of<br />

devices along the<br />

roadway?<br />

• How is the information<br />

being transmitted to a<br />

central facility?<br />

• How is information<br />

processed?<br />

• PTZ or fixed camera?<br />

• New or existing<br />

structure?<br />

• Is there an existing<br />

video system?<br />

• Leased line or agencyowned<br />

communications?<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

communications<br />

infrastructure?<br />

• Structure needs to<br />

support a camera<br />

• Where to draw power?<br />

$2,000­5,000<br />

per site<br />

O&M Cost<br />

$500­1,000<br />

per year<br />

$8,000­40,000<br />

each<br />

O&M Cost<br />

$2,000­3,000<br />

per camera<br />

per year<br />

Does not include<br />

communications to the<br />

devices or processing<br />

of information.<br />

Cost depends on<br />

installation on existing<br />

or new structure and<br />

other design<br />

considerations, and<br />

includes equipment<br />

and installation. Does<br />

not include<br />

communications and<br />

power installation.<br />

• For use with high occupancy toll<br />

lanes, agencies have the ability to<br />

collect revenue<br />

• Can be used for travel time<br />

information<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• Camera provides faster identification<br />

and response to incidents<br />

• Improve performance of traffic signal<br />

system by monitoring conditions<br />

remotely<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Improved staff efficiency when<br />

troubleshooting or verifying field<br />

issues<br />

• Makes the HOV lane<br />

available for single<br />

occupants<br />

• When used for travel<br />

times, this provides<br />

another source of data<br />

collection<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

from proactive use of<br />

cameras<br />

• Improved information<br />

for travel planning using<br />

real­time images<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

113 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Freeway<br />

Changeable<br />

Message<br />

Signs<br />

Ramp Meters<br />

Vehicle<br />

Detection<br />

• Freeway<br />

Construction<br />

• Freeway<br />

Widening<br />

• Auxiliary<br />

Lanes<br />

• Interchange<br />

Reconfiguration<br />

• Freeway<br />

Construction<br />

• High Occupancy<br />

Vehicle (HOV)<br />

Lanes<br />

• Freeway<br />

Widening<br />

• Interchange<br />

Reconfiguration<br />

• Auxiliary Lanes<br />

Sign, structure,<br />

foundation, power,<br />

communications,<br />

communications<br />

device for<br />

displaying traveler<br />

information<br />

Signal heads, pole,<br />

vehicle detection,<br />

conduit, pull boxes,<br />

striping, signing,<br />

control cabinet,<br />

power,<br />

communications to<br />

allow vehicles to be<br />

metered as they<br />

enter the freeway<br />

Detection device,<br />

cabling to signal<br />

cabinet, power to<br />

measure traffic<br />

volume and flow<br />

along corridors<br />

• Sign technology.<br />

• Communications<br />

medium.<br />

• Is there an existing<br />

central system or will<br />

this be stand­alone?<br />

• Where to draw<br />

power?<br />

• Is a ramp meter<br />

warranted?<br />

• Does the existing ramp<br />

geometry need to be<br />

modified to support the<br />

warranted ramp<br />

configuration?<br />

• Is there an existing<br />

system to support the<br />

addition?<br />

• Detection technology<br />

(in­pavement vs. nonintrusive).<br />

$75,000­<br />

250,000 each<br />

O&M Cost<br />

$3,000­6,000<br />

per sign per<br />

year<br />

$30,000­<br />

50,000<br />

O&M Cost<br />

$2,000­4,000<br />

per ramp per<br />

year<br />

$3,000­20,000<br />

per location<br />

O&M Cost<br />

$1,000­2,000<br />

per location<br />

per year<br />

Depends on<br />

technology, size of<br />

sign, type of structure.<br />

Does not include<br />

communications and<br />

power installation.<br />

Depends on length of<br />

ramp, location of<br />

cabinet, lane<br />

configuration; does not<br />

include geometric<br />

improvements or<br />

communications<br />

Depends on<br />

technology and<br />

installation/ mounting<br />

requirements<br />

• Cost savings in construction (traffic<br />

control, mobilization)<br />

• With CMS, have ability to disseminate<br />

traffic condition information<br />

• Cost savings could lead to additional<br />

transportation projects<br />

• Significant cost savings when<br />

constructed with interchange<br />

modifications<br />

• Mechanism for reducing traffic<br />

congestion freeways<br />

• If added to another project, disruption<br />

to traffic is minimized<br />

• Reliable source of traffic data<br />

• Minimize disruption to<br />

traffic<br />

• Travel information<br />

made available to<br />

public<br />

• Improved traffic flow on<br />

the freeway<br />

• Reduces merge area<br />

accidents<br />

• Real­time traffic flow<br />

data could be available<br />

• No privacy issues<br />

compared with other<br />

technologies<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

114 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Communications<br />

Conduit<br />

Communications<br />

Cable<br />

Project<br />

Types<br />

• Freeway<br />

Construction<br />

• High Occupancy<br />

Vehicle (HOV)<br />

Lanes<br />

• Freeway<br />

Widening<br />

• Interchange<br />

Reconfiguration<br />

• Auxiliary Lanes<br />

• Grade<br />

Separation<br />

• Freeway<br />

Construction<br />

• High Occupancy<br />

Vehicle (HOV)<br />

Lanes<br />

• Freeway<br />

Widening<br />

• Interchange<br />

Reconfiguration<br />

• Auxiliary Lanes<br />

• Grade<br />

Separation<br />

Solution<br />

Descriptions<br />

Minimum 2­3”<br />

conduit, pull boxes,<br />

splice vault (for fiber)<br />

for future<br />

communications<br />

between field devices<br />

and the central facility<br />

Copper twisted wire<br />

cable, fiber optic<br />

cable, or wireless<br />

communications<br />

between field<br />

devices and the<br />

central facility<br />

<strong>Deployment</strong><br />

Considerations<br />

• How many conduits<br />

are needed?<br />

• Communications<br />

medium that will be<br />

considered (copper,<br />

fiber, wireless)<br />

• Adequate conduit<br />

sweeps if fiber is used<br />

• Other design elements<br />

may be different<br />

depending on medium.<br />

• Placement in roadway<br />

or behind curb?<br />

• Communications<br />

medium (copper,<br />

fiber, wireless,<br />

Ethernet… )<br />

• Tie to existing<br />

system?<br />

Cost<br />

Cost<br />

Considerations<br />

Freeway<br />

$65,000 per<br />

mile<br />

O&M Cost<br />

Minimal<br />

$9,000­20,000<br />

per mile<br />

O&M Cost<br />

$500­1,000<br />

per mile per<br />

year<br />

Costs vary depending<br />

on number of conduit<br />

and frequency of pull<br />

boxes<br />

Depends on<br />

communications<br />

medium, does not<br />

include conduit (see<br />

above). Additional<br />

O&M costs if leased<br />

lines are used<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings<br />

could lead to additional transportation<br />

projects<br />

• Little to no recurring costs<br />

• Major cost savings in construction<br />

(traffic control, mobilization,<br />

installation) – costs are substantial if<br />

done separately<br />

• Provides private infrastructure with the<br />

ability to coordinate traffic signals to<br />

improve traffic flow along a corridor<br />

• Provides a private infrastructure for<br />

communications to other equipment<br />

• Cost effective when combined with<br />

other larger projects and savings could<br />

lead to additional transportation projects<br />

• Little to no recurring costs<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

along a corridor<br />

• Minimize disruption to<br />

traffic<br />

• Improved traffic flow<br />

along corridor<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

115 Final Report<br />

September 2005


Sacramento Area Council of Governments (SACOG)<br />

SOLUTIONS TOOLBOX FOR MAINSTREAMING ITS<br />

ITS<br />

Solutions<br />

Project<br />

Types<br />

Solution<br />

Descriptions<br />

<strong>Deployment</strong><br />

Considerations<br />

Cost<br />

Cost<br />

Considerations<br />

Benefits to Project or<br />

Agency<br />

(of Concurrent<br />

ITS <strong>Deployment</strong>)<br />

Benefits to Public<br />

(of ITS<br />

<strong>Deployment</strong>)<br />

Freeway<br />

Highway<br />

Advisory<br />

Radio<br />

Roadway<br />

Weather<br />

Information<br />

System<br />

Portable<br />

Traffic<br />

Management<br />

Devices<br />

Curve<br />

Warning<br />

Systems<br />

• Freeway<br />

Construction<br />

• Freeway<br />

Widening<br />

• Freeway<br />

Construction<br />

• Freeway<br />

Construction<br />

• High<br />

Occupancy<br />

Vehicle<br />

(HOV) Lanes<br />

• Freeway<br />

Widening<br />

• Freeway<br />

Construction<br />

• Interchange<br />

Reconfiguration<br />

Antenna, pole,<br />

power, broadcast<br />

equipment for<br />

broadcasting<br />

traveler advisories<br />

In­pavement<br />

equipment, control<br />

cabinet, power,<br />

communications<br />

cabling and<br />

equipment<br />

• Need to do a<br />

frequency evaluation.<br />

• Consider the area of<br />

coverage.<br />

• How will the<br />

information be<br />

stored?<br />

• Where to draw<br />

power?<br />

Portable CCTV, • How will devices<br />

changeable message communicate?<br />

signs traffic signal or • Not the preferred<br />

other equipment solution for long term<br />

powered by a use in a single<br />

generator, utilizing location.<br />

wireless<br />

communications to be<br />

used primarily during<br />

construction or<br />

special events<br />

In­vehicle equipment,<br />

field equipment to<br />

notify a driver of an<br />

upcoming dangerous<br />

curve<br />

• How is power being<br />

provided?<br />

• What are the criteria<br />

for deploying at a<br />

particular location?<br />

$25,000­<br />

50,000 per<br />

location<br />

O&M Cost<br />

$1,500­2,000<br />

per location<br />

$25,000 per<br />

site<br />

O&M Cost<br />

$500­3,000<br />

per year<br />

$1,000­<br />

25,000<br />

O&M Cost<br />

$1,000 per<br />

year<br />

$1,000­5,000<br />

O&M Cost<br />

$0­500 per<br />

year<br />

Depends primarily on<br />

signal strength. Does<br />

not include<br />

communications and<br />

power installation.<br />

Does not include<br />

communications to the<br />

site. Does not include<br />

integration into an<br />

existing system for<br />

dissemination.<br />

Depending on<br />

equipment. Does not<br />

include<br />

communications.<br />

Includes complete<br />

installation for one<br />

location.<br />

• Resource for disseminating traveler<br />

information<br />

• Can easily broadcast traffic advisories<br />

• Low construction and maintenance<br />

costs<br />

• Improved efficiency in detecting<br />

potentially dangerous roadway<br />

conditions<br />

• Offer the ability to disseminate realtime<br />

roadway conditions<br />

• Cost effective way to disseminate<br />

traveler information, especially during<br />

construction activities or special<br />

events<br />

• Cost efficient to install during roadway<br />

construction<br />

• Improve safety of roadway<br />

• Real­time traveler<br />

information made<br />

available to public<br />

• Can receive localized<br />

travel information with a<br />

standard radio<br />

• Access to real­time<br />

roadway conditions<br />

• Receive traveler<br />

information during<br />

construction or special<br />

events<br />

• Provides advanced<br />

warning for drivers<br />

approaching dangerous<br />

curves<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

116 Final Report<br />

September 2005


7 DEPLOYMENT<br />

7.1 Project Prioritization<br />

To achieve the vision of the ITS Partnership and the systems defined by the Regional ITS<br />

Architecture, the stakeholders in the region must deploy projects that provide the functionality and<br />

interoperability identified in the architecture and meet the objectives of the vision. A key step<br />

toward that vision is to define a deployment strategy that identifies specific projects, timeframes,<br />

and responsible agencies, in particular, to help implement the Preferred Blueprint Scenario.<br />

Input from all stakeholders is required in order for the stakeholders to have ownership in the<br />

deployment strategy and also to be sure that the plan has realistically identified projects and<br />

timeframes for the region. Cost is another important factor. Cost can vary a great deal for many<br />

ITS elements, depending on the level of deployment, maturity of the technology, type of<br />

communications, etc.<br />

The Sacramento ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> includes project prioritization of existing projects<br />

identified in the MTP and refined by the stakeholders. In many ways, all of these projects can help<br />

to implement the goals of the Preferred Blueprint Scenario. This list of projects represents the<br />

recommended order of deployment of ITS central systems, projects, or infrastructure based on<br />

stakeholder preference according to the following categories:<br />

• Short­Term Projects (meaning it was currently deployed or planned for deployment in the<br />

next 5 years);<br />

• Mid­Term Projects (meaning it would be considered for deployment in the 5­10 year<br />

timeframe);<br />

• Long­Term Projects (meaning it would be<br />

ITS Vision Goals<br />

considered for deployment in the 10­20 year<br />

timeframe); and<br />

1. Quality of Life<br />

• Not planned for deployment at this time.<br />

2. Access and Mobility<br />

The market package priorities during the architecture<br />

stage assisted in determining interdependencies and<br />

connections. The project shown in the following<br />

tables are presented in more detail in Appendix F.<br />

The final column of each table, labeled “ITS<br />

VISION”, relates each of the projects to one or more<br />

of the Sacramento Region’s ITS Vision goals<br />

described in Section 2 of this report and included in<br />

Appendix B as a standalone document. The numbers<br />

refer to the Vision goals shown to the right.<br />

3. Air Quality<br />

4. Travel Choices<br />

5. Economic Vitality<br />

6. Equity<br />

7. Transportation and Land Use<br />

8. Funding and Revenue<br />

9. Health and Safety<br />

10. Environmental Sustainability<br />

The short­term projects identified in Table 7.1 provide an indication of projects recommended in<br />

the 0­ to 5­year timeframe. These projects represent the highest priority according to the<br />

stakeholders and should be strongly considered for implementation in the short­term. Table 7.2<br />

reflects mid­term projects that fall into the 5­ to 10­year timeframe. These projects are important to<br />

the stakeholders, but will need further review at the time of their deployment to ensure they are still<br />

a priority for the Region. The long­term projects in Table 7.3 fall into the 10­ to 20­year<br />

timeframe. While these projects represent the current needs for the region, it is possible that these<br />

needs will change. As the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is updated in the future, the stakeholders will<br />

have the opportunity to reassess and reprioritize these projects to maintain overall objectives.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

117 Final Report<br />

September 2005


Priority<br />

Level<br />

Table 7.1: Project Sequencing ­ Short Term Projects (0­5 years)<br />

Location<br />

Description<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

H Caltrans District 3 Signal installation at U.S. 50 eastbound $250,000 2006 2<br />

ramps<br />

per signal<br />

M Caltrans District 3 Install ramp metering, traffic monitoring $5,600,000 2005 2• 3<br />

stations, Closed Circuit TV installation,<br />

message signs, and upgrade count stations<br />

to Traffic Management System on I­80 from<br />

Yolo Co. line to Route 244 (Longview Dr.).<br />

M Caltrans District 3 Install ramp meters, HOV Bypasses, $6,000,000 2005 2• 3<br />

additional on ramps, traffic monitoring<br />

stations and Closed Circuit TV installation<br />

on I­5 from Pocket Rd. to I­80.<br />

M Caltrans District 3 Yolo County portion of I­5 traffic operations $120,000 2005 2• 3<br />

system and ramp metering.<br />

M Caltrans District 3 Construct Traffic Operation System (US 50 $5,000,000 2006 2• 3<br />

from Scott Road to Cameron Park)<br />

M Caltrans District 3 Construct Traffic Operation System (Jct. 50 $3,000,000 2006 2• 3<br />

to I­5)<br />

M Caltrans District 3 Yolo County portion of U.S. 50 traffic $4,800,000 2006 2• 3<br />

operations system and ramp metering at<br />

various locations.<br />

M Caltrans District 3 Ramp metering at all interchanges from $4,200,000 2006 2• 3<br />

Foresthill Road to the Sacramento County<br />

Line.<br />

H Citrus Heights Traffic Monitoring Phase I ­ Deploy traffic TBD TBD 2• 3<br />

monitoring devices (e.g. flow detectors,<br />

CCTV cameras) along segments of US 50 in<br />

South Shore area, and along Highways 28,<br />

89 and 267 in the North Shore<br />

M Citrus Heights Upgrade the traffic signal controllers. TBD TBD 2• 3<br />

M Citrus Heights Downtown/Natomas/Airport (DNA) ­ new TBD TBD 1• 4<br />

transit options between downtown<br />

Sacramento and South and North Natomas<br />

and the Sacramento International Airport<br />

M Citrus Heights Extend the existing signal interconnect<br />

TBD TBD 2• 3<br />

system along Greenback Road<br />

H EDCTC US 50 Signal Timing through Placerville $50,000 2007 2• 3<br />

M EDCTC US 50 Ramp Meters from El Dorado Hills<br />

Blvd to El Dorado Road (8 interchanges)<br />

H Elk Grove Install ATMS, inaugurate the Elk Grove<br />

Transportation Management Center,<br />

integrate TMC with signal system, deploy<br />

Ethernet based signal comm., demonstrate<br />

CCTV<br />

H Elk Grove Install fiber optic backbone links to support<br />

TMC and STARNET operations<br />

$900,000 2006 2• 3<br />

$2,700,000 2005­<br />

2006<br />

$2,200,000 2006­<br />

2007<br />

2• 3• 4• 5<br />

2• 3• 4• 5<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

118 Final Report<br />

September 2005


Priority<br />

Level<br />

Table 7.1: Project Sequencing ­ Short Term Projects (0­5 years)<br />

Location<br />

Description<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

H Elk Grove Coordinate signal operations across<br />

$0 Ongoing 2• 3• 4• 5<br />

boundaries with Sacramento County and<br />

Caltrans<br />

H Elk Grove Deploy traffic surveillance cameras at<br />

selected locations<br />

$250,000 2006 1• 2• 3• 4<br />

• 5<br />

M Elk Grove GPS­ATMS integration with fire, police, and<br />

transit<br />

$1,000,000 2008 1• 2• 3• 4<br />

• 5<br />

M Elk Grove Upgrade remaining on­street signal control $500,000 2008 2• 3• 4• 6<br />

system and comm. equipment<br />

M Folsom Construct ITS infrastructure within the City $2,000,000 2007 2• 3<br />

H Roseville Construct Traffic Management Center $500,000 2010 2• 3<br />

(TMC)<br />

H Roseville Upgrade traffic signal system $1,500,000 2006 2• 3<br />

H Roseville Enhance emergency vehicle preemption $400,000 2006 9<br />

system<br />

H Roseville Deploy CCTV cameras along major arterials $350,000 2007 2• 3• 9<br />

M Roseville Integrate communications between<br />

Roseville Police and Fire, Emergency<br />

Operations Center, Dispatch, and Roseville<br />

Transit<br />

M Roseville Integrate ramp meter operations with traffic<br />

signal operations<br />

H Sacramento Connect traffic signals, including ITS<br />

technology, that are located outside of the<br />

Central City to the City’s existing Traffic<br />

Operations Center.<br />

M Sacramento Install Smart Traffic Calming in south<br />

Midtown area<br />

H SACOG STARNET Various traffic and transit<br />

operation centers in the region; hardware<br />

and software upgrades enabling a wide­area<br />

network to share transportation data and<br />

operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

M SACOG Expand Traveler Information Management<br />

(includes DMS, kiosks, web pages, HAR,<br />

H<br />

M<br />

Sacramento<br />

County<br />

Sacramento<br />

County<br />

media, NOAA Weather radio)<br />

Hazel Avenue Corridor – Highway 50 to<br />

Placer County Line – Traffic signal<br />

coordination, transit priority, monitoring<br />

equipment and traveler information on a<br />

major arterial corridor, plus supporting<br />

communications.<br />

Bus Rapid Transit in Sacramento County,<br />

implement bus rapid transit on the Sunrise<br />

Boulevard corridor.<br />

$350,000 2007 9<br />

$300,000 2010 2• 3<br />

$8,500,000 2006 2• 3<br />

$250,000 2006 2• 3• 4<br />

$3,000,000 2007 2• 3<br />

TBD TBD 2• 3• 4<br />

$3,000,000 2006 2• 3• 4<br />

$20,000,00<br />

0<br />

2009 4• 5• 6<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

119 Final Report<br />

September 2005


Priority<br />

Level<br />

M<br />

H<br />

H<br />

M<br />

H<br />

H<br />

H<br />

M<br />

M<br />

Table 7.1: Project Sequencing ­ Short Term Projects (0­5 years)<br />

Location<br />

Sacramento<br />

County<br />

Sacramento<br />

Regional Transit<br />

Sacramento<br />

Regional Transit<br />

Sacramento<br />

Regional Transit<br />

City of West<br />

Sacramento<br />

City of West<br />

Sacramento<br />

City of West<br />

Sacramento<br />

City of West<br />

Sacramento<br />

City of West<br />

Sacramento<br />

Description<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

Watt Corridor ­ Phase 2 and 3. Traffic signal<br />

coordination, transit priority, monitoring<br />

equipment and traveler information on a<br />

major arterial corridor, plus supporting<br />

communications.<br />

$2,800,000 2007 2• 3• 4<br />

Deploy video surveillance at transit stations $100,000 2008 2• 3<br />

(currently underway)<br />

per station<br />

Deploy video surveillance on­board vehicles $25,000 2005 2• 3<br />

per vehicle<br />

Purchase computerized train tracking<br />

system that will provide automatic train<br />

locations and a public address system to<br />

advise customers of train approaches and<br />

service delays.<br />

Implement Traffic Management System<br />

Upgrade traffic signal controllers and<br />

communication on Jefferson Blvd and<br />

Harbor Blvd<br />

Establish wireless communication from the<br />

TOC to Jefferson Blvd and Harbor Blvd<br />

Implement Traffic Operations Center<br />

Deploy CCTV cameras on Jefferson Blvd,<br />

West Capitol Avenue, Reed Avenue,<br />

Sacramento Avenue, Industrial Blvd, and<br />

Harbor Blvd<br />

Install pedestrian countdown timers at<br />

critical intersections<br />

M City of West<br />

Sacramento<br />

L City of West<br />

Sacramento<br />

Deploy Highway Advisory Radio<br />

M Yolo County Implement ITS, Phase I, joint project of Yolo<br />

County Transportation District, Unitrans, and<br />

Davis Community Transit.<br />

$3,000,000 2006 4• 5• 6<br />

$1,000,000 2006 2• 3<br />

$200,000 2006 2• 3<br />

$100,000 2006 2• 3<br />

$500,000 2007 2• 3<br />

$600,000 2007 2• 3• 9<br />

$75,000 2007 4• 9<br />

$40,000 2008 6• 10<br />

$500,000 2006 2• 3<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

120 Final Report<br />

September 2005


Priority<br />

Level<br />

Table 7.2: Project Sequencing ­ Medium Term Projects (5­10 years)<br />

Location<br />

Description<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

L Amtrak Expansion of Capitol Corridor Train Service TBD 2012 1• 2• 4• 5<br />

H Caltrans District 3 Traffic Monitoring Phase I ­ Deploy traffic TBD TBD 2• 3• 4<br />

monitoring devices (e.g. flow detectors,<br />

CCTV cameras) along segments of US 50<br />

in South Shore area, and along Highways<br />

28, 89 and 267 in the North Shore<br />

M Caltrans District 3 Portable Traffic Management Devices<br />

TBD TBD 2• 3• 4<br />

(customized for portability including DMS,<br />

HAR, CCTV/web cameras, temporary<br />

signals, incident command center, and<br />

communications to RTMC)<br />

M Caltrans District 3 Upgrade Caltrans District 3 Regional TMC TBD TBD 2• 3• 4<br />

to manage US­50, I­80 and other ITS<br />

deployments (includes coordination with<br />

Nevada, Tahoe Gateway, and Tahoe Basin<br />

to ensure consistency)<br />

M Caltrans District 3 Completion of Valleywide GIS Mapping $1,500,000 2011 2• 4• 7<br />

L Caltrans District 3 Truck Stop Information Demo $500,000 2008 5<br />

L Caltrans District 3 Alternate Route <strong>Plan</strong>s Database/Website ­ $200,000 2008 4• 5• 6<br />

access to the plans via the Internet<br />

L Caltrans District 3 Six Ramp meters on SR65 between Lincoln $250,000 TBD 2• 3<br />

and I­80<br />

L Caltrans District 3 US 50 Surveillance (including 4 CCTV or $400,000 2012 2• 3• 4<br />

web cameras and 6 traffic monitoring<br />

stations)<br />

L Caltrans District 3 Weather/ATMS Integration and Automation $1,500,000 2011 2• 3• 4<br />

L Caltrans District 3 Dynamic Alternate Route signing system ­ $600,000 2011 2• 3• 4<br />

implement dynamic variable message signs<br />

(VMS) specifically sited, and primarily<br />

devoted, to detouring traffic onto alternate<br />

routes during incidents, including accidents<br />

and weather related road closures.<br />

H Elk Grove Signals ­ Upgrade City’s existing onstreet $1,500,000 2007 2• 3• 4<br />

system. Replace controllers/cabinets as<br />

needed and add system detectors on all<br />

segments<br />

L Elk Grove Provide advanced traveler information $300,000 2011 2• 3• 4• 6<br />

(ATIS) system and disseminate concise,<br />

useful road and traffic condition reports to<br />

drivers.<br />

L Rancho Cordova A Rancho Cordova to South Placer multimodal<br />

$400,000,0 2010 2• 3• 4• 6<br />

connector<br />

00<br />

H Roseville Traffic monitoring stations near the<br />

$25,000 2009 2• 3• 4<br />

Sacramento/Placer County line in Roseville<br />

M Roseville Upgrade communications network TBD TBD 2• 3<br />

L Roseville Provide transit information at Roseville bus<br />

stops.<br />

$700,000 2010 4<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

121 Final Report<br />

September 2005


Priority<br />

Level<br />

Table 7.2: Project Sequencing ­ Medium Term Projects (5­10 years)<br />

Location<br />

Description<br />

H Roseville Roseville Transit ­ Fixed Route and<br />

Paratransit<br />

H Sacramento Eleven Ramp meters between<br />

County, El Sacramento/El Dorado County line and<br />

Dorado County Placerville<br />

H SACOG Expand Regional Traveler Information<br />

System<br />

M SACOG Regional Incident/Emergency Management<br />

<strong>Plan</strong> (incorporates proposed AVI/AVL<br />

technologies for emergency response<br />

vehicles)<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

TBD TBD 2• 3• 4<br />

5• 6<br />

$500,000 2008 2• 3• 4<br />

$600,000 2007 2• 3• 4<br />

TBD TBD 9<br />

L SACOG Remote ATIS workstations $125,000 2007 2• 3• 4<br />

L SACOG, CHP Expand Emergency Vehicle Pre­emption TBD 2008 9<br />

(EVP) <strong>Deployment</strong><br />

L SACOG, CHP Emergency Vehicles ­ AVI/AVL (including TBD 2008 9<br />

tracking equipment in dispatch and TMC)<br />

H City of West Expand signal interconnect network $400,000 2009 2• 3<br />

Sacramento<br />

M City of West Upgrade traffic signal controllers throughout $400,000 2007 2• 3<br />

Sacramento the City<br />

M City of West Install bicycle detection at select<br />

$250,000 2009 4• 9<br />

Sacramento intersections<br />

L City of West Expand wireless traffic signal<br />

$200,000 2009 2• 3<br />

Sacramento communication network<br />

L City of West<br />

Sacramento<br />

Deploy CCTV cameras with communication<br />

to the TOC along minor arterials<br />

$60,000<br />

per location<br />

2012 2• 3• 9<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

122 Final Report<br />

September 2005


Table 7.3: Project Sequencing ­ Long Term Projects (10­20 years)<br />

Responsible<br />

Agency<br />

Description<br />

Caltrans District 3<br />

Commercial Vehicle Parking<br />

Management System ­ system to<br />

monitor commercial vehicle parking<br />

availability at a number of locations<br />

in real­time, and utilize a variety of<br />

dissemination tools to make the<br />

information available to commercial<br />

vehicle operators.<br />

Caltrans District 3<br />

Deploy a system to detect and<br />

classify the movement of HAZMAT<br />

materials.<br />

Caltrans District 3<br />

Dynamic Speed Signing System for<br />

weather conditions<br />

Caltrans District 3<br />

Deploy an automatic vehicle location<br />

(AVL) system to manage routine and<br />

corrective maintenance on<br />

maintenance and construction<br />

vehicles.<br />

Caltrans District 3<br />

Deploy a system to monitor and<br />

maintain winter weather conditions<br />

and roadway treatment.<br />

Caltrans District 3<br />

Install signals on U.S. 50 ramps at<br />

Ponderosa Road, South Shingle<br />

Springs, and North Shingle Road<br />

Caltrans District 3<br />

U.S. 50 From I­80 to Sacramento<br />

County line— install traffic operations<br />

system (message signs, ramp<br />

metering, CCTV)<br />

Caltrans District 3<br />

U.S. 50 Install ramp meters and<br />

modify ramp design at South River<br />

Rd. interchange.<br />

Caltrans, Emergency services Computer Aided Dispatch Integration:<br />

integrate the computer­aided dispatch<br />

systems of various emergency<br />

response and transportation agencies<br />

that jointly participate in traffic incident<br />

management, including local police,<br />

state patrol, HAZMAT response,<br />

Caltrans, and fire departments.<br />

Elk Grove<br />

Expand DMS system by deploying<br />

approximately six additional signs,<br />

appropriate locations to be<br />

determined<br />

Emergency Services Emergency Response<br />

Sacramento Regional<br />

Transit<br />

Telecommunications Center.<br />

Expansion of bus and van service<br />

regionwide, including a large<br />

increase in service for elderly and<br />

disabled persons.<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

TBD 2020 2• 5<br />

TBD 2020 9<br />

$5,000,000 2015 9<br />

TBD 2015 10<br />

TBD 2015 2<br />

$1,900,000 2015 2• 3<br />

$600,000 2015 2<br />

$4,300,000 2021 2<br />

$2,000,000 2015 9<br />

$250,000. 2011 2• 3• 4<br />

TBD 2015 9<br />

TBD 2015 4• 5• 6<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

123 Final Report<br />

September 2005


Table 7.3: Project Sequencing ­ Long Term Projects (10­20 years)<br />

Roseville<br />

Responsible<br />

Agency<br />

Roseville Transit<br />

SACOG<br />

SACOG<br />

SACOG<br />

SACOG<br />

Sacramento County<br />

Sacramento Regional<br />

Transit<br />

City of West Sacramento<br />

City of West Sacramento<br />

City of West Sacramento<br />

City of West Sacramento<br />

City of West Sacramento<br />

Description<br />

Implement arterial dynamic message<br />

signs (DMS)<br />

Fixed Route and Paratransit<br />

Expansion<br />

Deploy in­vehicle or handheld<br />

technology to monitor external<br />

conditions to provide route planning<br />

and guidance.<br />

Deploy an ISP­based system that<br />

develops route planning and<br />

multimodal information.<br />

Deploy a virtual TMC network that<br />

allows rural or remote agencies to<br />

access STARNET via the Internet.<br />

Integrate communications between<br />

freight­rail, Amtrak, and local TMCs<br />

to provide coordination between rail<br />

and roadway traffic.<br />

Deploy in­vehicle equipment and<br />

roadside communications equipment<br />

to collect and monitor travel<br />

conditions.<br />

Retrofit existing communication kits<br />

with upgraded audio system and<br />

automatic interior exterior visual<br />

signs for stop announcements and<br />

train destinations.<br />

Install Trailblazer signs on West<br />

Capitol Ave<br />

Complete signal interconnect<br />

network<br />

Complete wireless traffic signal<br />

network<br />

Complete the upgrade of traffic<br />

signal controllers throughout the City<br />

Complete deployment of CCTV<br />

cameras and associated<br />

communication<br />

Project<br />

Cost<br />

Year<br />

ITS<br />

Vision<br />

TBD TBD 2• 3• 4<br />

TBD 2015 4• 5• 6<br />

TBD 2025 4• 5<br />

TBD 2020 2• 3• 4• 5<br />

TBD 2015 2• 3• 4<br />

TBD 2025 2• 3• 4<br />

TBD 2025 2• 3• 4<br />

TBD 2015 4• 5• 6<br />

$400,000 2015 3• 9<br />

$200,000 2015 2• 3<br />

$100,000 2015 2• 3<br />

$200,000 2015 2• 3<br />

$60,000 per<br />

location<br />

2016 2• 3• 9<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

124 Final Report<br />

September 2005


7.2 Early Winners<br />

“Early Winners”are projects that can be implemented almost immediately if funding is available;<br />

or projects that have recently been completed that offer benefits to the region. These projects have<br />

little or no external conflicts or dependencies. The focus of early winner projects for the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> is to identify projects that will serve a regional benefit. Detailed descriptions of<br />

each project follow.<br />

Table 7.4: Early Winner Projects<br />

Early Winner projects include:<br />

Project #1 –STARNET Systems Engineering Report and Implementation<br />

Project #2 –Sacramento 511 Traveler Information System<br />

Project #3 –Elk Grove communication connection to future STARNET<br />

Project #4 –Folsom communication connection to future STARNET via 50­Fig<br />

Project #5 –Roseville backbone connection to Citrus Heights for future STARNET<br />

Project #6 –Extension of Regional Transit Backbone<br />

Project #7 –Arden Way ITS<br />

Project #8 –Watt Avenue Smart Corridor<br />

Project #9 –Caltrans Fiber Interconnect Project to future STARNET<br />

Project #10 –Stockton Boulevard Enhanced Bus<br />

Project #1 –STARNET Systems Engineering Report<br />

Description – Prepare a Systems Engineering Report according to FHWA Guidelines that<br />

establishes functional, operational, and maintenance requirements for deployment of a regional<br />

communications network (STARNET).<br />

The regional ITS partners have outlined a vision for a Sacramento Transportation ARea NETwork<br />

(STARNET), a regional communications network that will allow local and regional agencies to<br />

communicate between Traffic Management Centers (TMCs) and enhance regional traffic<br />

management coordination. Although several communications segments between agencies have<br />

been or are being installed, the functionality of a center­to­center communications network has not<br />

yet been defined. The Systems Engineering Report will give the partners a developmental<br />

framework for the functions, operations, and maintenance activities desired by the ITS partners.<br />

Once the Systems Engineering Report is complete, the partners will be able to complete the<br />

infrastructure, hardware, and software to satisfy the partners’needs.<br />

Benefits<br />

o Provides a clear definition of the STARNET functionality and the requirements for<br />

deploying a center­to­center network.<br />

o Provides compliance with FHWA Guidelines for future federal funding considerations.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

125 Final Report<br />

September 2005


Project #2 –Sacramento 511 Traveler Information System<br />

Description – Implement an on­line and telephone system that provides real­time traveler<br />

information to users.<br />

SACOG has deployed a system that provides real­time traveler information to users via the phone<br />

(511) and internet (www.sacregion511.org). This system will be expanded in the future.<br />

Benefits<br />

o Provides real­time traveler information to the public.<br />

Project #3 –Elk Grove communication connection to future STARNET<br />

Description – Design and construct a fiber optic communications link between the Elk Grove<br />

ATMS and Sacramento County fiber network near Bradshaw Road and Calvine Road to provide<br />

infrastructure for STARNET.<br />

The City of Elk Grove is actively deploying a fiber optic and copper network throughout the city.<br />

The City has an opportunity to install a fiber optic communications link that will provide a<br />

connection between the city’s network and Sacramento County’s network. This will consist of<br />

approximately 4 miles of new fiber optic cable, half of which is installed in existing conduit. When<br />

complete, the STARNET communications infrastructure will be in place to Elk Grove.<br />

Benefits<br />

o Provide infrastructure that will include Elk Grove in the regional communications network<br />

that will become STARNET.<br />

o Expand Elk Grove’s fiber optic communications network.<br />

Project #4 –Folsom communication connection to future STARNET via 50­FIG<br />

Description – Install conduit and fiber optic communications cable from Folsom City Hall to<br />

Regional Transit’s 50­FIG fiber optic trunkline to provide Folsom with a connection to STARNET.<br />

The city has an opportunity to complete a fiber optic communications link that will provide a<br />

connection to the future STARNET communications infrastructure. The city needs to design and<br />

construct one mile of infrastructure to complete this link. When complete, the STARNET<br />

communications infrastructure will be in place to Folsom.<br />

Benefits<br />

o Provide infrastructure that will include Folsom in the regional communications network<br />

that will become STARNET.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

126 Final Report<br />

September 2005


Project #5 –Roseville backbone connection to Citrus Heights for future STARNET<br />

Description –Design and construct a fiber connection between the City of Roseville and the City of<br />

Citrus Heights<br />

The city has an opportunity to complete a fiber optic communications link between the Roseville<br />

City Hall and the City of Citrus Heights existing communications network. The city needs to<br />

design and construct approximately 3 miles of infrastructure (some of which is existing conduit) to<br />

complete this link. When complete, Roseville will have a communications connection to the future<br />

STARNET infrastructure and will also provide the opportunity for agencies to the north of<br />

Roseville to install future connections to STARNET.<br />

Benefits<br />

o Provide infrastructure that will include Folsom in the regional communications network<br />

that will become STARNET.<br />

o Give agencies to the north of Roseville the opportunity to connect to the future STARNET<br />

infrastructure.<br />

Project #6 –Extension of Regional Transit Backbone<br />

Description –Install the final 8 miles of fiber optic infrastructure to complete Regional Transit’s<br />

38­mile regional network.<br />

Sacramento Regional Transit (RT) is proposing to extend the existing communications<br />

infrastructure along the North Line segment. This 8­mile segment of 144­strand fiber optic cable<br />

would extend the North Line infrastructure from the Alkali Flat light rail station to the Watt/I­80<br />

light rail station. By installing this link, RT will complete the 38­mile network of fiber optic<br />

communications infrastructure throughout the Sacramento region. This network will give any<br />

agency in the vicinity the ability to utilize this cable as a communications link for center­to­center<br />

communications. This could also provide redundancy to existing communications owned by the<br />

local agencies.<br />

Benefits<br />

o Completes a regional communications network.<br />

o Provides potentially easier access by local agencies to a regional network.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

127 Final Report<br />

September 2005


Project #7 –Arden Way ITS<br />

Description –Design and construct a communications network along Arden Way from Del Paso to<br />

Watt Avenue to communicate with field devices and provide a communications connection between<br />

the City of Sacramento and Sacramento County.<br />

The City of Sacramento is nearing completion of the design of this communications link along<br />

Arden Way. This project will include CCTV cameras and arterial changeable message signs along<br />

this 8­mile segment, as well as provide the final communications connection between the City and<br />

County Traffic Management Centers (TMCs). This will provide a major communications link for<br />

the future STARNET infrastructure.<br />

Benefits<br />

o Provides the City of Sacramento and Sacramento County a communications link.<br />

o Provides a major communications link for the future STARNET.<br />

Project #8 –Watt Avenue Smart Corridor<br />

Description – <strong>Deployment</strong> of video surveillance, vehicle detection, and a communications<br />

backbone along Watt Avenue.<br />

Sacramento County has deployed ITS along Watt Avenue to monitor and manage traffic<br />

conditions. Closed circuit television cameras, vehicle detection, and a communications backbone<br />

provide information to the Sacramento County Traffic Management Center. A future phase will<br />

extend this system on Watt Avenue to Folsom Boulevard.<br />

Benefits<br />

o Provides Sacramento County information on traffic conditions on Watt Avenue at the<br />

Traffic Management Center.<br />

Project #9 –Caltrans Fiber Interconnect Project for future STARNET<br />

Description –Install conduit and fiber communications infrastructure between Caltrans District 3,<br />

Sacramento County TMC, and Regional Transit’s 50FIG fiber backbone. This will link all of these<br />

agencies toward the STARNET center­to­center system.<br />

Sacramento Regional Transit has deployed a fiber communications network along the entire light<br />

rail transit network. Some of this fiber has been offered to help facilitate completion of the<br />

regional STARNET center­to­center communications network. By completing this early winner<br />

projects, Caltrans will be able to complete the communications link to Sacramento County and<br />

Regional Transit by installing approximately one mile of conduit and fiber. This will provide a<br />

major communications link for the future STARNET infrastructure.<br />

Benefits<br />

o Provides a communications link between Caltrans, Sacramento County, and Caltrans.<br />

o Provides a major communications link for the future STARNET.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

128 Final Report<br />

September 2005


Project #10 –Stockton Boulevard Enhanced Bus<br />

Description – <strong>Deployment</strong> of queue jumper lanes and transit signal priority at 5 locations on<br />

Stockton Boulevard.<br />

The City of Sacramento has deployed transit enhancements along a portion of Stockton Boulevard<br />

as an enhanced bus demonstration project. The equipment includes transit signal priority, which<br />

will give transit vehicles an early or extended green phase at a traffic signal under certain<br />

conditions. There are also queue jumper lanes that allow transit vehicles to bypass a queue of<br />

vehicles and receive an early green phase to advance in front of the queued vehicles.<br />

Benefits<br />

o Improves transit operations – better schedule adherence, increased reliability, increased<br />

readership.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

129 Final Report<br />

September 2005


7.3 Gap Resolution<br />

In Section 3.3 the results of the Gap Assessment were presented. This included areas of the ITS<br />

Vision and Regional Architecture (based on Market Packages) that did not currently have existing,<br />

planned, or programmed projects associated with them. As part of the deployment<br />

recommendations, Table 7.5 presents projects that the region can deploy to fulfill the gaps in the<br />

Regional Architecture. The prioritization of each project is based on the stakeholder’s<br />

prioritization of that particular market package. Table 7.6 presents projects that the region can<br />

deploy to fulfill the gaps in the ITS Vision. All of these projects are new to the region and are not<br />

currently being considered in any program. However, these projects will help the region achieve<br />

the Blueprint objectives. As these projects are further defined, they should be added to the MTP<br />

and/or added to Tables 7.1­7.3 as the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is updated.<br />

All of the projects concepts identified in this section are somewhat general in nature. There are no<br />

project limits established and no costs or specific timeframes identified. As an agency moves<br />

forward with a particular project, additional project development will be required as the project is<br />

programmed. A project description and project limits will need to be defined so the project can be<br />

included in a CIP, master plan, or other planning documentation. The responsible agencies<br />

identified below are subject to change. These suggested projects could also result in multiple<br />

projects or multiple phases.<br />

Table 7.5: Projects for Regional Architecture Gaps<br />

Priority<br />

Market<br />

Package<br />

Responsible<br />

Agency<br />

Description<br />

Project<br />

Cost<br />

Year<br />

H<br />

Work Zone<br />

Management<br />

(MC08)<br />

Caltrans District 3<br />

Provide real­time construction activity region­wide. TBD TBD<br />

Deploy surveillance and detection systems for truck<br />

activity within construction zones.<br />

TBD<br />

TBD<br />

M<br />

Work Zone Safety<br />

Monitoring (MC09)<br />

Caltrans District 3<br />

Develop a Work Zone Safety <strong>Plan</strong>. TBD TBD<br />

Deploy technologies to enhance work zone safety. TBD TBD<br />

M<br />

Transit Maintenance<br />

(APTS06)<br />

Sacramento<br />

Regional Transit<br />

Install on­board real­time transit vehicle monitoring<br />

devices. This includes the notification of impending<br />

failures within the transit vehicle.<br />

Integrate vehicle monitoring devices with the AVL<br />

systems and maintenance scheduling system<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

M<br />

HAZMAT<br />

Management<br />

(CVO10)<br />

Caltrans District 3<br />

Prepare a region­wide HAZMAT Incident Response<br />

<strong>Plan</strong> including incident reporting, management and<br />

recovery.<br />

Install a real­time AVL system for tracking commercial<br />

HAZMAT vehicles<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

M<br />

Emissions<br />

Monitoring and<br />

Management<br />

(ATMS11)<br />

SMAQMD<br />

Install vehicle (tail pipe) emissions monitoring sensors<br />

along key congested corridors and reliever routes<br />

Install a vehicle emissions collection, warning and<br />

reporting system<br />

Integrate the emissions monitoring and reporting<br />

system with the TMCs in the region<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

130 Final Report<br />

September 2005


Table 7.5: Projects for Regional Architecture Gaps (cont’d.)<br />

Priority<br />

Market<br />

Package<br />

Responsible<br />

Agency<br />

Description<br />

Project<br />

Cost<br />

Year<br />

M<br />

M<br />

M<br />

M<br />

M<br />

M<br />

Transportation<br />

Infrastructure<br />

Protection (EM05)<br />

Evacuation and<br />

Reentry<br />

Management<br />

(EM09)<br />

Standard Rail<br />

Grade Crossing<br />

(


Table 7.5: Projects for Regional Architecture Gaps (cont’d.)<br />

Priority<br />

Market<br />

Package<br />

Responsible<br />

Agency<br />

Description<br />

Project<br />

Cost<br />

Year<br />

M<br />

On­Board CVO and<br />

Freight Safety and<br />

Security (CVO08)<br />

Caltrans District 3<br />

Design and integrate on­board safety and security<br />

monitoring devices with the roadside CVO systems<br />

including early warning systems and vehicle<br />

identification information<br />

TBD<br />

TBD<br />

M<br />

CVO Fleet<br />

Maintenance<br />

(CVO09)<br />

Caltrans District 3<br />

Install real­time monitoring devices on­board<br />

commercial fleet vehicles. This includes the<br />

notification of impending failures within the vehicle.<br />

Integrate vehicle monitoring devices with existing and<br />

future AVL systems and maintenance scheduling<br />

systems<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

M<br />

Freight Assignment<br />

Tracking (CVO13)<br />

Caltrans District 3<br />

Design and deploy freight tracking system on­board<br />

commercial vehicles and at key access points to cargo<br />

shipping facilities.<br />

Integrate the freight tracking system with the<br />

Emergency Management System for emergency<br />

response and management<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

L<br />

Advanced Rail<br />

Grade Crossing<br />

(>80 mph)<br />

(ATMS14)<br />

Amtrak<br />

Provide active warning devices such as dynamic<br />

message signs to display predictive arrival information<br />

for approaching trains near at­grade rail crossings<br />

TBD<br />

TBD<br />

Implement a toll tag probe vehicle system for<br />

extracting travel times<br />

TBD<br />

TBD<br />

Implement a demonstration project to test the viability<br />

of dedicated short range communications (DSRC)<br />

technologies for real­time data collection<br />

TBD<br />

TBD<br />

L<br />

Probe Surveillance<br />

(ATMS02)<br />

Caltrans District 3<br />

Integrate AVL systems with traffic management<br />

systems to utilize transit vehicles as prove vehicles<br />

Build on VII technologies to implement a probe vehicle<br />

system<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

Deploy roadside beacons and backhaul<br />

communications along key freeway corridors to collect<br />

and forward information from probe vehicles<br />

TBD<br />

TBD<br />

Design and integrate an electronic toll collection<br />

system of toll readers, toll tags, fare payment and fare<br />

management systems along key corridors (subject to<br />

the development and implementation of the <strong>Plan</strong>)<br />

TBD<br />

TBD<br />

L<br />

Railroad Operations<br />

Coordination<br />

(ATMS15)<br />

Sacramento<br />

Regional Transit<br />

Caltrans District 3<br />

Design and integrate a center­to­center link between<br />

the rail operations and control system and the local<br />

and regional TMCs<br />

Develop a plan for the deployment of roadway access<br />

control systems<br />

Design and install an integrated roadway access<br />

control system at key locations throughout the region<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

132 Final Report<br />

September 2005


Table 7.5: Projects for Regional Architecture Gaps (cont’d.)<br />

Priority<br />

Market<br />

Package<br />

Responsible<br />

Agency<br />

Description<br />

Project<br />

Cost<br />

Year<br />

L<br />

Driver Safety<br />

Monitoring<br />

(AVSS02)<br />

SACOG<br />

Design and integrate on­board vehicle sensors with<br />

geographic information systems and global positioning<br />

satellite systems to detect impending incidents with<br />

vehicles, including bicycles<br />

Utilize VII technologies (OBE, RSU and backhaul<br />

communications) to deploy an early warning system<br />

between vehicles and roadside sensors<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

L<br />

Longitudinal Safety<br />

Warning (AVSS03)<br />

SACOG<br />

Install collision warning/avoidance systems within<br />

public agency vehicles<br />

Integrate collision warning and avoidance systems<br />

within commercial vehicles with TMCs<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

Utilize VII technologies including on­board and<br />

roadside equipment for a collision warning system<br />

TBD<br />

TBD<br />

L<br />

Intersection<br />

Collision Avoidance<br />

(AVSS10)<br />

SACOG<br />

Design and deploy roadside sensors to monitor in<br />

real­time the speeds and directions of vehicles<br />

approaching and within intersections<br />

Design and integrate the collision avoidance system<br />

with the local TMCs for data and commanding of<br />

traffic signal controllers<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

Design and integrate a cargo tracking system between<br />

the various port and cargo facilities and the local and<br />

regional TMCs<br />

TBD<br />

TBD<br />

L<br />

Electronic<br />

Clearance (CVO03)<br />

Caltrans District 3<br />

Design and deploy an Automated Vehicle<br />

Identification (AVI) System along key freeway<br />

checkpoints and weigh­in stations<br />

Integrate commercial on­board equipment<br />

(transponders, DSRC units, transaction units) with the<br />

AVI system and roadside units<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

L<br />

Roadside CVO<br />

Safety (CVO07<br />

Caltrans District 3<br />

Design and integrate an automated roadside safety<br />

monitoring system at existing and future weigh­in<br />

stations<br />

TBD<br />

TBD<br />

L<br />

Roadside HAZMAT<br />

Security Detection<br />

and Mitigation<br />

(CVO11)<br />

Caltrans District 3<br />

Design and install on­board monitoring devices for the<br />

detection of hazardous materials on commercial<br />

vehicles and reporting of unauthorized HAZMAT<br />

vehicles<br />

Design and install a roadside sensing system for<br />

sensing hazardous materials on commercial vehicles<br />

and reporting of unauthorized HAZMAT vehicles<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

L<br />

CV Driver Security<br />

Detection and<br />

Mitigation (CVO12)<br />

Caltrans District 3<br />

Design and install on­board security access control<br />

systems for commercial vehicles<br />

Integrate the on­board security system with the<br />

Emergency Management System for response and<br />

management of security breaches<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

133 Final Report<br />

September 2005


Table 7.6: Projects for ITS Vision Gaps<br />

ITS Vision Objective<br />

Responsible<br />

Agency<br />

Description<br />

Project<br />

Cost<br />

Year<br />

Improve bicycle and<br />

pedestrian mobility and safety<br />

Improve mobility and reliability<br />

for pedestrians and bicycles<br />

Improve mobility and reliability<br />

for pedestrians and bicycles<br />

Improve mobility and reliability<br />

for pedestrians and bicycles<br />

Implement automated<br />

enforcement<br />

Provide traveler information in<br />

accessible formats<br />

Provide traveler information in<br />

accessible formats<br />

Provide traveler information in<br />

accessible formats<br />

Provide ITS education for the<br />

region<br />

Provide ITS education for the<br />

region<br />

All<br />

All<br />

All<br />

All<br />

All<br />

SACOG<br />

SACOG<br />

Sacramento<br />

Regional Transit<br />

SACOG<br />

SACOG<br />

Design and implement surveillance, signal operations,<br />

and detection devices along key bicycle and pedestrian<br />

facilities<br />

Design and implement a bike and walking trip planning<br />

system within transit trip planning system currently<br />

under development<br />

Implement a bike and walking trip planning system<br />

within the 511 system for the region<br />

Install bicycle detection and improve signal timing to<br />

enhance bicycle mobility<br />

Install equipment at intersections other locations to<br />

provide automatic enforcement of traffic violations<br />

Design and implement a voice recognition system<br />

within the region’s 511 system<br />

Design and implement an interactive system within the<br />

region’s 511 system to allow users the option to hear<br />

and read the information in different languages<br />

Design and deploy traveler information kiosks at transit<br />

centers and key transit stops<br />

Develop an ITS education program in the region that<br />

targets key stakeholders including public focus groups,<br />

policymakers and transportation planners<br />

Implement an ITS outreach program including public<br />

and business focus groups and media events<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

TBD<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

134 Final Report<br />

September 2005


7.4 Stakeholder Agreements<br />

As the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is implemented and ITS is further deployed in the region, several<br />

agency interfaces, information exchanges, and integration strategies need to be defined to provide<br />

the ITS services and systems identified by the stakeholders in the region. Interfaces and data flows<br />

among public and private entities in the Sacramento Region will require agreements among<br />

agencies that establish parameters for sharing agency information to support traffic management,<br />

incident management, provide traveler information, and other functions identified in the Regional<br />

ITS Architecture.<br />

Currently, there are no formal agreements in place in the Sacramento Region with regards to ITS.<br />

Stakeholders acknowledged that in order to successfully deploy ITS solutions in the Region,<br />

agreements will need to be put in place. With the implementation of ITS technologies, integrating<br />

systems from one or more agencies, the anticipated level of information exchange identified in the<br />

architecture, it is likely that formal agreements will be needed. These agreements, while perhaps<br />

not requiring a financial commitment from agencies in the Region, should outline specific roles,<br />

responsibilities, data exchanges, levels of authority, and other facets of regional operations. Some<br />

agreements also will outline specific funding responsibilities, where appropriate and applicable.<br />

Table 7.7 provides a list of potential agreements for the Sacramento Region based on the interfaces<br />

identified in the Regional ITS Architecture. Many of these agreements will need to be instigated as<br />

STARNET becomes active. Since agreements often take several months to route through the<br />

proper review and approval channels, there should be a focus on development coordination as each<br />

of these agreements are anticipated and then a commitment by stakeholders to carry the agreement<br />

through to the adoption stage. This will help streamline the agreement process.<br />

It is important to note that as ITS services and systems are implemented in the Region, part of the<br />

planning and review process for those projects should include a review of potential agreements that<br />

would be needed for implementation or operations.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

135 Final Report<br />

September 2005


Table 7.7: Potential Agreements for the Sacramento Region<br />

Agreement and<br />

Agencies<br />

Status Agreement Description Considerations<br />

SDP<br />

Implementation<br />

All project<br />

stakeholders<br />

Drafted<br />

as the<br />

ITS MOU<br />

This agreement would define the<br />

responsibilities of stakeholders to implement<br />

the recommendations of the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong>. Each stakeholder will be<br />

asked to commit to utilizing the ITS tools in<br />

an effort to include ITS solutions as part of<br />

typical CIP projects, when applicable.<br />

This agreement is a zero­dollar<br />

agreement, in that there is no<br />

charge among agencies to<br />

implement the SDP.<br />

This agreement should be<br />

executed as soon as possible<br />

after the completion and<br />

approval of the Final SDP.<br />

Data Sharing and<br />

Usage (Public)<br />

Caltrans and Public<br />

Agencies within the<br />

Region<br />

Future<br />

This agreement would define the parameters,<br />

guidelines, and policies for inter­ and intraagency<br />

ITS data sharing. This data sharing<br />

would support regional activities related to<br />

traffic management, incident management,<br />

traveler information, and other functions. The<br />

terms of this agreement should generally<br />

address such items as:<br />

• Types of data and information to be<br />

shared<br />

• Repository for information (i.e., Caltrans<br />

TMC as central hub)<br />

• How the information will be used (traffic<br />

incident management, displayed on web<br />

site for travel information, distributed to<br />

private media, etc.)<br />

• Parameters for data format, quality,<br />

security<br />

These agreements are typically<br />

zero­dollar agreements, in that<br />

there is no charge among<br />

agencies for the actual data,<br />

although there might be some<br />

cost incurred for infrastructure,<br />

systems or fiber to enable<br />

communications between<br />

agencies.<br />

This agreement will or should<br />

be addressed as part of the<br />

establishment of STARNET<br />

Data Sharing and<br />

Usage<br />

(Public­Private)<br />

Caltrans and Private<br />

Media/Information<br />

Service Providers<br />

Future<br />

This agreement would define the parameters,<br />

guidelines, and policies for private media use<br />

of regional ITS­related information from<br />

STARNET. This type of agreement is<br />

recommended between the data provider and<br />

the media (data user) to define terms of use<br />

for broadcasting public­agency information<br />

regarding traffic conditions, closures,<br />

restrictions, as well as video images.<br />

Agreements can also include requirements<br />

for the media to ‘source’the information (i.e.,<br />

using an agency logo on all video images<br />

broadcast).<br />

These agreements can be zerodollar<br />

agreements, although<br />

some agencies have stipulated<br />

identifying the information,<br />

public service announcements<br />

by the media, or other<br />

requirements as a term of use.<br />

The private media entity is<br />

typically responsible for paying<br />

any necessary costs for access<br />

(i.e., communications<br />

infrastructure to link to<br />

STARNET or a video switch).<br />

These agreements also typically<br />

include a sunset clause to allow<br />

the agency to periodically<br />

review the agreement and make<br />

any modifications prior to<br />

renewal.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

136 Final Report<br />

September 2005


Table 7.7: Potential Agreements for the Sacramento Region<br />

Agreement and<br />

Agencies<br />

Status Agreement Description Considerations<br />

Shared Video<br />

Monitoring (Public)<br />

STARNET Entities<br />

and Public Safety<br />

Agencies<br />

Future<br />

This agreement would enable shared video<br />

monitoring of CCTV cameras by public safety<br />

and emergency services agencies in the<br />

Sacramento Region for incident management<br />

purposes. This agreement would define the<br />

parameters and policies for public safety<br />

agencies to access video images via<br />

STARNET. It is recommended that the<br />

agreement include policies relating to video<br />

images (including archiving, privacy,<br />

disclaimers, use of video and redistribution)<br />

as well as processes for agency requests for<br />

specific views. Shared video monitoring does<br />

not address shared use or shared control of<br />

video equipment functions.<br />

These agreements are typically<br />

zero­dollar agreements, in that<br />

there is no charge among<br />

agencies for the actual data,<br />

although there might be some<br />

cost incurred for infrastructure<br />

or systems to enable<br />

communications between<br />

agencies, particularly with the<br />

high bandwidth required for<br />

transmitting live video images.<br />

Mutual Aid<br />

Agreements<br />

(Public)<br />

CHP, Caltrans,<br />

Public Agencies<br />

Future<br />

Formal mutual aid agreements will become<br />

more important as agencies integrate<br />

systems and capabilities, particularly<br />

automated dispatch and notification. This<br />

likely will become a requirement as part of<br />

STARNET.<br />

These agreements are typically<br />

zero­dollar agreements,<br />

although there might be some<br />

funding required to support<br />

regional incident management<br />

activities. The agreement also<br />

would outline resource<br />

commitments that would be part<br />

of any mutual aid arrangement<br />

(personnel, equipment,<br />

facilities, etc.).<br />

Joint<br />

Operations/Shared<br />

Control<br />

Agreements<br />

(Public)<br />

Caltrans, CHP,<br />

Public Agencies<br />

Future<br />

These agreements are formal arrangements<br />

to allow joint operations or control of certain<br />

systems and equipment. The agreement<br />

would need to define the terms of this<br />

arrangement, such as hours of operation and<br />

time of day/time of week where shared<br />

control would take effect, circumstances or<br />

incidents where shared control would take<br />

effect, notification procedures between the<br />

agencies agreeing to shared control<br />

arrangements, etc. Additional agencies (such<br />

as CHP) could be part of a joint<br />

operations/shared control agreement for<br />

certain types of devices.<br />

Joint operations/shared control<br />

agreements could consider<br />

some form of mutual funding for<br />

certain system elements,<br />

primarily communication links.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

137 Final Report<br />

September 2005


7.5 Mainstreaming<br />

“Mainstreaming”refers to processes that provide for the systematic and strategic consideration of<br />

ITS in all aspects of transportation planning whether it is being done on a local, corridor or regional<br />

level, or specifically tied to smart growth projects. Since planning is the underpinning of<br />

investment decisions, identification of transportation projects and ITS components within those<br />

projects need to emanate from the planning process. This will result in the incorporation of<br />

technologies into the future transportation system as projects are delivered.<br />

The goal of mainstreaming is to ensure that ITS strategies and technologies are an integral<br />

component of the metropolitan transportation planning and programming process and are<br />

incorporated into the Metropolitan Transportation <strong>Plan</strong> (MTP) and Metropolitan Transportation<br />

Improvement Program (MTIP).<br />

Both processes should incorporate ITS solutions that work with existing and planned systems,<br />

complement the existing transportation infrastructure, and work with other investments. Thus, ITS<br />

should not be presented or perceived as an alternative to conventional transportation investments,<br />

but seen as a part of conventional transportation programs and projects. To achieve this goal, the<br />

project stakeholders should institutionalize ITS into the transportation planning and programming<br />

process and address the use of advanced technology solutions as a routine part of the transportation<br />

decision making process.<br />

Strategies that assist in “mainstreaming” ITS include the use of committees with regional<br />

stakeholders, education of policymakers, staff and the public; inclusion of ITS in planning<br />

documents; a program of regional projects; and methodologies to encourage consideration of<br />

advanced technology into transportation investment alternatives. Some project stakeholders have<br />

already initiated or undertaken many of these strategies. Below is a brief overview of what has<br />

already been undertaken and recommendations for furthering the “mainstreaming”process.<br />

The “mainstreaming”of ITS into the metropolitan transportation planning process was initiated by<br />

SACOG during the development of the 1999 Metropolitan Transportation <strong>Plan</strong> (MTP) and was<br />

expanded in the Metropolitan Transportation <strong>Plan</strong> for 2025. ITS was incorporated in the SACOG<br />

MTP for 2025 in an appendix titled “ITS Strategies”which includes a historical overview of ITS<br />

planning and requirements, current planning and development activities, and major ITS projects<br />

included in the MTP.<br />

In addition, SACOG has implemented a series of projects over the past 10 years to bring ITS to the<br />

attention of both local staff and policymakers as a potential solution to congestion and safety<br />

issues. The ITS Partnership, a group of staff engaged in traffic operations from cities, counties,<br />

transit operators and Caltrans was formed to serve as an advisory group to the SACOG Board on<br />

ITS matters and to bring the discussion on ITS integration to a regional level. SACOG has<br />

undertaken educational activities by developing an ITS video, conducting a tour of existing and<br />

planned ITS facilities in the region, and providing opportunities for policy Board members to<br />

participate in tours of ITS facilities in other metropolitan areas. Through the work of the Regional<br />

ITS Partnership, a number of studies have been undertaken that lay the groundwork for a regionally<br />

integrated ITS system, project deployment, and use of federal earmarks.<br />

SACOG’s member agencies and transportation partners also have taken steps to create a climate<br />

for technical staff and policy makers to consider ITS as a candidate solution for identified<br />

transportation problems both at the local and regional level. Many jurisdictions have developed<br />

ITS master plans and have incorporated ITS into traditional transportation projects. One example<br />

of member agency support for integrating ITS into corridor planning is found in the analytical<br />

approach taken in the Mobility Strategies Study recently completed by the County of Sacramento<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

138 Final Report<br />

September 2005


Department of Transportation. In the Department’s evaluation of options for reducing congestion<br />

on the most congested County corridors, ITS was evaluated in conjunction with other physical<br />

improvements and service improvements such as bus rapid transit, pedestrian and bicycle<br />

improvements, and capacity increases to the corridor. Thus, most options contained some level of<br />

ITS integrated into the solution sets to address corridor congestion and mobility.<br />

There are a number of additional steps that can be taken to consider ITS on a level playing field<br />

with other transportation options. Other opportunities to encourage and implement<br />

“mainstreaming”ITS solutions into the regional transportation planning and programming process<br />

include:<br />

1. Utilize priority list presented earlier in Section 7 to program projects that will capitalize on<br />

the benefits of advancing the ITS program in the region.<br />

a. These projects will be included in the update of the SACOG MTP, so they should<br />

also be included in local agency CIP programs.<br />

b. Consider these projects in conjunction with other capital improvement projects to<br />

capture cost benefits by combining projects.<br />

2. Develop an awareness and education program on the benefits of ITS in general and<br />

specifically on projects deployed in the region.<br />

a. More information about deployed projects and what they contribute to improve<br />

travel and productivity can bring attention to the value of ITS solutions. When ITS<br />

works, the transportation system performs smoothly, and travelers are unaware of<br />

the how that benefit is achieved. A proactive program that demonstrates the value<br />

and benefit of ITS by reducing congestion, increasing safety and traveler<br />

productivity should be implemented.<br />

b. Use the SACOG regional report, web site or other communication outlets to<br />

showcase new technologies and services not yet used in the region but may be<br />

beneficial to the region.<br />

c. Promote technology applications successfully being used by local agencies.<br />

3. Link ITS solutions to the Blueprint Preferred Scenario using the ITS Solutions Toolbox.<br />

a. Prepare a program on ITS solutions supporting smart growth and present it at one<br />

of the monthly SACOG seminars on implementation of the Blueprint principles or<br />

other community forum. The program should focus on benefits that can enhance<br />

the travel environment of smart growth projects. The ITS Solutions Toolbox<br />

provides a starting point for materials and a program.<br />

b. As smart growth projects are proposed by the development community, the ITS<br />

Solution Toolbox should be available to local land use planners and transportation<br />

planners who review development projects. Integration of ITS infrastructure into<br />

new development and associated transportation projects, where possible, should be<br />

encouraged. ITS should not be an after thought to the planning and design process.<br />

c. Consider how ITS can be incorporated into general plan circulation elements.<br />

4. Utilize the ITS Solutions Toolbox in all planning and programming activities.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

139 Final Report<br />

September 2005


a. When planning projects, use ITS Solutions Toolbox to identify opportunities to<br />

include ITS elements; and to program design, construction, operations, and<br />

maintenance costs.<br />

b. Using the examples presented in Section 7, identify existing and future<br />

opportunities for including ITS elements in combination with other capital<br />

improvement projects. This will result in cost savings and schedule efficiencies.<br />

5. Incorporate components of the SDP into the main body of the next Metropolitan<br />

Transportation <strong>Plan</strong> with a focus on outcomes that benefit users of the system. The <strong>Plan</strong><br />

can include:<br />

a. A discussion on new technologies that improve system performance without<br />

adding capacity with minimal reference to ITS “jargon”.<br />

b. Identification of key ITS projects and initiatives that should be targeted early in the<br />

planning process to promote integration with other transportation projects and<br />

strategies.<br />

c. Incorporation of the ITS Vision into the long range transportation goals.<br />

d. References and descriptions of regional ITS Architecture and SDP components to<br />

provide better definition of project costs and define the regional ITS integrated<br />

network and system (i.e., identify potential technologies as part of project<br />

descriptions).<br />

6. Schedule a joint meeting of the ITS Partnership and Regional <strong>Plan</strong>ning Partnership at least<br />

annually to provide a forum for topics of common interest and to initiate a procedure that<br />

ensures ITS solutions are considered when projects are nominated for federal or state<br />

funding.<br />

7. Consider separating the ITS Partnership into two groups –a technical working group and a<br />

policy steering group and identify the roles of each group. Maintain the current schedule<br />

for the technical working group and bring the policy group members together at key<br />

milestones in the planning and programming process. The addition of a policy steering<br />

group will raise the level of discussion to management level and reinforce the need to<br />

integrate ITS at the planning stage of project development.<br />

8. Create incentives for incorporating and maintaining ITS in MTP and MTIP projects that<br />

can demonstrate a measurable outcome. Incentives could include additional funding for<br />

maintaining ITS components in projects and/or earlier project delivery schedule for ITS<br />

projects.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

140 Final Report<br />

September 2005


8 NEXT STEPS<br />

The Sacramento Regional ITS Architecture and ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> (SDP) should be<br />

considered living documents.<br />

As with other recent regional planning documents, this report can be an active resource that builds<br />

upon other major regional planning initiatives such as the Sacramento Region Blueprint, and the<br />

Metropolitan Transportation <strong>Plan</strong>. Stakeholders in Sacramento and the adjacent regions are<br />

encouraged to use this document in tandem with other regional documents and related plan<br />

updates.<br />

In order to make this document successful, it is necessary to carry forward several key elements:<br />

1. It is critical to execute an SDP Memorandum of Understanding as soon as possible<br />

following approval of the documents. This will keep the momentum going forward and help to<br />

include ITS solutions in the planning processes that will be updated over the next year.<br />

2. The responsible agencies should follow up on Early Winner projects in their jurisdiction to<br />

identify opportunities to provide greater benefit and cost savings by implementing them.<br />

3. ITS planning encompasses Commercial Vehicle Operations (CVO). As ITS mainstreaming<br />

moves forward, stakeholders from freight agencies and goods movement organizations (such as<br />

the Port of Sacramento) should be identified and engaged more actively in future discussions.<br />

4. Incorporate SDP outputs into Next Step action items from Blueprint. One of the Next Steps of<br />

Blueprint is to “Develop a toolbox of Best <strong>Plan</strong>ning and Development Practices”, including<br />

design guidelines and on­line tutorials. The ITS Solutions Toolbox can be linked to, or be one<br />

of the “tools”in the Blueprint Toolbox.<br />

5. Execute the conditions of the ITS Maintenance <strong>Plan</strong> to ensure that the ITS Architecture will<br />

continue to be updated.<br />

6. As part of the ITS Partnership or other group of stakeholders, set a schedule for discussing the<br />

SDP on a regular basis. Many of the ideas and concepts contained in this document can change<br />

regularly and it is essential to the success of the region to evaluate the contents of the document<br />

on an ongoing basis. In addition, set a schedule to conduct a joint meeting with the Regional<br />

<strong>Plan</strong>ning Partnership to include ITS mainstreaming as a discussion.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

141 Final Report<br />

September 2005


Appendix A


Community Outreach <strong>Plan</strong><br />

Prepared for:<br />

Prepared by:<br />

February 2005<br />

097860000<br />

Copyright © 2005, Kimley­Horn and Associates, Inc.


TABLE OF CONTENTS<br />

COMMUNITY OUTREACH PLAN<br />

1. INTRODUCTION.............................................................................................................................1<br />

2. OUTREACH PROGRAM OBJECTIVES.............................................................................................2<br />

3. IDENTIFICATION OF PROJECT STAKEHOLDERS AND CHAMPIONS...............................................3<br />

4. MEETINGS AND WORKSHOPS .......................................................................................................4<br />

4.1 Project Stakeholder Kick Off Meeting [March 8, 2005]......................................................4<br />

4.2 Stakeholder Workshop #1 [March 30, 2005; 9:00 AM –4:00 PM; at SACOG] .................5<br />

4.3 Stakeholder Workshop #2 [May 10, 2005; 9:00 AM –4:00 PM; at SACOG).....................5<br />

4.4 SACOG Board Workshop [March 17, 2005] .......................................................................6<br />

5. PROJECT AWARENESS AND EDUCATION ......................................................................................7<br />

5.1 Project Web Site....................................................................................................................7<br />

5.2 Stakeholder Email List and Notification Process.................................................................7<br />

5.3 Regional Report Articles.......................................................................................................7<br />

5.4 PowerPoint Presentation.......................................................................................................7<br />

6. FACILITATE TECHNICAL REVIEW AND STAKEHOLDER INVOLVEMENT......................................8<br />

7. BUILDING CONSENSUS..................................................................................................................9<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc i Community Outreach <strong>Plan</strong><br />

02/09/05


1. INTRODUCTION<br />

The Sacramento Area Council of Governments (SACOG), in a cooperative effort with local<br />

government, the Federal Highway Administration, and Caltrans, is undertaking the preparation of an<br />

Intelligent Transportation Systems (ITS) <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. This project builds upon ITS work<br />

previously undertaken by SACOG as well as local and state transportation agencies over the past several<br />

years and will result in the replacement of the SACOG 1996 Early <strong>Deployment</strong> <strong>Plan</strong> with a new<br />

document, the ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

The development of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will incorporate and build upon recent efforts of<br />

various local agencies and SACOG to demonstrate the importance of land use in planning fin planning<br />

for future transportation improvements. The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will be a first effort to integrate<br />

ITS planning and ITS project development strategies within the broader transportation and land use<br />

planning efforts.<br />

This document will outline the outreach program tasks and events that will be undertaken during the<br />

preparation of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 1 Community Outreach <strong>Plan</strong><br />

02/09/05


2. OUTREACH PROGRAM OBJECTIVES<br />

The objectives of the outreach activities are as follows:<br />

• Create awareness of the project (how land use and economic development studies and plans, air<br />

quality regulations, and market trends influence transportation planning decisions; noting where ITS<br />

can be used to advance the goals and objectives in these planning studies);<br />

– Identify champions for this project at the local level and ask them to encourage their local<br />

officials to attend appropriate meetings<br />

– Identify the appropriate SACOG Board sub committee to create a strong understanding of the<br />

ITS effort at SACOG<br />

– Provide awareness of project through web site, email notification and regional report articles<br />

– Invite high level stakeholders or their designees (planning managers, executive directors, chief<br />

executive officers of area agencies) to the kick­off meeting. In addition to a written invitation<br />

and an email reminder, the Consultant will make telephone calls to key stakeholders to<br />

encourage their attendance Provide opportunities for input to the project through the SACOG<br />

website, Regional Report and email.<br />

• Provide education on Intelligent Transportation Systems and how they can help the SACOG region<br />

achieve its land use and transportation goals;<br />

– Utilize PowerPoint presentations containing graphics and photographs and present fact sheets to<br />

educate the stakeholders<br />

– Highlight the achievements of local agencies (e.g. local and state traffic operations centers,<br />

Stockton enhanced bus, Watt Avenue and Arden Way ITS improvements)<br />

– Explain the connection between land use planning, transportation planning and ITS. Why<br />

should ITS be considered in all of these stages of urban planning?<br />

– Provide the connection between other transportation planning efforts and underlying ITS<br />

components<br />

• Facilitate technical review and involvement in the ITS architecture and strategic deployment plan<br />

development and explain how it is used and why;<br />

– Provide materials to the working group prior to public meetings to ensure accuracy<br />

– Prepare materials in layman language<br />

• Build consensus on the ITS vision, updated architecture, strategic direction, project concepts,<br />

recommended projects, and implementation priorities.<br />

– Identify areas of agreement<br />

– As an optional activity, conduct follow up interview and/or attend meetings to promote<br />

understanding and find areas of agreement where there appears to be disagreement. (at an<br />

additional cost)<br />

– As an optional activity, conduct additional meetings if agreement cannot be reached. (at an<br />

additional cost)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 2 Community Outreach <strong>Plan</strong><br />

02/09/05


3. IDENTIFICATION OF PROJECT STAKEHOLDERS AND CHAMPIONS<br />

This project will engage three groups of stakeholders. Appendix A includes a list of all stakeholders<br />

included in the outreach process. First is the traditional ITS stakeholder group who are actively involved<br />

in ITS projects. This group is composed of members of the ITS Partnership as well as the management<br />

of the organizations represented on this committee.<br />

Second is the group of interested parties who are aware of ITS through past project deployment. This<br />

group consists of community organizations and/or agencies who believe they are impacted by ITS<br />

projects and members of the Regional <strong>Plan</strong>ning Partnership involved in transportation planning.<br />

Community organizations that have expressed either an interest or concern about ITS include<br />

environmental groups, community groups within Sacramento County, and County advisory groups<br />

representing the disabled community. The stakeholder list will include the Environmental Council of<br />

Sacramento, American Lung Association, Walk Sacramento, Sacramento Area Bicycle Advocates, all<br />

city and county disabled advisory committees, Metropolitan Chamber of Commerce, Building Industry<br />

Association, Sacramento County community advisory councils, Sacramento Transportation and Air<br />

Quality Collaborative, as well as other organizations identified during the first ITS Partnership or<br />

Regional <strong>Plan</strong>ning Partnership meeting.<br />

The third group encompasses all newcomers to ITS. This group will most likely have limited<br />

knowledge of what ITS is, how it works, that it has been deployed throughout Sacramento County and<br />

adjacent urban areas, or that it is an underpinning of many planning efforts including the SACOG<br />

Blueprint Project. This group, for purposes of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> development, consists of<br />

the land use planners and air quality planners, and some non profit organizations who are interested in<br />

smart growth and supportive of transportation measures that encourage use of public transportation,<br />

walking and bicycling, but who may not be aware of how ITS strategies can be used and are necessary<br />

to support use of alternative modes of transportation. This third group will be drawn from participants<br />

of the SACOG Blueprint Project and the County Mobility Strategies Study including land use planners<br />

at each jurisdiction (not already on an existing SACOG committee), Valley Vision, American Lung<br />

Association, and business groups within the region to the kick off meeting.<br />

In addition to stakeholders, the project team will work to identify ITS champions at the management<br />

and policy level (including elected officials) who are interested in smart growth and use of alternative<br />

modes of transportation in consultation with the ITS Partnership, the SACOG project manager, and the<br />

Regional <strong>Plan</strong>ning Partnership.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 3 Community Outreach <strong>Plan</strong><br />

02/09/05


4. MEETINGS AND WORKSHOPS<br />

The SACOG ITS Partnership is a committee composed of staff from jurisdictions with an interest or<br />

active involvement in ITS planning and deployment. The project team will meet with the Partnership at<br />

project initiation to review the project scope, schedule, process, deliverable review procedures and<br />

answer any questions about the project. A PowerPoint presentation will be prepared to support the team<br />

presentation. In addition, the project team will seek input from the Partnership on relevant stakeholders,<br />

identification of ITS champions and other matters needing local input. After this initial presentation, the<br />

project team will make project status presentations to the committee as appropriate. [February 2, 2005]<br />

The SACOG Regional <strong>Plan</strong>ning Partnership is a committee composed of staff from jurisdictions<br />

throughout the SACOG region representing transportation, planning, and air quality interests. In<br />

addition, state and federal transportation and air quality representatives serve on the committee along<br />

with some community interest groups. The project team will meet with this group at the project<br />

initiation and cover the same items as noted for the ITS Partnership; however, since most of these<br />

committee members are not familiar with ITS, the project team will also provide a short informative<br />

presentation on what is ITS. After this initial presentation, the project team will provide monthly status<br />

reports as requested by the project manager. [February 2, 2005]<br />

4.1 Project Stakeholder Kick Off Meeting [March 8, 2005]<br />

The project kick off meeting will be scheduled shortly after the Partnerships’presentation and<br />

will be held at the SACOG offices. Invitees will include all relevant stakeholders in the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> preparation as noted above. Invitations will be sent via email at least two<br />

weeks before the scheduled meeting and will include the purpose and intent of meeting. A<br />

courtesy email or phone call will be made two days before the kick off meeting to remind and<br />

encourage folks to attend. The kick off meeting will be run as working sessions allowing<br />

participants to actively participate.<br />

The kick off meeting will be four hours with the first two hours consisting of a high level<br />

presentation oriented for non­technical attendees, followed by discussion and questions. A<br />

PowerPoint presentation will be used to support the team presentation. The second part of the<br />

kick off meeting will be more technical and interactive. It is anticipated that only parties<br />

interested in the technical aspects of the study will stay. Each two hour session will be segmented<br />

by a lunch break. Arrangements for lunch will be coordinated with SACOG (however,<br />

participants may be responsible for their own lunch). The notes of the kick off meeting<br />

comments will be prepared. The meeting will be facilitated as required. The agenda for the kick<br />

off meeting may include (may vary on actual agenda):<br />

AM SESSION<br />

• Project overview and schedule<br />

• Overview of process for preparing and approving the architecture, maintenance plan and<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

• Description of ITS and its value in mobility<br />

• Link between ITS and land use planning and transportation planning; and how ITS can assist<br />

in meeting land use and transportation goals<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 4 Community Outreach <strong>Plan</strong><br />

02/09/05


• Presentation of regional planning efforts (studies, general plan updates, transportation<br />

planning efforts)<br />

• Presentation of current ITS Vision document<br />

PM SESSION<br />

• Presentation and review of draft inventory of ITS in Sacramento region<br />

• Comments on current ITS Vision document<br />

• Presentation of gaps between existing and planned ITS deployment<br />

• Identification and agreement on regional and local objectives for the use of ITS<br />

It is anticipated that most participants will be technical staff as well as some management and<br />

policy staff. Invitations to the SACOG Board or other elected officials to the kick off meeting<br />

will be included.<br />

4.2 Stakeholder Workshop #1 [March 30, 2005; 9:00 AM – 4:00 PM; at SACOG]<br />

The first stakeholder workshop will be held after draft materials for the maintenance plan,<br />

regional architecture, operational concept, market packages and their prioritization are available<br />

for review and comment for at least one week prior to the meeting. All stakeholders will be<br />

invited. The same invitation process and timing will be used.<br />

The workshop format will be similar to the kick off meeting to allow non­technical participants to<br />

learn about ITS and the project during the first hour of the meeting, but allow key stakeholders to<br />

stay for the technical review session. The primary focus of the workshop will be technical. The<br />

workshop will be facilitated and comments recorded to identify all issues, areas of agreement, and<br />

areas of disagreement. All comments will be submitted in writing to the SACOG project<br />

manager and forwarded to the consultant after resolving any conflicting comments in<br />

collaboration with the project team. The agenda may include (content and order of items may<br />

vary):<br />

• Presentation of regional planning efforts and priorities;<br />

• Presentation and comments on the maintenance plan;<br />

• Presentation and comments of the draft architecture;<br />

• Presentation and comments on the operational concept (roles and responsibilities); and<br />

• Suggested project priority.<br />

Action items or recommendations from the workshop will be posted to the web site.<br />

4.3 Stakeholder Workshop #2 [May 10, 2005; 9:00 AM – 4:00 PM; at SACOG)<br />

The second and final stakeholder workshop will be focused on finalizing all documents in<br />

preparation for their inclusion in the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> document. The workshop will<br />

again be open to all interested parties and stakeholders. The same protocol will be used to invite<br />

participants. A presentation supported by PowerPoint will be used to describe revisions and final<br />

documents. All materials will be distributed at least one week prior to the meeting. Comments<br />

sent via email within two weeks after the workshop will be incorporated. SACOG will receive<br />

the comments and resolve conflicting comments in collaboration with the project team. Only<br />

comments on the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will be taken at this workshop.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 5 Community Outreach <strong>Plan</strong><br />

02/09/05


All comments received at the first workshop will be listed along with a response by the project<br />

team. Areas of disagreement will be highlighted, if any exist, and the project team will facilitate<br />

discussion to move the parties to agreement. The agenda will include:<br />

• Revisions to the draft architecture (final architecture presentation);<br />

• Revisions to the maintenance plan (final maintenance plan presentation);<br />

• Project list and timeframe for deployment(present draft and discuss comments);<br />

• Performance criteria;<br />

• Proposed methods for measuring performance criteria;<br />

• Revisions to roles and responsibilities (final operational concept);<br />

• List of agreements (e.g. MOU); and<br />

• Draft <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> incorporating all of the above.<br />

4.4 SACOG Board Workshop [March 17, 2005]<br />

At a major milestone in the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> development, the project team will<br />

prepare a PowerPoint presentation and/or materials to be presented at a workshop of the SACOG<br />

Board. The workshop will consist of an overview of the project, an understanding of ITS<br />

planning and deployment in the region and how ITS relates to and supports the land use and<br />

transportation planning currently underway in the region. This presentation will be consistent<br />

with the information presented at the kick off meeting.<br />

The workshop will also include a high level overview of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. The<br />

PowerPoint presentation and supporting materials will be provided to SACOG staff by February<br />

24, 2004.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 6 Community Outreach <strong>Plan</strong><br />

02/09/05


5. PROJECT AWARENESS AND EDUCATION<br />

5.1 Project Web Site<br />

Project web pages will be designed by the project team for inclusion on the SACOG web site.<br />

The web pages will be a major educational and project awareness tool. It will include all<br />

materials prepared for meetings including meeting schedule, meeting notices, and agendas,<br />

meeting notes, the meeting PowerPoint presentations, all deliverables that require review and<br />

comment will be posted to the web site. Once documents are updated, they will be replaced with<br />

the newer version to maintain version control unless SACOG can accommodate an archived<br />

report file. All stakeholders will be directed to the web site by an email notification list with<br />

appropriate notices.<br />

5.2 Stakeholder Email List and Notification Process<br />

The stakeholder email list will be initially developed using the rosters of the ITS Partnership, the<br />

Regional <strong>Plan</strong>ning Partnership, land use planners from each jurisdiction, community groups with<br />

an interest in ITS, and other interested parties as noted above. The list will be updated as needed<br />

during the course of the project. The email list will be the primary form of communication to<br />

notify stakeholders of meetings, availability of deliverables, and review timeline and deadline for<br />

comments.<br />

5.3 Regional Report Articles<br />

Two articles will be prepared, at major project milestones, in consultation with the project<br />

manager. The purpose of the articles is to convey awareness and education of ITS as well as the<br />

project through whatever means is available to SACOG. The articles will be prepared for the<br />

SACOG Regional Report in layman language.<br />

5.4 PowerPoint Presentation<br />

A “library”of PowerPoint slides will be developed to convey the messages and present agenda<br />

items identified in the above meetings. The PowerPoint slides will be segmented for each<br />

meeting beginning with the ITS Partnership and Regional <strong>Plan</strong>ning Partnership presentations; and<br />

modified as needed for each subsequent meeting. In some instances the same material will be<br />

used for different meetings and audiences.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 7 Community Outreach <strong>Plan</strong><br />

02/09/05


6. FACILITATE TECHNICAL REVIEW AND STAKEHOLDER<br />

INVOLVEMENT<br />

It is anticipated that there will be two levels of involvement in this project. First, the traditional ITS<br />

staff who implement, manage, and operate ITS projects in the region will be actively involved in the<br />

development of the architecture, maintenance plan, and <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. This group will be<br />

closely involved in all aspects of the project including meeting attendance, a high level of interaction<br />

and review of all deliverables. Use of meetings as well as electronic distribution of materials will<br />

provide flexibility to those staff in accessing material and providing comments via email. In instances<br />

where a number of key staff do not attend meetings, but follow up discussion is required, an optional<br />

one hour teleconference will be scheduled after each Stakeholder Workshop to capture comments and<br />

questions at the discretion of the project team.<br />

Second, newcomers and interested parties will most likely attend part or all of the meetings but with<br />

limited technical knowledge. Use of the project web site as an information tool with other web site<br />

links providing additional references and information about ITS will allow those parties to obtain more<br />

information about ITS, access project related deliverables without physically showing up for meetings<br />

and allow for comments. The project web site information will support the layman type of presentation<br />

material that will be used by the project team.<br />

To facilitate attendance, and meeting discussion and review, the meeting schedule will be posted to the<br />

web site prior to the kick off meeting and distributed at the kick off meeting, materials for each meeting<br />

will be posted to the web site at least one week prior to the workshop or meeting, and a reminder email<br />

notice of meetings, review period deadlines, and other appropriate milestones will be sent to all<br />

stakeholders.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 8 Community Outreach <strong>Plan</strong><br />

02/09/05


7. BUILDING CONSENSUS<br />

The development of a regional architecture and maintenance plan is based on a consensus model in<br />

which one step builds upon the next. Consensus will be obtained by first providing layman presentation<br />

of the material, then delving into the more technical issues with the traditional stakeholder group,<br />

finding areas of agreement and disagreement through discussion; and finally finding those issues that<br />

are “deal killers”.<br />

Areas of disagreement will be facilitated by working with each party to identify the underlying concerns<br />

or issues associated with disagreements. This will be accomplished with follow up phone calls to the<br />

concerned stakeholders after the stakeholder workshops. In consultation with the project manager,<br />

revisions will be proposed or areas of disagreement may be deleted.<br />

Consensus needs to build upon a common understanding of the project purpose and objectives, project<br />

deliverables, allowing for adequate discussion and comment, and facilitating a discussion of areas of<br />

disagreement.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Outreach <strong>Plan</strong>.doc 9 Community Outreach <strong>Plan</strong><br />

02/09/05


Appendix B


INTELLIGENT TRANSPORTATION SYSTEMS (ITS)<br />

UPDATED VISION FOR THE SACRAMENTO REGION<br />

September 1, 2005<br />

Why Consider Intelligent Transportation Systems in Regional <strong>Plan</strong>ning?<br />

Sacramento’s population is projected to grow by one million people over the next 20<br />

years. While this growth will generate more inter­ and intra­regional travel, transportation<br />

agencies are limited in the number and scope of infrastructure projects they can undertake<br />

to accommodate the additional travel by households and businesses. Seeking a solution<br />

to this dilemma, regional transportation agencies have embraced Intelligent<br />

Transportation Systems (ITS) to help them improve the operating efficiency of our<br />

existing infrastructure. ITS helps emergency service agencies reduce response time and<br />

clear accidents sooner. Roadway technologies are available that reduce stop­and­go<br />

traffic conditions, thereby improving mobility on our roadways and reducing vehicle<br />

emissions. ITS technologies that improve timeliness and facilitate transfers are the<br />

cornerstone of efforts to expand transit operations. Traveler information, made available<br />

via the internet, telephone, or smart transit kiosks, will help people make better decisions<br />

about when, where, and how to travel. Collectively, these and other ITS technologies<br />

will improve mobility and accessibility throughout the region without relying solely on<br />

major infrastructure investments.<br />

ITS and the Goals of the 2025 Metropolitan Transportation <strong>Plan</strong><br />

The ten goals of the MTP are listed below and followed by brief descriptions of how ITS<br />

can help achieve those goals.<br />

1. OVERARCHING GOAL: QUALITY OF LIFE<br />

Develop a fully integrated, multi­modal transportation system to serve as a catalyst<br />

to enhance the quality of life enjoyed by the current and future residents of the<br />

Sacramento region.<br />

ITS is the technology needed to develop a fully integrated, multi­modal<br />

transportation system. With the ability of ITS to enhance and integrate transit<br />

services, smooth traffic flow, and provide traveler information, the region can<br />

achieve this goal with a likely benefit of reduced vehicle emissions.<br />

2. ACCESS AND MOBILITY<br />

Improve access to goods, jobs, services, housing, and other destinations; provide<br />

mobility for people and goods throughout the region, in a safe, affordable, efficient<br />

and convenient manner.<br />

ITS will be a critical component in achieving this goal. Its provides the technology needed


to integrate various transit services, improve transit timeliness, create new Bus Rapid<br />

Transit (BRT) transit trunk lines, and eventually make possible neighborhood­scale<br />

paratransit services that provide virtual door­to­door access either as a stand­alone<br />

service or as a feeder service to transit trunk lines. Traffic Operations Centers (TOC) will<br />

be able to leverage this ITS infrastructure investment to increase traveler mobility using<br />

applications that will allow engineers to remotely monitor the roadway system and<br />

optimize operations according to changing conditions throughout the day. These<br />

technologies can also be used to reduce conflicts between non­motorized modes and<br />

vehicles. Traveler information made available via STARNET, will help residents make<br />

travel decisions that best meet their needs given conditions on the region’s roadways and<br />

the availability of transit.<br />

3. AIR QUALITY<br />

Develop a transportation system and related strategies that contribute to achieving<br />

healthy air in the region.<br />

There are two important ways ITS may help reduce vehicle emissions. First, the transit<br />

improvements mentioned above will make bus and light rail service a more convenient and<br />

viable option for travelers in the region. With even a modest number of trips shifting from<br />

auto to transit, cold starts and VMT may be reduced thereby reducing emissions. For auto<br />

trips, ITS can be employed to smooth traffic flow thereby possibly reducing stop­and­go<br />

conditions, which tend to have higher rates of emissions on a per mile basis.<br />

4. TRAVEL CHOICES<br />

Provide affordable, convenient, safe, and integrated travel choices.<br />

As mentioned above, ITS is the technology needed to integrate the various modes of transit<br />

in the region. Not only can ITS integrate modes of transit (paratransit, bus, and rail), it<br />

can integrate service between transit districts creating a potentially seamless system that<br />

will enable travelers to access most parts of the region. With the deployment of ITSenhanced<br />

paratransit service, transit can become a virtual door­to­door service making it<br />

a convenient alternative to the automobile. On­board cameras and cameras at transit<br />

stops will improve the security of the transit system by making surveillance easier and<br />

uninterrupted. Advances in signal operations have the potential to help reduce vehicle<br />

conflicts with bicyclists and pedestrians. Additionally, traveler information made<br />

available via STARNET will help people make better decisions about mode, route, and time<br />

of travel.<br />

5. ECONOMIC VITALITY<br />

Enhance the economic vitality of our region by efficiently and effectively<br />

connecting people to jobs, goods, and services, and by moving goods within our<br />

region and beyond with an integrated multi­modal freight system.<br />

In addition to increasing the efficiency of transit and the roadway system, ITS is the<br />

technology that businesses can use to improve the efficiency of moving goods and services<br />

throughout the region. Improvements in freight movement are already being seen from<br />

weigh­in­motion sensors in the roadway. Other improvements will be possible using real­<br />

2


time roadway condition information, made available via STARNET, enabling businesses to<br />

re­route or re­schedule commercial vehicles according to changing conditions on the<br />

system. Not only will businesses benefit from improved freight movement, but also their<br />

employees will have better access to jobs by focusing initial ITS improvements on<br />

corridors that feed job centers in the region. Access improvement will come in the form of<br />

improved transit service, as well as in the ability of TOCs to integrate operations across<br />

jurisdictional boundaries. These interconnected TOCs will be able to maintain roadway<br />

capacity during peak periods by facilitating faster accident clearing, adjusting signals to<br />

smooth traffic flow, and providing alternate routes when needed.<br />

6. EQUITY<br />

Pursue a transportation system that addresses the needs of all people in all parts of<br />

the region and assure that impacts of transportation projects don’t adversely affect<br />

particular communities disproportionately.<br />

Focusing ITS improvements on transit in corridors feeding job centers not only addresses<br />

unmet transit needs in those corridors, but also helps balance investments made in<br />

roadway improvements. While initial ITS deployments will be in select priority corridors;<br />

they will nonetheless help expand and improve the transit system making it a more<br />

attractive option for travelers. For those who are unable or unwilling to drive, these ITS<br />

transit applications will noticeably improve the level of service in existing and new transit<br />

corridors, providing greater frequency, timeliness, and easier transfers. These ITS<br />

improvements will also help traffic engineers relieve congestion in many of the same<br />

corridors by adding functionality that will reduce stop­and­go traffic conditions.<br />

Consideration for bike and pedestrian movement can also be included making this a<br />

comprehensive corridor improvement effort.<br />

7. TRANSPORTATION AND LAND USE<br />

Influence land use policies to improve access to jobs, services and housing to<br />

everyone in the region by using market forces and the regulatory process.<br />

ITS will be used to create BRT corridors like those planned for Stockton Blvd. and Watt<br />

Ave. These new trunk line transit facilities can be targeted for transit oriented<br />

development (TOD) improvements such as those that have come out of the Transit for<br />

Livable Communities (TLC) effort at Regional Transit. Just as the TLC planning effort<br />

focused on station area land use plans that would support light rail, a similar planning<br />

effort can be undertaken for BRT corridors. Such an effort will explore how to densify<br />

areas along BRT corridors via redevelopment and infill, thereby supporting transit and<br />

helping to reduce sprawl.<br />

8. FUNDING AND REVENUE<br />

In order to adequately fund the <strong>Plan</strong>, develop appropriate, innovative, equitable,<br />

and stable funding sources (both short­ and long­term) and identify cost­reduction<br />

measures.<br />

While ITS will have to compete with other projects for funding, TEA21 (and likely<br />

3


subsequent transportation bills) includes discretionary money for ITS integration, which is<br />

distributed via an earmarking process. The earmarks provide up to 50 percent of project<br />

cost with a required 20 percent local match. That means that a $1,000,000 ITS project can<br />

potentially cost the region only $200,000 (not including the opportunity cost of the 30<br />

percent paid for with other federal funds). The ITS earmarks provide a means to leverage<br />

local and federal funds for projects with an ITS integration component.<br />

9. HEALTH AND SAFETY<br />

Improve the health of our residents by developing systems that would encourage<br />

walking and biking, and improve the safety and security of people on all modes in<br />

all areas.<br />

An outcome of increasing transit service would likely be an increase in walking and biking<br />

to access the transit network. Even if a neighborhood paratransit service were<br />

implemented, patrons would still have to walk short distances between their origin or<br />

destination and transit stops. Transit­oriented development along BRT corridors would<br />

also create urban designs conducive to walking and biking. Such designs coupled with<br />

signal timing that accommodates pedestrian and bike movement could create a much safer<br />

environment for non­motorized modes.<br />

As mentioned above, ITS could help reduce emissions and resultant respiratory distress.<br />

Also discussed above are the improvements in safety resulting from monitoring<br />

technologies at transit stops and on vehicles. Cameras on roadways and signal<br />

preemption technology would also accelerate the detection of emergencies and reduce the<br />

response time of fire, police, and ambulance personnel. Additionally, an ITS enhanced<br />

transportation system can help reduce vehicle emissions by encouraging more transit use<br />

and by smoothing traffic flow thereby minimizing stop­and­go conditions, which tend to<br />

have a higher level of emissions on a per­mile basis.<br />

10. ENVIRONMENTAL SUSTAINABILITY<br />

Develop the transportation system to promote and enhance environmental quality<br />

for present and future generations.<br />

As mentioned above, ITS­enhanced BRT could lead to TOD land use designs along these<br />

transit trunk line corridors. Such development reduces pressure to convert agriculture and<br />

other open space for future development. As well, TODs supports walk, bike and transit<br />

use, which translates to a reduction in vehicle use and resultant emissions. Additionally,<br />

ITS will help reduce stop­and­go traffic conditions, which tend to have higher levels of<br />

vehicle emissions.<br />

4


Appendix C


TABLE OF CONTENTS<br />

ITS EXISTING CONDITIONS REPORT<br />

1. INTRODUCTION...................................................................................................................................1<br />

1.1 <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Background ..................................................................................1<br />

2. EXISTING CONDITIONS REFERENCES...............................................................................................3<br />

3. COMMON ISSUES ................................................................................................................................5<br />

APPENDIX A – EXISTING CONDITIONS SUMMARIES ...............................................................................6<br />

APPENDIX B – ITS PROJECT INVENTORY..............................................................................................72<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 i Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


1. INTRODUCTION<br />

This report is the output for Task 1.1: Existing Conditions Summary Report of the Sacramento Council<br />

of Governments (SACOG) Intelligent Transportation Systems (ITS) <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. It<br />

contains an evaluation summary of numerous existing plans and studies of local and regional agencies<br />

in the Sacramento Region. The existing plans and studies often contain valuable recommendations or<br />

strategies for growth that could benefit from the addition of advanced technology. The Existing<br />

Conditions Summary Report contains a summary of key recommendations from each plan or study that<br />

pertain to land use and circulation (transportation) growth issues.<br />

1.1 <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Background<br />

This <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> replaces the 1996 Early <strong>Deployment</strong> <strong>Plan</strong> and updates the<br />

Sacramento ITS Regional Architecture which was completed in 2001. This <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> will incorporate work completed since the Early <strong>Deployment</strong> <strong>Plan</strong> was<br />

released. The project addresses the current USDOT Rule and Federal Transit Administration<br />

Policy for National ITS Architecture, and provides the additional required detail in the following<br />

areas: new subsystems, operational concept, system functional requirements, system interfaces,<br />

project sequencing, and agency operational agreements. The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will<br />

bring the Sacramento region into full compliance with Architecture requirements; provide a<br />

vision for ITS; outline a program of low, medium and high priority projects; identify a funding<br />

strategy; and establish a plan for managing, integrating and operating the ITS elements in the<br />

region that are to be implemented over a designated planning period.<br />

The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will also incorporate and build upon recent efforts by various<br />

local agencies and SACOG which demonstrate the importance of land use in planning for future<br />

transportation improvements, and the interrelation between land use and circulation. This<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will represent a first effort to integrate ITS planning and ITS project<br />

deployment strategies within the broader transportation and land use planning efforts. The<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will also address ways in which advanced technologies can improve<br />

mobility and air quality in the region.<br />

The individual elements of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> project are listed on the following<br />

page. The items in bold have been completed or are part of the current deliverable. Throughout<br />

the project, many sections will be completed as separate deliverables. When combined, the<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will culminate in a comprehensive, usable document to guide future<br />

ITS deployment in the region.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 1 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Project<br />

TASK 1: DEVELOP OUTREACH PROGRAM<br />

TASK 1.1: EXISTING CONDITIONS SUMMARY REPORT<br />

TASK 1.2: DEVELOP OUTREACH PLAN<br />

TASK 2: PLANNING PROCESS<br />

TASK 2.1: GAP ASSESSMENT<br />

TASK 2.2: REFINE ITS VISION<br />

TASK 2.3: MARKET PACKAGES<br />

TASK 2.4: UPDATE REGIONAL ITS ARCHITECTURE<br />

TASK 3: STRATEGIC DEPLOYMENT PLAN<br />

TASK 3.1: PROJECT SEQUENCING<br />

TASK 3.2: AGREEMENTS<br />

TASK 3.3: STRATEGIC DEPLOYMENT PLAN REPORT<br />

TASK 3.4: EXECUTIVE SUMMARY<br />

TASK 4: MAINTENANCE PLAN<br />

TASK 4.1: MAINTENANCE PLAN<br />

THIS REPORT<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 2 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


THIS REPORT<br />

2. EXISTING CONDITIONS REFERENCES<br />

Forty-one documents were reviewed to provide background for the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>, to<br />

provide an update since the Early <strong>Deployment</strong> <strong>Plan</strong> was released, and to strengthen the connection<br />

between land use and transportation. The documents are listed below, along with their dates of<br />

publication. In Appendix A, each document is summarized by its agency, main purpose, and<br />

recommendations. For consistency, content is taken directly from the source document with<br />

representative recommendations chosen from each document typically pertaining to land use and<br />

transportation concerns. For quick reference, URL addresses appear where the document is available on<br />

the internet. Depending on the type of publication (for example, a General <strong>Plan</strong> vs. an ITS Master<br />

<strong>Plan</strong>), the documents also contain differing levels of granularity and detail depending on the document’s<br />

purpose. Documents for areas adjacent to SACOG’s jurisdiction but deemed to have or potentially have<br />

effects on this SDP are also included (for example, the Bay Area Regional ITS <strong>Plan</strong>).<br />

ITS projects listed in these documents are listed separately in the Project Inventory in Appendix B.<br />

They are categorized according to three categories: Existing, <strong>Plan</strong>ned (potential projects recommended<br />

for implementation), and Programmed (projects with allocated funding awaiting implementation).<br />

These projects will be incorporated into this <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

List of Background Documents for this SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Report Date Land<br />

Development<br />

SACOG Blueprint Transportation/Land Use Study Dec 2004<br />

SACOG Metropolitan Transportation <strong>Plan</strong> 2025 May 2002<br />

City and County General <strong>Plan</strong>s<br />

City of Citrus Heights General <strong>Plan</strong> Nov 2000<br />

City of Davis General <strong>Plan</strong> May 2001<br />

City of Elk Grove General <strong>Plan</strong> Jan 2005<br />

City of Isleton Comprehensive General <strong>Plan</strong> and<br />

Environmental Impact Report<br />

City of Lincoln General <strong>Plan</strong> – Goals and Policies<br />

Report<br />

Town of Loomis General <strong>Plan</strong> 2001<br />

Sept 2000<br />

Sept 2003<br />

City of Placerville General <strong>Plan</strong> Policy Document Jan 1989<br />

City of Rancho Cordova General <strong>Plan</strong> Aug 2004<br />

City of Rocklin General <strong>Plan</strong> Apr 1991<br />

City of Roseville General <strong>Plan</strong> 1992<br />

City of Sacramento General <strong>Plan</strong> 2004<br />

City of South Lake Tahoe General <strong>Plan</strong> Apr 1999<br />

City of West Sacramento General <strong>Plan</strong> 2000<br />

City of Woodland General <strong>Plan</strong> 2002<br />

General Category<br />

Transportation<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 3 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


List of Background Documents for this SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> (continued)<br />

General Category<br />

Report Date Land<br />

Development<br />

Transportation<br />

City and County General <strong>Plan</strong>s (continued)<br />

Yuba City General <strong>Plan</strong> Apr 2004<br />

El Dorado County General <strong>Plan</strong> Jul 2004<br />

Placer County General <strong>Plan</strong> Update Aug 1994<br />

Sacramento County General <strong>Plan</strong> Dec 1993<br />

Sutter County General <strong>Plan</strong> Nov 1996<br />

Yolo County General <strong>Plan</strong> Jul 1993<br />

Yuba County General <strong>Plan</strong> Dec 1996<br />

Transportation and ITS <strong>Plan</strong>s<br />

Sacramento Transportation ARea NETwork<br />

(STARNET) Needs Assessment<br />

Nov 2001<br />

City of Elk Grove ITS Master <strong>Plan</strong> Nov 2004<br />

City of Citrus Heights ITS Master <strong>Plan</strong> Nov 2004<br />

City of Roseville ITS Master <strong>Plan</strong> Feb 2005<br />

Sacramento Regional ITS Architecture Jun 2001<br />

Placer Parkway Interconnect Project Jan 2000<br />

Elk Grove – Rancho Cordova – El Dorado<br />

Connector Concept <strong>Plan</strong><br />

Aug 2004<br />

Sacramento Exploratory Process 1998<br />

San Joaquin Valley ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Sept 2001<br />

Tahoe Gateway ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> 2002<br />

Tahoe Basin ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Mar 2003<br />

Bay Area Regional ITS <strong>Plan</strong> Jun 2004<br />

Regional Street Network and Address Database<br />

System Architecture and Design<br />

Regional Transit Multi-Corridor Study – System<br />

Expansion and Phasing Strategy<br />

California Statewide ITS Architecture and System<br />

<strong>Plan</strong><br />

Feb 2002<br />

Jun 2001<br />

October 2004<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 4 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


3. COMMON ISSUES<br />

Among the reports above, prevalent general themes include the following:<br />

Encourage mixed use developments, “village concept” developments, transit-oriented<br />

developments. Encourage land use plans that support public transit.<br />

Enhance the accessibility and attractiveness of existing and planned employment areas.<br />

Focus growth inward (infill development, using existing assets).<br />

Facilitate integration among different technologies, applications, and jurisdictions (for example,<br />

through Transportation Management Centers or agreements between neighboring and overlapping<br />

jurisdictions). Investigate different ITS solutions.<br />

Provide intermodal choices – Encourage and facilitate transit, bicycle, and pedestrian modes of<br />

transportation. Reduce automobile use by improving transit service. Encourage carpools and<br />

vanpools.<br />

Improve emergency response capabilities.<br />

Ensure safety (for example, minimizing cut-through traffic in residential areas).<br />

Decrease noise and air pollution.<br />

Provide or improve traffic signals and control. Use signal pre-emption where beneficial.<br />

Revitalize existing downtown areas. Transform and revitalize existing commercial corridors.<br />

Designate truck routes and facilitate improved goods movement.<br />

Standardize data types and nomenclature (for example, as described in the Regional Street Network<br />

and Address Database System Architecture and Design).<br />

Future <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> tasks and deliverables will draw upon the information in these<br />

documents. The next task is to take the information gathered on the existing conditions to prepare the<br />

Gap Assessment, which is part of the “User Needs and User Services” section in the Final <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> Report. It will discuss existing projects and subsequent gaps pertaining to different<br />

service areas (for example, service areas such as traffic management, public transportation, and traveler<br />

information or commercial vehicle operations). This is a major step toward identifying and refining the<br />

recommended ITS deployment solutions in the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 5 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


APPENDIX A – EXISTING CONDITIONS SUMMARIES<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 6 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE<br />

PURPOSE<br />

SUMMARY<br />

SACOG Blueprint Transportation/Land Use Study<br />

(Special Report/Summary: www.<strong>sacog</strong>.org)<br />

SACOG<br />

Approved December 2004<br />

The Blueprint Proj ect is an integrated, coordinated effort for regional<br />

growth over the next 50 years. Stakeholders include the public, local<br />

officials, environmental advocates, development groups and business<br />

leaders. Extensive input was solicited through workshops, public telephone<br />

polls, and forums.<br />

Base Case for 2050: result if current growth patterns continue<br />

Preferred Blueprint Scenario: built on principles of smart growth<br />

o Detailed maps depict more housing choices, developed<br />

areas, protection of natural resource areas, and more<br />

transportation choices.<br />

o Typical residents living in a future typical of the Preferred<br />

Blueprint Scenario in 2050 would probably live in a house on<br />

a smaller lot, in a neighborhood with some larger houses<br />

and some attached row houses, apartments and<br />

condominiums. They would drive to work, but the trip<br />

would be shorter than today, and the time needed to get<br />

there would be about the same as today. Sometimes they<br />

might take the train or bus. Most of their shopping and<br />

entertainment trips would still be in a car, but the<br />

distances would be shorter. And some of these shopping<br />

trips might be taken by walking or biking down the block to<br />

a village or town center that has neighborhood stores with<br />

housing on top of them, and a small park or plaza.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Detailed SMART GROWTH principles upon which the Preferred Blueprint Scenario is based:<br />

Housing Choice and Diversity: Providing a variety of places where people can live - apartments,<br />

condominiums, townhouses, and single-family detached homes on varying lot sizes - creates<br />

opportunities for the variety of people who need them: families, singles, seniors, and people<br />

with special needs. Under the Blueprint Scenario, most housing would still be detached singlefamily,<br />

but about 17 percent would be single-family homes on small lots while 35 percent would<br />

be attached homes.<br />

Use Existing Assets: In urbanized areas, development on infill or vacant lands, intensification of<br />

the use of underutilized parcels (for example, more development on the site of a low-density<br />

retail strip shopping center), or redevelopment can make better use of existing public<br />

infrastructure. This can also include rehabilitation and reuse of historic buildings, denser<br />

clustering of buildings in suburban office parks, and joint use of existing public facilities such as<br />

schools and parking garages. Under the Blueprint Scenario 13 percent of all new housing, and 10<br />

percent of all new jobs, would occur through reinvestment towards existing assets.<br />

Compact Development: Creating environments that are more compactly built and that use<br />

space in an efficient but aesthetic manner can encourage more walking, biking, and public<br />

transit use, and shorten auto trips. In the Blueprint Scenario, 304 square miles of new land<br />

would be needed for urban uses (vs. 661 square miles needed in the Base Case scenario).<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 7 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

SACOG Blueprint Transportation/Land Use Study<br />

(Special Report/Summary: www.<strong>sacog</strong>.org)<br />

Natural Resources Conservation: This principle encourages the incorporation of public-use<br />

open space (such as parks, town squares, trails, and greenbelts) within development projects,<br />

over and above state requirements. It also includes wildlife and plant habitat preservation,<br />

agricultural preservation and promotion of environment-friendly practices such as energy<br />

efficient design, water conservation and stormwater management, and shade trees to reduce the<br />

ground temperatures in the summer. With the Blueprint Scenario, 102 square miles would be<br />

converted from agricultural to urban uses (vs. 166 miles in the Base Case Scenario).<br />

Design for Quality: The design details of any land use development—such as the relationship to<br />

the street, setbacks, placement of garages, sidewalks, landscaping, the aesthetics of building<br />

design, and the design of the public right-of-way (the sidewalks, connected streets and paths,<br />

bike lanes, the width of streets)—are all factors that can influence the attractiveness of living in<br />

a compact development and facilitate the ease of walking and biking to work or neighborhood<br />

services. In the Blueprint Scenario, 69 percent of people would live in pedestrian-friendly<br />

neighborhoods.<br />

Mixed Use developments: Buildings homes and shops, entertainment, office and even light<br />

industrial uses near each other create active, vital neighborhoods, or villages. This mixture of<br />

uses can be either in a vertical arrangement (mixed in one building) or horizontal (with a<br />

combination of uses in close proximity). These types of projects function as local activity<br />

centers, contributing to a sense of community, where people tend to walk or bike to destinations<br />

and interact more with each other. Separated land uses, on the other hand, lead to more, and<br />

longer, automobile trips because of the distance between uses. In the Blueprint Scenario, 53<br />

percent of people would live in communities with a good, or balanced, mix of land uses by 2050.<br />

Provide Transportation Choices: Developments should be designed to encourage people to<br />

sometimes walk, ride bicycles, ride the bus, ride light rail, take the train or carpool. Use of<br />

Blueprint growth concepts for land use and right-of-way design will encourage use of these<br />

modes of travel and the remaining auto trips will be, on average, shorter. The Blueprint<br />

Scenario reduces the number of trips taken by car by about 10 percent. These trips are shifted to<br />

transit, walking or biking. In the Blueprint Scenario, 38 percent of new housing and 41 percent<br />

of new jobs are located within walking distance of 15-minute bus or train service. The number<br />

of vehicle miles traveled per day per household declines from 47.2 miles to 34.9 miles. Total<br />

time devoted to travel per household per day declines from 81 minutes to 67 minutes. With the<br />

Blueprint Scenario, per capita, there would be 14 percent less carbon dioxide (greenhouse gas)<br />

and particulates (related to asthma) compared to the Base Case.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 8 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE<br />

SACOG Metropolitan Transportation <strong>Plan</strong> 2025<br />

http://www.<strong>sacog</strong>.org/mtp/pdf/Final%20Interim%20MTP%2005-07.pdf<br />

SACOG<br />

May 15, 2002<br />

This plan pursues ten goals [described under “Summary” below and also<br />

described in the ITS VISION document], under an over-arching goal of<br />

improving quality of life.<br />

Quality of life may mean somewhat different things to different people, but it<br />

generally encompasses quiet and safe neighborhoods, affordable housing, j ob<br />

opportunities, good schools, limited environmental pollution, recreational and<br />

social activities— and adequate transportation to allow access to places where<br />

these activities occur. Toward that end, this plan seeks to promote development<br />

that is less dependent on autos, increase transit service and use, control the<br />

spread and amount of congestion, attain clean air, and rein in urban sprawl.<br />

PURPOSE<br />

The region needs a new transportation vision and plan. Even with the high<br />

priority given to transit expansion in this plan, transit ridership is expected to<br />

only slightly more than double; and even with this plan’ s commitment of<br />

regional funds to bicycle and pedestrian proj ects, the share of trips made by<br />

cycling and walking is not predicted to change much. That leaves the region<br />

facing a 40 percent or greater increase in auto travel. Obviously it makes a<br />

difference whether those people will drive alone or ride in carpools, and where<br />

on the system they travel. Steps to reduce travel, or change the way people<br />

travel, will become imperative. The predominance of low-density suburban<br />

development with j obs and shopping separated from residential areas cannot<br />

continue indefinitely. While the region cannot reasonably be expected to build<br />

its way out of congestion, the investments in this plan do make a difference,<br />

lessening congestion in some corridors depending on where the region invests in<br />

more transit and road capacity or land use changes.<br />

This plan will guide the proj ect programming process in two ways — first, by the<br />

requirement that proj ects must be consistent with this plan to be eligible for<br />

funding through the Metropolitan Transportation Improvement Program (MTIP)<br />

process, of which this report is a part, and second, by virtue of the fact that this<br />

plan will directly identify candidate proj ects for funding in the upcoming state<br />

and federal funding cycles.<br />

The Metropolitan Transportation <strong>Plan</strong> places proj ect areas within the context of<br />

ten goals. These ten goals are as follows:<br />

SUMMARY<br />

QUALITY OF LIFE. The plan is designed to meet the needs of everyday<br />

travel for all types of purposes as well as for large regional movements over<br />

the long term. The stakeholders recognized that transportation is closely<br />

connected with many other issues, such as air quality, the environment,<br />

and land use, health, safety, and economic vitality and developed goals and<br />

actions in the plan to address these issues.<br />

ACCESS AND MOBILITY. Access to Downtown Sacramento, other urban core<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 9 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

SACOG Metropolitan Transportation <strong>Plan</strong> 2025<br />

http://www.<strong>sacog</strong>.org/mtp/pdf/Final%20Interim%20MTP%2005-07.pdf<br />

areas, and older suburbs is emphasized in the plan, if infill development is<br />

to be attractive and if jobs are going to continue to expand in these areas.<br />

Access is also affected by barriers such as rivers, railroads, and freeways<br />

themselves that have a limited number of crossings. The American River is a<br />

particularly problematic barrier, since a large amount of development in<br />

Sacramento County exists and is planned on both sides of the river and<br />

there are few bridges.<br />

AIR QUALITY. Continued regional funding for a regional air quality grant<br />

program (SECAT, SACOG’s existing program and successor programs) will<br />

provide incentives for implementing clean air technology, travel reduction,<br />

and other effective air quality strategies, until the region is in attainment.<br />

TRAVEL CHOICES. Major increases in rail, bus, bicycle, and pedestrian<br />

modes are envisioned, along with promotion of telecommuting and sharing<br />

rides, are planned. In this plan, the transit systems of the region will<br />

become integrated through information technology and universal passes,<br />

bicycles will be accommodated on buses and trains, pedestrians will feel<br />

more comfortable crossing arterial streets, and kids will feel safer walking<br />

to school.<br />

ECONOMIC VITALITY. New corridors will connect areas around the<br />

periphery of the urban core, providing better access to the region’s three<br />

major job centers —downtown Sacramento, Rancho Cordova/Folsom, and<br />

South Placer County. The plan also includes significant new light rail and<br />

bus transit, carpool lanes for commuters, and a larger Transportation<br />

Demand Management program to help manage demand. Access to<br />

Sacramento Airport is provided with the Downtown-Natomas-Airport light<br />

rail line and road improvements in the airport vicinity, as well as around<br />

the Port of Sacramento and Mather Airport.<br />

EQUITY. Jobs Access Reverse Commute funding is intended to offer<br />

convenient transit for entry-level workers, particularly those transitioning<br />

from welfare to work. Community circulator van routes will supplement the<br />

mainline transit system, offering more convenient travel by transit from<br />

neighborhoods, particularly important for elderly and disabled persons. A<br />

large increase in paratransit service (door-to-door wheelchair-equipped van<br />

service called for in the ADA) is included for the expected increase in the<br />

elderly population over the plan period.<br />

TRANSPORTATION AND LAND USE. The Community Design grant program,<br />

which could pay for planning grants to local governments and for bicycle,<br />

pedestrian, and streetscape improvements that accompany “smart growth”<br />

projects, would encourage local trips and the use of alternative modes of<br />

transportation. SACOG has also recently initiated a 3-year Transportation-<br />

Land Use Study. This project, which will develop information for the next<br />

update of the MTP, concerns the application of smart growth planning in<br />

the Sacramento Region.<br />

FUNDING AND REVENUE Overall, this plan proposes to spend $7.6 billion for<br />

transit operations and improvements, $6.8 billion for highway, street and<br />

road improvements, $5.9 billion for highway, street and road maintenance<br />

and rehabilitation, and $1.6 billion for other kinds of improvements<br />

(bicycle, pedestrian, community design, demand management, clean air<br />

programs).<br />

HEALTH AND SAFETY. Pedestrian and bicycle plans and projects are<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 10 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

SACOG Metropolitan Transportation <strong>Plan</strong> 2025<br />

http://www.<strong>sacog</strong>.org/mtp/pdf/Final%20Interim%20MTP%2005-07.pdf<br />

specifically allocated $529 million in the plan, both to develop local and<br />

regional systems. Freeway service patrols are also funded in this plan.<br />

Public transit security, both for passengers and their parked cars, is a<br />

priority because people will be much more likely to use transit if they feel<br />

safe doing so. Finally, a replacement of the Folsom Dam Road with a<br />

separate bridge downriver from the Folsom Dam is a national security issue<br />

and a high priority in this plan, with most of the funding expected to come<br />

from the Federal Bureau of Reclamation.<br />

ENVIRONMENTAL SUSTAINABILITY. The air quality program, a continuation<br />

of SECAT, will help the region to attain air quality standards.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Key recommendations among those in the <strong>Plan</strong> include:<br />

The development of a regional ITS communication system that links the operations centers in the<br />

region. In early 1999, a conceptual report on the Sacramento Transportation Area-wide Network<br />

(STARNET) was completed. STARNET soon became a regional priority leading to the<br />

completion of a Needs Assessment Study in late 2001, which identifies system improvements<br />

needed at each operation center in order link them via STARNET.<br />

A list of eighteen ITS projects identified as candidates for federal ITS funding. This list was<br />

compiled by the Partnership to help prioritize projects, mostly corridor improvements, that<br />

support the EDP. The list will continue to be updated as studies are completed and projects<br />

advanced.<br />

The development of a federally-required regional ITS architecture. Through a two-tiered<br />

Federal Highway Administration process, the ITS Partnership developed a draft ITS architecture<br />

in early 2000. This draft became the basis for the final working architecture completed in June<br />

of 2001, which identifies stakeholders, their ITS elements, and the interconnections between<br />

systems.<br />

Significant increases are proposed for the transit system —continued expansion of the Capitol<br />

Corridor train service to the Bay Area; commuter rail service between Davis/Dixon and Auburn<br />

using the UP/Amtrak facilities; light rail extensions to Natomas and Sacramento International<br />

Airport, Cosumnes River College/Elk Grove, from Watt to Antelope, and to West Sacramento;<br />

expansion of bus and van service regionwide, including a large increase in service for elderly and<br />

disabled persons; community circulator vans that serve neighborhoods, commercial areas and job<br />

centers; and bus rapid transit systems in the Stockton, Watt, and Sunrise commute corridors.<br />

The expansions of bus service include more commuter buses that can take advantage of carpool<br />

lanes that are proposed for the freeways.<br />

Access improvements by road include a series of connectors —a Placer Parkway connecting<br />

Roseville at Route 65 to Routes 99/70 near the Sacramento Airport (bordered by conservation<br />

easements), improved connections between Rancho Cordova, Elk Grove, and I-5 (with protected<br />

open space components in unpopulated areas), and a Rancho Cordova to South Placer multimodal<br />

connector. The connector projects, particularly the Rancho Cordova-Elk Grove-I-5<br />

projects, are conceptual at this time and must undergo extensive planning and analysis processes<br />

with community involvement.<br />

Intelligent Transportation Systems (or ITS) - “smart corridors” that can smooth the flow of traffic<br />

on Watt, Greenback/Sunrise, and Arden, signal pre-emption systems for transit and emergency<br />

vehicles, freeway ramp meters, message signs, and cameras, and freeway service patrols to<br />

clear accidents and vehicle breakdowns quickly off of the freeways.<br />

Funding for transportation demand management programs such as the regional rideshare<br />

program, marketing of alternative modes of transportation, and incentive programs for bicycles,<br />

telecommuting, transit use, and carsharing.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 11 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE<br />

PURPOSE<br />

City of Citrus Heights General <strong>Plan</strong><br />

http://www.ci.citrus-heights.ca.us/docs/citrus_heights_gp.pdf<br />

City of Citrus Heights<br />

November 2000<br />

The General <strong>Plan</strong> defines the qualities that make Citrus Heights<br />

a special place and establishes policies and actions to preserve and<br />

enhance the quality of life for the City’s residents, workers, merchants<br />

and visitors.<br />

This General <strong>Plan</strong> also addresses State general plan requirements.<br />

California law requires that every city and county adopt a long-term<br />

General <strong>Plan</strong> that addresses seven specific topics or “elements,”<br />

organized in any format or structure preferred by the community. The<br />

general plan may also address other topics the community feels are<br />

relevant.<br />

The high degree of consistency between the workshop conclusions,<br />

General <strong>Plan</strong> Advisory Committee (GPAC) recommendations and survey<br />

responses can be summarized in the following vision for the future of Citrus<br />

Heights:<br />

Citrus Heights is a highly livable place that:<br />

Is safe because of excellent public services and controlled traffic;<br />

Has a strong sense of identity, character and pride;<br />

Offers ample business and job opportunities in attractive commercial<br />

areas; and<br />

Is supported by a strong and fiscally responsible City government.<br />

SUMMARY<br />

Through the general plan process and resident surveys, the following areas of<br />

emphasis were identified and are addressed throughout the plan:<br />

Single family homes were the most preferred type of future residential<br />

development<br />

the favored commercial development was small-scale, resident-serving<br />

uses like gift shops, restaurants, grocery stores and medical clinics<br />

road maintenance, crime prevention, and creating an attractive visual<br />

environment were cited as the most important actions for preserving<br />

quality of life<br />

traffic was identified as the biggest problem<br />

residents supported extending light rail to Citrus Heights, increasing<br />

bike and walking routes, and reducing traffic<br />

the most popular methods for improving the local economy were using<br />

vacant buildings and lots, redeveloping older shopping centers, and<br />

encouraging new businesses, such as high technology and research and<br />

development<br />

recommended funding priorities by residents included road<br />

maintenance, police protection, street trees, public landscaping, flood<br />

control, drainage improvements, and bus service<br />

the highest rated services and facilities were fire and emergency<br />

medical, police, and parks<br />

the lowest rated services were bus service and road maintenance<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 12 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Citrus Heights General <strong>Plan</strong><br />

http://www.ci.citrus-heights.ca.us/docs/citrus_heights_gp.pdf<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Major General <strong>Plan</strong> Advisory Committee (GPAC) recommendations include the following:<br />

Protect neighborhoods from cut-through traffic;<br />

Discourage strip commercial development along primary arterial streets;<br />

Encourage and facilitate bicycle, pedestrian and transit use;<br />

Diversify the economy to increase job opportunities and the tax base;<br />

Improve library and animal control services; and<br />

Develop a master plan for creeks, trails and open space.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 13 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Davis General <strong>Plan</strong><br />

http://www.city.davis.ca.us/pb/gp/<br />

City of Davis<br />

DATE May 2001<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> strives toward the following Visions of purpose:<br />

Quality of Life<br />

Small Town Character<br />

Diversity<br />

Arts and Culture<br />

Natural Resource Protection and Restoration<br />

Distinct Neighborhood Identity<br />

Broad Range of Services and Businesses<br />

Neighborhood-Oriented Transportation System<br />

Parks and Open Space Program<br />

Agriculture<br />

Synergistic Partnership with UC Davis<br />

Regional Context<br />

Regional Leadership<br />

Accountable, Citizen-Based <strong>Plan</strong>ning<br />

Embracing Technology<br />

The <strong>Plan</strong> covers elements including the following:<br />

Land Use<br />

Circulation<br />

Housing<br />

Conservation<br />

Open Space<br />

Noise<br />

Safety<br />

The <strong>Plan</strong> also overlaps or is adj acent to the following plans and these<br />

interfaces are incorporated into the planning process:<br />

Gateway/Olive Drive Specific <strong>Plan</strong><br />

East Davis Specific <strong>Plan</strong><br />

South Davis Specific <strong>Plan</strong><br />

Bikeway <strong>Plan</strong><br />

RECOMMENDATIONS FROM DOCUMENT<br />

Develop a strategy that targets higher value-added, technology oriented industrial uses that are<br />

attracted to Davis' competitive advantages, particularly its University linkages, educated<br />

workforce and quality of life for employees;<br />

Offer a variety of lot sizes for these industries, including affordable incubator facilities for startups,<br />

flexible R&D space, and large lots (20-50 acre lots that may be assembled) for manufacturing<br />

firms and build-to-suit developments;<br />

Focus growth inward to accommodate population increases. Infill development is supported as an<br />

appropriate means of meeting some of the city’s housing needs.<br />

Create and maintain housing patterns that promote energy conserving transportation methods.<br />

Accommodate new buildings with floor area ratios that can support transit use especially within ¼<br />

mile from commercial areas and transit stops, but maintain scale transition and retain enough<br />

older buildings to retain small-city character.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 14 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


City of Davis General <strong>Plan</strong><br />

STUDY<br />

http://www.city.davis.ca.us/pb/gp/<br />

Support the opportunity for efficient public transit by sitting large apartment complexes on<br />

arterial streets, in the core and near neighborhood centers and the University.<br />

Site local services, retail and recreation strategically to minimize the lengths of trips and to<br />

facilitate walking, bicycling and transit use as alternatives to auto use.<br />

All neighborhoods, both new and existing, should include a centrally located hub or activity node<br />

within walking distance of housing in the neighborhood. Transit stops, neighborhood commercial<br />

uses and activity centers should be in this hub. Hubs should be designed to support transit,<br />

pedestrian and bicycle travel, and to serve neighborhood needs.<br />

Provide attractive streets designed to serve a broad spectrum of travel modes as well as<br />

automobiles.<br />

Balance the needs to provide adequate parking in residential and commercial developments with<br />

the desire to limit automobile travel.<br />

Increase walking and the use of non-polluting forms of transportation, including bicycles.<br />

Reduce automobile use by improving transit service and encouraging transit use.<br />

Develop alternative transportation solutions which will help alleviate peak hour congestion and<br />

improve air quality.<br />

Increase safety of and decrease noise and air pollution from transportation throughout the city.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 15 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Elk Grove General <strong>Plan</strong><br />

http://www.egplanning.org/gp_zoning/general_plan/<br />

City of Elk Grove <strong>Plan</strong>ning<br />

DATE November 19, 2003 (Updated January 5, 2005)<br />

PURPOSE<br />

The General <strong>Plan</strong> is a broad framework for planning the future of the City of<br />

Elk Grove. It is the official policy statement of the City Council to guide the<br />

private and public development of the City in a manner to gain the maximum<br />

social and economic benefit to the citizens. All other City codes and<br />

standards, including Specific <strong>Plan</strong>s and Development Code, must be<br />

consistent with the General <strong>Plan</strong>.<br />

SUMMARY<br />

Although this General <strong>Plan</strong> is expected to guide development until the year<br />

2023 (a 20-year timeframe), changes to the <strong>Plan</strong> are expected to occur as<br />

circumstances change and the City’ s responds to these changes—or alters its<br />

vision for the future.<br />

As required by the California Government Code, the Elk Grove General <strong>Plan</strong><br />

addresses the following seven basic topics:<br />

Land Use<br />

Circulation<br />

Housing<br />

Conservation<br />

Open Space<br />

Noise<br />

Safety<br />

RECOMMENDATIONS FROM DOCUMENT<br />

A pattern of land use which enhances the community character of Elk Grove, provides employment<br />

and shopping opportunities to serve residents and the region, which provides for use of transit,<br />

and which protects Elk Grove’s unique historical and natural features.<br />

The City’s efforts to encourage alternative modes of transportation will therefore focus on<br />

incentives to reduce vehicle use, rather than disincentives (which are generally intended to make<br />

driving and parking less convenient, more costly, or both).<br />

Incentives may include:<br />

Preferential carpool and vanpool parking;<br />

Bus turnouts; and<br />

Pedestrian-friendly project designs.<br />

The City shall encourage an approach to public transit service in Elk Grove which will provide the<br />

opportunity for workers living in other areas of Sacramento County to use all forms of public<br />

transit—including bus rapid transit and light rail—to travel to jobs in Elk Grove, as well as for Elk<br />

Grove workers to use public transit to commute to jobs outside the city.<br />

The City shall regulate truck travel as appropriate for the transport of goods, consistent with<br />

circulation, air quality, congestion management, and land use goals.<br />

The City shall require the installation of traffic pre-emption devices for emergency vehicles<br />

(police and fire) at all newly constructed intersections, and shall seek to retrofit all existing<br />

intersections to incorporate these features.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 16 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Isleton Comprehensive General <strong>Plan</strong> and Environmental Impact<br />

Report<br />

City of Isleton<br />

DATE September 13, 2000<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> has three basic functions:<br />

To enable the City Council, upon the advice of its <strong>Plan</strong>ning Commission,<br />

to express agreement on development policies;<br />

To provide clear guidance in judging whether projects proposed by<br />

public agencies and private developers or individuals are in close<br />

agreement with policies of the General <strong>Plan</strong>; and<br />

To allow and provide the basis for making intelligent amendments to<br />

the <strong>Plan</strong> as time and changing circumstances may dictate, while being<br />

true to its purposes.<br />

The 10 Goals of the General <strong>Plan</strong> are:<br />

The costs and benefits of urbanization are to be balanced through<br />

economic development.<br />

Provide equality in opportunity in the provision and availability of public<br />

services and facilities and in meeting housing needs.<br />

Old and new areas of the community should make a strong contribution<br />

toward maintaining and enhancing the identity of the entire community.<br />

New development and redevelopment is to reflect quality in community<br />

design and image.<br />

The quality of life is to be enhanced by preventing the degradation of<br />

the natural environment and to offset that degradation that has already<br />

occurred.<br />

Existing and future development are to be protected from the hazards<br />

of flooding.<br />

All new development shall be required to pay for the direct and indirect<br />

capital and operating costs associated with that development.<br />

Tax increment revenues of redevelopment shall be allocated to<br />

rehabilitate existing commercial and residential areas and public<br />

facilities, and to create recreation open space.<br />

The open space and amenities of the Sacramento River should be made<br />

more accessible while protecting the river environment.<br />

Existing commercial centers are to be improved and historic structures<br />

are to be preserved to the extent practical.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 17 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Isleton Comprehensive General <strong>Plan</strong> and Environmental Impact<br />

Report<br />

RECOMMENDATIONS FROM DOCUMENT<br />

The following impacts and mitigation measures are described in the Transportation and Circulation<br />

element of the plan.<br />

In the long-range, important intersections within Isleton will reach summer traffic volumes where<br />

signals will be required. Intersection levels of service at State Route 160/ A Street and Route 160/ Main<br />

Street are expected to operate at unacceptable levels of service during peak hours. The intersections<br />

of Terminous Road, Jackson Slough Road and State Route 160 with State Route 12 are expected to<br />

operate at unacceptable peak hour levels of service by the year 2020 or before. The curving alignment<br />

and poor paving condition of Jackson Slough Road will create significant safety concerns and accident<br />

potential. These adverse conditions will be exaggerated by development of an RV Park adj acent to<br />

Jackson Slough Road which will also create traffic congestion on arterial streets of the community.<br />

Mitigation Measures:<br />

Provide traffic signals at the following intersections:<br />

SR 160/A Street<br />

SR 160/Main Street<br />

SR 160/Isleton Road<br />

SR 12/Jackson Slough Road<br />

SR 12/Terminous Road<br />

Realign and reconstruct Jackson Slough Road from Isleton to Terminous Road.<br />

Revise traffic and parking patterns through the Second Street commercial center.<br />

<strong>Plan</strong> for the relocation of State Route 160 South of the City limits.<br />

Provide separate access from State Route 160 to the proposed RV Park at the west end of town.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 18 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Lincoln General <strong>Plan</strong> – Goals and Policies Report<br />

Steering Committee Draft<br />

http://www.westplanning.com/docs/lincoln/pdf/lincoln_steering_comm_20<br />

03_09_19.pdf<br />

City of Lincoln<br />

DATE September 2003<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> update addresses concerns which have arisen in recent<br />

years in the City. These include Community Design, Economic Development,<br />

State Route 65 Bypass Corridor, and City Sphere of Influence.<br />

COMMUNITY DESIGN<br />

Community design and the enhancement of community identity can best be<br />

achieved during the early stages of growth that a community such as Lincoln<br />

is experiencing.<br />

ECONOMIC DEVELOPMENT<br />

Given the extensive amount of growth in the City of Lincoln since the last<br />

General <strong>Plan</strong> was adopted, economic development has become an issue of<br />

increasing importance. Between 1990 and 2000, Placer County’s employment<br />

base grew by 61,000 j obs, with Roseville capturing close to 20 percent of<br />

countywide employment growth during this period. The General <strong>Plan</strong><br />

addresses this issue in both the Economic Development and Land Use and<br />

Community Design Elements.<br />

STATE ROUTE 65 BYPASS CORRIDOR<br />

The SR 65 Bypass proj ect will provide a new alignment of SR 65 through the<br />

Lincoln area. The Bypass proj ect will bring the roadway off towards the west<br />

around the City of Lincoln. The proj ect will be approximately 10 miles long,<br />

ranging between 2 and 4 lanes, and will extend from SR 65 at Industrial<br />

Boulevard in Lincoln to a point on the highway j ust north of Sheridan. The<br />

General <strong>Plan</strong> addresses this issue in the Circulation and Transportation<br />

Element and the land use alternatives.<br />

CITY SPHERE OF INFLUENCE<br />

The Cortese/ Knox/ Hertzberg Act defines a sphere of influence as “ a plan for<br />

the probable ultimate physical boundaries and service area of a local<br />

agency.” In practice, “ ultimate” is defined as 20 years. As part of the<br />

General <strong>Plan</strong> Update, the General <strong>Plan</strong> Team and City staff felt that there<br />

were areas within the current SOI that no longer meet the criteria<br />

mentioned above. Therefore, the land use alternatives developed for the<br />

General <strong>Plan</strong> suggest a reduction in the SOI on the eastern and southwestern<br />

ends of the <strong>Plan</strong>ning Area. At the same time, in order to meet future urban<br />

growth, expansion of the SOI was recommended for consideration on the<br />

northern and western sides of the <strong>Plan</strong>ning Area as well.<br />

This general plan addresses the seven topics (referred to as “ elements” ) of<br />

land use, circulation, housing, open-space, conservation, safety, and noise as<br />

identified in state law (Government Code Section 65302), to the extent that<br />

the topics are locally relevant. It may also include other topics of local<br />

interest, as chosen by the City (Government Code Section 65303).<br />

RECOMMENDATIONS FROM DOCUMENT<br />

promote efficient use of larger vacant parcels and vacant areas of the city by encouraging mixed<br />

use development<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 19 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


City of Lincoln General <strong>Plan</strong> – Goals and Policies Report<br />

Steering Committee Draft<br />

STUDY<br />

http://www.westplanning.com/docs/lincoln/pdf/lincoln_steering_comm_20<br />

03_09_19.pdf<br />

promote the renovations and reuse of existing buildings in the Downtown as mixed use areas<br />

pursue the development of vacant infill parcels in and around the Downtown area<br />

encourage active involvement by individuals and organized citizens in maintaining and upgrading<br />

existing residential neighborhoods<br />

promote and renew the existing central business district in order to provide diversified business<br />

opportunities<br />

attract industrial development that avoids or minimizes substantial pollution, noise, glare, odor,<br />

or other significant offensive activity that would negatively affect adjacent uses and other areas<br />

of the city<br />

design open space areas, bicycle and pedestrian systems, and housing projects so that there is as<br />

much informal surveillance by people as possible to deter crime<br />

ensure that lighting and landscaping plans respond to public safety concerns<br />

coordinate with Caltrans in developing transportation policies pertaining to SR 65 and SR 193 that<br />

are consistent with Caltrans transportation policies for these roadways<br />

coordinate with SACOG in developing transportation policies pertaining to SR 65 and SR 193 that<br />

are consistent with SACOG’s transportation policies for these roadways<br />

coordinate with Placer County Transportation <strong>Plan</strong>ning Agency (PCTPA) in developing City<br />

transportation policies that are consistent with PCTPA’s transportation policies<br />

seek to maintain a minimum level of service (LOS) "C" for City streets and intersections and all<br />

new streets and intersection within the City. For the purpose of this policy, City streets and<br />

intersections exclude state highways<br />

designate truck routes and restrict truck traffic on residential streets<br />

actively pursue measures that will help reduce vehicle trips by maintaining a ridesharing program<br />

minimize the number, properly space, and interconnect traffic signals to maximize progression<br />

and minimize the acceleration/deceleration that produces significantly higher vehicle emissions<br />

and noise levels<br />

promote and support public transit services that meet residents needs<br />

promote the use of public transit through development conditions requiring park-and-ride lots, bus<br />

turnouts and passenger shelters along major streets adjacent to areas of high residential density<br />

expand fixed route transit service where required to serve new development areas, including<br />

direct connections to employment and commercial areas<br />

promote and support the development of local and regional bikeway links as established in the<br />

City Bikeways Master <strong>Plan</strong> and the County Bikeway Master <strong>Plan</strong><br />

provide pedestrian/bicycle crossings at appropriate intervals along new roadways that will<br />

adequately serve new large-scale commercial office, industrial development, and residential<br />

development as well as parks and schools<br />

provide traffic signal phasing that is adequate for bicycle turning and straight-through movements<br />

encourage specific plans and development plans to include design of pedestrian access that<br />

enables residents to walk from their homes to places of work, recreation and shopping<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 20 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Town of Loomis General <strong>Plan</strong><br />

http://www.loomis.ca.gov/index.php?rootPos=2&subPos=2<br />

Town of Loomis<br />

DATE Adopted Update in 2001<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> is intended to provide guidance in a wide variety of<br />

important decisions be the Town’ s elected and appointed officials, and its<br />

staff. California law requires that all provisions of the Zoning Ordinance be<br />

consistent with the General <strong>Plan</strong>, and that no subdivision be approved unless<br />

it is consistent with the General <strong>Plan</strong>. State law also requires that all<br />

municipal decisions on capital improvements planning and budgeting be<br />

preceded by a review of their conformity with the General <strong>Plan</strong>.<br />

The community’ s vision for the future of Loomis is based primarily on<br />

retaining the small town aspects of its character through the revitalization of<br />

the downtown village and the expansion of family-oriented community<br />

facilities; and maintaining the rural aspects of its character by continuing<br />

the pattern of progressively lower residential densities as distance increases<br />

from the downtown, thereby preserving low-intensity agricultural uses and<br />

natural open spaces. Town residents value the community’ s distinct<br />

identity, featuring good public services and facilities, cultural activities, and<br />

agricultural heritage.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Focus more intensive land uses near the downtown and freeway interchange, while maintaining<br />

the predominantly agricultural/rural character of Loomis outside the core area.<br />

Strive for service levels that reflect a balance between mobility, cost-effectiveness, and financial<br />

resources.<br />

Develop standards that protect public safety and provide mobility for all forms of transportation.<br />

Implement additional bicycle facilities that result in increased bicycle usage.<br />

Devote resources for the promotion of transit service that are appropriate for its size and financial<br />

resources using comparable cities as a benchmark.<br />

Take action to minimize cut-through traffic and manage speeds on residential streets.<br />

Roadway extensions or improvements based on 1997 Circulation Study<br />

Develop additional Class II and Class III bicycle facilities<br />

Rail station revitalization<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 21 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Placerville<br />

General <strong>Plan</strong> Policy Document<br />

City of Placerville<br />

DATE January 1989<br />

PURPOSE<br />

As required by State law, the General <strong>Plan</strong> addresses seven elements: land<br />

use, circulation (transportation), housing, conservation, open space, noise,<br />

and safety. The plan analyzes issues of importance to the community, sets<br />

forth policies in text and diagrams for conservation and development, and<br />

outlines specific programs for implementing the policies.<br />

The goals and policies outlined in the <strong>Plan</strong> most focused on the following<br />

problem areas:<br />

SUMMARY<br />

Land Use and <strong>Plan</strong>ning Issues: problems identified in this area ranged<br />

from a concern for the poor quality of recent development to lack of<br />

coordination between the City and County. Several people mentioned<br />

that recent projects have been poorly designed and constructed. Highdensity<br />

residential development in older, low-density neighborhoods<br />

concerned many people. Too much commercial development in<br />

residential areas and the proliferation of shopping centers were also<br />

cited as problems. The amount and pace of growth in Placerville was<br />

frequently mentioned.<br />

Traffic and Circulation Issues: Traffic congestion and circulation<br />

patterns were the most often identified problems. More specifically,<br />

individuals mentioned limited access in and out of parts of the city,<br />

congestion downtown, the narrowness and steepness of streets, poor<br />

road maintenance, heavy traffic on Placerville Drive, and Broadway and<br />

Pacific Streets. By consensus, Highway 50 is the prime contributor to<br />

the traffic problems: the highway bisects the city at grade, includes<br />

numerous signalized intersections, and disrupts cross-town travel. The<br />

intersection of Bedford and Main was frequently cited as the most<br />

congested intersection. Several people noted that the lack of adequate<br />

pedestrian and bicycle facilities created a hazardous situation. Lack of<br />

parking in residential areas and in new commercial developments was<br />

also noted.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Some specific recommendations resulting from the General <strong>Plan</strong> process include the following:<br />

City should expand/annex to keep residential densities low<br />

Growth should be toward Smith Flat<br />

Develop where there are already adequate roads and services<br />

Expand/develop pedestrian facilities<br />

Use a village concept of future development in the city<br />

Increase public transportation opportunities in and out of town<br />

Integrate local services and tourism in downtown area<br />

Add more parking downtown<br />

Provide alternate transportation access<br />

Route delivery trucks, vans and buses around Main Street<br />

Expand bike routes and lanes<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 22 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE<br />

PURPOSE<br />

SUMMARY<br />

City of Rancho Cordova General <strong>Plan</strong><br />

http://gp.cityofranchocordova.org/<br />

City of Rancho Cordova<br />

Ongoing preparation of City’s first General <strong>Plan</strong>, completion by June 2005. A<br />

Vision Book/Interim General <strong>Plan</strong> was adopted in August 2004.<br />

To develop a set of policies and programs for the 96-square mile desired<br />

ultimate boundary. The planning process will incorporate extensive public<br />

outreach, including visioning workshops with the public, monthly public<br />

meetings with the General <strong>Plan</strong> Advisory Committee, and special study<br />

sessions and public hearings with the <strong>Plan</strong>ning Commission and the City<br />

Council.<br />

The Vision Book/ Interim General <strong>Plan</strong> reflects the compilation of ideas from<br />

the community on a wide variety of topics related to the future of Rancho<br />

Cordova. It includes ideas which relate to specific sites and issues, as well<br />

as ideas which are more conceptual in nature. Some of the visions can be<br />

achieved in the near term and will be reflected in the short-term<br />

development of the city; others may take longer to achieve and will rely on<br />

regional cooperation and the dedication of the City to reach the goals.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Land uses in Rancho Cordova should generally reflect the types and intensity of land uses shown in<br />

the Blueprint’s “Scenario C” which envisions relatively higher overall residential densities than<br />

currently in place. While not establishing “build-out targets”, this land use scenario anticipates<br />

the addition of approximately 54,000 to 60,000 new households and 48,000 new hobs in the<br />

Rancho Cordova city limits (based on assumptions used in the Blueprint process), with possible<br />

additional growth in the planning area.<br />

Redevelopment along Folsom Boulevard which focuses regeneration of retail development and<br />

Transit-Oriented Development near light rail stations, in particular new the Mills Station light rail<br />

stop and other underutilized areas.<br />

Create walkable neighborhoods and pedestrian oriented new development<br />

Transformation and revitalization of existing commercial corridors and centers and of the City’s<br />

neighborhoods<br />

Reduce congestion on streets and highways<br />

Expanded and improved public transit including light rail, bus, and other modes<br />

Intra-city bus service<br />

User-friendly public transit facilities<br />

Mixed use roadway system<br />

Expanded and new bike and pedestrian routes and options for local and regional connectivity<br />

Improved connectivity to the American River Parkway bike trail<br />

Pedestrian circulation that provides safer alternative routes independent from high-volume<br />

roadways<br />

Neighborhood traffic calming<br />

The use of ITS ideas including “smart highways”<br />

Multimodal solutions<br />

Expand use of alternative transportation (bicycle and pedestrian, light rail, and bus) to reduce air<br />

pollution<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 23 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Rocklin General <strong>Plan</strong><br />

City of Rocklin<br />

DATE April 1991<br />

PURPOSE<br />

SUMMARY<br />

The Rocklin General <strong>Plan</strong> satisfies the California State law requirement for<br />

planning and coordinating future development. The <strong>Plan</strong> serves as a longterm<br />

guide for the orderly growth and development of Rocklin. It forms the<br />

basis for zoning, subdivision regulation, and other planning decisions on the<br />

location, intensity, and design of public facilities and land use.<br />

The <strong>Plan</strong> outlines specific Goals and Policies in land use, open space,<br />

circulation, community safety, noise and public services and facilities. It<br />

includes one specific Area <strong>Plan</strong> (the Southeast Rocklin Circulation Element)<br />

as well as several subsequent amendments to the General <strong>Plan</strong>.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

The following main Goals within the Land Use and Transportation Elements are central to the <strong>Plan</strong>:<br />

Land Use: To designate, protect, and provide land to ensure sufficient residential development to<br />

meet community needs.<br />

To encourage the use of the “village concept” in new projects of 500 acres of more in size, in<br />

order to encourage higher density core areas and encourage alternatives to the use of the<br />

automobile for short trips<br />

To encourage the design of neighborhoods that interconnect streets and pedestrian pathways<br />

for vehicle and pedestrian use to provide for social interaction and the efficient movement of<br />

service and emergency vehicles<br />

Circulation: To provide and maintain a safe and efficient system of streets, highways, and public<br />

transportation to meet community needs and promote sound land use.<br />

To require bike lanes in the design and construction of major new street and highway<br />

improvements<br />

To designate truck routes in order to keep truck traffic away from residential areas<br />

To promote and support coordinated public transit services that meet residents’ needs<br />

To promote the use of public transit through development conditions requiring park-and-ride<br />

lots, bus turnouts and passenger shelters along major streets<br />

To promote pedestrian convenience through development conditions requiring sidewalks,<br />

walking paths, or hiking trails that connect residential areas with commercial, shopping and<br />

employment centers<br />

To enforce the transportation system management requirements of the existing ridesharing<br />

ordinance<br />

To maintain truck routes in such a manner that they can be used for the safe hauling of<br />

hazardous materials<br />

To restrict vehicular access to emergency and service vehicles only from the Clover Lakes<br />

Community Area onto the existing portions of Clover Valley Road and Rawhide Road within the<br />

Mission Hills-Clover Valley Community Area<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 24 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Roseville General <strong>Plan</strong><br />

http://www.roseville.ca.us/index.asp?page=521<br />

City of Roseville<br />

DATE Adopted in 1992, technical update in 2003<br />

The General <strong>Plan</strong> serves as a long-term policy guide for the physical,<br />

economic, and environmental growth of a city and a statement of the<br />

community’ s vision of its ultimate physical growth. City actions, such as<br />

those relating to land use allocations, annexations, zoning, subdivision, and<br />

design review, redevelopment, and capital improvements must be consistent<br />

with the General <strong>Plan</strong>.<br />

PURPOSE<br />

The General <strong>Plan</strong> also designates land use categories for the entire city.<br />

Each land use category is identified and defined within the General <strong>Plan</strong> and<br />

includes information on the general uses, development, intensity, siting and<br />

compatibility standards.<br />

The City of Roseville General <strong>Plan</strong> enables the City Council and <strong>Plan</strong>ning<br />

Commission to establish long-range development policies; provide a basis for<br />

j udging whether private development proposals and public proj ects are in<br />

harmony with the policies; and guide public agencies and private developers<br />

in designing projects that are consistent with City policies.<br />

The General <strong>Plan</strong> discusses nine elements including land use, circulation, air<br />

quality, open space and conservation, parks and recreation, public facilities,<br />

safety, noise, and housing.<br />

SUMMARY<br />

The main overarching goals in land use and circulation, the prevalent<br />

elements, are as follows:<br />

promote a balanced land use pattern that supports innovative land use<br />

approaches and retains and enhances the distinct character and identity<br />

of Roseville<br />

It is the underlying goal of the entire Circulation Element that the City’s<br />

circulation system promote<br />

o the safe, efficient, and reliable movement of people and<br />

goods;<br />

o shift from the automobile to other modes of transportation;<br />

and<br />

o provide an adequate level of transportation service for all<br />

persons traveling in and through Roseville.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 25 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Roseville General <strong>Plan</strong><br />

http://www.roseville.ca.us/index.asp?page=521<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Continue to update and implement the long-range and short-range transit master plan<br />

Implement Bikeway Master <strong>Plan</strong><br />

Establish Pedestrian Districts to promote walkability with the district<br />

Improve pedestrian walkability by considering mid-block crossing treatments, intersection crossing<br />

treatments, traffic calming, and pedestrian enhancements<br />

Evaluate existing transit capital and services<br />

Define potential transit corridors<br />

Expand Capitol Corridor Intercity Rail<br />

Develop commuter rail service between Colfax and Davis<br />

Expand light rail<br />

Area-wide carpool/vanpool matching assistance<br />

City or county trip reduction ordinances<br />

Employer-sponsored car/van/buspool programs<br />

Staggered work schedules, flexible work hours, compressed work week<br />

Suburban park and ride lots<br />

Provision of bikeway and bicycling support facilities<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 26 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Sacramento General <strong>Plan</strong><br />

City of Sacramento<br />

DATE 1998, Update in 2004<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> is the City’ s long-term comprehensive policy guide for the<br />

physical, economic, and environmental growth and renewal of the city. The<br />

General <strong>Plan</strong> is strongly oriented toward physical development of land uses,<br />

a circulation network, and supporting facilities and services. It is comprised<br />

of goals, policies, programs and actions, which are based on an assessment<br />

of current and future needs and available resources. The document is the<br />

principal tool for City use in evaluating public and private building proj ects<br />

and municipal service improvements. Conformance of proj ects and<br />

improvements with the General <strong>Plan</strong> is a major step toward their approval.<br />

The goals of the General <strong>Plan</strong> are:<br />

Create a safe, efficient surface transportation network for the<br />

movement of people and goods.<br />

Provide all citizens in all communities of the City with access to a<br />

transportation network which serves both the City and region, either by<br />

personal vehicle or transit. Make a special effort to maximize<br />

alternatives to single occupant vehicle use, such as public transit.<br />

Maintain a desirable quality of life, including good air quality while<br />

supporting planned land use and population growth.<br />

Consider air quality along with traffic flow efficiency when making<br />

decisions about transportation.<br />

Create and maintain a street system which protects residential<br />

neighborhoods from unnecessary levels of traffic.<br />

Increase the commute vehicle occupancy rate by 50%.<br />

Develop a balanced transportation system which will encourage the use<br />

of public transit, multiple occupancy of the private automobile, and<br />

other forms of transportation.<br />

Provide adequate parking to support continued downtown development,<br />

alternative modes of transportation, and the Central City Urban Design<br />

<strong>Plan</strong>.<br />

Promote a well designed and heavily patronized light rail and transit<br />

system.<br />

Increase the use of the pedestrian mode as a mode of choice for all<br />

areas of the city.<br />

Provide a network of safe and convenient bikeways. Promote bicycling<br />

as a feasible transportation alternative which conserves energy,<br />

improves air quality, reduces traffic congestion, and improves public<br />

health.<br />

Improve quality of residential neighborhoods by protecting, preserving,<br />

and enhancing their character.<br />

Identify areas of potential change where density development would be<br />

appropriate along major thoroughfares, commercial strips and near light<br />

rail stations, and modify plans to accommodate this change.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 27 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Sacramento General <strong>Plan</strong><br />

RECOMMENDATIONS FROM DOCUMENT<br />

Request Sacramento Regional Transit to provide a plan for the provisions of adequate transit<br />

services which meets the needs of the General <strong>Plan</strong>, and that the transit plan is regularly updated.<br />

Work towards a more efficient use of the City’s existing street system.<br />

Explore alternative transportation modes that will lead to a decrease in demand of the City’s<br />

surface street system.<br />

Encourage and support programs that increase vehicle occupancy.<br />

Support actions/ordinances/ developments/agreements that reduce peak hour trips.<br />

Encourage the use of light rail transit and other alternative modes of transportation.<br />

Consider the use of pedestrian pathways that can support the efficient movement of people, new<br />

development, and Central City Design Concepts<br />

Create a multi-modal transportation center in the Central City.<br />

Provide transit service to newly developed areas.<br />

Consider mitigation impacts to support light rail or bus transit improvements.<br />

Provide pedestrian and bicycle access to existing and planned light rail stations.<br />

Improve frequency and location of bus service in residential areas.<br />

Encourage park-and-ride lots to promote alternative transportation and reduce traffic congestion.<br />

New developments should have safe pedestrian walkways with direct links to major destinations.<br />

Promote use of public bikeways.<br />

Incorporate adequate street widths into street plans and developments to ensure a reasonable<br />

level of safety for bicyclists and motorists.<br />

Design on-street and off-street bicycle parking facilities for maximum security and, when possible,<br />

for protection from the elements.<br />

Provide adequate signing, and other traffic control measures in all bikeway design plans to ensure<br />

a reasonably high level of safety for bicyclists and motorists.<br />

Future developments should conform to the Bikeways Master <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 28 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

1999 General <strong>Plan</strong><br />

City of South Lake Tahoe<br />

City of South Lake Tahoe <strong>Plan</strong>ning Division<br />

DATE April 13, 1999<br />

PURPOSE<br />

The City General <strong>Plan</strong> was developed to include the seven mandatory<br />

elements required by State law: land use, circulation, housing, conservation,<br />

open space, noise, and safety.<br />

The <strong>Plan</strong> includes comprehensive listings of technical references, as well as<br />

specific Goals, Objectives and Action <strong>Plan</strong>s for each of the <strong>Plan</strong> elements.<br />

SUMMARY<br />

NOTE: The Tahoe Regional <strong>Plan</strong>ning Agency (TRPA) uses a land use<br />

regulatory tool called <strong>Plan</strong> Area Statements (PAS). The PAS delineate a<br />

discrete area composed of many parcels of like uses which are combined into<br />

one land use classification. Specific goals, policies, programs, and allowed<br />

uses are then identified for each <strong>Plan</strong> Area. The PAS can thus be flexible to<br />

reflect the unique aspects of an area.<br />

With traditional zoning (followed by most local j urisdictions), each parcel is<br />

designated for a specific land use classification and refers to a generalized<br />

set of land use controls. Since both land use regulation approaches (PAS and<br />

zoning) are used within the same geographical area by different entities<br />

(local or regional), some confusion may result. Where there is a conflict, the<br />

most restrictive regulation applies which is usually the PAS regulation. The<br />

City of South Lake Tahoe General <strong>Plan</strong> uses PAS to be consistent with TRPA<br />

plans.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Land Use<br />

The population shall be guided by the limitations placed within the PAS, including the mix of<br />

land use, density of development, and people per parcel per land use as provided for under the<br />

Population section of the General <strong>Plan</strong>.<br />

Encourage a high degree of commercial compactness within commercial areas to create a high<br />

level of shopper convenience and area drawing power<br />

Circulation<br />

Reduce vehicle miles traveled by 10% measured from the 1981 base year in the plan.<br />

Expand transit service to provide service to the transit dependent of the City and to visitors<br />

alike and thereby reduce dependency on the automobile.<br />

<strong>Plan</strong> for the land use changes and development patterns which will encourage the use of<br />

alterative transportation modes.<br />

Continue to implement the Bicycle Master <strong>Plan</strong>.<br />

Provide for pedestrian linkages along U.S. 50.<br />

Ensure hazardous material is immediately removed from the City street system.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 29 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of West Sacramento General <strong>Plan</strong><br />

http://www.ci.westsacramento.ca.us/cityhall/departments/comdev/documents/plan_gppolicy.<br />

pdf<br />

City of West Sacramento<br />

DATE Revised and adopted 2000<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> serves the following purposes:<br />

To establish within local government the capacity to analyze local and<br />

regional conditions and needs in order to respond effectively to the<br />

problems and opportunities facing the community;<br />

To identify the community’s environmental, social, and economic goals;<br />

To record the local government’s policies and standards for the<br />

maintenance and improvement of existing development and the location<br />

and characteristics of future development;<br />

To provide citizens with information about their community and with<br />

opportunities to participate in the local planning and decision-making<br />

process;<br />

To improve the coordination of community development and<br />

environmental protection activities among local, regional, state, and<br />

federal agencies; and<br />

To establish a basis for subsequent planning efforts, such as preparation<br />

of specific plans, redevelopment plans, and special studies, to deal with<br />

unique problems or areas in the community.<br />

The goals of the General <strong>Plan</strong> are:<br />

Provide for orderly, well-planned, and balanced growth consistent with<br />

the limits imposed by the city’s infrastructure and the city’s ability to<br />

assimilate new growth.<br />

Designate adequate land in a range of residential densities to meet the<br />

housing needs of all income groups expected to reside in West<br />

Sacramento; provide support for the development of commercial uses<br />

providing goods and services to West Sacramento residents and West<br />

Sacramento’s market area; provide support for the development of<br />

office uses serving both West Sacramento and the region; provide<br />

support for light, heavy, and water-related industrial uses that create<br />

jobs and enhance the economy of West Sacramento; and development<br />

of public and quasi-public uses to support existing and new residential,<br />

commercial, and industrial land uses.<br />

Create and maintain a roadway network which will ensure the safe and<br />

efficient movement of people and goods throughout the city.<br />

Promote and maintain public and private transit systems that are<br />

responsive to the needs of all West Sacramento residents.<br />

Promote increased efficiency in automobile use.<br />

Encourage communication and cooperation within the community, with<br />

adjacent jurisdictions, and with state and federal agencies concerning<br />

all transportation-related issues.<br />

Ensure adequate provisions of both on- and off-street parking.<br />

Promote pedestrian and bicycle travel as alternatives to automobile<br />

use.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 30 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of West Sacramento General <strong>Plan</strong><br />

http://www.ci.westsacramento.ca.us/cityhall/departments/comdev/documents/plan_gppolicy.<br />

pdf<br />

Provide a network of pedestrian and bicycle pathways connecting parks<br />

and open space areas with other destination points within and beyond<br />

the city of West Sacramento.<br />

Ensure that City emergency response procedures are adequate in the<br />

event of natural or man-made disasters.<br />

Promote development of neighborhoods and districts that emphasize<br />

pedestrian convenience.<br />

Create a distinctive Central Business District which serves as the City’s<br />

most important civic and pedestrian-oriented commercial area.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Conduct a feasibility study for development of a major trucking center<br />

Maintain a master list of traffic counts.<br />

Maintain a Street Master <strong>Plan</strong><br />

Enhance internal circulation and access between Sacramento and West Sacramento<br />

Maintain existing long-term Major Projects Financing <strong>Plan</strong><br />

Upgrade and maintain traffic signals<br />

Review and revise off-street parking standards of the Zoning Ordinance<br />

Establish park-and-ride facilities<br />

Maintain Transportation Systems Management (TSM) ordinance for air quality mitigation<br />

Maintain Pedestrian and Bicycle Route Master <strong>Plan</strong><br />

Ensure that signalized intersections are programmed to respond to actual traffic volumes.<br />

Maximize the use of existing air quality mitigation measures, including offsets, so new<br />

development helps reduce the existing regional air pollution emissions.<br />

Periodically update the City’s Emergency Operations <strong>Plan</strong> and maintain training in the Standard<br />

Emergency Management System.<br />

Prepare detailed plans for street improvements in the CBD, including specifying the number of<br />

lanes, necessary realignments, signalization, and cross sections, as well as requirements for<br />

parking, curb cuts, sidewalks, and landscaping of medians and street frontages.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 31 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Woodland General <strong>Plan</strong><br />

http://www.ci.woodland.ca.us/commdev/PoliciesDocs.htm#GP<br />

City of Woodland<br />

DATE Update adopted in 2002<br />

PURPOSE<br />

The General <strong>Plan</strong> formalizes a long-term vision for the physical evolution of<br />

Woodland and outlines policies, standards, and programs to guide day-to-day<br />

decisions concerning development through 2020. The <strong>Plan</strong> is designed to<br />

meet state planning requirements.<br />

The General <strong>Plan</strong> sets the framework for future growth and development<br />

within which Woodland can expand while still maintaining the small-town<br />

feeling and quality of life that are so important to Woodland residents. The<br />

maj or theme of the General <strong>Plan</strong> is to retain and build upon Woodland’ s<br />

small-town and neighborhood qualities while achieving an economicallyhealthy<br />

and self-sufficient community.<br />

SUMMARY<br />

To retain and enhance Woodland’s quality of life, its separate identity,<br />

and small-town characteristics.<br />

To achieve an orderly pattern of community development consistent<br />

with economic, social, and environmental needs.<br />

To provide for a diversified economic base with a range of employment<br />

opportunities for all residents.<br />

To preserve and protect prime agricultural lands and their uses in the<br />

areas between the Urban Limit Line and the boundary of the General<br />

<strong>Plan</strong> Area.<br />

To revitalize the Downtown district as the heart of the city.<br />

to promote the provision of adequate housing including a variety of<br />

housing sizes and types for all persons in the community regardless of<br />

income, age, gender, race, or ethnic background.<br />

To coordinate land and transportation planning measures to foster<br />

reduced dependence on automobile and increased opportunities for<br />

alternative modes of travel.<br />

To provide adequate levels of public service.<br />

To promote a wide range of parks and recreational facilities and<br />

activities.<br />

To plan for diverse educational opportunities and adequate school<br />

facilities.<br />

To preserve and enhance the historical and cultural resources of the<br />

Woodland area.<br />

To protect and improve the quality of the natural environment.<br />

To prevent loss of life, injury, and property damage due to natural and<br />

manmade hazards.<br />

To ensure that Woodland remains a safe place to live.<br />

To foster increased cooperation and coordination among governmental<br />

entities.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 32 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Woodland General <strong>Plan</strong><br />

http://www.ci.woodland.ca.us/commdev/PoliciesDocs.htm#GP<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Provide or new residential development in planned neighborhoods to be developed at an orderly<br />

pace and style and designed to promote walking, bicycling, and transit use, including the use of a<br />

modified grid system.<br />

Revitalize and maintain the East Street Corridor as an economically-viable and physicallyattractive<br />

mixed-use corridor.<br />

Provide for the long-range planning and development of the city’s roadway system to ensure the<br />

safe and efficient movement of people and goods<br />

Protect residential areas from high-volume and high-speed traffic and its effects and promote<br />

bicycling and walking on residential streets.<br />

Provide a sufficient amount of convenient, safe, and attractive parking to serve existing and new<br />

development throughout the city.<br />

Promote a safe and efficient transit system to reduce congestion, improve the environment, and<br />

provide viable non-automotive means of transportation in and through Woodland.<br />

Provide a safe, comprehensive, and integrated system of facilities for non-motorized<br />

transportation.<br />

Maintain a balanced freight transportation system to provide for the safe and efficient movement<br />

of goods.<br />

Support the continued operation of local air transportation facilities while ensuring compatibility<br />

between urban development in Woodland and aircraft operations.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 33 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Yuba City General <strong>Plan</strong><br />

http://www.yubacity.net/index.cfm?navID=210<br />

Yuba City<br />

DATE April, 2004<br />

The Yuba City General <strong>Plan</strong> is a document required by State law and adopted<br />

by the City Council that addresses issues related to physical development,<br />

growth, and conservation of City resources. The <strong>Plan</strong>:<br />

PURPOSE<br />

SUMMARY<br />

Outlines a vision of long-range physical planning and land uses in order<br />

to address the economic development and resource conservation<br />

aspirations of the community;<br />

Provides strategies and specific implementing actions that will allow<br />

this vision to be accomplished;<br />

Establishes <strong>Plan</strong> policies and standards to be used as a basis for judging<br />

whether specific development proposals are in concert with the goals of<br />

the community;<br />

Provides guidelines and policies by which City departments, public<br />

agencies, and private developers can design projects that will enhance<br />

the character of the community, preserve and enhance critical<br />

environmental resources, and minimize hazards; and<br />

Provides that basis for establishing and setting priorities for detailed<br />

plans and implementing programs, such as the Zoning Ordinance,<br />

specific plans, impact fee studies, and the Capital Improvement<br />

Program.<br />

This General <strong>Plan</strong> addresses the elements of growth and economic<br />

development; land use; community design; transportation; parks, schools,<br />

and community facilities; public utilities; environmental conservation; and<br />

noise and safety.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Design new residential streets with sidewalks, planting strips, and traffic calming elements to<br />

create a pedestrian-friendly environment<br />

Develop separate bike paths on at least one side of parkways buffered from vehicular traffic by<br />

planting strips<br />

Install pedestrian amenities such as pedestrian-scale street lighting, benches, and planting strips<br />

where community commercial core is planned.<br />

Promote convenient vehicular and transit access to Regional Activity Centers<br />

Establish minimum standards for pedestrian-oriented circulation<br />

Improve alternative transportation modes and establish provisions for more direct routes for<br />

pedestrians and bicyclists<br />

Maintain acceptable levels of service and ensure that future development and the circulation<br />

system are in balance<br />

With all roadway improvements, plan for usage of roadway space by all users including motor<br />

vehicles, transit vehicles, bicyclists, and pedestrians<br />

Expand and improve the existing transit network to provide convenient and efficient public<br />

transportation<br />

Preserve options for future transit use when designing improvements for roadways<br />

Locate transit stops and hubs at locations that are convenient for transit users, and promote<br />

increased transit ridership through the provisions of shelters, benches, and other amenities<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 34 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Yuba City General <strong>Plan</strong><br />

http://www.yubacity.net/index.cfm?navID=210<br />

Identify and implement Park & Ride sites with convenient access to public transit<br />

New developments must include transit improvements and accommodate transit use<br />

Develop a systems of sidewalks and bikeways that promote safe walking and bicycle riding for<br />

transportation and recreation<br />

Develop bicycle routes that provide access to schools, parks, and the Feather River Parkway<br />

Develop rails-to-trails corridors<br />

Provide bike lanes on new and existing streets<br />

Increase bicycle safety<br />

Provide attractive and convenient parking facilities<br />

Provide adequate circulation and off-street parking and loading facilities for trucks and facilitate<br />

intermodal goods delivery<br />

Provide guidance for truck routes<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 35 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

El Dorado County General <strong>Plan</strong><br />

http://www.co.el-dorado.ca.us/generalplan/<br />

El Dorado County<br />

DATE July 2004<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> outlines several clear objectives including the following:<br />

To develop a strong diversified and sustainable local economy;<br />

To foster a rural quality of life;<br />

To sustain a quality environment;<br />

To accommodate the County's fair share of regional growth projections<br />

and affordable housing while encouraging those activities that comprise<br />

the basis for the County's customs, culture, and economic stability;<br />

To oversupply residential and non-residential land use designations in<br />

order to provide market and landowner flexibility to more feasibly<br />

accommodate the market;<br />

To concentrate and direct urban growth where infrastructure is present<br />

and/or can be more feasibly provided;<br />

To recognize that funding limitations for infrastructure and services will<br />

result in lower levels of service while the County improves employment<br />

and housing opportunities;<br />

To conserve, protect, and manage the County's abundant natural<br />

resources for economic benefits now and for the future;<br />

To encourage infill development that more efficiently utilizes existing<br />

infrastructure and minimizes land use conflicts while avoiding the<br />

premature development of non-contiguous lands where direct and life<br />

cycle costs are greater;<br />

To accomplish the retention of permanent open space/natural areas on<br />

a project-by-project bases through clustering;<br />

To minimize down planning and/or down zoning where feasible;<br />

To improve the jobs-to-housing ratio by giving preference to the<br />

development of high technology and value added employment centers<br />

and regional retail and tourism uses.<br />

Through various elements of the plan (Land Use, Circulation, Housing, Public<br />

Services and Utilities, Public Health, Conservation, Agriculture, Parks and<br />

Recreation, and Economic Development), the above objectives are pursued.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Obj ectives appear throughout the report in the appropriate elements.<br />

pertaining to land use and transportation include the following:<br />

Obj ectives specifically<br />

Provide opportunities that allow for continued population growth and economic expansion while<br />

preserving the character and extent of existing rural centers and urban communities, emphasizing<br />

both the natural setting and built design elements which contribute to the quality of life and<br />

economic health of the County.<br />

Recognize existing defined places as centers within the Rural Regions which provide a focus of<br />

activity and provides goods and services to the surrounding areas.<br />

Creation and development of balanced communities in areas identified as suitable for intensive<br />

development due to the availability of adequate infrastructure and services.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 36 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

El Dorado County General <strong>Plan</strong><br />

http://www.co.el-dorado.ca.us/generalplan/<br />

Coordinate the Transportation System with the Land Use <strong>Plan</strong> to ensure that new development is<br />

efficiently, safely, and conveniently accessed. The Circulation Map adopted as a part of this<br />

element will show all existing and planned arterial and collector roads. The transportation system<br />

will be consistent with the Regional Highway System (RHS) and make the most efficient use of the<br />

County's existing regional highway system.<br />

Develop and enforce safe and efficient roadway design standards that consider the variety of<br />

terrain and environmental conditions throughout the County and minimize the degradation of<br />

environmental quality.<br />

Ensure that safe and efficient transportation and circulation facilities are provided for concurrently<br />

with new development.<br />

Distribute the costs for necessary transportation improvements equitably among those who will<br />

burden the system and who will benefit from the improvements.<br />

Improve interchanges along U.S. Highway 50 and the roadway system in the central urban corridor<br />

extending from the Sacramento/El Dorado County Line to Camino.<br />

Development projects directly or cumulatively affecting State highways shall mitigate impacts,<br />

while recognizing level of service standards and expectations for the future funding for highway<br />

improvements.<br />

Provide a regional highway system which, to the extent practical, is compatible with the physical<br />

environment, enhances the environmental quality, and conserves the natural resources of the<br />

County.<br />

Maintain LOS "E" on all County roads. The annual Capital Improvement Program shall target those<br />

areas where LOS or safety standards are not being met.<br />

Identify public transportation system improvements throughout the County to meet the needs of<br />

both the general public and the public transportation dependent.<br />

Assist in providing multi-modal transportation service to all residents of the County.<br />

Increase commuter usage and service.<br />

<strong>Plan</strong> for the extension of rail service from Sacramento into El Dorado County.<br />

Identify and support the implementation and development of assistance to the public<br />

transportation dependent.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 37 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Placer County General <strong>Plan</strong> Update<br />

http://elib.cs.berkeley.edu/docs/data/0700/781/HYPEROCR/hyperocr.html<br />

Placer County<br />

DATE August 16, 1994<br />

The General <strong>Plan</strong> outlines the following broad purposes for the general plan<br />

process:<br />

PURPOSE<br />

SUMMARY<br />

To expand the capacity of local government to analyze local and<br />

regional conditions and needs in order to respond effectively to the<br />

problems and opportunities facing the community;<br />

To define the community's environmental, social, and economic goals;<br />

To record the local government's policies and standards for the<br />

maintenance and improvement of existing development and the location<br />

and characteristics of future development;<br />

To provide citizens with information about their community and with<br />

opportunities to participate in setting goals and determining policies<br />

and standards for the community's development;<br />

To foster the coordination of community development and<br />

environmental protection activities among local, regional, state, and<br />

federal agencies;<br />

To guide and coordinate the many actions and day-to-day decisions for<br />

local government that are necessary to developing and protecting the<br />

community.<br />

To provide local decision makers and the community with a forum for<br />

resolving conflicts among competing interests and values.<br />

The law specifically requires that the general plan address seven topics or<br />

“ elements” . These are land use, circulation (transportation), housing,<br />

conservation, open space, noise, and safety. The plan must analyze issues of<br />

importance to the community, set forth policies in text and diagrams for<br />

conservation and development, and outline specific programs for<br />

implementing these policies.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

To promote the wise, efficient, and environmentally-sensitive use of Placer County lands to meet<br />

the present and future needs of Placer County residents and businesses.<br />

To provide adequate land in a range of residential densities to accommodate the housing needs of<br />

all income groups expected to reside in Placer County.<br />

To designate adequate commercial land for and promote development of commercial uses to meet<br />

the present and future needs of Placer County residents and visitors and maintain economic<br />

vitality.<br />

To establish and maintain interconnected greenbelts and open spaces for the protection of native<br />

vegetation and wildlife and for the community's enjoyment.<br />

The County shall encourage the use of bicycles as an alternative mode of travel for recreational<br />

purposes in scenic corridors.<br />

To provide a safe, comprehensive, and integrated system of facilities for non-motorized<br />

transportation.<br />

The County shall require that bikeways recommended in the Bikeways/Trails Master <strong>Plan</strong> be<br />

developed when roadway projects are constructed and when street frontage improvements are<br />

required of new development.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 38 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Placer County General <strong>Plan</strong> Update<br />

http://elib.cs.berkeley.edu/docs/data/0700/781/HYPEROCR/hyperocr.html<br />

To provide for the long-range planning and development of the county's roadway system to ensure<br />

the safe and efficient movement of people and goods.<br />

Placer County shall recommend that a ramp-metering program for the 1-80 corridor between<br />

Auburn and the Sacramento County line be included in the next Regional Transportation <strong>Plan</strong> (RTP)<br />

prepared by the Placer County Transportation Commission (PCTC).<br />

To promote a safe and efficient mass transit system, including both rail and bus, to reduce<br />

congestion, improve the environment, and provide viable non-automotive means of transportation<br />

in and through Placer County.<br />

To maximize the efficient use of transportation facilities so as to: 1) reduce travel demand on the<br />

county's roadway system; 2) reduce the amount of investment required in new or expanded<br />

facilities; 3) reduce the quantity of emissions of pollutants from automobiles; and 4) increase the<br />

energy-efficiency of the transportation system.<br />

To maintain a balanced freight transportation system to provide for the safe and efficient<br />

movement of goods.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 39 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

County of Sacramento General <strong>Plan</strong><br />

http://www.saccounty.net/general-plan/gp-home.html<br />

Updates<br />

http://www.saccounty.net/planning/gpupdate/gpu-index.html<br />

County of Sacramento<br />

DATE December 15, 1993<br />

PURPOSE<br />

SUMMARY<br />

The General <strong>Plan</strong> strategy which supports new approaches and new<br />

directions is based upon the beliefs that:<br />

The environmental impacts of growth are inadequately mitigated at the<br />

project scale, and, because they are inadequately mitigated,<br />

accumulate at the regional scale. Among them are the impacts which<br />

fall on infrastructure, air quality, and the fiscal base of the respective<br />

jurisdictions.<br />

Inadequate mitigation works as an incentive to growth on the urban<br />

periphery and as a disincentive to regional planning that seeks to<br />

mitigate these impacts.<br />

Intra-regional competition for employment, tax revenues and growth in<br />

general compromises the achievement of regional coordination<br />

necessary to address transportation and air quality issues.<br />

These issues can best be addressed by land use plans in all communities<br />

in the region that seek to balance housing, support services, and<br />

employment at small rather than large geographic scales, and that<br />

create major centers of employment and public interest linked by<br />

balanced rather than specialized transportation systems.<br />

Specific land use, circulation, open space, safety, noise, air quality,<br />

conservation and housing “elements” are part of the general plan.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

An orderly pattern of land use that concentrates urban development, enhances community<br />

character and identity through the creation and maintenance of neighborhoods, is functionally<br />

linked with transit, and protects the County's natural, environmental and agricultural resources.<br />

Accommodate projected population and employment growth in areas where the appropriate level<br />

of public infrastructure and services are or will be available during the planning period.<br />

Additional population and employment growth accommodated in areas having the potential for<br />

redevelopment. One percent of projected housing demand (1,000 new residential units) located in<br />

unincorporated redevelopment areas.<br />

Sixty-six percent of projected population growth accommodated through the development of<br />

urban uses on vacant urban and underutilized Agricultural-Residential lands: 21,900 units (23%) in<br />

established urban and Agricultural-Residential communities, 35,100 units (37%) in planned<br />

communities, and 5,300 units (6%) on excess industrial office park acreage.<br />

Thirty percent of projected population growth (28,300 units) accommodated through efficient<br />

transit-oriented development in new urban growth areas at the urban fringe.<br />

Neighborhoods with a balanced mix of employment, neighborhood service and different housing<br />

types.<br />

Communities, neighborhoods, and single projects that promote pedestrian circulation and safety<br />

through amenities, good design, and a mix of different land uses in close proximity.<br />

A community wide pattern of development with the most intensive land uses in close proximity to<br />

transit stops.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 40 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


County of Sacramento General <strong>Plan</strong><br />

http://www.saccounty.net/general-plan/gp-home.html<br />

STUDY<br />

Updates<br />

http://www.saccounty.net/planning/gpupdate/gpu-index.html<br />

New development that accommodates projected population increases, yet provides direct and<br />

multiple pedestrian and a automobile linkages to other developments, maintains community<br />

identity, and is compatible with existing neighborhoods.<br />

High intensity, mixed use neighborhoods that provide a pedestrian environment and are closely<br />

linked to transit.<br />

A sufficient, yet efficient supply of parking.<br />

Sacramento County shall conduct planning for road, parking, clean alternative fuel and low<br />

emission vehicles, transit, clean intercity rail, bikeway, and pedestrian facilities in a manner that<br />

is consistent with achieving air quality goals.<br />

Require full and accurate analysis of all alternatives for public transit, including expanded bus<br />

service, private carrier operations, road capacity improvements, and rail transit, prior to<br />

committing funds for construction. Evaluation shall specifically include full social and economic<br />

costs and benefits, as well as net system effects and per-new-rider costs.<br />

Encourage transit, bicycle, and pedestrian projects when making decisions for the expenditure of<br />

discretionary local, state, or federal funds and in the Sacramento County Capital Improvement<br />

Program and the Congestion Management <strong>Plan</strong>.<br />

Sacramento County shall reduce automobile travel demand by promoting mixed use development<br />

throughout the County, including the development of neighborhood support commercial services in<br />

areas that are primarily residential.<br />

Sacramento County shall support a minimum level transit service in suburban areas of the county<br />

that do not have the densities to generate sufficient ridership to justify high quality transit service<br />

so that transit dependent residents of those areas are not cut off from community services,<br />

events, and activities.<br />

Sacramento County shall regulate truck travel as appropriate for the transport of goods, consistent<br />

with circulation, air quality, congestion management, and land use goals.<br />

Sacramento County shall support the development of multimodal centers with passenger facilities<br />

for heavy rail, light rail, and bus.<br />

Sacramento County will support the expansion of transit service to and within commercial<br />

airports.<br />

Sacramento County shall continue to support intercity bus transportation and intermodal links with<br />

the downtown bus terminal.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 41 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Sutter County General <strong>Plan</strong><br />

http://www.co.sutter.ca.us/depts/cs/ps/PDF/General_<strong>Plan</strong>-<br />

Policy_Document.pdf<br />

Sutter County<br />

DATE November 25, 1996<br />

PURPOSE<br />

SUMMARY<br />

Carrying out California State law, the Sutter County General <strong>Plan</strong> serves the<br />

following purposes:<br />

To define the community's environmental, social, and economic goals;<br />

To provide citizens with information about their community and to<br />

provide them with opportunities to participate in the planning process;<br />

To provide a forum for resolving conflicts among competing interests<br />

and values;<br />

To provide for the coordination of community and environmental<br />

protection activities among local, regional, state and federal agencies;<br />

To guide and coordinate the actual development of the community.<br />

The Policy Document is divided into nine sections or elements. Those<br />

sections are:<br />

Land Use<br />

Transportation and Circulation<br />

Public Facilities and Services<br />

Conservation/Open Space - Natural Resources<br />

Conservation/Open Space - Recreation and Cultural Resources<br />

Agricultural Resources<br />

Health and Safety<br />

Noise<br />

Rural Communities and Area <strong>Plan</strong>s<br />

(The Housing Element is bound as a separate document.)<br />

Each section of the Policy Document includes several goals relating to<br />

different subj ect areas in that section. For each goal there can be several<br />

policies that set forth the criteria or commitment that is to be adhered to,<br />

and in some cases a set of implementation programs.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

The County shall plan, design and regulate roadways in accordance with the functional<br />

classification system and circulation diagram contained within the Circulation section. The County<br />

shall require that road rights-of-way be wide enough to accommodate all necessary road<br />

improvements identified in Table 4 to handle forecasted travel volume(s) at or above adopted<br />

service level standards.<br />

All streets and roadways shall be dedicated and improved to the roadway design standards as<br />

generally defined in this section and the roadway design standards maintained by the Public Works<br />

Department. Exceptions may be necessary but should be kept to a minimum and shall be<br />

permitted only upon determination by the Public Works Director and Community Services Director<br />

that safe and adequate public access and circulation are preserved by such exceptions.<br />

Intersection spacing on roadways should be maximized. Driveway encroachment should be<br />

minimized. Access control restrictions for each class of roadway are specified on Table 6.<br />

The County shall strive to develop and manage its roadway system to maintain a minimum Level of<br />

Service D (LOS D).<br />

The County's level of service standards for the state highway system shall be those standards<br />

adopted in the Bi-County Congestion Management <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 42 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


Sutter County General <strong>Plan</strong><br />

STUDY http://www.co.sutter.ca.us/depts/cs/ps/PDF/General_<strong>Plan</strong>-<br />

Policy_Document.pdf<br />

The County shall require all new development projects to analyze their contribution to increased<br />

traffic and to implement improvements necessary to address the increase.<br />

The County shall assess fees on new development sufficient to cover the costs of the project’s<br />

impact on the local and regional transportation system.<br />

The cities and the County shall attempt to coordinate the establishment of future road alignments<br />

within the cities’ sphere of influence which would reserve the maximum right-of-way as shown in<br />

Table 6, General Roadway Standards by Functional Class or as determined jointly by the cities and<br />

County. Future road alignments and extensions should consider build out of the sphere of<br />

influence, logical east-west and north-south roadway extensions and ultimate desired circulation<br />

patterns.<br />

The County shall maintain ongoing coordination with the Bi-County Transportation Commission,<br />

Caltrans, SACOG and other jurisdictions to address local and regional transportation issues.<br />

The County shall encourage and support projects that will improve traffic flows and safety on<br />

Highway 99.<br />

The County shall support, as appropriate, major highway projects including Route 102 that will<br />

improve traffic flows and safety within Sutter County.<br />

The County shall encourage the City of Yuba City and Caltrans to explore the feasibility of<br />

synchronizing signalized intersections on Highway 20, Highway 99 and other main arterials to<br />

improve traffic flows.<br />

The County shall encourage, where feasible, the development of local roads parallel to State<br />

Highways to reduce congestion and increase traffic safety on state facilities.<br />

The County shall work with Yuba-Sutter Transit to plan and implement appropriate transit services<br />

within the County.<br />

The County shall encourage Yuba-Sutter Transit to comment on development proposals to ensure<br />

that appropriate transit facilities are addressed.<br />

Where feasible, the County shall encourage the development of rideshare facilities within<br />

underutilized parking lots or new proposed parking areas.<br />

The County shall strongly encourage expansion of freight and passenger rail service and facilities<br />

within Sutter County.<br />

Protection and enhancement of existing rail facilities shall be encouraged. In instances where rail<br />

lines are considered for abandonment, efforts should be made to convert these corridors into bikepedestrian<br />

paths or other similar uses.<br />

The County shall work toward developing a comprehensive and safe system of bicycle routes that<br />

will serve both commuter and recreational cyclists through ongoing implementation of the Yuba-<br />

Sutter Bikeway Master <strong>Plan</strong> to the extent feasible and where funding is available.<br />

The County shall continually attempt to identify and pursue available sources of funding for the<br />

planning, development and improvement of bikeways.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 43 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Yolo County<br />

http://www.yolocounty.org/org/PPW/planning/general_plan_documents.htm<br />

Yolo County Community Development Agency<br />

DATE July, 1993<br />

PURPOSE<br />

SUMMARY<br />

This General <strong>Plan</strong> organizes Yolo County’ s perceptions of present and future<br />

problems, outlines how the County plans to deal with them, and prescribes<br />

some procedures to move toward their resolution.<br />

Following is a concise list of the basic goals expressed in this Yolo County<br />

General <strong>Plan</strong> and related <strong>Plan</strong> documents:<br />

Wise land use based on both physical and social characteristics of the<br />

County.<br />

Protect prime and other agricultural land from urban development.<br />

Provide for industrial growth in the County to provide employment,<br />

services, and tax base while minimizing hazards and nuisances and while<br />

conserving resources and agricultural lands.<br />

Provide recreational opportunities.<br />

Encourage conservation (energy, open space, and materials).<br />

Maintain good road conditions.<br />

Provide for and encourage alternate transportation modes (bus,<br />

pedestrian, bike).<br />

Correct Zoning Ordinance violations.<br />

Provide decent and affordable housing.<br />

Establish natural and wildlife areas (preserves).<br />

Create urban open spaces, green belts, and scenic highways.<br />

Conserve and manage water resources (groundwater, stream, and the<br />

Delta).<br />

Make land use compatible with culture and rural setting.<br />

Work on noise problems and their solutions.<br />

Control pollution.<br />

Provide services for elderly and handicapped.<br />

Provide for seismic safety.<br />

Work to improve air quality.<br />

Promote Health and Safety.<br />

Discourage urban sprawl.<br />

Discourage segregation in neighborhoods.<br />

Preserve County history and historical sites.<br />

Ensure that efficient utility service is provided.<br />

Control erosion and practice soil management.<br />

Aesthetics – landscaping to enhance the community and preservation of<br />

rural scenery.<br />

Provide health services.<br />

Control flooding and avoid the effects of flooding.<br />

Continue to improve existing urban uses and place new urban uses in<br />

existing planned urban areas.<br />

Conserve natural resources.<br />

Conserve and enhance cultural resources.<br />

Avoid, mitigate, or eliminate hazards and nuisances.<br />

Periodically upgrade the General <strong>Plan</strong> and its implementing systems.<br />

Maintain and enhance an effective planning agency.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 44 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Yolo County<br />

http://www.yolocounty.org/org/PPW/planning/general_plan_documents.htm<br />

Recognize and provide the means to achieve the needs of the statewide<br />

goals and objectives.<br />

Provide long term assurance of the terms of permits and approvals.<br />

Increase interagency cooperation and cooperation with individuals and<br />

institutions to more effectively achieve the goals of this <strong>Plan</strong>.<br />

Protect property values.<br />

Resolve the Issues set forth in this <strong>Plan</strong>.<br />

Improve the beauty, peace, and quiet of the County.<br />

Assure that the costs of new development are borne by the beneficiaries<br />

of such development.<br />

Increase the speed and reduce the cost of providing governmental<br />

services.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Yolo County shall use land use planning to reduce auto travel and encourage alternative transit and<br />

transportation. Specific devices include:<br />

Increased densities in multiple activity centers.<br />

Multiple activity centers on transportation corridors.<br />

Restrain urban development to presently planned areas.<br />

Centrally locate government offices and services.<br />

Evaluate new development proposals for impact on energy consumption changes.<br />

Avoid major trip generators in scattered locations or at the urban fringe.<br />

Require bicycle and pedestrian ways in all new development.<br />

Discourage sprawl.<br />

Yolo County shall require the design of buildings, sidewalks, and other public facilities and<br />

transportation modes to facilitate their use by the handicapped.<br />

Yolo County shall plan, develop, and maintain a comprehensive, coordinated transportation system<br />

and road net to insure all persons the opportunity for safe, efficient, convenient, and pleasant<br />

movement of persons and goods without substantial congestion or delay, while encouraging greater<br />

efficiency, including the substitution of alternate transportation and consideration of ground, air,<br />

and water modes.<br />

Yolo County shall seek to design and implement a circulation and transportation system which:<br />

Reduces conflicts between land use and circulation-transportation<br />

Shields adjoining areas and community from noise, fumes, dust, and congestion.<br />

Promotes new non-polluting forms of transportation.<br />

Requires routing, construction, and operation of transportation facilities to protect or enhance<br />

environmental quality.<br />

Develops intracommunity ties by creating a functional and aesthetically pleasing system of<br />

transportation corridors, pedestrian and bicycle ways and landscaped open areas which<br />

harmonize development in areas of transition.<br />

Yolo County shall seek to establish, expand, and improve a balanced public transportation system,<br />

integrated with the Regional System, to meet basic transportation needs as expeditiously as<br />

possible; to encourage diversion of substantial numbers of riders from autos to transit; to meet the<br />

transportation needs of the elderly, the handicapped, and the young; and to facilitate<br />

interconnections with other modes of transit.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 45 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Yuba County General <strong>Plan</strong><br />

http://www.yubacomdev.org/planning/gp/1996GP_Vol2_Complete.pdf<br />

Yuba County<br />

DATE December 1996<br />

PURPOSE<br />

SUMMARY<br />

According to the St at e General <strong>Plan</strong> Guidelines, the process of adopting and<br />

implementing the Yuba County General <strong>Plan</strong> serves to:<br />

Identify the community's land use, circulation, environmental,<br />

economic, and social goals and policies as they relate to land use and<br />

development.<br />

Provide a basis for local government decision making, including a<br />

"nexus", or connection, to support development exactions (fees or other<br />

requirements).<br />

Provide citizens with opportunities to participate in the planning and<br />

decision making processes of local government.<br />

Inform citizens, developers, decision makers, and other cities and<br />

counties of the ground rules that will guide development within the<br />

community.<br />

Bridge the gap between community values and actual physical decisions.<br />

The general plan must address seven "elements" or subj ects: land use,<br />

circulation (transportation), housing, open space, conservation, safety, and<br />

noise. These elements must address the following issues:<br />

The land use element designates the general distribution and intensity<br />

of uses of the land for housing, business, industry, open space,<br />

education, public buildings and grounds, waste disposal facilities, and<br />

other categories of public and private uses.<br />

The circulation element is correlated with the land use element and<br />

identifies the general location and extent of existing and proposed<br />

major thoroughfares, transportation routes, terminals and other local<br />

public utilities and facilities.<br />

The housing element is a comprehensive assessment of current and<br />

projected housing needs for all segments of the community and all<br />

economic groups. In addition, it embodies policy for providing adequate<br />

housing and includes action programs for this purpose.<br />

The conservation element addresses the conservation, development,<br />

and use of natural resources including water, forests, soils, rivers, and<br />

mineral deposits.<br />

The open space element details plans and measures for preserving open<br />

space for natural resources, the managed production of resources,<br />

outdoor recreation, public health and safety, and agricultural land.<br />

The noise element identifies and appraises noise problems within the<br />

community and forms the basis for land use distribution.<br />

The safety element establishes policies and programs to protect the<br />

community from risks associated with seismic, geologic, flood, and fire<br />

hazards.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 46 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Yuba County General <strong>Plan</strong><br />

http://www.yubacomdev.org/planning/gp/1996GP_Vol2_Complete.pdf<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Adequate opportunity for higher densities in a variety of locations, including single family,<br />

multiple family and cluster developments.<br />

Industrial/business parks shall be located with access to the regional transportation network and<br />

in areas where adequate infrastructure and services are available or can be made available.<br />

Diversify and expand the local economy, including promotion of recreation and tourism, while<br />

retaining the benefits of growth locally.<br />

The utilization of sites along State Highways 70, 65 and 20 by uses which would attract business<br />

activity from traffic passing through Yuba County shall be encouraged and promoted.<br />

Development of a comprehensive circulation system providing adequate levels of service while<br />

minimizing vehicle miles traveled (VMT) through appropriate application of alternative forms of<br />

transportation, including consideration of existing rail lines in future transportation planning.<br />

Development of a program to regularly monitor traffic levels to confirm the adequacy of current<br />

roadway improvements and assist in prioritizing future improvements.<br />

Closely coordinate land use planning and transportation planning to assure that roadways and<br />

other forms of transportation are adequate to handle projected need.<br />

Continuing promotion of regional transportation planning through appropriate intergovernmental<br />

forums, including but not limited to the regular update of the Yuba Sutter Congestion Management<br />

<strong>Plan</strong>.<br />

Evaluation and consideration of the effects of future land use changes on regional circulation,<br />

including State Highways 65, 70 and 20, as part of future land use decision making.<br />

Through-traffic routes and truck routes shall be designated by the County to discourage the use of<br />

neighborhood roadways, particularly Local/Residential Streets, by truck traffic.<br />

Project-specific environmental reviews shall include alternative roadway alignments that reduce<br />

or avoid impacts to nearby residents and businesses.<br />

Identification and incorporation of bikeways into the circulation system where it is determined<br />

that non-automobile travel modes are appropriate.<br />

Utilitarian and commuter bicycling facilities shall have higher priority than recreational facilities.<br />

Utilitarian trips include those made to work, school, shopping, appointments and similar<br />

destinations.<br />

The needs of bicyclists shall be considered when new roads are constructed or existing roads are<br />

upgraded.<br />

Secure bicycle parking shall be provided at or near public buildings, business districts, parks,<br />

playgrounds, shopping centers, schools, transit terminals, bus stops, and other bicycle traffic<br />

generators.<br />

The County shall promote mixed use development projects which incorporate residential,<br />

commercial and employment opportunities in a manner which reduces dependence on the private<br />

automobile.<br />

Adoption of the Yuba-Sutter Bikeway Master <strong>Plan</strong> and establishment of an ongoing bikeway and<br />

trail facility planning and development process under the auspices of an interested group such as<br />

the Trails Commission.<br />

Promote alternatives to single occupant automobile commuting, including paratransit, public<br />

transit and various forms of non-automotive travel, in order to reduce roadway congestion and<br />

enhance air quality.<br />

Promote development patterns which reduce automobile trips, including out-of-county commutes,<br />

in order to reduce traffic congestion and improve air quality.<br />

As population increases, the County shall support the development of multimodal transportation<br />

centers which integrate heavy rail, light rail and bus services.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 47 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Sacramento Transportation ARea NETwork (STARNET)<br />

Needs Assessment<br />

SACOG<br />

DATE November 2001<br />

The STARNET system design is based on an open and modular system<br />

architecture that facilitates system and subsystem component integration<br />

through standard communications interfaces.<br />

PURPOSE<br />

SUMMARY<br />

Several meetings were conducted with the agencies who currently had<br />

deployed transportation related systems within the Sacramento<br />

metropolitan area. During these meetings, the goal was to collect<br />

information regarding their hardware and software, as well as discuss<br />

agencies’ goals and obj ectives relative to the sharing and exchange of<br />

data/information within the region.<br />

The following list summarizes the high-level needs for STARNET.<br />

Ability to share cross jurisdictional signal timing data to improve<br />

traffic flow<br />

Ability to identify incidents which impact upstream/downstream<br />

traffic flow<br />

Ability to share video among agencies<br />

Ability to centrally archive traffic volumes<br />

“ This document has identified an architectural approach that essentially<br />

centralizes the data processing activity and provides a uniform data and<br />

control interface to the various stakeholders in the region. This is not<br />

the only approach that could be followed. In other parts of the country,<br />

agencies with similar goals to the STARNET stakeholders have opted for<br />

system architectures that distribute the processing throughout the agencies<br />

involved in a peer-to-peer configuration. While this type of an approach has<br />

performance benefits and affords greater functionality for the user<br />

community, it was deemed that such an approach for STARNET would<br />

require unnecessary capital investment for the initial functional<br />

requirements identified as part of this conceptual development process.”<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Specific improvements and recommendations are outlined in the report for the following interfaces<br />

with the STARNET system:<br />

City of Roseville<br />

City of Sacramento<br />

Caltrans RTMC<br />

Regional Transit<br />

Sacramento County<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 48 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Sacramento Transportation ARea NETwork (STARNET)<br />

Needs Assessment<br />

For new agencies, the following recommendations are presented:<br />

New Agencies (with traffic operations system)<br />

For new agencies with an existing Traffic Operations Center, it is also assumed that an existing video<br />

switcher and viewing system is already in place. If the new agency has devices and traffic data it<br />

would like to make available to the STARNET system, the Adapters and Device Servers (e.g., CCTV,<br />

Signals, DMS) would need to also be developed.<br />

New Agencies (device monitoring only)<br />

For new agencies that desire only device monitoring, a PC capable of web browsing is needed. If<br />

CCTV video-in-a-window viewing is desired, then there will need to be an ATM Network switch and<br />

frame grabber hardware in the PC. If a system of digitizing the CCTV video and making it available to<br />

the Internet is put in place, then the ATM switch and frame grabber would not be necessary to view<br />

CCTV video within the web browser.<br />

Backbone Communications<br />

While not specific to a single agency, a significant commitment is required to support the<br />

communications required for the STARNET deployment. As mentioned in this document, a preliminary<br />

communications analysis must be completed early-on in the design phase to capture the available<br />

options and summarize the costs / benefits associated with each approach. As part of the STARNET<br />

Needs Assessment analysis for each of the participating agencies, an assumption was made that an<br />

ATM communications backbone would be utilized. This was selected as a “ best-case” scenario for<br />

system performance.<br />

There may be other opportunities, which should be explored during the preliminary engineering phase<br />

of this project, to solidify the communications aspect of this project. If budget considerations require<br />

a less costly approach, the functionality of the system may be reduced. However, this must be<br />

assessed as part of the detailed system design process.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 49 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

City of Elk Grove Intelligent Transportation Systems Master <strong>Plan</strong><br />

City of Elk Grove<br />

DATE November 2004<br />

PURPOSE<br />

SUMMARY<br />

The Elk Grove Intelligent Transportation Master <strong>Plan</strong> Proj ect is to assess<br />

existing traffic signal operations on maj or arterials and to develop a plan to<br />

accommodate future development by providing the groundwork for future<br />

systems integration within the City of Elk Grove and between City systems<br />

and other external systems and agencies including but not limited to the City<br />

of Sacramento, the County of Sacramento, Sacramento Area Council of<br />

Government (SACOG) and Sacramento County Regional Transit. The Master<br />

<strong>Plan</strong> contains a concept plan as well as phased implementation plan.<br />

The report includes an existing needs analysis, technology analysis,<br />

functional requirements, communications analysis, funding alternatives,<br />

improvements recommendations, and an implementation plan.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Short-term recommendations for communication and ITS element improvement, include the following:<br />

Connection between Laguna/Bond Master location and Corporation Yard (Corp Yard wiring)<br />

Upgrade City’s existing onstreet system. Replace controllers/cabinets as needed and add system<br />

detectors on all segments (all construction during Phase 2 unless otherwise noted)<br />

Coordinate border signal responsibilities with the County of Sacramento and Caltrans where<br />

applicable<br />

Monitor recommended policy and process for collecting impact fees for ITS purposes or in-kind<br />

equipment/materials. Revise as necessary. Top defray program expenses, continue to require<br />

installation of new/upgraded conduit and equipment as a condition of new development or<br />

redevelopment<br />

Mid-term recommendations include:<br />

Initiate Traffic Management Center (TMC) in new Corporation Yard to manage signals and other<br />

devices (i.e. CCTV, DMS, etc.) (only if not done in the short term)<br />

Interconnect more signalized intersections and system detectors to new traffic control system<br />

Provide new conduit and twisted pair cabling to complete system on various roadways (specified<br />

in report)<br />

Upgrade existing twisted pair communication system to fiber optic cable on various roadways<br />

(specified in report). Add CCTV and system detectors.<br />

Deploy CCTV Cameras at key intersections<br />

Deploy approximately four dynamic message signs (DMS), appropriate locations to be identified<br />

Long-term recommendations include:<br />

Expand fiber optic communications system<br />

Expand CCTV system to include additional portions of Calvine, Sheldon, Bond and Elk Grove Blvd.<br />

as needed<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 50 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

City of Elk Grove Intelligent Transportation Systems Master <strong>Plan</strong><br />

Expand DMS system by deploying approximately six additional signs, appropriate locations to be<br />

determined<br />

Provide advanced traveler information (ATIS) system and disseminate concise, useful road and<br />

traffic condition reports to drivers<br />

Negotiate agreements with Regional Transit and cooperate on providing compatible transit<br />

enhancements<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 51 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Sacramento Regional ITS Architecture<br />

Sacramento Regional ITS Partnership<br />

DATE June 2001<br />

PURPOSE<br />

The Regional ITS Architecture for the Sacramento area proposes the ideal<br />

synthesis of cross-functional projects and sub-projects to better enhance and<br />

integrate the ITS infrastructure, functions and operations to achieve<br />

immediate and long term regional benefits to the residents of the<br />

Sacramento metropolitan area. Although benefit is realized through the<br />

deployment of individual ITS projects such as signal timing and control, the<br />

real benefit of ITS is achieved through the integration of systems and<br />

institutions. This region is still in the process of accomplishing these goals,<br />

demonstrated by documentation in this Report.<br />

The figure below excerpted from the report summarizes ITS deployments<br />

currently existing or under development:<br />

SUMMARY<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Recommendations in the architecture pertained to ITS planning and institutional issues include:<br />

Member agencies of the ITS Partnership pursue funding for a Regional Information Network that<br />

will allow regional integration or center-to-center communications between all traffic<br />

management and operations centers in the Sacramento area.<br />

A “user needs” study that will represent the result of individual systems review for: City of<br />

Sacramento, City of Roseville, Sacramento Regional Transit District (RT), Sacramento County, City<br />

of Citrus Heights and Caltrans. This study will identify some preliminary costs for systems<br />

integration, identify interface issues perhaps it will identify some additional benefits, preliminary<br />

to the Early <strong>Deployment</strong> <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 52 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Placer Parkway Interconnect Project<br />

http://www.pctpa.org/placerparkway/index.htm<br />

Placer County Transportation <strong>Plan</strong>ning Agency<br />

DATE January 2000<br />

PURPOSE<br />

SUMMARY<br />

The general purpose of Placer Parkway as identified in the Conceptual <strong>Plan</strong><br />

includes the following:<br />

Maximize mobility with a high-speed route that provides reliable interregional<br />

travel times over the long term (beyond 20 years) for the<br />

movement of people and goods, thereby facilitating access to jobs and<br />

accommodating growth under existing General <strong>Plan</strong>s;<br />

Avoid inducing urban growth in the agricultural areas not designated<br />

for development in existing General <strong>Plan</strong>s, and maintain the rural<br />

character of west Placer County and South Sutter County;<br />

Minimize environmental impacts;<br />

Improve public safety.<br />

As such, Placer Parkway is also an important component of the SACOG 2025<br />

Metropolitan Transportation <strong>Plan</strong>.<br />

Phase 1: Identify feasible corridor alternatives. As described in the<br />

Placer Parkway Corridor Preservation update: “Placer Parkway is<br />

envisioned to be an approximate 15-mile long high-speed<br />

transportation facility to connect State Route (SR) 65 in Placer County<br />

and SR 70/99 in Sutter County. It will link existing and planned<br />

development in the two counties. The Placer Parkway will also improve<br />

access to downtown Sacramento and to the Sacramento International<br />

Airport. Other transportation modes, such as bus rapid transit, may be<br />

developed in the corridor as well. The aim of the project is to preserve<br />

a corridor for right-of-way acquisition in this rapidly growing area.”<br />

Phase 2: Environmental Impact Statement/Environmental Impact<br />

Report<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Several modifications to the proposed alignments are outlined in the Technical Memorandum (11<br />

combinations of these conceptual alternative alignments are described). The PSR noted these<br />

subsequent studies would likely result in refinements to the corridor alternatives to avoid<br />

environmental issues that are identified.<br />

Work with the Sutter and Placer County staff to more specifically identify farm units, and<br />

evaluate corridor alignments using this information to minimize agricultural impacts.<br />

Modify alignments to reduce impacts to biological resources (for example, snake and bird<br />

habitats, and pool complexes)<br />

Modify each PSR (Project Study Report) corridor alignment alternative to avoid or minimize<br />

effects on resources such as vernal pools, existing communities and agricultural lands<br />

identify a corridor through the central and western segments that could avoid most impacts to<br />

existing communities, homes and businesses —either by adjusting the alignment that connects<br />

at Sankey Road northward slightly to avoid displacement of homes and businesses along Sankey<br />

Road, or by routing an alignment north of the Baseline community, then through the abandoned<br />

nursery property on Pleasant Grove Road and south of the existing industries on Pacific Avenue.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 53 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Placer Parkway Interconnect Project<br />

http://www.pctpa.org/placerparkway/index.htm<br />

Based on an analysis of the available cultural resources data presented above, the southern<br />

corridor alignments in the vicinity of the historic ranch complex should be considered a<br />

significant environmental impact that would be difficult to mitigate. This alignment should be<br />

moved to the west in this location to avoid this resource.<br />

It would be possible modify the PSR corridor alignment alternatives through the central segment<br />

that would reduce impacts to the developed environment and conflicts with major planned<br />

developments. The Placer Ranch and De La Salle University and Community development<br />

proposals are very recent in comparison. Because these projects are in the early conceptual<br />

stages, it is recommended that the Placer Parkway process use best efforts to coordinate with<br />

the Placer County’s planning process for Placer Ranch and De La Salle University and Community<br />

as these projects proceed.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 54 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE August 31, 2004<br />

PURPOSE<br />

Elk Grove-Rancho Cordova-El Dorado Connector<br />

Concept <strong>Plan</strong><br />

Southeast Corridor Study Draft<br />

SACOG<br />

(Prepared by DKS Associates, The Hoyt Company, LandPeople)<br />

Two primary goals:<br />

To engage a wide range of stakeholders in a discussion of purpose and<br />

need for the Connector project. The emphasis in this discussion was<br />

stakeholder input, specifically stakeholder needs and benefits.<br />

Develop a range of conceptually-defined project alternatives to begin<br />

the process of identifying viable project alternatives to be taken into a<br />

more detailed, technical environmental process. The emphasis was<br />

brainstorming, documenting ideas, and formulating alternatives.<br />

SUMMARY<br />

This study was intended to generate a wide range of stakeholder input on<br />

proj ect purpose and need for the Connector corridor, and to define a set of<br />

conceptually-defined proj ect alternatives to be considered in the<br />

environmental review process.<br />

The "Elk Grove-Rancho Cordova-El Dorado Connector" will link residential<br />

areas and employment centers in the corridor, relieving congestion on the<br />

overcrowded existing two-lane roadways that currently serve the corridor.<br />

The connector concept itself is intended to meet multiple purposes:<br />

Improve access and mobility, and develop new connections in the Elk<br />

Grove-Rancho Cordova-El Dorado County corridor (connecting from I-5<br />

and State Route 99 in the south to US 50 in the east).<br />

Preserve open space and wildlife habitat, with $15 million to serve as<br />

seed money for a larger program to preserve open space and critical<br />

wildlife habitat in the corridor.<br />

Enhance economic vitality by preserving accessibility to jobs centers in<br />

the corridor.<br />

Bring jurisdictions together to maximize funding for the Connector and<br />

develop a plan to build individual segments in a coordinated and<br />

integrated fashion.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Recommendations/Stakeholder needs identified in the study:<br />

Bring jurisdictions together to maximize funding to the region; capture discretionary funding for<br />

cost-effective projects for the Connector.<br />

Provide more options for travelers and the movement of goods and services to, from and within<br />

the corridor:<br />

Route options (e.g. avoiding I-5, US 50 and SR 99 for shorter trips, and avoiding<br />

local/residential streets for longer trips)<br />

Mode options (auto, transit, non-motorized)<br />

Coordinate the design and phasing of transportation improvements across jurisdictional lines for<br />

the Connector itself, and for intersecting roadways.<br />

Improve safety and security of multi-modal travel in the corridor (automobile, transit bicycling<br />

pedestrian, etc).<br />

Relieve traffic from local streets.<br />

Balance local general plan policies and circulation goals with the regional needs of the corridor.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 55 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


Elk Grove-Rancho Cordova-El Dorado Connector<br />

STUDY<br />

Concept <strong>Plan</strong><br />

Southeast Corridor Study Draft<br />

Provide and all-weather transportation facility (i.e. not subject to flooding).<br />

Provide flexibility to develop appropriate levels and modes of transit service in the future,<br />

incorporating ITS elements.<br />

Provide better mobility for travel to/from/within the corridor.<br />

Enhance the accessibility and attractiveness of existing and planned employment areas in the<br />

corridor.<br />

Balance needs for local access to land uses and shorter trips with regional needs for longer trips.<br />

Establish continuity and regional identity for the Connector; develop consistent design &<br />

maintenance standards, and signage throughout the corridor.<br />

Develop recreational open space in the corridor.<br />

Preserve sensitive habitat in the corridor.<br />

Develop and implement transportation improvements in a way that allows continuation of<br />

productive agricultural uses in the corridor.<br />

Develop the Connector project in a manner that minimizes induced growth.<br />

Protect the natural historic, and cultural resources within the corridor.<br />

Enhance/maintain the livability of communities adjacent to the Connector.<br />

Provide/enhance access to recreational open space:<br />

Vehicular (e.g. staging areas, parking, access roadways).<br />

Non-motorized (e.g. hiking, biking, equestrian trails).<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 56 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Sacramento Exploratory Process<br />

Sacramento Transportation & Air Quality Collaborative<br />

DATE 1998<br />

PURPOSE<br />

SUMMARY<br />

Recognizing the urgency of the issues and challenges of developing answers<br />

to the rapid growth question commands widespread community support. In<br />

the fall of 1998, eight public agencies j oined together to create the<br />

Sacramento Exploratory Process for Transportation and Air Quality. The<br />

sponsoring agencies include the Cities of Citrus Heights, Folsom, Galt,<br />

Sacramento, SACOG, Sacramento County, Sacramento Metropolitan Air<br />

Quality Management District, and Sacramento Regional Transit District.<br />

Aware of the fact that transportation and air quality are key elements in the<br />

future health and vitality of the region, the sponsoring agencies established<br />

the Exploratory Process to assess the need for and the possible outcome of a<br />

comprehensive planning process which would address transportation, air<br />

quality and possibly other closely-related issues (i.e., land use). This<br />

assessment was to have included recommendations concerning geographic<br />

area; likelihood of commitment and participation by affected parties; and<br />

potential for community consensus.<br />

Guiding principles of the process include:<br />

Move people and goods efficiently;<br />

Provide personal mobility and access for all people to all parts of the<br />

community;<br />

Enhance neighborhoods;<br />

Achieve measurable progress towards meeting air quality standards;<br />

Encourage economic development;<br />

Recognize political and market place realities;<br />

Create innovative solutions; and<br />

Recognize the regional context.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Attainment of the State Implementation <strong>Plan</strong> for Ozone.<br />

Consideration of a multi-modal connector between Highway 50 and Interstate 80<br />

Identify other major travel corridors and initiate procedures necessary for project implementation<br />

Ensure better linkage between people and job centers, with a focus on job access for lower<br />

income, disabled, and senior persons.<br />

Consideration of relevant land use initiatives to reduce travel demand and increase use of<br />

alternative modes<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 57 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

San Joaquin Valley ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

AGENCY<br />

San Joaquin Valley ITS Technical Advisory Committee and Steering<br />

Committee<br />

San Joaquin Council of Governments (SJCOG)<br />

California Department of Transportation<br />

DATE September 30, 2001<br />

The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> is intended to provide a starting point for<br />

regional ITS coordination, programming, and implementation efforts over the<br />

next twenty years. Over the past decade, ITS has become a recognized tool<br />

for improving the operation and efficiency of the transportation system.<br />

Several agencies in the San Joaquin Valley have already undertaken various<br />

ITS deployment efforts ranging from traffic signal system improvements to<br />

transit management systems and from enhanced emergency service<br />

Computer Aided Dispatch to freeway surveillance projects.<br />

PURPOSE<br />

SUMMARY<br />

The development of this <strong>Plan</strong> represents a new level of effort in the<br />

coordinated deployment of ITS projects. The objectives of the study are to:<br />

Gain the participation of transportation stakeholders and community<br />

members;<br />

Identify transportation needs that have the potential to be addressed by<br />

ITS technologies;<br />

Evaluate which ITS elements would be beneficial, cost-effective and<br />

implementable to meet the identified needs; and<br />

Develop a plan outlining the short-, medium-, and long-range<br />

application of ITS technology including specific operations and<br />

maintenance plans and financing.<br />

This document identifies and prioritizes ITS Proj ects for the San Joaquin<br />

Valley Intelligent Transportation System (ITS) <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

These proj ects were prioritized through a development process that mapped<br />

the region’ s needs to ITS market packages. Market Packages define ITS<br />

building blocks for meeting user needs within the guidelines defined by the<br />

National ITS Architecture.<br />

The selection of Market Packages was the first of two steps in the<br />

development of a full ITS system architecture for the San Joaquin Valley. A<br />

technical depiction of existing and planned ITS elements and the<br />

relationships between them, both technical and institutional, is the subj ect<br />

of specific sections of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 58 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

San Joaquin Valley ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

RECOMMENDATIONS FROM DOCUMENT<br />

A cornerstone of the ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> for the Region is the continued development of two<br />

regional Transportation Management Centers (TMCs). The recommendation in the <strong>Strategic</strong> <strong>Plan</strong> is to<br />

move forward with a more fully functional TMC for both districts that has many of the elements of a<br />

TMC in a more urban setting, but that is tailored to the urban and rural character of the Valley.<br />

Personnel in charge of the TMC will:<br />

Monitor traffic flow through roadway sensors and CCTV cameras at strategic locations<br />

Control ramp meters installed in congested freeway sections to help traffic flow more smoothly<br />

Serve as a focal point for regional traveler information that would include, for example, sending<br />

messages to strategically placed roadside changeable message signs (CMS) or highway advisory<br />

radio (HAR) systems and providing traveler information to kiosks located at rest areas, truck stops,<br />

etc. to allow long-distance traffic to avoid major incidents and road closures.<br />

Coordinate communications with the CHP to more rapidly respond to traffic incidents and better<br />

perform incident management activities<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 59 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Tahoe Gateway ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Report #1/Report #2<br />

Prepared for Nevada, Sierra, Placer, El Dorado Counties and Caltrans<br />

DATE January 2002 (Report #1) / May 2002 (Report #2)<br />

PURPOSE<br />

The proj ected growth within the study area, as well as the surrounding<br />

areas, will be significant in the next decade and beyond. This ongoing growth<br />

will continue to stress the current transportation facilities and resources of<br />

the Tahoe Gateway Region beyond their capacity. Intelligent Transportation<br />

Systems (ITS) offer potential new solutions that require further evaluation.<br />

The overall goal of the proj ect will be to, in a coordinated and cooperative<br />

manner, develop a strategic deployment plan defining the potential ITS<br />

applications available to address the identified needs of the region.<br />

After the functional requirements for the Tahoe Gateway Architecture were<br />

determined through stakeholder input and outlined in Report #1, the<br />

architecture of existing ITS and communications in the Region was mapped.<br />

The selected architecture alternative was chosen by the Region and Caltrans<br />

because it maintains primary control of most ITS elements with Caltrans, but<br />

allows all of the agencies to share data in real time. It also provides the<br />

flexibility for some ITS elements to be controlled by other agencies without<br />

diminishing the sharing of data throughout the region. The selected<br />

architecture is shown below.<br />

SUMMARY<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 60 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Tahoe Gateway ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Report #1/Report #2<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Provide Regional ITS Program Leadership. This oversight continuance should include regular<br />

meetings of the group, monitoring of ITS implementation progress, coordination with the Caltrans<br />

District 3 Regional TMC, and a responsibility to oversee maintenance of the regional ITS plan and<br />

architecture. In addition the committee will need to be involved in coordination of system<br />

linkages, integration and interoperability issues within the region and with statewide and national<br />

systems, and agreements regarding data sharing with neighboring regions such as the Sierra<br />

Nevada region, Tahoe Basin, California/Oregon Advanced Transportation Systems (COATS) region,<br />

and the San Francisco Bay area.<br />

Mainstream ITS into the Transportation Process. Although many ITS projects are already<br />

included in the process, others will need to be added. In some cases ITS technologies may need to<br />

be incorporated into the planning and programming process as stand alone projects, while more<br />

frequently these deployments can simply be included in the scope of larger transportation<br />

projects that share location or objective.<br />

Implement and Maintain the ITS <strong>Plan</strong>. In addition to pursuit of implementation of the projects<br />

identified herein, the stakeholder committee should revise this regional ITS strategic plan as<br />

necessary. This could include revisions of top level issues such as program goals or it could focus<br />

on specific issues such as project scoping and scheduling and detailed architecture refinements.<br />

Establish Mechanisms to Coordinate with Adjacent Regions. The approach will need to provide<br />

a method to address the coordination issues on a day to day basis. The approach must provide the<br />

flexibility for responsible individuals to accommodate dynamic and unforeseen issues associated<br />

with traveler information dissemination and systems integration.<br />

Maintain the Regional Architecture. The architecture should remain a valuable tool to aid in<br />

systems integration throughout implementation of the plan and beyond. As ITS elements are<br />

deployed and connections are made enhancing integration, agencies that will be newly impacted<br />

by this integration will need to be contacted to validate the architecture in general and the<br />

elements which represent their involvement in particular. This maintenance oversight effort will<br />

require Committee members to become familiar with the architecture and thereby understand<br />

how changes in the transportation infrastructure impact it.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 61 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Tahoe Basin ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

AGENCY<br />

DATE March 2003<br />

PURPOSE<br />

Tahoe Metropolitan <strong>Plan</strong>ning Organization and Tahoe Regional <strong>Plan</strong>ning<br />

Agency<br />

The Tahoe Basin ITS <strong>Strategic</strong> <strong>Plan</strong> is a road map to implement an integrated<br />

system of technology-based transportation strategies within this five-county,<br />

bi-state region. This report identifies the technology-based opportunities for<br />

improving the transportation system in the Tahoe Basin. The <strong>Plan</strong> is intended<br />

to establish the need for ITS investments in the region, identify relative<br />

priorities to direct ITS investment, and to identify specific proj ects to be<br />

deployed to address identified needs. The phasing of the recommended<br />

proj ects reflects the relative priorities identified in the development of the<br />

plan.<br />

The report describes existing and planned ITS proj ects, a Regional ITS<br />

Architecture, <strong>Deployment</strong> Considerations and Program Management in<br />

accordance with the following Vision for the Tahoe Basin:<br />

SUMMARY<br />

ITS will be integrated into the Tahoe Basin transportation system<br />

infrastructure and operations on a strategic basis:<br />

To provide accurate and timely information to all travelers,<br />

To provide public education about and awareness of travel options and<br />

conditions,<br />

To address congestion and safety problems,<br />

To enhance emergency preparedness and response,<br />

To encourage use of transit and other modes as alternatives to the<br />

automobile whenever possible,<br />

To improve the efficiency and effectiveness of operational and<br />

maintenance functions of all transportation modes,<br />

To support transportation planning and system management functions<br />

and,<br />

To support and encourage interagency operability and effectiveness.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Roadway Traveler Information<br />

Inform travelers about travel delays from recurrent congestion, special events, incidents, weather<br />

problems, and other emergencies.<br />

Increase the knowledge of visitors about travel conditions and activities during the off-peak times,<br />

days of the week or seasons.<br />

Improve the ability of transportation agencies to warn travelers of potentially difficult roadway<br />

conditions.<br />

Traffic Management and Safety<br />

Enhance traffic flow on the major roads providing access to and circling the lake, improve safety,<br />

and reduce the impact of visitor volumes during peak travel times.<br />

Enhance traffic monitoring capabilities to collect and verify information on roadway conditions<br />

and vehicle flows.<br />

Facilitate traffic flow to improve ingress to and egress from, and minimize the traffic impact of<br />

activity centers and special events.<br />

Improve the ability of transportation agencies to identify the nature and location of difficult<br />

driving conditions.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 62 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Tahoe Basin ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Reduce number and severity of crashes related to congestion, roadway incidents or other<br />

conditions affecting the roadway.<br />

Provide safe opportunities for walking and the use of bicycles.<br />

Transit Accessibility and Service<br />

Increase awareness of visitors and residents about the travel options available including transit,<br />

bicycling, walking and other non-motorized forms of transport.<br />

Provide travelers with real-time information about transit services, routing, schedules, and fares.<br />

Improve the efficiency of transit service.<br />

Improve the reliability of transit service.<br />

Improve the coordination between transit service providers.<br />

Increase the ability of operators to manage fleet vehicles.<br />

Maintenance Activities<br />

Improve the safety and efficiency of highway maintenance, snow clearance activities, and<br />

roadway anti-icing and de-icing.<br />

Inform travelers about travel delays from construction, maintenance, and special events.<br />

System Integration and Coordination<br />

Increase the speed, consistency, accuracy and comprehensiveness with which transportation<br />

system information is shared between the transportation and emergency response agencies of the<br />

Basin.<br />

Increase the ability of agencies to communicate directly to coordinate traffic management, transit<br />

management, special event management or emergency response.<br />

Improve the clarity of roles and responsibilities of Tahoe Basin agencies in responding to<br />

emergencies on the Basin’s transportation system.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 63 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Bay Area Regional ITS <strong>Plan</strong><br />

http://www.iteris.com/mtcits/assets/documents/Bay_Area_ITS_<strong>Plan</strong>_-<br />

_final_-_submittal.pdf<br />

Metropolitan Transportation Commission<br />

DATE June 2004<br />

PURPOSE<br />

SUMMARY<br />

The main purposes for the Bay Area Regional ITS <strong>Plan</strong> are stated in the<br />

report as follows:<br />

The need for transportation system management to function at a larger<br />

corridor and regional scale to address growing problems; individual<br />

projects can only address a portion of the problem<br />

Concerns over the lack of an explicit coordination framework across all<br />

projects<br />

Potential technical incompatibilities preventing needed information<br />

exchange<br />

Missed opportunities for enhanced functions or services within and<br />

across projects from lack of regional perspective<br />

Phase 1 – focused on the collection of ITS project inventory and an<br />

assessment of that inventory compared to regional transportation<br />

planning goals. Those goals include the following:<br />

Mobility – improve the ease and convenience of using the<br />

transportation system<br />

Safety<br />

Equity<br />

Environment<br />

Economic Vitality<br />

Community Vitality<br />

Phase 2 – proceeded through a regional architecture development<br />

process as suggested by the FHWA, resulting in a Regional ITS <strong>Plan</strong> for<br />

implementing systems based on a regional architecture and for<br />

providing technical guidance on the existing and planned system<br />

connections. Functional requirements were defined through an<br />

extensive stakeholder participation process. Specific elements of the<br />

architecture including interconnects and information flows can be seen<br />

in the report, along with potential ITS projects recommended for the<br />

regional architecture.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

The various activities and deliverables in the Bay Area Regional ITS <strong>Plan</strong> Process area are available as<br />

separate Technical Memoranda. In the Operational Concepts, Functional Requirements, Proj ect<br />

Sequencing and other activities, the overall, general regional ITS Action Goals guiding the proj ects are<br />

as follows:<br />

Mobility<br />

Mitigate Congestion<br />

Improve travel times in congested corridors<br />

Improve the reliability of the transportation system<br />

Enhance Transit Use<br />

Increase coordination and convenience of transit<br />

Expand Travel Options<br />

Provide travelers with good information<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 64 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


Bay Area Regional ITS <strong>Plan</strong><br />

STUDY http://www.iteris.com/mtcits/assets/documents/Bay_Area_ITS_<strong>Plan</strong>_-<br />

_final_-_submittal.pdf<br />

Safety<br />

Improve Safety and Security<br />

Ensure the safety of motorists<br />

Ensure the safety and security of transit system users<br />

Ensure effective transportation operations coordination during emergencies<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 65 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Regional Street Network and Address Database System Architecture and<br />

Design<br />

Sacramento Region GIS Cooperative<br />

DATE February 27, 2002<br />

SACOG, with the city and county governments of the region formed the<br />

Sacramento Area GIS Cooperative to improve the use of GIS and spatial data<br />

within the region through effective utilization of the available GIS resources.<br />

Primary obj ectives of the Cooperative are to reduce redundant data and<br />

application development activities, improve regional data quality, provide<br />

access to a common and standardized GIS data framework, and encourage<br />

technology and knowledge transfer. To accomplish these obj ectives, the GIS<br />

Cooperative adopted a GIS <strong>Strategic</strong> <strong>Plan</strong> that that lays out the vision and<br />

specific recommendations for the development of common datasets,<br />

applications, and institutional processes.<br />

PURPOSE<br />

SUMMARY<br />

To follow-through on recommendations from the strategic and street<br />

network management plans, the Cooperative has initiated this proj ect to<br />

develop a system that will allow all member agencies to contribute and<br />

maintain an integrated and centrally located street network database with<br />

complete street address database as per the Cooperative requirements.<br />

Through this project, the Cooperative will build a street network and address<br />

database that will serve multiple applications across the member agencies<br />

ranging from simple mapping, routing, permitting, and asset management<br />

applications to more complex vehicle dispatching and tracking, ITS, and<br />

emergency response applications. When fully implemented, it is expected<br />

that public and private organizations responsible for public safety, transit,<br />

planning, engineering, health, public works, and other local/ regional<br />

services will be the primary users of the system.<br />

Key components of the planned system include:<br />

A central framework data repository that will be the regional system of<br />

records<br />

A communication system that will allow member agencies to connect to<br />

the central database, and use and maintain relevant data over a<br />

secured network<br />

Tools and applications that will facilitate agency specific transactional<br />

or complete data upload/download, agency specific online data<br />

maintenance, data validation and error checking, browsing of metadata<br />

and content of the repository, and selection, extraction, and download<br />

of necessary data through proper user authentication, etc.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 66 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

Regional Street Network and Address Database System Architecture and<br />

Design<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Due to the nature of this project, the recommended steps to complete the street and address database<br />

are as follows:<br />

Requirements gathering and analysis – A very important part of the planning and designing phase<br />

of any information system development is the requirements gathering. Under this task,<br />

requirements will be gathered from key Cooperative member agencies through meetings and<br />

discussions. A list of system and database requirements will be produced following analysis of<br />

gathered information.<br />

System Architecture Design – Under this task, a comprehensive design of the system architecture<br />

that will meet the requirements identified in the previous task will be produced.<br />

Database Design – Central database will be the heart of this system. This task will result in a<br />

database design that will fulfill the data requirements of the member agencies.<br />

Data Development and System Implementation <strong>Plan</strong> – To implement a pilot system based on the<br />

system architecture and the database design, a plan that will layout methodologies and procedures<br />

to bring in data from various sources will be developed. A set of system implementation guidelines<br />

will also be developed to facilitate the commencement of the system.<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 67 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

Multi-Corridor Study<br />

System Expansion and Phasing Strategy<br />

Sacramento Regional Transit District<br />

DATE June 2001<br />

PURPOSE<br />

SUMMARY<br />

The System Expansion and Phasing Strategy of the Multi-Corridor Study<br />

outlines investment priorities so that Regional Transit can effectively pursue<br />

new funding.<br />

This report provides Regional Transit with a first phase, 10-Year strategy and<br />

a broad Long-Range (Post 2012) for expanding transit service. The strategy<br />

calls for a mix of federal, state, regional, and local funding commitments.<br />

Most of the elements in the strategy are located within Regional Transit’s<br />

service area, Sacramento County, including two high-priority light rail<br />

corridors and three bus enhancement corridors. The strategy is also<br />

regional, including proj ects outside Regional Transit’ s service area, including<br />

Regional Rail, light rail expansion to West Sacramento/ Davis and enhanced<br />

bus connections to Placer County.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

Specific recommendations in the 10-Year strategy include:<br />

High priority light rail corridors: South Sacramento Corridor Phase 2 “Locally Preferred<br />

Alternative” (LPS) Extension, DNA Extension, West Sacramento/Davis Extension<br />

Bus enhancement corridors<br />

Auburn to Davis corridor<br />

Expansion of transit fleet<br />

Additional maintenance facilities<br />

Transit supportive land uses<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 68 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

AGENCY<br />

DATE<br />

PURPOSE<br />

SUMMARY<br />

California Statewide ITS Architecture<br />

Caltrans<br />

October 25, 2004<br />

The California ITS Architecture and System <strong>Plan</strong> accomplishes two main<br />

goals:<br />

Development of an ITS architecture focusing on state-level services and<br />

identifying potential interregional services (those services that are<br />

regionally deployed, but that have a potential for improvement through<br />

coordination among regions) in California that supplements the regional<br />

ITS Architectures and deployment plans. The intent is to ensure that<br />

statewide services are deployed in a coordinated and cost-effective<br />

manner, thereby adhering to the “regional architecture” requirement<br />

described in the above summary of the Final Rule for those projects<br />

developed at this level and to facilitate partnership, coordination and<br />

potentially integration among regions where added benefit to the<br />

transportation system may be affected by such interregional<br />

cooperation.<br />

Development of a 10-year System <strong>Plan</strong> that describes the blueprint for<br />

deployment of specific projects that fall within this category of<br />

statewide and interregional services. Based on the Final Rule<br />

summarized above, each of these projects will require that a systems<br />

engineering approach be taken when it is developed and throughout the<br />

project life cycle.<br />

The proj ect includes an existing statewide and inter-regional ITS proj ect<br />

inventory, user needs assessment, operational concept and functional<br />

requirements specifications, technical details of the architecture interfaces,<br />

and plans for project implementation and architecture maintenance plans.<br />

RECOMMENDATIONS FROM DOCUMENT<br />

The following “ Desired Outcomes” for the next 10 years were developed and agreed upon by the<br />

proj ect stakeholders, including SACOG. The outcomes are intended to serve as guidelines for ITS<br />

deployment throughout the state, not as mandatory milestones that must be achieved within the 10-<br />

year timeframe.<br />

TRAFFIC MANAGEMENT:<br />

Coordinated traffic management operational strategies (including traffic management, incident<br />

management, Amber Alert, others) among state, regional, and local agencies resulting in improved<br />

interregional mobility<br />

Uniform traffic management software systems in each Caltrans District (where traffic management<br />

systems are used/needed) that are consistent and increase efficiency of system maintenance<br />

Availability of the same traffic management data in a variety of accessible formats (for example,<br />

visual, audio, large-print) (see also Traveler Information, Public Transportation)<br />

A comprehensive, real-time data collection infrastructure for multiple agencies, multiple levels,<br />

and multiple purposes (see also Traveler Information)<br />

Systems that comply with National ITS Standards (see also Traveler Information)<br />

Improved mobility on state routes serving Ports (see also Goods Movement)<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 69 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

California Statewide ITS Architecture<br />

TRAVELER INFORMATION:<br />

Traveler information systems on a region-by-region basis, as desired by each region, with provision<br />

for links between regional systems<br />

Public and private opportunities for dissemination for traveler information<br />

CVO-tailored real-time traveler information for truckers statewide (see also Goods Movement)<br />

Availability of the same traveler information in a variety of accessible formats (for example,<br />

visual, audio, large-print) (see also Traffic Management, Public Transportation)<br />

A comprehensive, real-time data collection infrastructure for multiple agencies, multiple levels,<br />

and multiple purposes (see also Traffic Management)<br />

Systems that comply with National ITS Standards (see also Traffic Management)<br />

An inter-regional multi-modal trip planner that serves as a gateway or interface to other trip<br />

planners, and that incorporates real-time transit information (see also Public Transportation)<br />

En-route real-time public transportation information available on a statewide basis on key<br />

corridors (see also Public Transportation)<br />

PUBLIC TRANSPORTATION:<br />

Single e-payment accounts for users for both electronic toll collection and transit fare payment at<br />

regional and inter-regional levels with account reconciliation that is seamless to users (see also<br />

Electronic Payment)<br />

Universal e-payment devices for users for [each of] electronic toll collection and fare payment,<br />

which make(s) the system(s) transparent to the users (see also Electronic Payment)<br />

Ability to expand the e-payment account/media to cover other transactions such as goods<br />

movement payments, electronic parking payments, etc. (see also Electronic Payment)<br />

Inter-regional coordination of delays on major transit services to avoid stranding passengers<br />

making common connections between regions (this concept is also known as connection<br />

protection)<br />

An inter-regional multi-modal trip planner that serves as a gateway or interface to other trip<br />

planners, and that incorporates real-time transit information (see also Traveler Information)<br />

En-route real-time public transportation information available on a statewide basis on key<br />

corridors (see also Traveler Information)<br />

Availability of en-route real-time public transportation traveler information in a variety of<br />

accessible formats (for example, visual, audio, large-print) (see also Traffic Management, Traveler<br />

Information)<br />

Communications systems accessible by drivers and passengers that notify appropriate agencies<br />

(the transit agency itself, or police, fire or ambulance) in emergency situations.<br />

ELECTRONIC PAYMENT:<br />

Single e-payment accounts for users for both electronic toll collection and transit fare payment at<br />

regional and inter-regional levels with account reconciliation that is seamless to users (see also<br />

Public Transportation)<br />

Universal e-payment devices for users for [each of] electronic toll collection and fare payment,<br />

which make(s) the system(s) transparent to the users (see also Public Transportation)<br />

Ability to expand the e-payment account/media to cover other transactions such as goods<br />

movement payments, electronic parking payments, etc. (see also Public Transportation)<br />

GOODS MOVEMENT:<br />

One-stop state, interstate, and federal credentialing for all commercial vehicles traveling in<br />

California with opportunities for local agencies to be involved on a voluntary basis<br />

Integrated public agency goods and carrier data collection/tracking software for real-time data<br />

exchange and coordination of agency efforts<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 70 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


STUDY<br />

California Statewide ITS Architecture<br />

CVO-tailored real-time traveler information to truckers throughout the state<br />

Improved mobility on state routes serving Ports<br />

VEHICLE SAFETY AND CONTROL:<br />

Caltrans leadership at the state level (including resources and recommendations) to ensure that<br />

vehicle safety and control initiatives throughout the state are capable of interfacing with federal<br />

VII (Vehicle Infrastructure Integration) or other vehicle-infrastructure related initiatives and<br />

programs<br />

DATA ARCHIVING:<br />

A statewide archived data service for state-level data that is available for use by regions as a<br />

resource as desired by each region<br />

EMERGENCY MANAGEMENT:<br />

Coordinated HAZMAT transportation routes and procedures statewide and with adjoining states,<br />

with voluntary involvement by local and regional agencies<br />

Coordinated statewide response procedures for disasters and evacuations that are developed in<br />

coordination with adjoining states' and national procedures and guidelines, with voluntary<br />

involvement by local and regional agencies<br />

MAINTENANCE AND CONSTRUCTION MANAGEMENT:<br />

A real-time work zone monitoring system for use in Caltrans work zones that is coordinated with<br />

District traffic management systems<br />

Roadway condition monitoring that is implemented as needed at a district level for detection of<br />

icy bridges and other pavement conditions, that is coordinated with District traffic management<br />

and traveler information systems<br />

097860000 SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

Existing Conditions Summary Report 050105 71 Task 1.1 – ITS Existing Conditions Report<br />

03/15/05


Appendix D


SACOG ITS System <strong>Deployment</strong> <strong>Plan</strong><br />

Task 1.1: Existing Conditions Report ­ APPENDIX<br />

Projects Inventory as cited in Existing Documents<br />

System Existing <strong>Plan</strong>ned Programmed Source Date Agency<br />

STARNET Various traffic and transit operation centers in the region; hardware and software upgrades enabling a<br />

wide­area network to share transportation data and operations. Fiber optic and wireless infrastructure is included<br />

in the project.<br />

•<br />

STARNET Needs Assessment 11/1/01 SACOG<br />

Expansion of Capitol Corridor Train Service • MTP2025 5/15/02 SACOG<br />

Commuter rail service between Davis/Dixon and Auburn using the UP/Amtrak facilities ($135 mil) • MTP2025 5/15/02 SACOG<br />

Light rail extended to Natomas Town Center and Sacramento Airport, from Meadowview to Cosumnes River •<br />

College and Elk Grove, from Watt to Antelope, and from Downtown Sacramento to West Sacramento.<br />

MTP2025 5/15/02 SACOG<br />

Expansion of bus and van service regionwide, including a large increase in service for elderly and disabled<br />

•<br />

persons.<br />

MTP2025 5/15/02 SACOG<br />

A Rancho Cordova to South Placer Multi­modal Connector. • MTP2025 5/15/02 SACOG<br />

Install signals on U.S. 50 ramps at Ponderosa Road, South Shingle Springs, and North Shingle Road<br />

Signal installation at U.S. 50 eastbound ramps<br />

Ramp metering at all interchanges from Foresthill Road to the Sacramento County Line.<br />

Install Smart Traffic Calming in south Midtown area.<br />

•<br />

•<br />

•<br />

•<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.).<br />

Construct Traffic Operation System (Jct. 50 to I­5)<br />

Operating and Maintenance for Arden Way Smart Corridor from 2010 to 2025.<br />

•<br />

•<br />

•<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

Smart Corridor on Arden Way from Del Paso to Watt Ave.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

Connect traffic signals, including ITS technology, that are located outside of the Central City to the City’s existing<br />

Traffic Operations Center.<br />

Widen Fair Oaks Blvd from Marconi Ave. to Engle Rd. from 4 to 6 lanes including signal modifications at Marconi,<br />

Stanley, Grant, and Engle Rd.<br />

•<br />

•<br />

•<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

Sacramento Regional Transit District: purchase computerized train tracking system that will provide automatic<br />

train locations and a public address system to advise customers of train approaches and service delays.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Bus Rapid Transit In Sacramento: Stockton Boulevard, construct bus rapid transit improvements from Cosumnes<br />

College to downtown Sacramento.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Kimley­Horn and Associates 1 5/4/2005


SACOG ITS System <strong>Deployment</strong> <strong>Plan</strong><br />

Task 1.1: Existing Conditions Report ­ APPENDIX<br />

Projects Inventory as cited in Existing Documents<br />

System Existing <strong>Plan</strong>ned Programmed Source Date Agency<br />

Bus Rapid Transit In Sacramento County, implement bus rapid transit on the Sunrise Boulevard corridor.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Bus Rapid Transit In Sacramento County, implement bus rapid transit on Watt Avenue corridor.<br />

•<br />

MTP2025 5/15/02 SACOG<br />

Sacramento Regional Transit District: retrofit existing communication kits with upgraded audio system and<br />

automatic interior exterior visual signs for stop announcements and train destinations.<br />

Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp metering,<br />

CCTV)<br />

Yolo County portion of I­5 traffic operations system and ramp metering.<br />

U.S. 50 Install ramp meters and modify ramp design at South River Rd. interchange.<br />

U.S. 50 Jefferson Blvd. interchange— expand the ramps and signals from 1 to 2 lanes, add ramp metering and<br />

turn lanes, and related street closures.<br />

Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

•<br />

•<br />

•<br />

•<br />

•<br />

•<br />

•<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

MTP2025 5/15/02 SACOG<br />

Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations, closed<br />

•<br />

circuit television cameras, changeable message signs, highway advisory radio, weather monitoring systems, loop<br />

detectors, etc.<br />

MTP2025 5/15/02 SACOG<br />

California High Speed Rail • MTP2025 5/15/02 SACOG<br />

• Elk Grove ­ Rancho Cordova ­ El Dorado<br />

Elk Grove ­ Rancho Cordova ­ El Dorado Connector<br />

Connector Concept <strong>Plan</strong> 8/31/04 SACOG<br />

Regional Street Network System Design<br />

•<br />

Regional Street Network and Address<br />

Database System Architecture and Design 2/27/02 SACOG<br />

City of Sacramento City Traffic Operations Center • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

County of Sacramento Traffic Operations Center • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Caltrans and CHP Regional Transportation Management Center • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Sacramento International Airport Transportation Management Center • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Emergency Response Telecommunications Center • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

City of Sacramento Signal System/Surveillance • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Citrus Heights Signal System/Surveillance • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

City of Roseville Signal and Communications System • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Caltrans Ramp Meter/Survillance • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Sacramento Regional Transit District ­ Fixed Route • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Roseville Transit ­ Fixed Route and Paratransit • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Yolo Transit ­ Fixed Route • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Sacramento Regional Transit District ­ Light Rail and Bus TMC • Sacramento Regional ITS Architecture 6/01 Regional ITS Partnership Committee<br />

Eleven Ramp meters planned between Sacramento/El Dorado County line and Placerville • Tahoe Gateway ITS SDP 01/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Six Ramp meters on SR65 between Lincoln and I­80 • Tahoe Gateway ITS SDP 01/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Traffic monitoring stations near the Sacramento/Placer County line in Roseville • Tahoe Gateway ITS SDP 01/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA Weather<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

radio)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Sacramento 511<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Communications Study (emphasizes transit, emergency services, planned ITS, highway maintenance, cellular<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

coverage, incident management, links to virtual TMCs)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Kimley­Horn and Associates 2 5/4/2005


SACOG ITS System <strong>Deployment</strong> <strong>Plan</strong><br />

Task 1.1: Existing Conditions Report ­ APPENDIX<br />

Projects Inventory as cited in Existing Documents<br />

System Existing <strong>Plan</strong>ned Programmed Source Date Agency<br />

Upgrade Caltrans District 3 Regional TMC to manage US­50, I­80 and other ITS deployments (includes<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

coordination with Nevada and Tahoe Basin to ensure consistency)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Regional Incident/Emergency Management <strong>Plan</strong> (incorporates proposed AVI/AVL technologies for emergency<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

response vehicles)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

temporary signals, incident command center, and communications to RTMC)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Placerville Signal System Technology Advances<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Placerville Signal Replacement on Highway 50<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

US 50 Surveillance (including 4 CCTV or web cameras and 6 traffic monitoring stations)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Public Transit ­ Implement/Expand AVI/AVL/CAD technologies<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Install Animal Vehicle Collision Avoidance Systems ­ Highway 49 and US 89 in El Dorado County<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Emergency Vehicles ­ AVI/AVL (including tracking equipment in dispatch and TMC)<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Install Rock/Mudslide and Avalanche Detection and Warning System<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Tahoe Gateway ITS SDP ­ Regional Arch and<br />

•<br />

Maintenance Vehicle Guidance Technology<br />

Implementation <strong>Plan</strong> 05/02 Placer, El Dorado, Nevada, Sierra Counties and Caltrans<br />

Sacramento Regional Transit District website<br />

•<br />

Amtrak Folsom Light Rail Extension<br />

(http://www.sacrt.com) current Sacramento Regional Transit District<br />

Sacramento Regional Transit District website<br />

•<br />

South Line Phase II (South Sacramento Corridor)<br />

(http://www.sacrt.com) current Sacramento Regional Transit District<br />

Downtown/Natomas/Airport (DNA) ­ new transit options between downtown Sacramento and South and North<br />

Sacramento Regional Transit District website<br />

•<br />

Natomas and the Sacramento International Airport<br />

(http://www.sacrt.com) current Sacramento Regional Transit District<br />

Elk Grove signals ­ Connection between Laguna/Bond Master location and Corporation Yard (Corp Yard wiring)<br />

•<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Elk Grove signals ­ Upgrade City’s existing onstreet system. Replace controllers/cabinets as needed and add<br />

•<br />

system detectors on all segments<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Elk Grove signals ­ Coordinate border signal responsibilities with the County of Sacramento and Caltrans where<br />

•<br />

applicable.<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Initiate Traffic Management Center (TMC) in new Corporation Yard to manage signals and other devices (i.e.<br />

•<br />

CCTV, DMS, etc.)<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Deploy CCTV Cameras at key intersections • Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Expand fiber optic communications system • Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Expand DMS system by deploying approximately six additional signs, appropriate locations to be determined<br />

•<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic condition<br />

•<br />

reports to drivers.<br />

Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Negotiate agreements with RT and cooperate on providing compatible transit enhancements. • Elk Grove ITS Master <strong>Plan</strong> 11/02 City of Elk Grove<br />

Prepare a Telecommunications Concept of Operations and Master Design • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Provide communications with the Roseville Police and Fire Departments, Roseville Emergency Operations<br />

City of Roseville Intelligent Transportation<br />

•<br />

Center, Roseville Dispatch and Roseville Transit.<br />

Systems Master <strong>Plan</strong> 02/05 City of Roseville<br />

City of Roseville Intelligent Transportation<br />

•<br />

Upgrade and expand the City’s emergency vehicle preemption system.<br />

Systems Master <strong>Plan</strong> 02/05 City of Roseville<br />

City of Roseville Intelligent Transportation<br />

•<br />

Integrate ramp metering operations with traffic signal operations<br />

Systems Master <strong>Plan</strong> 02/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications and install fiber trunkline, CCTV cameras, EVP, and<br />

•<br />

DMS on Douglas Boulevard.<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, and EVP on<br />

•<br />

Cirby Way.<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, and EVP on<br />

•<br />

Eureka Road.<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Upgrade the City's Central Traffic Control System • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Construct an ITS Control Room • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Integrate with STARNET • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, EVP and<br />

•<br />

kiosks on Atlantic/Vernon/Riverside<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, and EVP on<br />

•<br />

Rocky Ridge Drive<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Implement video sharing with other agencies. • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Integrate the City's traffic signal operations with Caltrans ramp metering operations • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Kimley­Horn and Associates 3 5/4/2005


SACOG ITS System <strong>Deployment</strong> <strong>Plan</strong><br />

Task 1.1: Existing Conditions Report ­ APPENDIX<br />

Projects Inventory as cited in Existing Documents<br />

System Existing <strong>Plan</strong>ned Programmed Source Date Agency<br />

Provide transit information at Roseville Transit bus stops • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Integrate Roseville ITS Operations with the region's 511 system • Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install CCTV cameras, EVP and DMS on<br />

•<br />

Galleria/Stanford Ranch<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, install fiber trunkline, upgrade copper communications, install CCTV cameras, EVP<br />

•<br />

and DMS on Galleria/Stanford Ranch<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, install fiber trunkline, upgrade copper communications, install CCTV cameras, EVP<br />

•<br />

and DMS on Roseville Parkway<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install CCTV cameras, EVP and DMS on Sunrise<br />

•<br />

Avenue<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, install fiber trunkline, upgrade copper communications, install CCTV cameras, EVP<br />

•<br />

and DMS on Sierra College Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, install fiber trunkline, upgrade copper communications, install CCTV cameras, EVP<br />

•<br />

and DMS on Roseville Parkway<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install CCTV cameras, EVP and DMS on<br />

•<br />

Washington Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install CCTV cameras, EVP and DMS on Pleasant<br />

•<br />

Grove Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install CCTV cameras, EVP and DMS on<br />

•<br />

Woodcreek Oaks Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, EVP and DMS<br />

•<br />

on Baseline Road<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, EVP and DMS<br />

•<br />

on Fiddyment Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, install fiber trunkline, CCTV cameras, EVP and DMS<br />

•<br />

on Blue Oaks Boulevard<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Replace traffic controllers, upgrade copper communications, CCTV cameras, EVP and DMS on Foothills Parkway<br />

Replace traffic controllers, upgrade copper communications, CCTV cameras, EVP and DMS on Junction<br />

Boulevard<br />

•<br />

•<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Roseville ITS Master <strong>Plan</strong> 2/05 City of Roseville<br />

Extend the existing signal interconnect system along Greenback Road<br />

Complete the buildout of a fiber optic network loop.<br />

• City of Citrus Heights Traffic Control System<br />

Transportation <strong>Plan</strong>ning Guidelines 11/04 City of Citrus Heights<br />

• City of Citrus Heights Traffic Control System<br />

Transportation <strong>Plan</strong>ning Guidelines 11/04 City of Citrus Heights<br />

• City of Citrus Heights Traffic Control System<br />

Deploy CCTV cameras on Antelope Road and Auburn Boulevard.<br />

Transportation <strong>Plan</strong>ning Guidelines 11/04 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Upgrade traffic signal controllers<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Obtain an electronic link to the County's CCTV network<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Deploy fiber optics on Greenback Lane, Auburn Boulevard and Sunrise Boulevard<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Deploy CCTV Cameras along Greenback Lane, Sunrise Boulevard and Auburn Boulevard<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Deploy dynamic message signs at key locations<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Construct a Transportation Management Center<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Deploy a complete Advanced Traveler Information System (ATIS) consisting of HARs and trip planning systems<br />

Citrus Heights Traffic Control System<br />

•<br />

over the Internet<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Provide transit enhancements on Sunrise Boulevard<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Citrus Heights Traffic Control System<br />

•<br />

Upgrade the City's Central Traffic Control System<br />

Transportation <strong>Plan</strong>ning Guidelines 4/99 City of Citrus Heights<br />

Two Regional TMCs for Caltrans District 6 and Caltrans District 10 • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Curve Warning Systems ­curve warning system will consist of a static warning sign located well in advance of the<br />

curve, which reads “CURVE AHEAD”. A speed detection system will be installed to determine vehicle speed. If a<br />

vehicle’s speed indicates that safe curve negotiation is not likely, an LED display, attached to the static sign and<br />

•<br />

reading “REDUCE SPEED”would be illuminated.<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Alternate Route <strong>Plan</strong>s Database/Website ­ access to the plans via the Internet. • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Regional Traveler Information System • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Kimley­Horn and Associates 4 5/4/2005


SACOG ITS System <strong>Deployment</strong> <strong>Plan</strong><br />

Task 1.1: Existing Conditions Report ­ APPENDIX<br />

Projects Inventory as cited in Existing Documents<br />

System Existing <strong>Plan</strong>ned Programmed Source Date Agency<br />

CMS at Key Decision Points ­expand the number of changeable message signs (CMS) located at key routing<br />

decision points within the San Joaquin Valley, such as in advance of interstate­to­interstate interchanges and<br />

interchanges between interstate routes and major state routes.<br />

•<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Weather/ATMS Integration and Automation • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Data Exchange Network (DEN)/Communications Interties • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Dynamic Speed Signing System for weather conditions • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Remote ATIS workstations • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Integration of Communication Channels • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Commercial Vehicle Parking Management System ­ system to monitor commercial vehicle parking availability at a<br />

number of locations in real­time, and utilize a variety of dissemination tools to make the information available to<br />

commercial vehicle operators.<br />

•<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Smart Call Box Systems • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

CVO Traveller Information System • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Integrated Smart Corridors in selected urban areas • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

511 System • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Truck Stop Information Demo • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Completion of Valleywide GIS Mapping • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Regional ITS Design Guidelines • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Portable CMS Pool ­ pool of portable changeable message signs that would be made available to various public<br />

agencies for use in construction work zones, special event traffic control and other appropriate incident<br />

management applications.<br />

•<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Emergency Vehicle Pre­emption (EVP) <strong>Deployment</strong> • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Advanced Railroad Highway Interface <strong>Deployment</strong> • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically sited,<br />

and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents and weather<br />

related road closures.<br />

•<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Regional Transit Information Systems • San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Computer Aided Dispatch Integration: integrate the computer­aided dispatch systems of various emergency<br />

response and transportation agencies that jointly participate in traffic incident management, including local police,<br />

state patrol, HAZMAT response, Caltrans, and fire departments.<br />

•<br />

San Joaquin Valley ITS SDP 10/01 San Joaquin Council of Governments (SJCOG), Caltrans<br />

Kimley­Horn and Associates 5 5/4/2005


Appendix E


Task 2.1<br />

Gap Assessment<br />

Prepared for:<br />

Prepared by:<br />

March 2005<br />

097860000<br />

Copyright © 2005, Kimley­Horn and Associates, Inc.


1. INTRODUCTION<br />

This report is the output for Task 2.1: Gap Assessment of the Sacramento Council of<br />

Governments (SACOG) Intelligent Transportation Systems (ITS) <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

(<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>). It includes a review summary of the ITS Vision objectives and<br />

existing, planned, and programmed ITS deployments mapped to the market packages of the<br />

National ITS Architecture. The ITS Vision was a document prepared by the Sacramento ITS<br />

Partnership in 2002 and updated during the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> process. The existing,<br />

planned, and programmed ITS deployments were gathered from the SACOG Metropolitan<br />

Transportation <strong>Plan</strong> (MTP) and other land use and transportation plans in the region that included<br />

projects related to ITS. The Gap Assessment will reveal three major elements:<br />

o ITS Vision objectives that are being satisfied by a current project;<br />

o National ITS Architecture Market Packages that are relevant to the Sacramento Regional<br />

needs and vision; and<br />

o ITS Vision objectives and required Market Packages (defined by the stakeholders) that<br />

need to have projects identified in order to be satisfied.<br />

If an ITS Vision objective or a required Market Package does not currently have a project<br />

identified that satisfies that element, this is defined as a “gap”. A gap means that under the<br />

current scenario of planned projects, a portion of the ITS Vision would not be achieved; or a<br />

Market Package that the stakeholders identify as a necessary component of the Sacramento<br />

Regional ITS Architecture will not be satisfied. One facet of the final <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong><br />

will be to identify and recommend projects that will fulfill the “gaps”identified in the Gap<br />

Assessment.<br />

1.1 <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Background<br />

This <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> replaces the 1996 Early <strong>Deployment</strong> <strong>Plan</strong> and updates the<br />

Sacramento ITS Regional Architecture which was completed in 2001. This <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> will incorporate work completed since the Early <strong>Deployment</strong> <strong>Plan</strong> was<br />

released. The project addresses the current USDOT Rule and Federal Transit Administration<br />

Policy for National ITS Architecture, and provides the additional required detail in the following<br />

areas: new subsystems, operational concept, system functional requirements, system interfaces,<br />

project sequencing, and agency operational agreements. The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will<br />

bring the Sacramento region into full compliance with Architecture requirements; provide a<br />

vision for ITS; outline a program of low, medium and high priority projects; identify a funding<br />

strategy; and establish a plan for managing, integrating and operating the ITS elements in the<br />

region that are to be implemented over a designated planning period.<br />

The <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will also incorporate and build upon recent efforts by various<br />

local agencies and SACOG which demonstrate the importance of land use in planning for future<br />

transportation improvements, and the interrelation between land use and circulation. This<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will represent a first effort to integrate ITS planning and ITS project<br />

deployment strategies within the broader transportation and land use planning efforts. The<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will also address ways in which advanced technologies can improve<br />

mobility and air quality in the region.


The individual elements of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> project are listed on the following<br />

page. The items in bold have been completed or are part of the current deliverable. Throughout<br />

the project, many sections will be completed as separate deliverables. When combined, the<br />

<strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> will culminate in a comprehensive, usable document to guide future<br />

ITS deployment in the region.<br />

SACOG ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> Project<br />

TASK 1: DEVELOP OUTREACH PROGRAM<br />

• TASK 1.1: EXISTING CONDITIONS SUMMARY REPORT<br />

• TASK 1.2: DEVELOP OUTREACH PLAN<br />

TASK 2: PLANNING PROCESS<br />

• TASK 2.1: GAP ASSESSMENT<br />

THIS REPORT<br />

• TASK 2.2: REFINE ITS VISION<br />

• TASK 2.3: MARKET PACKAGES<br />

• TASK 2.4: UPDATE REGIONAL ITS ARCHITECTURE<br />

TASK 3: STRATEGIC DEPLOYMENT PLAN<br />

• TASK 3.1: PROJECT SEQUENCING<br />

• TASK 3.2: AGREEMENTS<br />

• TASK 3.3: STRATEGIC DEPLOYMENT PLAN REPORT<br />

• TASK 3.4: EXECUTIVE SUMMARY<br />

TASK 4: MAINTENANCE PLAN<br />

• TASK 4.1: MAINTENANCE PLAN


2. METHODOLOGY AND ANALYSIS<br />

To fully assess the potential gaps in the regional ITS program, there are three components that need to<br />

be considered: Sacramento Region ITS Vision; National ITS Architecture Market Packages; and<br />

Existing, <strong>Plan</strong>ned, and Programmed Projects. Each of these components are mapped to each other in<br />

order to identify what areas of the ITS Vision and Market Packages are not being satisfied by the current<br />

program of ITS deployment.<br />

2.1 Sacramento Region ITS Vision<br />

The starting point for the Gap Assessment is the Sacramento Region ITS Vision which was<br />

originally approved by the stakeholders in 2002 and refined during the <strong>Strategic</strong> <strong>Deployment</strong><br />

<strong>Plan</strong> project utilizing stakeholder input received at the Kickoff Meeting on March 8, 2005. The<br />

updated SACOG ITS Vision is available as a separate document on the project website at<br />

http://www.<strong>sacog</strong>.org/websites/kimley­horn/index.cfm. The ITS Vision is based on the<br />

following ten categories of the Metropolitan Transportation <strong>Plan</strong> Vision.<br />

o Quality of Life<br />

o Access and Mobility<br />

o Air Quality<br />

o Travel Choices<br />

o Economic Vitality<br />

o Equity<br />

o Transportation and Land Use<br />

o Funding and Revenue<br />

o Health and Safety<br />

o Environmental Sustainability<br />

The Sacramento Region ITS Vision developed in 2002 added an ITS component to the<br />

Metropolitan Transportation <strong>Plan</strong> Vision. Each of the goals listed above has a set of objectives<br />

that were developed during this <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> process. These objectives were<br />

derived from the original Vision and from input received from stakeholders. The updated<br />

objectives for each Vision component are shown below. Objectives voiced by stakeholders<br />

which are not necessarily ITS related but have strong potential for ITS deployment are also<br />

include in the ITS Vision with the note “ITS Opportunity””.<br />

Quality of Life<br />

o Enhance and integrate transit services<br />

o Improve traffic flow by reducing congestion (eg. on heavily traveled arterials), by<br />

reducing and/or enforcing speeds for safety (eg. in residential neighborhoods), and by<br />

improving facilities for alternative transportation modes such as walking or bicycling<br />

o Improve traveler experience and reduce congestion by providing traveler information<br />

o Reduce vehicle emissions<br />

o Market ITS to encourage the use of multi­modal transportation system<br />

o Reduce time residents spend in congestion


o Provide current traveler information via 511<br />

o Improve traffic management<br />

o Provide real­time transit vehicle arrival information system<br />

o Provide guidance to available parking<br />

o Provide electronic payment and/or regional fare collection system for transit (possibly<br />

multi­modal)<br />

o Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

o Have a better ITS education system in the region<br />

Access and Mobility<br />

o Integrate transit services where practical and desirable<br />

o Introduce new Bus Rapid Transit (BRT) transit trunk lines to enhance the local and<br />

regional transit service<br />

o Improve access and mobility by introducing local paratransit services with door­to­door<br />

service<br />

o Optimize operations (reduce congestion, improve the traveler experience)<br />

o Reduce conflicts between motorized and non­motorized modes and vehicles<br />

o Disseminate accurate, multimodal traveler information via STARNET<br />

o Improve traffic signal timing, coordination, and management across jurisdictional<br />

boundaries<br />

o Provide more predictable travel times<br />

o Improve reliability of alternate modes<br />

o Implement transit signal priority<br />

o Improve coordination among traffic, public safety and transit agencies<br />

o Provide for enhanced multi­modal transit transfers<br />

Air Quality<br />

o Reduce vehicle emissions by reducing total VMT<br />

o Reduce vehicle emissions by reducing congestion and thus possibly reducing stop­andgo<br />

conditions<br />

o Improve travel time along corridors<br />

o Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

o Streamline goods movement processes<br />

o Improve overall congestion<br />

o Improve traffic management<br />

o Increase ridership on transit vehicles by improving reliability<br />

o Consider addition of HOV/HOT lanes across region (ITS Opportunity)<br />

Travel Choices<br />

o Integrate transit services across different modes where practical and desirable<br />

o Integrate transit services across different jurisdictions where practical and desirable<br />

o Improve convenience of transit by introducing door­to­door paratransit service<br />

o Improve transit safety by deploying surveillance cameras on board transit vehicles and<br />

at transit stops


o When optimizing signal operations, emphasize bicycle and pedestrian safety while<br />

reducing conflicts with vehicles<br />

o Improve traveler experience via traveler information provided via STARNET<br />

o Improve bicycle and pedestrian safety<br />

o Provide priority for transit vehicles using transit priority, queue jumper lanes, and signal<br />

coordination<br />

o Provide advantageous transit service over the use of automobiles<br />

o Develop an ITS education program in the region<br />

o Integrate Sacramento region ITS initiatives with adjacent regions<br />

Economic Vitality<br />

o Improve commercial vehicle operations using technologies such as weigh­in­motion<br />

sensors and real­time roadway condition information for trucks and delivery fleets<br />

o Improve accessibility by integrating operations across jurisdictional boundaries via their<br />

TOCs. Interconnected TOCs can then optimize operations through actions such as<br />

accident response, real­time signal optimization, and provision of alternate routes when<br />

needed.<br />

o Improve access into and out of economic centers<br />

o Expedite commercial vehicle deliveries<br />

o Improve accessibility to parking<br />

o Develop an ITS education program in the region<br />

o Integrate Sacramento region ITS initiatives with adjacent regions<br />

Equity<br />

o Improve transit level of service in existing and new transit corridors through greater<br />

frequency, timeliness, and easier transfers<br />

o Improve mobility for alternate modes such as pedestrian and bicycle<br />

o Develop programs that have a regional focus<br />

o Develop compatible/consistent ITS deployment initiatives across region for similar<br />

deployments (i.e., transit priority deployed in one corridor has same technology as<br />

transit priority in another)<br />

o Improve access to and reliability of alternate modes<br />

o Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio,<br />

multi­lingual) and varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Transportation and Land Use<br />

o Encourage and facilitate planning efforts which emphasize land use plans supporting<br />

new BRT corridors. In particular the planning can explore how to densify the corridors<br />

via redevelopment and infill, targeting the corridors for transit oriented development<br />

(TOD) improvements (ITS Opportunity)<br />

o Consider alternate mode mobility in every development<br />

o Improve transit service to jobs, services and housing<br />

o Mainstream ITS initiatives into the transportation and land use planning process<br />

Funding and Revenue


o For CIP projects, create a funding incentive for including ITS on the project<br />

o Position the region to qualify for federal ITS funding<br />

o Seek multi­jurisdictional opportunities for funding<br />

o Promote benefits of ITS in the region to build support for funding<br />

o Track the number or types of projects that successfully integrate ITS into a project<br />

o Seek funding from traditional funding sources (i.e., Bicycle Transportation Account,<br />

Safe Routes to School, Federal Transit Authority)<br />

o Obtain Homeland Security funding<br />

Health and Safety<br />

o Design transit oriented development (TODs) along BRT corridors to be conducive to<br />

walking and bicycling (ITS Opportunity)<br />

o When optimizing signal operations, emphasize bicycle and pedestrian safety while<br />

reducing conflicts with vehicles<br />

o Improve transit safety by deploying surveillance cameras on board transit vehicles and<br />

at transit stops<br />

o Decrease emergency response times and capabilities using cameras and emergency<br />

vehicle signal preemption<br />

o Reduce vehicle emissions by reducing total VMT<br />

o Reduce vehicle emissions by reducing congestion and thus reducing stop­and­go<br />

conditions<br />

o Encourage use of alternate modes (i.e., bicycle, pedestrian) for mobility<br />

o Provide safer transit service<br />

o Improve emergency response time and coordination by integrating emergency response<br />

and traffic management activities<br />

o Reduce vehicle crashes<br />

Environmental Sustainability<br />

o Design transit oriented development (TODs) along BRT corridors thus limiting sprawl<br />

and reducing the conversion of agricultural and open space (ITS Opportunity)<br />

o Design transit oriented development (TODs) along BRT corridors to be conducive to<br />

walking and bicycling in addition to transit, thus reducing motorized vehicle use and<br />

resultant emissions<br />

o Reduce vehicle emissions by reducing congestion and thus reducing stop­and­go<br />

conditions<br />

o Use technology to help maintain a balance of environmentally friendly growth and the<br />

use of advanced technology<br />

o Provide real­time traveler information for ride­sharing and trip planning<br />

2.2 National ITS Architecture Market Packages<br />

The second component of the Gap Assessment is the National ITS Architecture Market<br />

Packages. Market packages help to define information flows, interconnects, and subsystems of<br />

various elements of ITS deployment. They are tailored to fit real world transportation<br />

problems and needs, addressing specific service requirements of traffic manager, transit


operators, travelers, and other ITS stakeholders. They were defined in enough detail to support<br />

specific benefits with clear ties to transportation problems.<br />

Market packages are illustrative rather than prescriptive. There is not a single project or system<br />

that will address each market package. The market packages are simply tools that can help<br />

guide the development of an implementation strategy to identify incremental ITS deployment<br />

strategies in a manner that is relevant to the architecture definition.<br />

A list of current market packages is shown below:<br />

Archived Data<br />

Management<br />

ITS Data Mart (focused archive, single agency)<br />

ITS Data Warehouse (multiple agencies, single repository,<br />

consistent format)<br />

ITS Virtual Data Warehouse (multiple locations)<br />

AD1<br />

AD2<br />

AD3<br />

Public Transportation<br />

Traveler Information<br />

Transit Vehicle Tracking<br />

Transit Fixed­Route Operations<br />

Demand Response Transit Operations<br />

Transit Passenger and Fare Management<br />

Transit Security<br />

Transit Maintenance<br />

Multi­modal Coordination<br />

Transit Traveler Information<br />

Broadcast Traveler Information<br />

Interactive Traveler Information<br />

Autonomous Route Guidance<br />

Dynamic Route Guidance<br />

ISP Base Route Guidance (pre­trip, turn by turn)<br />

Integrated Transportation Mgmt/Route Guidance<br />

Yellow Pages and Reservation<br />

Dynamic Ridesharing<br />

In­Vehicle Signing<br />

APTS1<br />

APTS2<br />

APTS3<br />

APTS4<br />

APTS5<br />

APTS6<br />

APTS7<br />

APTS8<br />

ATIS1<br />

ATIS2<br />

ATIS3<br />

ATIS4<br />

ATIS5<br />

ATIS6<br />

ATIS7<br />

ATIS8<br />

ATIS9


Traffic Management<br />

Vehicle Safety<br />

Network Surveillance<br />

Probe Surveillance<br />

Surface Street Control<br />

Freeway Control<br />

HOV Lane Management<br />

Traffic Information Dissemination<br />

Regional Traffic Control<br />

Traffic Incident Management System<br />

Traffic Forecast and Demand Management<br />

Electronic Toll Collection<br />

Emissions Monitoring and Management<br />

Virtual TMC and Smart Probe Data<br />

Standard Railroad Grade Crossing ( 80)<br />

Railroad Operations Coordination<br />

Parking Facility Management<br />

Regional Parking Management (Freight and TMC)<br />

Reversible Lane Management<br />

Speed Monitoring<br />

Drawbridge Management<br />

Roadway Closure Management<br />

Vehicle Safety Monitoring<br />

Driver Safety Monitoring<br />

Longitudinal Safety Warning<br />

Lateral Safety Warning<br />

Intersection Safety Warning (hazardous conditions)<br />

Pre­Crash Restraint <strong>Deployment</strong><br />

Driver Visibility Improvement<br />

Advanced Vehicle Longitudinal Control<br />

Advanced Vehicle Lateral Control<br />

Intersection Collision Avoidance<br />

Automated Highway System<br />

ATMS01<br />

ATMS02<br />

ATMS03<br />

ATMS04<br />

ATMS05<br />

ATMS06<br />

ATMS07<br />

ATMS08<br />

ATMS09<br />

ATMS10<br />

ATMS11<br />

ATMS12<br />

ATMS13<br />

ATMS14<br />

ATMS15<br />

ATMS16<br />

ATMS17<br />

ATMS18<br />

ATMS19<br />

ATMS20<br />

ATMS21<br />

AVSS01<br />

AVSS02<br />

AVSS03<br />

AVSS04<br />

AVSS05<br />

AVSS06<br />

AVSS07<br />

AVSS08<br />

AVSS09<br />

AVSS10<br />

AVSS11


Commercial Vehicle Operations<br />

Emergency Management<br />

Maintenance and<br />

Construction Management<br />

Fleet Administration<br />

Freight Administration (cargo itself)<br />

Electronic Clearance<br />

CV Administrative Processes<br />

International Border Electronic Clearance<br />

Weigh­In­Motion<br />

Roadside CVO Safety<br />

On­Board CVO and Freight Safety and Security<br />

CVO Fleet Maintenance<br />

HAZMAT Management<br />

Roadside HAZMAT Security Detection and Mitigation<br />

CV Driver Security Detection and Mitigation<br />

Freight Assignment Tracking<br />

Emergency Call­Taking and Dispatch<br />

Emergency Routing<br />

Mayday Support (user request, EMS = info)<br />

Roadway Service Patrols<br />

Transportation Infrastructure Protection<br />

Wide­Area Alert<br />

Early Warning System<br />

Disaster Response and Recovery<br />

Evacuation and Reentry Management<br />

Disaster Traveler Information<br />

Maintenance and Cons Vehicle and Equipment Tracking<br />

Maintenance and Cons Vehicle Maintenance<br />

Road Weather Data Collection<br />

Weather Information Processing and Distribution<br />

Roadway Automated Treatment<br />

Winter Maintenance<br />

Roadway Maintenance and Construction<br />

Work Zone Management<br />

Work Zone Safety Monitoring<br />

Maintenance and Cons Activity Coordination<br />

CVO01<br />

CVO02<br />

CVO03<br />

CVO04<br />

CVO05<br />

CVO06<br />

CVO07<br />

CVO08<br />

CVO09<br />

CVO10<br />

CVO11<br />

CVO12<br />

CVO13<br />

EM01<br />

EM02<br />

EM03<br />

EM04<br />

EM05<br />

EM06<br />

EM07<br />

EM08<br />

EM09<br />

EM10<br />

MC01<br />

MC02<br />

MC03<br />

MC04<br />

MC05<br />

MC06<br />

MC07<br />

MC08<br />

MC09<br />

MC10<br />

2.3 Existing, <strong>Plan</strong>ned, and Programmed Projects<br />

The final component of the Gap Assessment is the Existing, <strong>Plan</strong>ned, and Programmed<br />

projects. These projects were collected from the SACOG 2025 MTP, STARNET Needs<br />

Assessment, Elk Grove ­ Rancho Cordova ­ El Dorado Connector Concept <strong>Plan</strong>, the original


Sacramento Regional ITS Architecture, Tahoe Gateway ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>,<br />

Sacramento Regional Transit District, Elk Grove ITS Master <strong>Plan</strong>, and the San Joaquin Valley<br />

ITS <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong>. All of these documents included ITS projects considered for<br />

the Gap Assessment.<br />

3. GAPASSESSMENT OBSERVATIONS<br />

As the ITS Vision and Existing, <strong>Plan</strong>ned, and Programmed Projects were mapped to the<br />

National ITS Architecture Market Packages, there were several observations:<br />

o All of the Market Packages were satisfied by at least one ITS objective.<br />

o Several objectives of the ITS Vision are not part of a specific National ITS Architecture<br />

Market Package. Since the stakeholders identified these objectives in the ITS Vision,<br />

they are included as part of the Gap Assessment, but will not have a market package<br />

associated with them.<br />

o Several Market Packages do not have a Vision objective that can be mapped to it. The<br />

stakeholders need to determine if these are relevant to the Sacramento Region. These<br />

include:<br />

• ATMS12 –Virtual TMC and Smart Probe Data<br />

• ATMS18 –Reversible Lane Management<br />

• AVSS06 –Pre­Crash Restraint <strong>Deployment</strong><br />

• AVSS07 –Driver Visibility Improvement<br />

• AVSS11 –Automated Highway System<br />

• CVO05 –International Border electronic Clearance<br />

• MC01 –Maintenance and Construction Vehicle and Equipment Tracking<br />

• MC03 –Road Weather Data Collection<br />

• MC05 –Roadway Automated Treatment<br />

• MC06 –Winter Maintenance<br />

• MC07 –Roadway Maintenance and Construction<br />

• MC10 –Maintenance and Construction Activity Coordination<br />

3.1 System Gaps in Market Packages<br />

Of the market packages that were satisfied by one of the Vision objectives, not all of the market<br />

packages had a project associated with them. This is a “gap”. The market packages identified<br />

below represent the “gaps”in the current deployment plan of projects.<br />

• APTS05 –Transit Security<br />

• APTS06 –Transit Maintenance<br />

• ATMS02 –Probe Surveillance<br />

• ATMS10 –Electronic Toll Collection<br />

• ATMS11 –Emissions Monitoring and Management<br />

• ATMS13 –Standard Railroad Grade Crossing (


• ATMS14 –Advanced Railroad Grade Crossing (>80 mph)<br />

• ATMS15 –Railroad Operations Coordination<br />

• ATMS20 –Drawbridge Management<br />

• ATMS21 –Roadway Closure Management<br />

• AVSS02 –Driver Safety Monitoring<br />

• AVSS03 –Longitudinal Safety Warning<br />

• AVSS08 –Advanced Vehicle Longitudinal Control<br />

• AVSS10 –Intersection Collision Avoidance<br />

• CVO02 –Freight Administration (cargo)<br />

• CVO03 –Electronic Clearance<br />

• CVO04 –CV Administrative Processes<br />

• CVO06 –Weigh­In­Motion<br />

• CVO07 –Roadside CVO Safety<br />

• CVO08 –On­Board CVO and Freight Safety and Security<br />

• CVO09 –CVO Fleet Maintenance<br />

• CVO10 –HAZMAT Management<br />

• CVO11 –Roadside HAZMAT Security Detection and Mitigation<br />

• CVO12 –CV Driver Security Detection and Mitigation<br />

• CVO13 –Freight Assignment Tracking<br />

• EM05 –Transportation Infrastructure Protection<br />

• EM09 –Evacuation and Reentry Management<br />

• MC08 –Work Zone Management<br />

• MC09 –Work Zone Safety Monitoring<br />

For these gaps between the market packages and the projects, an objective of the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong> is to define projects that will satisfy all of the market packages. This will be<br />

done at a later stage of the <strong>Strategic</strong> <strong>Deployment</strong> <strong>Plan</strong> development.<br />

3.2 System Gaps in Market Packages<br />

In the ITS Vision, there were several objectives that were defined that do not relate to any<br />

market package. The following objectives do not have a project already identified that will<br />

fulfill that Vision objective. These represent “gaps”in the current deployment plan of projects<br />

that do not satisfy the objective.<br />

• Improve access to and reliability of alternate modes<br />

• Improve bicycle and pedestrian safety<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711,<br />

audio, multi­lingual) and varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

• Develop an ITS education program in the region<br />

• Mainstream ITS initiatives into the transportation and land use planning process<br />

• For CIP projects, create a funding incentive for including ITS on the project<br />

• Position the region to qualify for federal ITS funding<br />

• Seek multi­jurisdictional opportunities for funding<br />

• Promote benefits of ITS in the region to build support for funding


• Track the number or types of projects that successfully integrate ITS into a<br />

project<br />

• Seek funding from traditional funding sources (i.e., Bicycle Transportation<br />

Account, Safe Routes to School, Federal Transit Authority)<br />

• Obtain Homeland Security funding<br />

• Use technology to help maintain a balance of environmentally friendly growth<br />

and the use of advanced technology<br />

Projects that could fulfill the ITS Vision objectives will be developed at a later stage of the <strong>Strategic</strong><br />

<strong>Deployment</strong> <strong>Plan</strong>.<br />

3.3 Summary<br />

The next step in the process is to prioritize the market packages into low, medium, and high<br />

priorities. Then, the market packages will need to be customized so they are more applicable to<br />

the Sacramento Region. This effort will lead to a prioritization of the projects that satisfy the<br />

market packages as well as fulfill the ITS Vision objectives.


Summary of Prioritized Market Packages for the Sacramento Area<br />

High Priority Medium Priority Low Priority<br />

• Transit Vehicle Tracking<br />

(APTS1)<br />

• Transit Fixed­Route<br />

Operations (APTS2)<br />

• Transit Passenger and Fare<br />

Management (APTS4)<br />

• Transit Security (APTS5)<br />

• Multi­Modal Coordination<br />

(APTS7)<br />

• Transit Traveler Information<br />

(APTS8)<br />

• Broadcast Traveler<br />

Information (ATIS1)<br />

• Network Surveillance<br />

(ATMS01)<br />

• Surface Street Control<br />

(ATMS03)<br />

• Freeway Control (ATMS04)<br />

• Traffic Information<br />

Dissemination (ATMS06)<br />

• Regional Traffic Control<br />

(ATMS07)<br />

• Traffic Incident Management<br />

System (ATMS08)<br />

• Emergency Call­Taking and<br />

Dispatch (EM01)<br />

• Disaster Response and<br />

Recovery (EM08)<br />

• Disaster Traveler Information<br />

(EM10)<br />

• Work Zone Management<br />

(MC08)<br />

• Maintenance and<br />

Construction Activity<br />

Coordination (MC10)<br />

• ITS Data Mart (AD1)<br />

• ITS Data Warehouse (AD2)<br />

• ITS Virtual Data Warehouse<br />

(AD3)<br />

• Demand Response Transit<br />

Operations (APTS3)<br />

• Transit Maintenance (APTS6)<br />

• Interactive Traveler<br />

Information (ATIS2)<br />

• Dynamic Route Guidance<br />

(ATIS4)<br />

• Integrated Transportation<br />

Management/Route<br />

Guidance (ATIS6)<br />

• HOV Lane Management<br />

(ATMS05)<br />

• Traffic Forecast and Demand<br />

Management (ATMS09)<br />

• Emissions Monitoring and<br />

Management (ATMS11)<br />

• Standard Railroad Grade<br />

Crossing (ATMS13)<br />

• Speed Monitoring (ATMS19)<br />

• HAZMAT Management<br />

(CVO10)<br />

• Emergency Routing (EM02)<br />

• Roadway Service Patrols<br />

(EM04)<br />

• Transportation Infrastructure<br />

Protection (EM05)<br />

• Wide­Area Alert (EM06)<br />

• Early Warning System EM07)<br />

• Evacuation and Reentry<br />

Management (EM09)<br />

• Road Weather Data<br />

Collection (MC03)<br />

• Weather Information<br />

Processing and Distribution<br />

(MC04)<br />

• Roadway Maintenance and<br />

Construction (MC07)<br />

• Work Zone Safety Monitoring<br />

(MC09)<br />

• Autonomous Route Guidance<br />

(ATIS3)<br />

• ISP Based Route Guidance<br />

(ATIS5)<br />

• Yellow Pages and<br />

Reservation (ATIS7)<br />

• Dynamic Ridesharing<br />

(ATIS8)<br />

• In­Vehicle Signing (ATIS9)<br />

• Prove Surveillance (ATMS02)<br />

• Electronic Toll Collection<br />

(AMTS10)<br />

• Virtual TMC and Smart Prove<br />

Data (ATMS12)<br />

• Advanced Railroad Grade<br />

Crossing (ATMS14)<br />

• Railroad Operations<br />

Coordination (ATIS15)<br />

• Parking Facility Management<br />

(ATIS16)<br />

• Regional Parking<br />

Management (ATIS17)<br />

• Reversible Lane<br />

Management (ATIS18)<br />

• Roadway Closure<br />

Management (ATIS21)<br />

• Driver Safety Monitoring<br />

(AVSS2)<br />

• Longitudinal Safety Warning<br />

(AVSS3)<br />

• Lateral Safety Warning<br />

(AVSS4)<br />

• Intersection Safety Warning<br />

(AVSS5)<br />

• Pre­Crash Restraint<br />

<strong>Deployment</strong> (AVSS6)<br />

• Driver Visibility Improvement<br />

(AVSS7)<br />

• Intersection Collision<br />

Avoidance (AVSS10)<br />

• Fleet Administration (CVO1)<br />

• Electronic Clearance (CVO2)<br />

• Weigh­In­Motion (CVO3)<br />

• Roadside CVO Safety<br />

(CVO7)<br />

• On­Board CVO and Fright<br />

Safety and Security (CVO8)


• CVO Fleet Maintenance<br />

(CVO9)<br />

• Roadside HAZMAT Security<br />

Detection and Mitigation<br />

(CVO11)<br />

• CV Driver Security Detection<br />

and Mitigation (CVO12)<br />

• Freight Assignment Tracking<br />

(CVO13)<br />

• Mayday Support (EM3)<br />

• Maintenance and<br />

Construction Vehicle and<br />

Equipment Tracking (MC1)<br />

• Maintenance and<br />

Construction Vehicle<br />

Maintenance (MC2)<br />

• Roadway Automated<br />

Treatment (MC5)<br />

• Winter Maintenance (MC6)


High Priority Market Packages for the Sacramento Area<br />

Transit Vehicle Tracking (APTS01)<br />

High Priority<br />

This market package monitors current transit vehicle location using an Automated Vehicle Location System.<br />

The location data may be used to determine real­time schedule adherence and update the transit system’s<br />

schedule in real­time.<br />

Existing Infrastructure<br />

• LRT<br />

Responsible Agency<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

<strong>Plan</strong>ned Projects<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis<br />

Community Transit.<br />

• Sacramento Regional Transit District ­ Light Rail and Bus TMC<br />

• Public Transit ­ Implement/Expand AVI/AVL/CAD technologies<br />

• Provide transit information at Roseville transit stops<br />

Objectives Being Met<br />

• Enhance and integrate transit services<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Integrate transit services where practical and desirable<br />

• Provide more predictable travel times<br />

• Improve reliability of alternate modes<br />

• Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Provide advantageous transit service over the use of automobiles<br />

• Improve access to and reliability of alternate modes<br />

• Provide safer transit service<br />

Performance Measures<br />

• On­Time Performance. Percentage of runs with on­time performance.<br />

• Response times to bus operator calls for assistance. Measured in minutes from call to arrival of<br />

assistance.


Transit Fixed­Route Operations (APTS02)<br />

High Priority<br />

This market package performs vehicle routing and scheduling, as well as automatic driver assignment and<br />

system monitoring for fixed­route transit services. This service determines current schedule performance<br />

using AVL data and provides information displays for the Transit Management Subsystem. Static and real<br />

time transit data is exchanged with Information Service Providers where it is integrated with that from other<br />

transportation modes (e.g. rail, ferry, air) to provide the public with integrated and personalized dynamic<br />

schedules.<br />

Existing Infrastructure<br />

• LRT<br />

• BRT<br />

Responsible Agency<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

<strong>Plan</strong>ned Projects<br />

• Expansion of Capitol Corridor Train Service<br />

• Commuter rail service between Davis/Dixon and Auburn using the UP/Amtrak facilities<br />

• LRT extended to Natomas Town Center and Sacramento Airport, from Meadowview to Cosumnes River<br />

College and Elk Grove, from Watt to Antelope, and from Downtown Sacramento to West Sacramento.<br />

• Watt Corridor ­ Phase 2 and 3 ­ transit priority, monitoring equipment and traveler and communications.<br />

• Bus Rapid Transit on the Sunrise Boulevard corridor.<br />

• Bus Rapid Transit on Watt Avenue corridor.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis<br />

Community Transit.<br />

• Sacramento Regional Transit District ­ Light Rail and Bus TMC<br />

• Amtrak Folsom Light Rail Extension<br />

• South Line Phase II (South Sacramento Corridor)<br />

• Downtown/Natomas/Airport (DNA) ­ new transit options between downtown Sacramento and South and<br />

North Natomas and the Sacramento International Airport<br />

• California High Speed Rail<br />

• Elk Grove ­ Rancho Cordova ­ El Dorado Connector<br />

Objectives Being Met<br />

• Enhance and integrate transit services<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Integrate transit services where practical and desirable<br />

• Provide more predictable travel times<br />

• Improve reliability of alternate modes<br />

• Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Provide advantageous transit service over the use of automobiles<br />

• Improve access to and reliability of alternate modes<br />

• Provide safer transit service<br />

• Improve traffic flow by improving facilities for alternative transportation modes such as transit<br />

• Introduce new Bus Rapid Transit (BRT) transit trunk lines to enhance the local and regional transit<br />

service<br />

• Provide priority for transit vehicles using transit priority, queue jumper lanes, and signal coordination


• Improve transit level of service in existing and new transit corridors through greater frequency,<br />

timeliness, and easier transfers<br />

• Improve transit service to jobs, services and housing<br />

Performance Measures<br />

• On­Time Performance. Percentage of runs with on­time performance.<br />

• Response times to bus operator calls for assistance. Measured in minutes from call to arrival of<br />

assistance.


Transit Passenger and Fare Management (APTS04)<br />

High Priority<br />

This market package manages passenger loading and fare payments on­board transit vehicles using electronic<br />

means. It allows transit users to use a traveler card or other electronic payment device. Sensors mounted on<br />

the vehicle permit the operator and central operations to determine vehicle loads, and readers located either in<br />

the infrastructure or on­board the transit vehicle allows electronic fare payment. Data is processed, stored, and<br />

displayed on the transit vehicle and communicated as needed to the Transit Management Subsystem.<br />

Existing Infrastructure<br />

• LRT<br />

Responsible Agency<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

<strong>Plan</strong>ned Projects<br />

• Expansion of bus and van service regionwide, including a large increase in service for elderly and disabled<br />

persons.<br />

Objectives Being Met<br />

• Enhance and integrate transit services<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide electronic payment and/or regional fare collection system for transit (possibly multi­modal)<br />

• Integrate transit services where practical and desirable<br />

• Improve access and mobility by introducing local paratransit services with door­to­door service<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Integrate transit services across different modes where practical and desirable<br />

• Improve convenience of transit by introducing door­to­door paratransit service<br />

• Provide advantageous transit service over the use of automobiles<br />

• Provide safer transit service<br />

Performance Measures<br />

• Data collection costs. Measured as costs per year for fare data collection. Reduction in the cost of<br />

collecting fare data is expected.<br />

• Data collection accuracy. Measured as uncertainty of data collection statistics. Improvement in the<br />

accuracy of data collection is expected.<br />

• Reduction in fare evasion. Estimated through data collection information.


Transit Security (APTS05)<br />

High Priority<br />

This market package provides for the physical security of transit passengers. An on­board security system is<br />

deployed to perform surveillance and warn of potentially hazardous situations. Public areas (e.g. stops, park<br />

and ride lots, stations) are also monitored. Information is communicated to the Transit Management<br />

Subsystem using wireless or wireline infrastructure. Security related information is also transmitted to the<br />

Emergency Management Subsystem when an emergency is identified that requires an external response.<br />

Incident information is communicated to the Information Service Provider.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• LRT<br />

• BRT<br />

• Paratransit<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Improve transit safety by deploying surveillance cameras on board transit vehicles and at transit stops<br />

• Provide advantageous transit service over the use of automobiles<br />

• Improve transit safety by deploying surveillance cameras on board transit vehicles and at transit stops<br />

• Provide safer transit service<br />

Performance Measures<br />

• Response times to bus operator calls for assistance. Measured in minutes from call to arrival of<br />

assistance.<br />

• Response times to traveler calls for assistance. Measured in minutes from call to arrival of assistance.


Multi­Modal Coordination (APTS07)<br />

High Priority<br />

This market package establishes two way communications between multiple transit and traffic agencies to<br />

improve service coordination. Multimodal coordination between transit agencies can increase traveler<br />

convenience at transit transfer points and clusters (a collection of stops, stations, or terminals where transfers<br />

can be made conveniently) and also improve operating efficiency. Transit transfer information is shared between<br />

Multimodal Transportation Service Providers, Transit Agencies, and ISPs. Coordination between traffic and<br />

transit management is intended to improve on­time performance of the transit system to the extent that this can<br />

be accommodated without degrading overall performance of the traffic network. More limited local coordination<br />

between the transit vehicle and the individual intersection for signal priority is also supported by this package.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• LRT<br />

• BRT<br />

<strong>Plan</strong>ned Projects<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

• A Rancho Cordova to South Placer Multi­modal Connector.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

• Sacramento International Airport Transportation Management Center<br />

• Sacramento Regional Transit District ­ Light Rail and Bus TMC<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Downtown/Natomas/Airport (DNA) ­ new transit options between downtown Sacramento and South and<br />

North Natomas and the Sacramento International Airport<br />

• Advanced Railroad Highway Interface <strong>Deployment</strong><br />

Objectives Being Met<br />

• Enhance and integrate transit services<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Integrate transit services across different modes where practical and desirable<br />

• Improve convenience of transit by introducing door­to­door paratransit service<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Disseminate accurate, multimodal traveler information via STARNET<br />

• Improve traffic signal timing, coordination, and management across jurisdictional boundaries<br />

• Provide more predictable travel times<br />

• Implement transit signal priority<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Provide for enhanced multi­modal transit transfers<br />

• Improve travel time along corridors<br />

• Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Provide advantageous transit service over the use of automobiles


• Integrate Sacramento region initiatives with adjacent regions<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Expedite commercial vehicle deliveries<br />

• Improve transit level of service in existing and new transit corridors through greater frequency, timeliness,<br />

and easier transfers<br />

• Develop compatible/consistent ITS deployment initiatives across region for similar deployments (i.e., transit<br />

priority deployed in one corridor has same technology as transit priority in another)<br />

• Improve access to and reliability of alternate modes<br />

• Improve transit service to jobs, services and housing<br />

• Provide electronic payment and/or regional fare collection system for transit (possibly multi­modal)<br />

Performance Measures<br />

• On­Time Performance. Percentage of runs with on­time performance for those routes that have transit<br />

signal priority.


Transit Traveler Information (APTS08)<br />

High Priority<br />

This market package provides transit users at transit stops, transit centers and on­board transit vehicles with<br />

ready access to transit information. The information services include transit stop annunciation, imminent arrival<br />

signs with predicted arrival and departure times, and real­time transit schedule displays that are of general<br />

interest to transit users. Systems that provide custom transit trip itineraries and other tailored transit information<br />

services are also represented by this market package.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Transit website<br />

• Automatic visual signs<br />

<strong>Plan</strong>ned Projects<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• Sacramento Regional Transit District: purchase computerized train tracking system that will provide<br />

automatic train locations and a public address system to advise customers of train approaches and service<br />

delays.<br />

• Sacramento Regional Transit District: retrofit existing communication kits with upgraded audio system and<br />

automatic interior exterior visual signs for stop announcements and train destinations.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic<br />

condition reports to drivers.<br />

• Regional Traveler Information System<br />

• Deploy a complete Advanced Traveler Information System (ATIS) consisting of HARs and trip planning<br />

systems over the Internet<br />

Objectives Being Met<br />

• Enhance and integrate transit services<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Integrate transit services where practical and desirable<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Disseminate accurate, multimodal traveler information via STARNET<br />

• Provide more predictable travel times<br />

• Improve travel time along corridors<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Provide advantageous transit service over the use of automobiles<br />

• Improve access into and out of economic centers<br />

• Improve transit service to jobs, services and housing<br />

• Provide real­time traveler information for ride­sharing and trip planning<br />

Performance Measures<br />

• Use of transit information by travelers. Measured as number of page views on transit website. Also<br />

measured as number of page views on transit portion of 511 system.


Network Surveillance (ATMS01)<br />

High Priority<br />

This market package includes traffic detectors, other surveillance equipment, the supporting field equipment,<br />

and wireline communications to transmit the collected data back to the Traffic Management Subsystem. The<br />

derived data can be used locally or remotely. The data generated by this market package enables traffic<br />

managers to monitor traffic and road conditions, identify and verify incidents, detect equipment faults, and collect<br />

census data for traffic strategy development and long range planning. The collected data can also be analyzed<br />

and made available to users and the Information Service Provider Subsystem.<br />

Existing Infrastructure<br />

Agency<br />

• CCTV Cameras<br />

• Traffic Signal Controllers<br />

• Fiber optics, copper and wireless interconnect<br />

• Traffic Detectors<br />

• Ramp Meters<br />

<strong>Plan</strong>ned Projects<br />

• TMCs in the cities in Sacramento<br />

• County of Sacramento TMC<br />

• Caltrans TMC<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.).<br />

• Construct Traffic Operation System (Jct. 50 to I­5)<br />

• Smart Corridor on Arden Way from Del Paso to Watt Ave.<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

• U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp<br />

metering, CCTV)<br />

• Yolo County portion of I­5 traffic operations system and ramp metering.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Upgrade Caltrans District 3 Regional TMC to manage US­50, I­80 and other ITS deployments (includes<br />

coordination with Nevada and Tahoe Basin to ensure consistency)<br />

• US 50 Surveillance (including 4 CCTV or web cameras and 6 traffic monitoring stations)<br />

• Initiate Traffic Management Center (TMC) in new Corporation Yard to manage signals and other devices<br />

(i.e. CCTV, DMS, etc.)<br />

• Deploy CCTV Cameras at key intersections<br />

• Traffic Monitoring Phase I ­ Deploy traffic monitoring devices (e.g. flow detectors, CCTV cameras) along<br />

segments of US 50 in South Shore area, and along Highways 28, 89 and 267 in the North Shore<br />

Objectives Being Met<br />

• Reduce time residents spend in congestion<br />

• Provide current traveler information via 511<br />

• Improve traffic management<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Provide more predictable travel times<br />

• Improve transit safety by deploying surveillance cameras on board transit vehicles and at transit stops


• Improve access into and out of economic centers<br />

• Develop programs that have a regional focus<br />

• Decrease emergency response times and capabilities using cameras and emergency vehicle signal<br />

preemption<br />

Performance Measures<br />

• Sensor coverage. Measured in miles of highway or arterials covered by surveillance.<br />

• Sensor functionality. Measured as availability of sensor information from highways or arterials (hours<br />

operational vs. total number of hours in measurement period).


Surface Street Control (ATMS03)<br />

High Priority<br />

This market package provides the central control and monitoring equipment, communication links, and the signal<br />

control equipment that support local surface street control and/or arterial traffic management. A range of traffic<br />

signal control systems are represented by this market package ranging from static pre­timed control systems to<br />

fully traffic responsive systems that dynamically adjust control plans and strategies based on current traffic<br />

conditions and priority requests. This market package is consistent with typical urban traffic signal control<br />

systems.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

• Traffic Signal Controllers<br />

• Ramp meters<br />

• Fiber optics, copper and wireless interconnect<br />

• Emergency Vehicle Traffic Signal Preemption<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

• Install signals on U.S. 50 ramps at Ponderosa Road, South Shingle Springs, and North Shingle Road<br />

• Signal installation at U.S. 50 eastbound ramps<br />

• Install Smart Traffic Calming in south Midtown area.<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Smart Corridor on Arden Way from Del Paso to Watt Ave.<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Connect 100 traffic signals, including ITS technology, that are located outside of the Central City to the City’s<br />

existing Traffic Operations Center.<br />

• Widen Fair Oaks Blvd from Marconi Ave. to Engle Rd. from 4 to 6 lanes including signal modifications at<br />

Marconi, Stanley, Grant, and Engle Rd.<br />

• Bus Rapid Transit In Sacramento: Stockton Boulevard, construct bus rapid transit improvements from<br />

Cosumnes College to downtown Sacramento.<br />

• Bus Rapid Transit in Sacramento County, implement bus rapid transit on the Sunrise Boulevard corridor.<br />

• Bus Rapid Transit in Sacramento County, implement bus rapid transit on Watt Avenue corridor.<br />

• U.S. 50 Jefferson Blvd. interchange— expand the ramps and signals from 1 to 2 lanes, add ramp metering<br />

and turn lanes, and related street closures.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Placerville Signal System Technology Advances<br />

• Placerville Signal Replacement on Highway 50<br />

• Elk Grove signals ­ Connection between Laguna/Bond Master location and Corporation Yard (Corp Yard<br />

wiring)<br />

• Elk Grove signals ­ Upgrade City’s existing onstreet system. Replace controllers/cabinets as needed and<br />

add system detectors on all segments<br />

• Initiate Traffic Management Center (TMC) in new Corporation Yard to manage signals and other devices<br />

(i.e. CCTV, DMS, etc.)<br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents


and weather related road closures.<br />

• Various upgrades to Roseville’s ITS Program including the communications network, traffic signal<br />

controllers, CCTV cameras, DMS, and EVP.<br />

• Various upgrades to Citrus Heights ITS Program including the communications network, traffic signal<br />

controllers, CCTV cameras, DMS, and EVP.<br />

•<br />

Objectives Being Met<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or enforcing<br />

speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative transportation<br />

modes such as walking or bicycling<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve traffic management<br />

• Introduce new Bus Rapid Transit (BRT) transit trunk lines to enhance the local and regional transit service<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Improve traffic signal timing, coordination, and management across jurisdictional boundaries<br />

• Provide more predictable travel times<br />

• Implement transit signal priority<br />

• Reduce vehicle emissions by reducing congestion and thus possibly reducing stop­and­go conditions<br />

• Improve travel time along corridors<br />

• Improve overall congestion<br />

• When optimizing signal operations, emphasize bicycle and pedestrian safety while reducing conflicts with<br />

vehicles<br />

• Provide priority for transit vehicles using transit priority, queue jumper lanes, and signal coordination<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Improve access into and out of economic centers<br />

• Improve transit level of service in existing and new transit corridors through greater frequency, timeliness,<br />

and easier transfers<br />

• Improve mobility for alternate modes such as pedestrian and bicycle<br />

• Decrease emergency response times and capabilities using cameras and emergency vehicle signal<br />

preemption<br />

Performance Measures<br />

• Traffic flow. Measured at intersections with signal systems.<br />

• Travel time along a corridor (that contains coordinated signals)<br />

• Traffic signal system failure rates


Freeway Control (ATMS04)<br />

High Priority<br />

This market package provides the communications and roadside equipment to support ramp control, lane<br />

controls, and interchange control for freeways. This package is consistent with typical urban traffic freeway<br />

control systems. This package incorporates the instrumentation included in the Network Surveillance Market<br />

Package to support freeway monitoring and adaptive strategies as an option. This market package also includes<br />

the capability to utilize surveillance information for detection of incidents.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Ramp meters<br />

• Queue detectors<br />

• Fiber optics, copper and wireless interconnect<br />

• Dynamic Message Signs/Trailblazers<br />

• CCTV Cameras<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

<strong>Plan</strong>ned Projects<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

• Install signals on U.S. 50 ramps at Ponderosa Road, South Shingle Springs, and North Shingle Road<br />

• Signal installation at U.S. 50 eastbound ramps<br />

• Ramp metering at all interchanges from Foresthill Road to the Sacramento County Line.<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.).<br />

• Construct Traffic Operation System (Jct. 50 to I­5)<br />

• Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

• U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp<br />

metering, CCTV)<br />

• Yolo County portion of I­5 traffic operations system and ramp metering.<br />

• U.S. 50 Install ramp meters and modify ramp design at South River Rd. interchange.<br />

• U.S. 50 Jefferson Blvd. interchange— expand the ramps and signals from 1 to 2 lanes, add ramp metering<br />

and turn lanes, and related street closures.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Eleven Ramp meters planned between Sacramento/El Dorado County line and Placerville<br />

• Six Ramp meters on SR65 between Lincoln and I­80<br />

• Traffic monitoring stations near the Sacramento/Placer County line in Roseville<br />

• Upgrade Caltrans District 3 Regional TMC to manage US­50, I­80 and other ITS deployments (includes<br />

coordination with Nevada and Tahoe Basin to ensure consistency)<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

• US 50 Surveillance (including 4 CCTV or web cameras and 6 traffic monitoring stations)<br />

• Curve Warning Systems ­curve warning system will consist of a static warning sign located well in advance<br />

of the curve, which reads “CURVE AHEAD”. A speed detection system will be installed to determine vehicle<br />

speed. If a vehicle’s speed indicates that safe curve negotiation is not likely, an LED display, attached to the<br />

static sign and reading “REDUCE SPEED”would be illuminated.<br />

• CMS at Key Decision Points ­expand the number of changeable message signs (CMS) located at key<br />

routing decision points within the San Joaquin Valley, such as in advance of interstate­to­interstate


interchanges and interchanges between interstate routes and major state routes.<br />

• Smart Call Box Systems<br />

• Portable CMS Pool ­ pool of portable changeable message signs that would be made available to various<br />

public agencies for use in construction work zones, special event traffic control and other appropriate<br />

incident management applications.<br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents<br />

and weather related road closures.<br />

• Traffic Monitoring Phase I ­ Deploy traffic monitoring devices (e.g. flow detectors, CCTV cameras) along<br />

segments of US 50 in South Shore area, and along Highways 28, 89 and 267 in the North Shore<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Provide more predictable travel times<br />

• Consider addition of HOV/HOT lanes across region<br />

• Improve access into and out of economic centers<br />

Performance Measures<br />

• Traffic flow. Measured at on ramps and on highway.


Traffic Information Dissemination (ATMS06)<br />

High Priority<br />

This market package allows traffic information and road/bridge closures due to construction, maintenance, and<br />

weather, to be disseminated to drivers and vehicles using roadway equipment such as dynamic message signs<br />

or highway advisory radio. This package also covers the equipment and interfaces that provide traffic<br />

information from a traffic management center to the media (for instance via a direct tie­in between a traffic<br />

management center and radio or television station computer systems), Transit Management, Emergency<br />

Management, and Information Service Providers.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

• Expand DMS system by deploying approximately six additional signs, appropriate locations to be<br />

determined<br />

• Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic<br />

condition reports to drivers.<br />

• Regional Traveler Information System<br />

• Data Exchange Network (DEN)/Communications Interties<br />

• CVO Traveler Information System<br />

• Integrated Smart Corridors in selected urban areas<br />

• Truck Stop Information Demo<br />

• Portable CMS Pool ­ pool of portable changeable message signs that would be made available to various<br />

public agencies for use in construction work zones, special event traffic control and other appropriate<br />

incident management applications.<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Disseminate accurate, multimodal traveler information via STARNET<br />

• Provide more predictable travel times<br />

• Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

• Improve overall congestion<br />

• Improve access into and out of economic centers<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)


• Provide real­time traveler information for ride­sharing and trip planning<br />

Performance Measures<br />

• Number (or frequency) of advisory messages per DMS.


Regional Traffic Control (ATMS07)<br />

High Priority<br />

This market package provides for the sharing of traffic information and control among traffic management<br />

centers to support a regional control strategy. This package relies on roadside instrumentation supported by the<br />

Surface Street Control and Freeway Control Market Packages and adds hardware, software, and<br />

communications capabilities to implement traffic management strategies that are coordinated between allied<br />

traffic management centers. The extent of information and control sharing is determined through working<br />

arrangements between jurisdictions.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• None identified<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

• Install signals on U.S. 50 ramps at Ponderosa Road, South Shingle Springs, and North Shingle Road<br />

• Signal installation at U.S. 50 eastbound ramps<br />

• Ramp metering at all interchanges from Foresthill Road to the Sacramento County Line.<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.).<br />

• Construct Traffic Operation System (Jct. 50 to I­5)<br />

• Smart Corridor on Arden Way from Del Paso to Watt Ave.<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

• U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp<br />

metering, CCTV)<br />

• Yolo County portion of I­5 traffic operations system and ramp metering.<br />

• U.S. 50 Install ramp meters and modify ramp design at South River Rd. interchange.<br />

• U.S. 50 Jefferson Blvd. interchange— expand the ramps and signals from 1 to 2 lanes, add ramp metering<br />

and turn lanes, and related street closures.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis Community<br />

Transit.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Regional Street Network System Design<br />

• Eleven Ramp meters planned between Sacramento/El Dorado County line and Placerville<br />

• Six Ramp meters on SR65 between Lincoln and I­80<br />

• Upgrade Caltrans District 3 Regional TMC to manage US­50, I­80 and other ITS deployments (includes<br />

coordination with Nevada and Tahoe Basin to ensure consistency)<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

• Elk Grove signals ­ Coordinate border signal responsibilities with the County of Sacramento and Caltrans<br />

where applicable.<br />

• Initiate Traffic Management Center (TMC) in new Corporation Yard to manage signals and other devices


(i.e. CCTV, DMS, etc.)<br />

• Two Regional TMCs for Caltrans District 6 and Caltrans District 10<br />

• CMS at Key Decision Points ­expand the number of changeable message signs (CMS) located at key<br />

routing decision points within the San Joaquin Valley, such as in advance of interstate­to­interstate<br />

interchanges and interchanges between interstate routes and major state routes.<br />

• Data Exchange Network (DEN)/Communications Interties<br />

• Integrated Smart Corridors in selected urban areas<br />

Objectives Being Met<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or enforcing<br />

speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative transportation<br />

modes such as walking or bicycling<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide current traveler information via 511<br />

• Improve traffic management<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Improve traffic signal timing, coordination, and management across jurisdictional boundaries<br />

• Provide more predictable travel times<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Reduce vehicle emissions by reducing congestion and thus possibly reducing stop­and­go conditions<br />

• Improve travel time along corridors<br />

• Improve overall congestion<br />

• When optimizing signal operations, emphasize bicycle and pedestrian safety while reducing conflicts with<br />

vehicles<br />

• Provide priority for transit vehicles using transit priority, queue jumper lanes, and signal coordination<br />

• Integrate Sacramento region initiatives with adjacent regions<br />

• Improve access into and out of economic centers<br />

• Improve transit level of service in existing and new transit corridors through greater frequency, timeliness,<br />

and easier transfers<br />

• Improve mobility for alternate modes such as pedestrian and bicycle<br />

• Develop programs that have a regional focus<br />

Performance Measures<br />

• Traffic flow. Measured at intersections with interconnected signals across jurisdictions.


Traffic Incident Management System (ATMS08)<br />

High Priority<br />

This market package manages both unexpected incidents and planned events so that the impact to the<br />

transportation network and traveler safety is minimized. The market package includes incident detection<br />

capabilities through roadside surveillance devices (e.g. CCTV) and through regional coordination with other<br />

traffic management, maintenance and construction management, and emergency management centers as well<br />

as weather service entities and event promoters. Information from these diverse sources is collected and<br />

correlated by this market package to detect and verify incidents and implement an appropriate response.<br />

The response may include traffic control strategy modifications or resource coordination between center<br />

subsystems. The coordination with emergency management might be through a CAD system or through other<br />

communication with emergency field personnel. The coordination can also extend to tow trucks and other allied<br />

response agencies and field service personnel.<br />

Incident response also includes presentation of information to affected travelers using the Traffic Information<br />

Dissemination, Broadcast Traveler Information, or Interactive Traveler Information market packages.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

• Traffic Signal Controllers<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

• Computer Aided Dispatch Integration: integrate the computer­aided dispatch systems of various emergency<br />

response and transportation agencies that jointly participate in traffic incident management, including local<br />

police, state patrol, HAZMAT response, Caltrans, and fire departments.<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve traffic management<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Improve traffic signal timing, coordination, and management across jurisdictional boundaries<br />

• Provide more predictable travel times<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Improve access into and out of economic centers<br />

Performance Measures<br />

• Accident rates<br />

• Number of incidents detected or verified<br />

• Incident response times<br />

• Incident clearance times


Emergency Call­Taking and Dispatch (EM01)<br />

High Priority<br />

This market package includes emergency vehicle equipment, equipment used to receive and route emergency<br />

calls, and wireless communications that enable safe and rapid deployment of appropriate resources to an<br />

emergency. Coordination between Emergency Management Subsystems supports emergency notification and<br />

coordinated response between agencies.<br />

Existing Infrastructure<br />

• Emergency Response Telecommunications Center<br />

• Police Department Mobile Data Terminals<br />

• Computer Aided Dispatch<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Police and Fire Departments in Sacramento<br />

Area<br />

• Caltrans<br />

• Computer Aided Dispatch Integration: integrate the computer­aided dispatch systems of various emergency<br />

response and transportation agencies that jointly participate in traffic incident management, including local<br />

police, state patrol, HAZMAT response, Caltrans, and fire departments.<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Decrease emergency response times and capabilities using cameras and emergency vehicle signal<br />

preemption<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Call answering delay. Measured as time callers to 9­1­1 are on hold.<br />

• Average time to respond to emergency. Measured as the average time from receipt of call to arrival of<br />

emergency services at call site.


Disaster Response and Recovery (EM08)<br />

High Priority<br />

This market package enhances the ability of the surface transportation system to respond to and recover from<br />

disasters. It addresses the most severe incidents that require an extraordinary response from outside the local<br />

community. All types of disasters are addressed including natural disasters (hurricanes, earthquakes, floods,<br />

winter storms, tsunamis, etc.) and technological and man­made disasters (hazardous materials incidents,<br />

nuclear power plant accidents, and national security emergencies such as nuclear, chemical, biological, and<br />

radiological weapons attacks).<br />

The market package supports coordination of emergency response plans, including general plans developed<br />

before a disaster as well as specific tactical plans with short time horizon that are developed as part of a disaster<br />

response. The market package provides enhanced access to the scene for response personnel and resources,<br />

provides better information about the transportation system in the vicinity of the disaster, and maintains situation<br />

awareness regarding the disaster itself. In addition, this market package tracks and coordinates the<br />

transportation resources ­ the transportation professionals, equipment, and materials ­ that constitute a portion of<br />

the disaster response.<br />

The market package identifies the key points of integration between transportation systems and the public safety,<br />

emergency management, and other allied organizations that form the overall disaster response. In this market<br />

package, the Emergency Management subsystem represents the federal, regional, state, and local Emergency<br />

Operations Centers and the Incident Commands that are established to respond to the disaster. The interface<br />

between the Emergency Management Subsystem and the other center subsystems provides situation<br />

awareness and resource coordination among transportation and other allied response agencies. In its role, traffic<br />

management implements special traffic control strategies and detours and restrictions to effectively manage<br />

traffic in and around the disaster. Maintenance and construction provides damage assessment of road network<br />

facilities and manages service restoration. Transit management provides a similar assessment of status for<br />

transit facilities and modifies transit operations to meet the special demands of the disaster. As immediate public<br />

safety concerns are addressed and disaster response transitions into recovery, this market package supports<br />

transition back to normal transportation system operation, recovering resources, managing on­going<br />

transportation facility repair, supporting data collection and revised plan coordination, and other recovery<br />

activities.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Emergency Response Telecommunications Center<br />

• Police Department Mobile Data Terminals<br />

• Computer Aided Dispatch<br />

• CCTV cameras<br />

• Dynamic Message Signs/Trailblazers<br />

<strong>Plan</strong>ned Projects<br />

• Police and Fire Departments in Sacramento<br />

Area<br />

• Caltrans<br />

• TMCs in cities in Sacramento<br />

• County of Sacramento TMC<br />

• Transit agencies<br />

• Computer Aided Dispatch Integration: integrate the computer­aided dispatch systems of various emergency<br />

response and transportation agencies that jointly participate in traffic incident management, including local<br />

police, state patrol, HAZMAT response, Caltrans, and fire departments.<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Decrease emergency response times and capabilities using cameras and emergency vehicle signal<br />

preemption<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Average time to respond to emergency. Measured as the average time from receipt of call to arrival of<br />

emergency services at call site.


Disaster Traveler Information (EM10)<br />

High Priority<br />

This market package uses ITS to provide disaster­related traveler information to the general public, including<br />

evacuation and reentry information and other information concerning the operation of the transportation system<br />

during a disaster. This market package collects information from multiple sources including traffic, transit, public<br />

safety, emergency management, shelter provider, and travel service provider organizations. The collected<br />

information is processed and the public is provided with real­time disaster and evacuation information using ITS<br />

traveler information systems.<br />

A disaster will stress the surface transportation system since it may damage transportation facilities at the same<br />

time that it places unique demands on these facilities to support public evacuation and provide access for<br />

emergency responders. Similarly, a disaster may interrupt or degrade the operation of many traveler information<br />

systems at the same time that safety­critical information must be provided to the traveling public. This market<br />

package keeps the public informed in these scenarios, using all available means to provide information about the<br />

disaster area including damage to the transportation system, detours and closures in effect, special traffic<br />

restrictions and allowances, special transit schedules, and real­time information on traffic conditions and transit<br />

system performance in and around the disaster.<br />

This market package also provides emergency information to assist the public with evacuations when necessary.<br />

Information on mandatory and voluntary evacuation zones, evacuation times, and instructions are provided.<br />

Available evacuation routes and destinations and current and anticipated travel conditions along those routes are<br />

provided so evacuees are prepared and know their destination and preferred evacuation route. Information on<br />

available transit services and traveler services (shelters, medical services, hotels, restaurants, gas stations, etc.)<br />

is also provided. In addition to general evacuation information, this market package provides specific evacuation<br />

trip planning information that is tailored for the evacuee based on origin, selected destination, and evacueespecified<br />

evacuation requirements and route parameters.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Emergency Response Telecommunications Center<br />

• Police Department Mobile Data Terminals<br />

• Computer Aided Dispatch<br />

• 511<br />

• Dynamic Message Signs<br />

<strong>Plan</strong>ned Projects<br />

• Police and Fire Departments in Sacramento<br />

Area<br />

• Caltrans<br />

• TMCs in the cities in Sacramento<br />

• County of Sacramento TMC<br />

• Transit agencies<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Regional Traveler Information System<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Provide current traveler information via 511<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Usage of disaster traveler information system. Measured as number of times per time period that disaster<br />

information is propagated.


Work Zone Management (MC08)<br />

High Priority<br />

This market package directs activity in work zones, controlling traffic through portable DMS and informing other<br />

groups of activity (e.g., ISP, TM, other maintenance and construction centers) for better coordination<br />

management. Work zone speeds and delays are provided to the motorist prior to the work zones.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Transportation Management Centers<br />

• CCTV Cameras<br />

• 511<br />

• Dynamic Message Signs<br />

<strong>Plan</strong>ned Projects<br />

• Caltrans<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• None at this time<br />

Objectives Being Met<br />

• Improve travel time along corridors<br />

• Improve overall congestion<br />

Performance Measures<br />

• Number of accidents (or incidents) at work zones that have ITS elements. Measurement could include<br />

comparison of similar criteria for work zones without ITS elements.<br />

• Traffic flow in area of workzones. Again measurement could be compared with a similar measure calculated<br />

for workzones without ITS elements.


Maintenance and Construction Activity Coordination<br />

(MC10)<br />

High Priority<br />

This market package supports the dissemination of maintenance and construction activity information to centers<br />

which can utilize it as part of their operations, or to the Information Service Providers who can provide the<br />

information to travelers.<br />

Existing Infrastructure<br />

• TMCs<br />

• Websites<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Caltrans<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• None at this time<br />

Objectives Being Met<br />

Performance Measures<br />

• Frequency of activity updates<br />

• Number of agencies receiving updates.


Medium Priority Market Packages for the Sacramento Area<br />

ITS Data Mart (AD01)<br />

Medium Priority<br />

This market package provides a focused archive that houses data collected and owned by a single agency,<br />

district, private sector provider, research institution, or other organization. This focused archive typically<br />

includes data covering a single transportation mode and one jurisdiction that is collected from an operational<br />

data store and archived for future use. It provides general query and report access to archive data users.<br />

Existing Infrastructure<br />

• Accident Database<br />

• GIS Mapping System<br />

• Transit Ridership Database<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Regional Traveler Information System<br />

• 511 System<br />

• Completion of Valleywide GIS Mapping<br />

Objectives Being Met<br />

• Provide more predictable travel times<br />

• Develop programs that have a regional focus<br />

Performance Measures<br />

• Cost to collect data<br />

• Data accuracy


ITS Data Warehouse (AD02)<br />

Medium Priority<br />

This market package includes all of the data collection and management capabilities provided by the ITS Data<br />

Mart, and adds the functionality and interface definitions that allow the collection of data from multiple agencies<br />

and data sources spanning across modal and jurisdictional boundaries. It performs the additional transformations<br />

and provides the additional data management features that are necessary so that all the data can be managed in<br />

a single repository. The potential for large volumes of carried data suggests additional on­line analysis and data<br />

mining features that are also included in this market package in addition to the basic query and reporting user<br />

access features offered by the ITS Data Mart.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Accident Database<br />

• GIS Mapping System<br />

• Transit Ridership Database<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Regional Traveler Information System<br />

• 511 System<br />

• Completion of Valleywide GIS Mapping<br />

Objectives Being Met<br />

• Provide more predictable travel times<br />

• Develop programs that have a regional focus<br />

Performance Measures<br />

• Cost to collect data<br />

• Data accuracy


ITS Virtual Data Warehouse (AD03)<br />

Medium Priority<br />

This market package provides the same broad access to multimodal, multidimensional data from varied data<br />

sources as in the ITS Data Warehouse Market Package, but provides this access using enhanced<br />

interoperability between physically distributed ITS archives that are each locally managed. Requests for data that<br />

are satisfied by access to a single repository in the ITS Data Warehouse Market Package are parsed by the local<br />

archive and dynamically translated to requests to remote archives which relay the data necessary to satisfy the<br />

request.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Accident Database<br />

• GIS Mapping System<br />

• Transit Ridership Database<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• Alternate Route <strong>Plan</strong>s Database/Website ­ access to the plans via the Internet.<br />

• Regional Traveler Information System<br />

• 511 System<br />

• Completion of Valleywide GIS Mapping<br />

Objectives Being Met<br />

• Provide more predictable travel times<br />

• Develop programs that have a regional focus<br />

Performance Measures<br />

• Cost to collect data<br />

• Data accuracy


Demand Response Transit Operations (APTS03)<br />

Medium Priority<br />

This market package performs vehicle routing and scheduling as well as automatic driver assignment and<br />

monitoring for demand responsive transit services. This package monitors the current status of the transit<br />

fleet and supports allocation of these fleet resources to service incoming requests for transit service while<br />

also considering traffic conditions. The Transit Management Subsystem provides the necessary data<br />

processing and information display to assist the transit operator in making optimal use of the transit fleet.<br />

This service includes the capability for a traveler request for personalized transit services to be made<br />

through the Information Service Provider (ISP) Subsystem.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• LRT<br />

• BRT<br />

• Paratransit<br />

<strong>Plan</strong>ned Projects<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• Expansion of bus and van service regionwide, including a large increase in service for elderly and<br />

disabled persons.<br />

• Implement ITS, Phase I, joint project of Yolo County Transportation District, Unitrans, and Davis<br />

Community Transit.<br />

• Roseville Transit ­ Fixed Route and Paratransit<br />

Objectives Being Met<br />

• Enhance and integrate transit services where practical and desirable<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or<br />

enforcing speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative<br />

transportation modes such as walking or bicycling<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Improve access and mobility by introducing local paratransit services with door­to­door service<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Provide for enhanced multi­modal transit transfers<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Improve convenience of transit by introducing door­to­door paratransit service<br />

• Provide priority for transit vehicles using transit priority, queue jumper lanes, and signal coordination<br />

• Provide advantageous transit service over the use of automobiles<br />

• Improve transit level of service in existing and new transit corridors through greater frequency,<br />

timeliness, and easier transfers<br />

• Provide safer transit service<br />

• Design transit oriented development (TODs) along BRT corridors thus limiting sprawl and reducing the<br />

conversion of agricultural and open space<br />

• Design transit oriented development (TODs) along BRT corridors to be conducive to walking and<br />

bicycling in addition to transit, thus reducing motorized vehicle use and resultant emissions<br />

• Provide real­time traveler information for ride­sharing and trip planning<br />

Performance Measures<br />

• Passenger trips per day per vehicle. Having an automated dispatch system should improve the<br />

efficiency of pickups per vehicle.


Transit Maintenance (APTS06)<br />

Medium Priority<br />

This market package supports automatic transit maintenance scheduling and monitoring. On­board<br />

condition sensors monitor system status and transmit critical status information to the Transit Management<br />

Subsystem. Hardware and software in the Transit Management Subsystem processes this data and<br />

schedules preventative and corrective maintenance.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• LRT<br />

• BRT<br />

• Paratransit<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Increase ridership on transit vehicles by improving reliability<br />

• Provide advantageous transit service over the use of automobiles<br />

•<br />

Performance Measures<br />

• Maintenance actions per vehicle.


Interactive Traveler Information (ATIS02)<br />

Medium Priority<br />

This market package provides tailored information in response to a traveler request. Both real­time interactive<br />

request/response systems and information systems that "push" a tailored stream of information to the traveler<br />

based on a submitted profile are supported. The traveler can obtain current information regarding traffic<br />

conditions, roadway maintenance and construction, transit services, ride share/ride match, parking management,<br />

detours and pricing information. A range of two­way wide­area wireless and fixed­point to fixed­point<br />

communications systems may be used to support the required data communications between the traveler and<br />

Information Service Provider. A variety of interactive devices may be used by the traveler to access information<br />

prior to a trip or en route including phone via a 511­like portal, kiosk, Personal Digital Assistant, personal<br />

computer, and a variety of in­vehicle devices. This market package also allows value­added resellers to collect<br />

transportation information that can be aggregated and be available to their personal devices or remote traveler<br />

systems to better inform their customers of transportation conditions. Successful deployment of this market<br />

package relies on availability of real­time transportation data from roadway instrumentation, transit, probe<br />

vehicles or other means. A traveler may also input personal preferences and identification information via a<br />

“traveler card”that can convey information to the system about the traveler as well as receive updates from the<br />

system so the card can be updated over time.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic<br />

condition reports to drivers.<br />

• Regional Traveler Information System<br />

• Remote ATIS workstations<br />

• Truck Stop Information Demo<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide current traveler information via 511<br />

• Provide real­time transit vehicle arrival information system<br />

• Disseminate accurate, multimodal traveler information via STARNET<br />

• Provide more predictable travel times<br />

• Improve travel time along corridors<br />

• Promote increased use of alternate modes (walking, bicycle, transit, carpool, vanpool)<br />

• Improve overall congestion<br />

• Improve access into and out of economic centers<br />

• Develop programs that have a regional focus<br />

• Improve access to and reliability of alternate modes<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and


varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Performance Measures<br />

• Use of 511 information by travelers. Measured as number of page views on website or calls to 511 system.


Dynamic Route Guidance (ATIS04)<br />

Medium Priority<br />

This market package offers advanced route planning and guidance that is responsive to current conditions. The<br />

package combines the autonomous route guidance user equipment with a digital receiver capable of receiving<br />

real­time traffic, transit, and road condition information, which is considered by the user equipment in provision of<br />

route guidance.<br />

Existing Infrastructure<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Alternate Route <strong>Plan</strong>s Database/Website ­ access to the plans via the Internet.<br />

• Regional Traveler Information System<br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents<br />

and weather related road closures.<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve travel time along corridors<br />

• Improve overall congestion<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Improve access into and out of economic centers<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Performance Measures<br />

• Use of information by travelers. Viewed as number of page views on website.


Integrated Transportation Management/Route<br />

Guidance (ATIS06)<br />

Medium Priority<br />

This market package provides advanced route planning and guidance which is responsive to current conditions,<br />

and supports collection of near­real time information on intended routes for a proportion of the vehicles in the<br />

network. This comprehensive road network probe information can be used by the Traffic Management<br />

Subsystem to optimize the traffic control strategy based on anticipated vehicle routes. The Traffic Management<br />

Subsystem would utilize the individual and ISP route planning information to optimize signal timing while at the<br />

same time providing updated signal timing information to allow optimized route plans. The predictive link times<br />

used by this market package are provided by the market package ATMS9­­Traffic Forecast and Demand<br />

Management­­at the traffic management center.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Sacramento RT<br />

• Yolo County Transportation District<br />

• Davis Community Transit<br />

• Roseville Transit<br />

• STARNET Various traffic and transit operation centers in the region; hardware and software upgrades<br />

enabling a wide­area network to share transportation data and operations. Fiber optic and wireless<br />

infrastructure is included in the project.<br />

• Watt Corridor ­ Phase 2 and 3. Traffic signal coordination, transit priority, monitoring equipment and traveler<br />

information on a major arterial corridor, plus supporting communications.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

• Regional Traveler Information System<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve traffic management<br />

• Optimize operations (reduce congestion, improve the traveler experience)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Disseminate accurate, multimodal traveler information via STARNET<br />

• Improve travel time along corridors<br />

• Integrate transit services across different modes where practical and desirable<br />

• Integrate transit services across different jurisdictions where practical and desirable<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Improve access into and out of economic centers<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Performance Measures


• Use of information by travelers. Viewed as number of page views on website.


HOV Lane Management (ATMS05)<br />

Medium Priority<br />

This market package manages HOV lanes by coordinating freeway ramp meters and connector signals with<br />

HOV lane usage signals. Preferential treatment is given to HOV lanes using special bypasses, reserved lanes,<br />

and exclusive rights­of­way that may vary by time of day. Vehicle occupancy detectors may be installed to verify<br />

HOV compliance and to notify enforcement agencies of violations.<br />

Existing Infrastructure<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• CCTV Cameras<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Ramp metering at all interchanges from Foresthill Road to the Sacramento County Line.<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.).<br />

• Construct Traffic Operation System (Jct. 50 to I­5)<br />

• Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

• U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp<br />

metering, CCTV)<br />

• Yolo County portion of I­5 traffic operations system and ramp metering.<br />

• U.S. 50 Install ramp meters and modify ramp design at South River Rd. interchange.<br />

• U.S. 50 Jefferson Blvd. interchange— expand the ramps and signals from 1 to 2 lanes, add ramp metering<br />

and turn lanes, and related street closures.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Caltrans Ramp Meter/Surveillance<br />

• Eleven Ramp meters planned between Sacramento/El Dorado County line and Placerville<br />

• Six Ramp meters on SR65 between Lincoln and I­80<br />

• Upgrade Caltrans District 3 Regional TMC to manage US­50, I­80 and other ITS deployments (includes<br />

coordination with Nevada and Tahoe Basin to ensure consistency)<br />

• Portable Traffic Management Devices (customized for portability including DMS, HAR, CCTV/web cameras,<br />

temporary signals, incident command center, and communications to RTMC)<br />

Objectives Being Met<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or enforcing<br />

speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative transportation<br />

modes such as walking or bicycling<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide electronic payment and/or regional fare collection system for transit (possibly multi­modal)<br />

• Provide electronic payment and/or regional fare collection system for transit (possibly multi­modal)<br />

• Improve travel time along corridors<br />

• Improve traffic management<br />

• Consider addition of HOV/HOT lanes across region<br />

Performance Measures


• Reduced travel time. Measured by travel time along the corridor.


Traffic Forecast and Demand Management (ATMS09)<br />

Medium Priority<br />

This market package includes advanced algorithms, processing, and mass storage capabilities that support<br />

historical evaluation, real­time assessment, and forecast of the roadway network performance. This includes the<br />

prediction of travel demand patterns to support better link travel time forecasts. The source data would come<br />

from the Traffic Management Subsystem itself as well as other traffic management centers and forecasted traffic<br />

loads derived from route plans supplied by the Information Service Provider Subsystem. This market package<br />

provides data that supports the implementation of TDM programs, and policies managing both traffic and the<br />

environment. The package collects information on vehicle pollution levels, parking availability, usage levels, and<br />

vehicle occupancy to support these functions. Demand management requests can also be made to Toll<br />

Administration, Transit Management, and Parking Management Subsystems.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Connect traffic signals, including ITS technology, that are located outside of the Central City to the City’s<br />

existing Traffic Operations Center.<br />

Objectives Being Met<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or enforcing<br />

speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative transportation<br />

modes such as walking or bicycling<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Provide electronic payment and/or regional fare collection system for transit (possibly multi­modal)<br />

• Provide more predictable travel times<br />

• Improve overall congestion<br />

• Improve travel time along corridors<br />

• Improve traffic management<br />

• Improve access into and out of economic centers<br />

Performance Measures<br />

• Traffic flow. Measured at intersections with signal systems.<br />

• Travel time along a corridor (that contains coordinated signals)


Emissions Monitoring and Management (ATMS11)<br />

Medium Priority<br />

This market package monitors individual vehicle emissions and provides general air quality monitoring using<br />

distributed sensors to collect the data. The collected information is transmitted to the emissions management<br />

subsystem for processing. Both area wide air quality monitoring and point emissions monitoring are supported by<br />

this market package. For area wide monitoring, this market package measures air quality, identifies sectors that<br />

are non­compliant with air quality standards, and collects, stores and reports supporting statistical data. For point<br />

emissions monitoring, this market package measures tail pipe emissions and identifies vehicles that exceed<br />

emissions standards. Summary emissions information or warnings can also be displayed to drivers. The<br />

gathered information can be used to implement environmentally sensitive TDM programs, policies, and<br />

regulations.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• None at this time<br />

Objectives Being Met<br />

• Reduce vehicle emissions<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce vehicle emissions by reducing total VMT<br />

• Reduce vehicle emissions by reducing congestion and thus possibly reducing stop­and­go conditions<br />

• Use technology to help maintain a balance of environmentally friendly growth and the use of advanced<br />

technology<br />

Performance Measures<br />

• Number of vehicles tested.<br />

• Rate of compliance with emission standards.


Standard Railroad Grade Crossing (ATMS13)<br />

Medium Priority<br />

This Standard Railroad Grade Crossing market package manages highway traffic at highway­rail intersections<br />

(HRIs) where rail operational speeds are less than 80 miles per hour. Both passive (e.g., the crossbuck sign) and<br />

active warning systems (e.g., flashing lights and gates) are supported.<br />

These traditional HRI warning systems may also be augmented with other standard traffic management devices.<br />

The warning systems are activated on notification by interfaced wayside equipment of an approaching train. The<br />

equipment at the HRI may also be interconnected with adjacent signalized intersections so that local control can<br />

be adapted to highway­rail intersection activities. Health monitoring of the HRI equipment and interfaces is<br />

performed; detected abnormalities are reported to both highway and railroad officials through wayside interfaces<br />

and interfaces to the traffic management subsystem.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• None at this time<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve traffic management<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Improve access into and out of economic centers<br />

Performance Measures<br />

• Number of train/ vehicle crashes at HRIs interconnected with Traffic Signal System.


Advanced Railroad Grade Crossing (ATMS14)<br />

Medium Priority<br />

The Advanced Railroad Grade Crossing market package manages highway traffic at HRIs where operational<br />

requirements demand advanced features (e.g. where operational speeds are greater than 80 miles per hour).<br />

This market packages builds upon the services offered by Standard Railroad Grade Crossing with additional<br />

safety features to mitigate the risks associated with higher rail speeds.<br />

Existing Infrastructure<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

<strong>Plan</strong>ned Projects<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• None at this time<br />

Objectives Being Met<br />

• Market ITS to encourage the use of multi­modal transportation system<br />

• Reduce time residents spend in congestion<br />

• Improve traffic management<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Reduce conflicts between motorized and non­motorized modes and vehicles<br />

• Improve access into and out of economic centers<br />

Performance Measures<br />

• Number of train/ vehicle crashes at HRIs with advanced surveillance capabilities<br />

• Number of blocked intersection occurrences recognized by system.


Speed Monitoring (ATMS19)<br />

Medium Priority<br />

This market package monitors the speeds of vehicles traveling through a roadway system. If the speed is<br />

determine to be excessive, roadside equipment can suggest a safe driving speed. Environmental conditions may<br />

be monitored and factored into the safe speed advisories that are provided to the motorist. This service can also<br />

support notifications to an enforcement agency to enforce the speed limit on a roadway system.<br />

Existing Infrastructure<br />

• Closed Loop Signal Systems<br />

• Central Signal Systems<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

<strong>Plan</strong>ned Projects<br />

• Install Smart Traffic Calming in south Midtown area.<br />

• Install ramp meters, HOV Bypasses, additional on ramps, traffic monitoring stations and Closed Circuit TV<br />

installation on I­5 from Pocket Rd. to I­80.<br />

• Install ramp metering, traffic monitoring stations, Closed Circuit TV installation, message signs, and upgrade<br />

count stations to Traffic Management System on I­80 from Yolo Co. line to Route 244 (Longview Dr.)<br />

• Construct Traffic Operation System (Jct. 50 to I­5)<br />

• Yolo County portion of U.S. 50 traffic operations system and ramp metering at various locations.<br />

• U.S. 50 From I­80 to Sacramento County line— install traffic operations system (message signs, ramp<br />

metering, CCTV)<br />

• Yolo County portion of I­5 traffic operations system and ramp metering.<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Traffic monitoring stations near the Sacramento/Placer County line in Roseville<br />

• US 50 Surveillance (including 4 CCTV or web cameras and 6 traffic monitoring stations)<br />

• Elk Grove signals ­ Upgrade City’s existing onstreet system. Replace controllers/cabinets as needed and<br />

add system detectors on all segments<br />

• Dynamic Speed Signing System for weather conditions<br />

• Traffic Monitoring Phase I ­ Deploy traffic monitoring devices (e.g. flow detectors, CCTV cameras)<br />

• along segments of US 50 in South Shore area, and along Highways 28, 89 and 267 in the North Shore<br />

Objectives Being Met<br />

• Improve traffic flow by reducing congestion (e.g. on heavily traveled arterials), by reducing and/or enforcing<br />

speeds for safety (e.g. in residential neighborhoods), and by improving facilities for alternative transportation<br />

modes such as walking or bicycling<br />

Performance Measures<br />

• Traffic flow. Measured at intersections with signal systems.<br />

• Travel time along a corridor (that contains coordinated signals)


HAZMAT Management (CVO10)<br />

Medium Priority<br />

This market package integrates incident management capabilities with commercial vehicle tracking to assure<br />

effective treatment of HAZMAT materials and incidents. HAZMAT tracking is performed by the Fleet and Freight<br />

Management Subsystem. The Emergency Management Subsystem is notified by the Commercial Vehicle if an<br />

incident occurs and coordinates the response. The response is tailored based on information that is provided as<br />

part of the original incident notification or derived from supplemental information provided prior to the beginning<br />

of the trip or gathered following the incident depending on the selected policy and implementation.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Streamline goods movement processes<br />

• Improve commercial vehicle operations using technologies such as weigh­in­motion sensors and real­time<br />

roadway condition information for trucks and delivery fleets<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Occurrences of HAZMAT incidents where assistance requested.


Emergency Routing (EM02)<br />

Medium Priority<br />

This market package supports automated vehicle location and dynamic routing of emergency vehicles. The<br />

service also supports coordination with the Traffic Management Subsystem, collecting detailed road network<br />

conditions and requesting special priority or other specific emergency traffic control strategies on the selected<br />

route(s). The service provides for information exchange between care facilities and both the Emergency<br />

Management Subsystem and emergency vehicles.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Emergency Response Telecommunications Center<br />

• Police Department Mobile Data Terminals<br />

• Computer Aided Dispatch<br />

• Emergency Vehicle Preemption Systems<br />

<strong>Plan</strong>ned Projects<br />

• Police and Fire Departments in Sacramento<br />

Area<br />

• Caltrans<br />

• Emergency Vehicles ­ AVI/AVL (including tracking equipment in dispatch and TMC)<br />

• Emergency Vehicle Pre­emption (EVP) <strong>Deployment</strong><br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents<br />

and weather related road closures.<br />

• Computer Aided Dispatch Integration: integrate the computer­aided dispatch systems of various emergency<br />

response and transportation agencies that jointly participate in traffic incident management, including local<br />

police, state patrol, HAZMAT response, Caltrans, and fire departments.<br />

Objectives Being Met<br />

• Reduce time residents spend in congestion<br />

• Improve accessibility by integrating operations across jurisdictional boundaries via their TOCs.<br />

Interconnected TOCs can then optimize operations through actions such as accident response, real­time<br />

signal optimization, and provision of alternate routes when needed.<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Decrease emergency response times and capabilities using cameras and emergency vehicle signal<br />

preemption<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Average time to respond to emergency. Measured as the average time from receipt of call to arrival of<br />

emergency services at call site.


Roadway Service Patrols (EM04)<br />

Medium Priority<br />

This market package supports roadway service patrol vehicles that monitor roads that aid motorists, offering<br />

rapid response to minor incidents (flat tire, accidents, out of gas) to minimize disruption to the traffic stream. If<br />

problems are detected, the roadway service patrol vehicles will provide assistance to the motorist (e.g., push a<br />

vehicle to the shoulder or median). The market package monitors service patrol vehicle locations and supports<br />

vehicle dispatch to identified incident locations. Incident information collected by the service patrol is shared with<br />

traffic, maintenance and construction, and traveler information systems.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Emergency Response Telecommunications Center<br />

• Police Department Mobile Data Terminals<br />

• Computer Aided Dispatch<br />

<strong>Plan</strong>ned Projects<br />

• Police and Fire Departments in Sacramento<br />

Area<br />

• Caltrans<br />

• Emergency Vehicles ­ AVI/AVL (including tracking equipment in dispatch and TMC)<br />

Objectives Being Met<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Wait time for stranded motorists. Measured as time from receipt of call for assistance to arrival of freeway<br />

service patrol or other public safety vehicle.


Transportation Infrastructure Protection (EM05)<br />

Medium Priority<br />

This market package includes the monitoring of transportation infrastructure (e.g., bridges, tunnels and<br />

management centers) for potential threats using sensors and surveillance equipment and barrier and safeguard<br />

systems to preclude an incident, control access during and after an incident or mitigate impact of an incident.<br />

Threats can result from acts of nature (e.g., hurricanes, earthquakes), terrorist attacks or other incidents causing<br />

damage to the infrastructure (e.g., stray barge hitting a bridge support). Infrastructure may be monitored with<br />

acoustic, environmental threat (such as nuclear, biological, chemical, and explosives), infrastructure condition<br />

and integrity, motion and object sensors and video and audio surveillance equipment. Data from such sensors<br />

and surveillance equipment may be processed in the field or sent to a center for processing. The data enables<br />

operators at the center to detect and verify threats. When a threat is detected, agencies are notified. Detected<br />

threats or advisories received from other agencies result in an increased level of system preparedness. In<br />

response to threats, barrier and safeguard systems may be activated by Traffic Management Subsystems to<br />

deter an incident, control access to an area or mitigate the impact of an incident. Barrier systems include gates,<br />

barriers and other automated and remotely controlled systems that manage entry to transportation infrastructure.<br />

Safeguard systems include blast shields, exhaust systems and other automated and remotely controlled systems<br />

that mitigate impact of an incident.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

• None at this time<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Develop programs that have a regional focus<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Infrastructure coverage. Measured in transportation assets covered by surveillance.<br />

• Incidents detected.


Wide Area Alert (EM06)<br />

Medium Priority<br />

This market package uses ITS driver and traveler information systems to alert the public in emergency situations<br />

such as child abductions, severe weather events, civil emergencies, and other situations that pose a threat to life<br />

and property. The alert includes information and instructions for transportation system operators and the<br />

traveling public, improving public safety and enlisting the public’s help in some scenarios. The ITS technologies<br />

will supplement and support other emergency and homeland security alert systems such as the Emergency Alert<br />

System (EAS). When an emergency situation is reported and verified and the terms and conditions for system<br />

activation are satisfied, a designated agency broadcasts emergency information to traffic agencies, transit<br />

agencies, information service providers, toll operators, and others that operate ITS systems. The ITS systems, in<br />

turn, provide the alert information to transportation system operators and the traveling public using ITS<br />

technologies such as dynamic message signs, highway advisory radios, in­vehicle displays, transit displays, 511<br />

traveler information systems, and traveler information web sites.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

• HARs<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

• Transit agencies<br />

• Regional Incident/Emergency Management <strong>Plan</strong> (incorporates proposed AVI/AVL technologies for<br />

emergency response vehicles)<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Develop programs that have a regional focus<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Usage of alert system. Measured as number of alerts per time period.


Early Warning System (EM07)<br />

Medium Priority<br />

This market package monitors and detects potential, looming, and actual disasters including natural disasters<br />

(hurricanes, earthquakes, floods, winter storms, tsunamis, etc.) and technological and man­made disasters<br />

(hazardous materials incidents, nuclear power plant accidents, and acts of terrorism including nuclear, chemical,<br />

biological, and radiological weapons attacks). The market package monitors alerting and advisory systems, ITS<br />

sensors and surveillance systems, field reports, and emergency call­taking systems to identify emergencies and<br />

notifies all responding agencies of detected emergencies.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

• HARs<br />

<strong>Plan</strong>ned Projects<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

• Regional Incident/Emergency Management <strong>Plan</strong> (incorporates proposed AVI/AVL technologies for<br />

emergency response vehicles)<br />

Objectives Being Met<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Usage of warning system. Measured as number of warnings given per time period.


Evacuation and Reentry Management (EM09)<br />

Medium Priority<br />

This market package supports evacuation of the general public from a disaster area and manages subsequent<br />

reentry to the disaster area. The market package addresses evacuations for all types of disasters, including<br />

disasters like hurricanes that are anticipated and occur slowly, allowing a well­planned orderly evacuation, as<br />

well as disasters like terrorist acts that occur rapidly, without warning, and allow little or no time for preparation or<br />

public warning.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Improve traffic management<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Evacuation performance. Measured as time to evacuate x number of people or y area.


Road Weather Data Collection (MC03)<br />

Medium Priority<br />

This market package collects current road and weather conditions using data collected from environmental<br />

sensors deployed on and about the roadway (or guideway in the case of transit related rail systems). In addition<br />

to fixed sensor stations at the roadside, sensing of the roadway environment can also occur from sensor systems<br />

located on Maintenance and Construction Vehicles and on­board sensors provided by auto manufacturers. The<br />

collected environmental data is used by the Weather Information Processing and Distribution Market Package to<br />

process the information and make decisions on operations.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Emergency Response Telecommunications Center<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

• Police and Fire Departments in Sacramento<br />

• Sacramento RT<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Improve traffic management<br />

• Improve emergency response time and coordination by integrating emergency response and traffic<br />

management activities<br />

Performance Measures<br />

• Number of hazardous conditions identified by the devices.<br />

• Amount of road treatment materials used<br />

• Response time of crews to treat hazardous road conditions.


Weather Information Processing and Distribution<br />

(MC04)<br />

Medium Priority<br />

This market package processes and distributes the environmental information collected from the Road Weather<br />

Data Collection market package. This market package uses the environmental data to detect environmental<br />

hazards such as icy road conditions, high winds, and dense fog so that system operators and decision support<br />

systems can make decisions on corrective actions to take. The continuing updates of road condition information<br />

and current temperatures can be used by system operators to more effectively deploy road maintenance<br />

resources, issue general traveler advisories, issue location specific warnings to drivers using the Traffic<br />

Information Dissemination market package, and aid operators in scheduling work activity.<br />

Existing Infrastructure<br />

Responsible Agency<br />

• Weather Monitoring Systems<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

<strong>Plan</strong>ned Projects<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic<br />

condition reports to drivers.<br />

• Regional Traveler Information System<br />

• Weather/ATMS Integration and Automation<br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents<br />

and weather related road closures.<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Performance Measures<br />

• Amount of road treatment materials used<br />

• Response time of crews to treat hazardous road conditions.


Roadway Maintenance and Construction (MC07)<br />

Medium Priority<br />

This market package supports numerous services for scheduled and unscheduled maintenance and construction<br />

on a roadway system or right­of­way. Maintenance services would include landscape maintenance, hazard<br />

removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and<br />

repair and maintenance of both ITS and non­ITS equipment on the roadway (e.g., signs, traffic controllers, traffic<br />

detectors, dynamic message signs, traffic signals, CCTV, etc.). Environmental conditions information is also<br />

received from various weather sources to aid in scheduling maintenance and construction activities.<br />

Existing Infrastructure<br />

• Weather Monitoring Systems<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

Responsible Agency<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

<strong>Plan</strong>ned Projects<br />

• Caltrans District 3 TOS projects. Includes ramp meters, HOV onramp lanes, traffic monitoring stations,<br />

closed circuit television cameras, changeable message signs, highway advisory radio, weather monitoring<br />

systems, loop detectors, etc.<br />

• Traveler Information Management (includes 511 system, DMS, kiosks, web pages, HAR, media, NOAA<br />

Weather radio)<br />

• Sacramento 511<br />

• Provide advanced traveler information (ATIS) system and disseminate concise, useful road and traffic<br />

condition reports to drivers.<br />

• Regional Traveler Information System<br />

• Weather/ATMS Integration and Automation<br />

• Dynamic Alternate Route signing system ­ implement dynamic variable message signs (VMS) specifically<br />

sited, and primarily devoted, to detouring traffic onto alternate routes during incidents, including accidents<br />

and weather related road closures.<br />

Objectives Being Met<br />

• Improve traveler experience and reduce congestion by providing traveler information<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

• Provide traveler information in accessible formats (i.e., large print, Braille, 711, audio, multi­lingual) and<br />

varying media (i.e., web, TV, in­vehicle, 511, kiosks)<br />

Performance Measures<br />

• Average response time of maintenance crews. Measured as time from request for maintenance action to<br />

arrival of maintenance vehicle on scene.


Work Zone Safety Monitoring (MC09)<br />

Medium Priority<br />

This market package includes systems that improve work crew safety and reduce collisions between the<br />

motoring public and maintenance and construction vehicles. This market package detects vehicle intrusions in<br />

work zones and warns crew workers and drivers of imminent encroachment or other potential safety hazards.<br />

Crew movements are also monitored so that the crew can be warned of movement beyond the designated safe<br />

zone. The market package supports both stationary and mobile work zones. The intrusion detection and alarm<br />

systems may be collocated or distributed, allowing systems that detect safety issues far upstream from a work<br />

zone (e.g., detection of over dimension vehicles before they enter the work zone).<br />

Existing Infrastructure<br />

Responsible Agency<br />

• CCTV Cameras<br />

• Dynamic Message Signs/Trailblazers<br />

• 511<br />

• Cities in Sacramento<br />

• County of Sacramento<br />

• Caltrans<br />

<strong>Plan</strong>ned Projects<br />

• None at this time<br />

Objectives Being Met<br />

• Improve coordination among traffic, public safety and transit agencies<br />

• Improve safety for all modes (i.e., surveillance on transit vehicles, traffic calming)<br />

Performance Measures<br />

• Number of times safety monitoring equipment activated<br />

• Number of accidents (or incidents) at work zones with safety monitoring equipment.


Appendix G


APPENDIX: MARKET PACKAGE MAPPING TO ELEMENTS<br />

Market Market Package Name Element Name Status<br />

Package<br />

AD1 ITS Data Mart Archive Data User Systems <strong>Plan</strong>ned<br />

AD1 ITS Data Mart California HPMS <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Caltrans Performance Monitoring <strong>Plan</strong>ned<br />

System (PeMS)<br />

AD1 ITS Data Mart Capitol Corridor Train Stations <strong>Plan</strong>ned<br />

AD1 ITS Data Mart City of Roseville Police and Fire <strong>Plan</strong>ned<br />

Dispatch<br />

AD1 ITS Data Mart City of Sacramento TOC <strong>Plan</strong>ned<br />

AD1 ITS Data Mart County Sheriff Communications Centers <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Light Rail Station Parking Mgmt. <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Light Rail Transit Management Center <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Local Police Dispatch <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Municipal Maintenance Dispatch <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Paratransit, Inc. <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Regional Traffic Count Archive <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

AD1 ITS Data Mart RT Police Services <strong>Plan</strong>ned<br />

AD1 ITS Data Mart RT Transit Management Center <strong>Plan</strong>ned<br />

AD1 ITS Data Mart RTMC-CHP <strong>Plan</strong>ned<br />

AD1 ITS Data Mart RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Sacramento City Police Department <strong>Plan</strong>ned<br />

Communications<br />

AD1 ITS Data Mart Sacramento City Roadside Equipment <strong>Plan</strong>ned<br />

AD1 ITS Data Mart Sacramento County Maintenance <strong>Plan</strong>ned<br />

Service Center<br />

AD1 ITS Data Mart Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

AD1 ITS Data Mart Sacramento County Sheriff Dept. <strong>Plan</strong>ned<br />

Communications<br />

AD1 ITS Data Mart Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

AD1 ITS Data Mart Statewide Integrated Reporting System <strong>Plan</strong>ned<br />

(SWITRS)<br />

AD1 ITS Data Mart Traffic Accident and Surveillance <strong>Plan</strong>ned<br />

Analysis System (TASAS)<br />

AD2 ITS Data Warehouse Archive Data User Systems <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Davis TOC <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

AD2 ITS Data Warehouse City of Elk Grove TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Folsom TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Roseville TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Sacramento TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of West Sacramento TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse City of Woodland TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse e-tran Transit Center <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Local Transit Dispatch Centers <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Municipal TOCs <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Other County TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Paratransit, Inc. <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

AD2 ITS Data Warehouse RT Transit Management Center <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse SACOG Data Repository <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

AD2 ITS Data Warehouse Sacramento International Airport TMC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse STARNET Server <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Yuba City TOC <strong>Plan</strong>ned<br />

AD2 ITS Data Warehouse Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

AD3 ITS Virtual Data Warehouse SACOG Data Repository <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Capital Corridor Train Operations Center<strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Capital Corridor Trains <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking City of Roseville Website <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking El Dorado Transit Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking e-tran Transit Center <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking e-tran Transit Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Folsom Stage Line Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Light Rail Transit Management Center <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Local Transit Dispatch Centers <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Local Transit Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Municipal Websites <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

APTS1 Transit Vehicle Tracking Paratransit Vehicle <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Paratransit, Inc. <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Regional Transit LRT Vehicle <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

APTS1 Transit Vehicle Tracking Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking RT Transit Management Center <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking RT Website <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

APTS1 Transit Vehicle Tracking Sacramento Region 511 Website <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking School Bus Dispatch <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking School Buses <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Unitrans Transit Vehicles <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Yolo County Buses <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS1 Transit Vehicle Tracking Yuba-Sutter Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations El Dorado Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations e-tran Transit Center <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations e-tran Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Folsom Stage Line Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Light Rail Transit Management Center <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Local Transit Dispatch Centers <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Local Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Regional Transit LRT Vehicle <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

APTS2 Transit Fixed-Route Operations Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations RT Transit Management Center <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations School Bus Dispatch <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations School Buses <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Unitrans Transit Vehicles <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Yolo County Bus Website <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Yolo County Buses <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS2 Transit Fixed-Route Operations Yuba-Sutter Transit Vehicles <strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

El Dorado Transit Dispatch<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

El Dorado Transit Vehicles<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

e-tran Transit Center<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

e-tran Transit Vehicles<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Folsom Stage Line Vehicles<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Folsom Stage Lines Transit Dispatch<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Paratransit Vehicle<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Paratransit, Inc.<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Regional Transit Bus Vehicle<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

Roseville Transit Vehicles<br />

<strong>Plan</strong>ned<br />

APTS3<br />

Demand Response Transit<br />

Operations<br />

RT Transit Management Center<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

APTS4<br />

Market Package Name Element Name Status<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Transit Passenger and Fare<br />

Management<br />

Financial Institutions<br />

Paratransit Vehicle<br />

Paratransit, Inc.<br />

Regional Transit Bus Vehicle<br />

Regional Transit LRT Vehicle<br />

RT Police Services<br />

RT Transit Kiosks<br />

RT Transit Management Center<br />

Sacramento Regional Traveler Card<br />

Yolo Bus Dispatch Center<br />

Yolo County Buses<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

APTS5 Transit Security City of Roseville Police and Fire <strong>Plan</strong>ned<br />

Dispatch<br />

APTS5 Transit Security County Sheriff Communications Centers <strong>Plan</strong>ned<br />

APTS5 Transit Security El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

APTS5 Transit Security El Dorado Transit Vehicles <strong>Plan</strong>ned<br />

APTS5 Transit Security e-tran Transit Center <strong>Plan</strong>ned<br />

APTS5 Transit Security e-tran Transit Vehicles <strong>Plan</strong>ned<br />

APTS5 Transit Security Folsom Stage Line Vehicles <strong>Plan</strong>ned<br />

APTS5 Transit Security Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS5 Transit Security Light Rail Transit Management Center <strong>Plan</strong>ned<br />

APTS5 Transit Security Local Police Dispatch <strong>Plan</strong>ned<br />

APTS5 Transit Security Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS5 Transit Security Regional Transit LRT Vehicle <strong>Plan</strong>ned<br />

APTS5 Transit Security Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

APTS5 Transit Security Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS5 Transit Security RT Police Services <strong>Plan</strong>ned<br />

APTS5 Transit Security RT Transit Kiosks <strong>Plan</strong>ned<br />

APTS5 Transit Security RT Transit Management Center <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

APTS5 Transit Security Sacramento City Police Department <strong>Plan</strong>ned<br />

Communications<br />

APTS5 Transit Security Sacramento County Sheriff Dept. <strong>Plan</strong>ned<br />

Communications<br />

APTS5 Transit Security Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

APTS5 Transit Security Unitrans Transit Vehicles <strong>Plan</strong>ned<br />

APTS5 Transit Security Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS5 Transit Security Yolo County Buses <strong>Plan</strong>ned<br />

APTS5 Transit Security Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS5 Transit Security Yuba-Sutter Transit Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance El Dorado Transit Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance e-tran Transit Center <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance e-tran Transit Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Folsom Stage Line Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Light Rail Transit Management Center <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Regional Transit LRT Vehicle <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

APTS6 Transit Maintenance Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance RT Transit Management Center <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance School Bus Dispatch <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance School Buses <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Unitrans Transit Vehicles <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Yolo County Buses <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS6 Transit Maintenance Yuba-Sutter Transit Vehicles <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Capital Corridor Train Operations Center<strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination City of Roseville Roadside Equipment <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination City of Roseville TOC <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination City of Sacramento TOC <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination e-tran Transit Center <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Light Rail Station Parking Mgmt. <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Light Rail Transit Management Center <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

APTS7 Multi-modal Coordination Local Transit Dispatch Centers <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Paratransit, Inc. <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Private Transit Provider Dispatch <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Regional Transit LRT Vehicle <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

APTS7 Multi-modal Coordination Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination RT Transit Management Center <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Sacramento City Roadside Equipment <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

APTS7 Multi-modal Coordination Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

APTS7 Multi-modal Coordination Sacramento International Airport TMC <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Taxi Dispatch <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS7 Multi-modal Coordination Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information City of Roseville Website <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information El Dorado Transit Vehicles <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information e-tran Transit Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information e-tran Transit Vehicles <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Folsom Stage Line Vehicles <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Light Rail Transit Management Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Municipal Websites <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Paratransit Vehicle <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Paratransit, Inc. <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Regional Transit Bus Vehicle <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Regional Transit LRT Vehicle <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

APTS8 Transit Traveler Information Roseville Transit Vehicles <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information RT Passenger Information Signs <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information RT Transit Kiosks <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information RT Transit Management Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information RT Transit Monitors <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information RT Website <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Sacramento Region 511 Website <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information STARNET ISP <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

APTS8 Transit Traveler Information User Personal Computing Devices <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Yolo County Buses <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

APTS8 Transit Traveler Information Yuba-Sutter Transit Vehicles <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Caltrans D3 Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Capitol Corridor Train Stations <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Citrus Heights Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Citrus Heights Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Elk Grove TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Folsom Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Folsom TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Rancho Cordova Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

ATIS1 Broadcast Traveler Information City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Roseville TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Roseville Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

ATIS1 Broadcast Traveler Information City of Sacramento TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of Sacramento Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of West Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

ATIS1 Broadcast Traveler Information City of West Sacramento TOC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information City of West Sacramento Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information e-tran Transit Center <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Light Rail Transit Management Center <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Local Print and Broadcast Media <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Municipal Maintenance Dispatch <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Municipal Websites <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Private Traveler Information Service<br />

Providers<br />

<strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

ATIS1 Broadcast Traveler Information Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

ATIS1 Broadcast Traveler Information RT Transit Management Center <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information RTMC-CHP <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Sacramento County Maintenance <strong>Plan</strong>ned<br />

Service Center<br />

ATIS1 Broadcast Traveler Information Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

<strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

ATIS1 Broadcast Traveler Information Sacramento County Website <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Sacramento International Airport <strong>Plan</strong>ned<br />

Maintenance Dispatch<br />

ATIS1 Broadcast Traveler Information Sacramento International Airport TMC <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information Sacramento International Airport <strong>Plan</strong>ned<br />

Website<br />

ATIS1 Broadcast Traveler Information Sacramento Regional Fire/ EMS Comm. <strong>Plan</strong>ned<br />

Center<br />

ATIS1 Broadcast Traveler Information STARNET ISP <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information STARNET Server <strong>Plan</strong>ned<br />

ATIS1 Broadcast Traveler Information User Personal Computing Devices <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information City of Roseville TOC <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information City of Sacramento TOC <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information Municipal TOCs <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information RT Transit Kiosks <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

ATIS2 Interactive Traveler Information Sacramento International Airport TMC <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information STARNET ISP <strong>Plan</strong>ned<br />

ATIS2 Interactive Traveler Information User Personal Computing Devices <strong>Plan</strong>ned<br />

ATIS8 Dynamic Ridesharing STARNET ISP <strong>Plan</strong>ned<br />

ATIS8 Dynamic Ridesharing User Personal Computing Devices <strong>Plan</strong>ned<br />

ATMS01 Network Surveillance Caltrans D3 Data Server Existing<br />

ATMS01 Network Surveillance Caltrans D3 Website Existing<br />

ATMS01 Network Surveillance Caltrans Performance Monitoring Existing<br />

System (PeMS)<br />

ATMS01 Network Surveillance Caltrans Roadside Equipment Existing<br />

ATMS01 Network Surveillance Citrus Heights Roadside Equipment Existing


Market Market Package Name Element Name Status<br />

Package<br />

ATMS01 Network Surveillance Citrus Heights Traffic Operations Center Existing<br />

ATMS01 Network Surveillance City of Davis Field Equipment Existing<br />

ATMS01 Network Surveillance City of Davis TOC Existing<br />

ATMS01 Network Surveillance City of Elk Grove Field Equipment Existing<br />

ATMS01 Network Surveillance City of Elk Grove TOC Existing<br />

ATMS01 Network Surveillance City of Folsom Field Equipment Existing<br />

ATMS01 Network Surveillance City of Folsom TOC Existing<br />

ATMS01 Network Surveillance City of Rancho Cordova Field<br />

Existing<br />

Equipment<br />

ATMS01 Network Surveillance City of Rancho Cordova TOC Existing<br />

ATMS01 Network Surveillance City of Roseville Roadside Equipment Existing<br />

ATMS01 Network Surveillance City of Roseville TOC Existing<br />

ATMS01 Network Surveillance City of Roseville Website Existing<br />

ATMS01 Network Surveillance City of Sacramento TOC Existing<br />

ATMS01 Network Surveillance City of Sacramento Website Existing<br />

ATMS01 Network Surveillance City of West Sacramento Roadside Existing<br />

Equipment<br />

ATMS01 Network Surveillance City of West Sacramento TOC Existing<br />

ATMS01 Network Surveillance City of West Sacramento Website Existing<br />

ATMS01 Network Surveillance City of Woodland Field Equipment Existing<br />

ATMS01 Network Surveillance City of Woodland TOC Existing<br />

ATMS01 Network Surveillance Municipal Field Equipment Existing<br />

ATMS01 Network Surveillance Municipal TOCs Existing<br />

ATMS01 Network Surveillance Municipal Websites Existing<br />

ATMS01 Network Surveillance Private Traveler Information Service Existing<br />

Providers<br />

ATMS01 Network Surveillance RTMC-D3 - Traffic Operations Existing<br />

ATMS01 Network Surveillance Sacramento City Roadside Equipment Existing<br />

ATMS01 Network Surveillance Sacramento County Roadside Existing<br />

Equipment<br />

ATMS01 Network Surveillance Sacramento County Traffic Operations Existing<br />

Center<br />

ATMS01 Network Surveillance Sacramento County Website Existing<br />

ATMS01 Network Surveillance Sacramento International Airport Existing<br />

Roadside Equipment<br />

ATMS01 Network Surveillance Sacramento International Airport TMC Existing<br />

ATMS01 Network Surveillance Sacramento International Airport Existing<br />

Website<br />

ATMS01 Network Surveillance Sacramento Region 511 Website Existing<br />

ATMS01 Network Surveillance STARNET ISP Existing<br />

ATMS01 Network Surveillance Yuba City Field Equipment Existing


Market Market Package Name Element Name Status<br />

Package<br />

ATMS01 Network Surveillance Yuba City TOC Existing<br />

ATMS02 Probe Surveillance Municipal TOCs <strong>Plan</strong>ned<br />

ATMS02 Probe Surveillance Private Traveler Information Service <strong>Plan</strong>ned<br />

Providers<br />

ATMS02 Probe Surveillance Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

ATMS02 Probe Surveillance Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

ATMS02 Probe Surveillance Sacramento County Website <strong>Plan</strong>ned<br />

ATMS02 Probe Surveillance Sacramento International Airport <strong>Plan</strong>ned<br />

Roadside Equipment<br />

ATMS02 Probe Surveillance Sacramento International Airport TMC <strong>Plan</strong>ned<br />

ATMS02 Probe Surveillance Vehicles <strong>Plan</strong>ned<br />

ATMS03 Surface Street Control Caltrans Roadside Equipment Existing<br />

ATMS03 Surface Street Control Citrus Heights Roadside Equipment Existing<br />

ATMS03 Surface Street Control Citrus Heights Traffic Operations Center Existing<br />

ATMS03 Surface Street Control City of Davis Field Equipment Existing<br />

ATMS03 Surface Street Control City of Davis TOC Existing<br />

ATMS03 Surface Street Control City of Elk Grove Field Equipment Existing<br />

ATMS03 Surface Street Control City of Elk Grove TOC Existing<br />

ATMS03 Surface Street Control City of Folsom Field Equipment Existing<br />

ATMS03 Surface Street Control City of Folsom TOC Existing<br />

ATMS03 Surface Street Control City of Rancho Cordova Field<br />

Existing<br />

Equipment<br />

ATMS03 Surface Street Control City of Rancho Cordova TOC Existing<br />

ATMS03 Surface Street Control City of Roseville Roadside Equipment Existing<br />

ATMS03 Surface Street Control City of Roseville TOC Existing<br />

ATMS03 Surface Street Control City of Sacramento TOC Existing<br />

ATMS03 Surface Street Control City of West Sacramento Roadside Existing<br />

Equipment<br />

ATMS03 Surface Street Control City of West Sacramento TOC Existing<br />

ATMS03 Surface Street Control City of Woodland Field Equipment Existing<br />

ATMS03 Surface Street Control City of Woodland TOC Existing<br />

ATMS03 Surface Street Control Municipal Field Equipment Existing<br />

ATMS03 Surface Street Control Municipal TOCs Existing<br />

ATMS03 Surface Street Control Sacramento City Roadside Equipment Existing<br />

ATMS03 Surface Street Control Sacramento County Roadside<br />

Equipment<br />

ATMS03 Surface Street Control Sacramento County Traffic Operations<br />

Center<br />

Existing<br />

Existing


Market Market Package Name Element Name Status<br />

Package<br />

ATMS03 Surface Street Control Sacramento International Airport Existing<br />

Roadside Equipment<br />

ATMS03 Surface Street Control Sacramento International Airport TMC Existing<br />

ATMS03 Surface Street Control Yuba City Field Equipment Existing<br />

ATMS03 Surface Street Control Yuba City TOC Existing<br />

ATMS04 Freeway Control Caltrans Roadside Equipment Existing<br />

ATMS04 Freeway Control RTMC-D3 - Traffic Operations Existing<br />

ATMS06 Traffic Information Dissemination Caltrans D3 Data Server Existing<br />

ATMS06 Traffic Information Dissemination Caltrans D3 Website Existing<br />

ATMS06 Traffic Information Dissemination Caltrans Roadside Equipment Existing<br />

ATMS06 Traffic Information Dissemination Citrus Heights Roadside Equipment Existing<br />

ATMS06<br />

Traffic Information Dissemination Citrus Heights Traffic Operations Center Existing<br />

ATMS06 Traffic Information Dissemination City of Citrus Heights Website Existing<br />

ATMS06 Traffic Information Dissemination City of Davis Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination City of Davis TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Elk Grove Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination City of Elk Grove TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Folsom Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination City of Folsom TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Rancho Cordova Field<br />

Existing<br />

Equipment<br />

ATMS06 Traffic Information Dissemination City of Rancho Cordova TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Roseville Roadside Equipment Existing<br />

ATMS06 Traffic Information Dissemination City of Roseville TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Roseville Website Existing<br />

ATMS06 Traffic Information Dissemination City of Sacramento TOC Existing<br />

ATMS06 Traffic Information Dissemination City of Sacramento Website Existing


Market Market Package Name Element Name Status<br />

Package<br />

ATMS06 Traffic Information Dissemination City of Woodland Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination City of Woodland TOC Existing<br />

ATMS06 Traffic Information Dissemination Local Print and Broadcast Media Existing<br />

ATMS06 Traffic Information Dissemination Municipal Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination Municipal TOCs Existing<br />

ATMS06 Traffic Information Dissemination Paratransit, Inc. Existing<br />

ATMS06 Traffic Information Dissemination RTMC-D3 - Traffic Operations Existing<br />

ATMS06 Traffic Information Dissemination Sacramento City Roadside Equipment Existing<br />

ATMS06 Traffic Information Dissemination Sacramento County Roadside Existing<br />

Equipment<br />

ATMS06 Traffic Information Dissemination Sacramento County Traffic Operations Existing<br />

Center<br />

ATMS06 Traffic Information Dissemination Sacramento County Website Existing<br />

ATMS06 Traffic Information Dissemination Sacramento Region 511 Website Existing<br />

ATMS06 Traffic Information Dissemination STARNET ISP Existing<br />

ATMS06 Traffic Information Dissemination Yuba City Field Equipment Existing<br />

ATMS06 Traffic Information Dissemination Yuba City TOC Existing<br />

ATMS07 Regional Traffic Control Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of Elk Grove TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of Folsom TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of Roseville TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of Sacramento TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control City of West Sacramento TOC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control Municipal TOCs <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control Other Caltrans District TMCs <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control RTMC-CHP <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control Sacramento County Traffic Operations<br />

Center<br />

<strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

ATMS07 Regional Traffic Control Sacramento International Airport TMC <strong>Plan</strong>ned<br />

ATMS07 Regional Traffic Control STARNET Server <strong>Plan</strong>ned<br />

ATMS08 Traffic Incident Management Airport Dispatch Center<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management Caltrans D3 Maintenance Dispatch Existing<br />

System<br />

ATMS08 Traffic Incident Management Caltrans Roadside Equipment Existing<br />

System<br />

ATMS08 Traffic Incident Management CHP Vehicles<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management Citrus Heights Maintenance Dispatch Existing<br />

System<br />

ATMS08 Traffic Incident Management Citrus Heights Traffic Operations Center Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Davis Maintenance Dispatch Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Davis TOC<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Elk Grove Maintenance Dispatch Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Elk Grove TOC<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Folsom Maintenance Dispatch Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Folsom TOC<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management City of Rancho Cordova Maintenance Existing<br />

System<br />

Dispatch<br />

ATMS08 Traffic Incident Management City of Rancho Cordova TOC<br />

Existing<br />

System<br />

ATMS08 Traffic Incident Management<br />

System<br />

City of Roseville Maintenance Dispatch Existing<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

City of Roseville Police and Fire<br />

Dispatch<br />

City of Roseville TOC<br />

City of Sacramento Maintenance<br />

Dispatch<br />

City of Sacramento TOC<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento TOC<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing


Market<br />

Package<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

Market Package Name Element Name Status<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

City of Woodland Maintenance Dispatch Existing<br />

City of Woodland TOC<br />

County Maintenance Dispatch<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Vehicles<br />

Local Law Enforcement Vehicles<br />

Local Police Dispatch<br />

Local Print and Broadcast Media<br />

Municipal Maintenance Dispatch<br />

Municipal TOCs<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Other Law Enforcement Dispatch CenterExisting<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Vehicles<br />

Existing<br />

Existing<br />

Regional Emergency Operations Center Existing<br />

Regional Event Promoters<br />

Regional Railroad Operations<br />

RTMC-CHP<br />

RTMC-D3 - Traffic Operations<br />

Sacramento City Fire Vehicles<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Vehicles<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Roadside<br />

Equipment<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing


Market<br />

Package<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS08<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

Market Package Name Element Name Status<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Traffic Incident Management<br />

System<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Traffic Operations<br />

Center<br />

Sacramento International Airport<br />

Maintenance Dispatch<br />

Sacramento International Airport TMC<br />

Sacramento Region 511 Website<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

STARNET ISP<br />

Yuba City Maintenance Dispatch<br />

Yuba City TOC<br />

Air Quality Website<br />

Caltrans Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville TOC<br />

County AQMD<br />

Local Print and Broadcast Media<br />

Municipal TOCs<br />

Private Traveler Information Service<br />

Providers<br />

RTMC-D3 - Traffic Operations<br />

Sacramento County Roadside<br />

Equipment<br />

Sacramento County Traffic Operations<br />

Center<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS11<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS13<br />

ATMS14<br />

ATMS14<br />

ATMS14<br />

Market Package Name Element Name Status<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Emissions Monitoring and<br />

Management<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Standard Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Sacramento International Airport<br />

Roadside Equipment<br />

Sacramento International Airport TMC<br />

Sacramento Metro AQMD<br />

Sacramento Region 511 Website<br />

STARNET ISP<br />

Caltrans Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville TOC<br />

City of Sacramento TOC<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento TOC<br />

Heavy Rail Wayside Equipment<br />

Municipal TOCs<br />

RT Wayside Equipment<br />

RTMC-D3 - Traffic Operations<br />

Sacramento City Roadside Equipment<br />

Sacramento County Roadside<br />

Equipment<br />

Sacramento County Traffic Operations<br />

Center<br />

Sacramento International Airport<br />

Roadside Equipment<br />

Sacramento International Airport TMC<br />

City of Sacramento TOC<br />

Heavy Rail Wayside Equipment<br />

Regional Railroad Operations<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

ATMS14<br />

ATMS14<br />

ATMS14<br />

ATMS14<br />

ATMS15<br />

Market Package Name Element Name Status<br />

Advanced Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

Advanced Railroad Grade<br />

Crossing<br />

RT Wayside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento County Roadside<br />

Equipment<br />

Sacramento County Traffic Operations<br />

Center<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

Railroad Operations Coordination Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination City of Roseville TOC <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination City of Sacramento TOC <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination City of West Sacramento TOC <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination Municipal TOCs <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination Regional Railroad Operations <strong>Plan</strong>ned<br />

ATMS15 Railroad Operations Coordination Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

ATMS16 Parking Facility Management Financial Institutions <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management Light Rail Station Parking Mgmt. <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management RT Police Services <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management RT Transit Management Center <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management Sacramento International Airport TMC <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management STARNET Server <strong>Plan</strong>ned<br />

ATMS16 Parking Facility Management Vehicles <strong>Plan</strong>ned<br />

CVO10 HAZMAT Management Commercial Vehicle Fleet Dispatch <strong>Plan</strong>ned<br />

Systems<br />

CVO10 HAZMAT Management Commercial Vehicles <strong>Plan</strong>ned<br />

CVO10 HAZMAT Management RTMC-CHP <strong>Plan</strong>ned<br />

CVO10 HAZMAT Management Sacramento County Sheriff Dept. <strong>Plan</strong>ned<br />

Communications<br />

CVO10 HAZMAT Management Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

<strong>Plan</strong>ned<br />

CVO10 HAZMAT Management Sacramento Regional Fire/ EMS Comm. <strong>Plan</strong>ned<br />

Center<br />

CVO10 HAZMAT Management Vehicles <strong>Plan</strong>ned<br />

EM01 Emergency Call-Taking and<br />

Dispatch<br />

Airport Dispatch Center<br />

Existing


Market<br />

Package<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

EM01<br />

Market Package Name Element Name Status<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

California Office of Emergency Services<br />

Operations Centers<br />

CHP Vehicles<br />

City of Roseville Police and Fire<br />

Dispatch<br />

County EOC<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

County Sheriff Communications Centers Existing<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Vehicles<br />

Local Law Enforcement Vehicles<br />

Local Police Dispatch<br />

Municipal EOC<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Other Law Enforcement Dispatch Center Existing<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Vehicles<br />

Existing<br />

Existing<br />

Regional Emergency Communications Existing<br />

Network<br />

Regional Emergency Operations Center Existing<br />

RT Police Services<br />

RTMC-CHP<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Vehicles<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing<br />

Existing


Market<br />

Package<br />

EM01<br />

EM01<br />

Market Package Name Element Name Status<br />

Emergency Call-Taking and<br />

Dispatch<br />

Emergency Call-Taking and<br />

Dispatch<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

STARNET Server<br />

Existing<br />

Existing<br />

EM02 Emergency Routing Citrus Heights Roadside Equipment <strong>Plan</strong>ned<br />

EM02 Emergency Routing Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of Elk Grove Field Equipment <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of Elk Grove TOC <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of Roseville Roadside Equipment <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of Roseville TOC <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of Sacramento TOC <strong>Plan</strong>ned<br />

EM02 Emergency Routing City of West Sacramento Roadside <strong>Plan</strong>ned<br />

Equipment<br />

EM02 Emergency Routing City of West Sacramento TOC <strong>Plan</strong>ned<br />

EM02 Emergency Routing Local Fire/EMS Dispatch Centers <strong>Plan</strong>ned<br />

EM02 Emergency Routing Local Fire/EMS Vehicles <strong>Plan</strong>ned<br />

EM02 Emergency Routing Local Law Enforcement Vehicles <strong>Plan</strong>ned<br />

EM02 Emergency Routing Local Police Dispatch <strong>Plan</strong>ned<br />

EM02 Emergency Routing Private/Public Ambulance Dispatch <strong>Plan</strong>ned<br />

EM02 Emergency Routing Private/Public Ambulance Vehicles <strong>Plan</strong>ned<br />

EM02 Emergency Routing Regional Medical Centers <strong>Plan</strong>ned<br />

EM02 Emergency Routing Sacramento City Fire Vehicles <strong>Plan</strong>ned<br />

EM02 Emergency Routing Sacramento City Roadside Equipment <strong>Plan</strong>ned<br />

EM02 Emergency Routing Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

EM02 Emergency Routing Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

EM02 Emergency Routing Sacramento Regional Fire/ EMS Comm. <strong>Plan</strong>ned<br />

Center<br />

EM04 Roadway Service Patrols Freeway Service Patrol Vehicles Existing<br />

EM04 Roadway Service Patrols RTMC-CHP Existing<br />

EM04 Roadway Service Patrols RTMC-D3 - Traffic Operations Existing<br />

EM04 Roadway Service Patrols STARNET ISP Existing<br />

EM05 Transportation Infrastructure RT Police Services<br />

<strong>Plan</strong>ned<br />

Protection<br />

EM05 Transportation Infrastructure RT Security Monitoring Equipment <strong>Plan</strong>ned<br />

Protection<br />

EM05 Transportation Infrastructure RT Transit Management Center <strong>Plan</strong>ned<br />

Protection<br />

EM06 Wide-Area Alert California Office of Emergency Services <strong>Plan</strong>ned<br />

Operations Centers<br />

EM06 Wide-Area Alert Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

EM06 Wide-Area Alert CHP Website <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Davis TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Elk Grove TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Folsom TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Roseville TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Sacramento TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of West Sacramento TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert City of Woodland TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert County EOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Local Fire/EMS Dispatch Centers <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Local Police Dispatch <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Municipal EOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Other County TOC <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert RTMC-CHP <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Sacramento City Police Department <strong>Plan</strong>ned<br />

Communications<br />

EM06 Wide-Area Alert Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

<strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

EM06 Wide-Area Alert Sacramento Region 511 Website <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert STARNET ISP <strong>Plan</strong>ned<br />

EM06 Wide-Area Alert Yuba City TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System California Office of Emergency Services <strong>Plan</strong>ned<br />

Operations Centers<br />

EM07 Early Warning System Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Davis TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Elk Grove TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Folsom TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Roseville TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Sacramento TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of West Sacramento TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System City of Woodland TOC <strong>Plan</strong>ned<br />

EM07 Early Warning System County EOC <strong>Plan</strong>ned<br />

EM07 Early Warning System County Sheriff Communications Centers <strong>Plan</strong>ned<br />

EM07 Early Warning System Municipal TOCs <strong>Plan</strong>ned<br />

EM07 Early Warning System RTMC-CHP <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

EM07 Early Warning System RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

EM07 Early Warning System Sacramento County Sheriff Dept. <strong>Plan</strong>ned<br />

Communications<br />

EM07 Early Warning System Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

<strong>Plan</strong>ned<br />

EM07 Early Warning System Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

EM07 Early Warning System Weather Information Providers <strong>Plan</strong>ned<br />

EM07 Early Warning System Yuba City TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery California Office of Emergency Services <strong>Plan</strong>ned<br />

Operations Centers<br />

EM08 Disaster Response and Recovery Citrus Heights Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08<br />

Disaster Response and Recovery Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Davis Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Davis TOC <strong>Plan</strong>ned<br />

EM08<br />

Disaster Response and Recovery City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Elk Grove TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Folsom Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Folsom TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Rancho Cordova Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

EM08 Disaster Response and Recovery City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

EM08<br />

Disaster Response and Recovery City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Roseville Police and Fire <strong>Plan</strong>ned<br />

Dispatch<br />

EM08 Disaster Response and Recovery City of Roseville TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

EM08 Disaster Response and Recovery City of Sacramento TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of West Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

EM08 Disaster Response and Recovery City of West Sacramento TOC <strong>Plan</strong>ned


Market<br />

Package<br />

EM08<br />

Market Package Name Element Name Status<br />

Disaster Response and Recovery City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery City of Woodland TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery County EOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery County Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08<br />

Disaster Response and Recovery County Sheriff Communications Centers <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery El Dorado Transit Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery e-tran Transit Center <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Folsom Stage Lines Transit Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Light Rail Transit Management Center <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Local Fire/EMS Dispatch Centers <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Local Police Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Local Transit Dispatch Centers <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Municipal EOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Municipal Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Municipal TOCs <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Other County TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Paratransit, Inc. <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Private/Public Ambulance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Roseville Transit Management Center <strong>Plan</strong>ned<br />

(Dispatch)<br />

EM08 Disaster Response and Recovery RT Transit Management Center <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery RTMC-CHP <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

EM08<br />

Disaster Response and Recovery Sacramento City Police Department<br />

Communications<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

EM08<br />

EM08<br />

EM08<br />

Market Package Name Element Name Status<br />

Disaster Response and Recovery Sacramento County Maintenance<br />

Service Center<br />

Disaster Response and Recovery Sacramento County Sheriff Dept.<br />

Communications<br />

Disaster Response and Recovery Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

EM08 Disaster Response and Recovery Sacramento Regional Fire/ EMS Comm. <strong>Plan</strong>ned<br />

Center<br />

EM08 Disaster Response and Recovery School Bus Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Unitrans Transit Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Yolo Bus Dispatch Center <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Yuba City Maintenance Dispatch <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Yuba City TOC <strong>Plan</strong>ned<br />

EM08 Disaster Response and Recovery Yuba-Sutter Transit Center <strong>Plan</strong>ned<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

California Office of Emergency Services<br />

Operations Centers<br />

Citrus Heights Maintenance Dispatch<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

City of Davis Maintenance Dispatch<br />

City of Davis TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Elk Grove TOC<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom TOC<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

Market Package Name Element Name Status<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Roseville Police and Fire<br />

Dispatch<br />

City of Roseville TOC<br />

City of Sacramento Maintenance<br />

Dispatch<br />

City of Sacramento TOC<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Woodland TOC<br />

County EOC<br />

County Maintenance Dispatch<br />

El Dorado Transit Dispatch<br />

e-tran Transit Center<br />

Folsom Stage Lines Transit Dispatch<br />

Local Fire/EMS Dispatch Centers<br />

Local Police Dispatch<br />

Local Transit Dispatch Centers<br />

Municipal EOC<br />

Municipal Maintenance Dispatch<br />

Municipal TOCs<br />

Other County TOC<br />

Paratransit, Inc.<br />

Private/Public Ambulance Dispatch<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

EM09<br />

Market Package Name Element Name Status<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Evacuation and Reentry<br />

Management<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

RT Transit Management Center<br />

RTMC-CHP<br />

RTMC-D3 - Traffic Operations<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Traffic Operations<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

School Bus Dispatch<br />

Unitrans Transit Dispatch<br />

Yolo Bus Dispatch Center<br />

Yuba City Maintenance Dispatch<br />

Yuba City TOC<br />

Yuba-Sutter Transit Center<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information County EOC <strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information Local Print and Broadcast Media <strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information Municipal EOC <strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information Sacramento Region 511 Website <strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information School Bus Dispatch <strong>Plan</strong>ned<br />

EM10 Disaster Traveler Information STARNET ISP <strong>Plan</strong>ned<br />

MC01 Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Caltrans D3 Maintenance Dispatch Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Caltrans D3 Maintenance Vehicles<br />

Existing


Market<br />

Package<br />

MC01<br />

Market Package Name Element Name Status<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Citrus Heights Maintenance Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Davis Maintenance Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Elk Grove Maintenance Dispatch Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Folsom Maintenance Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Roseville Maintenance Dispatch Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Sacramento Maintenance<br />

Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Sacramento Maintenance<br />

Vehicles<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

City of Woodland Maintenance Dispatch Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

County Maintenance Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

County Maintenance Vehicles<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Municipal Maintenance Dispatch<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Municipal Maintenance Vehicles<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Sacramento County Maintenance<br />

Service Center<br />

Existing


Market<br />

Package<br />

MC01<br />

Market Package Name Element Name Status<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Sacramento County Maintenance<br />

Vehicles<br />

Existing<br />

MC01<br />

Maintenance and Construction<br />

Vehicle and Equipment Tracking<br />

Yuba City Maintenance Dispatch<br />

Existing<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

MC02<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans District Shop<br />

Citrus Heights Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Folsom Maintenance Dispatch<br />

<strong>Plan</strong>ned<br />

City of Rancho Cordova Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Sacramento Equipment Shop<br />

<strong>Plan</strong>ned<br />

City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Vehicles<br />

City of West Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

Municipal Equipment Repair Facility<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Vehicles<br />

Sacramento County Equipment Repair<br />

Facility<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Maintenance<br />

Vehicles<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

MC02<br />

Market Package Name Element Name Status<br />

Maintenance and Construction<br />

Vehicle Maintenance<br />

Yuba City Maintenance Dispatch<br />

<strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection Caltrans Roadside Equipment <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection City of Roseville Roadside Equipment <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection City of Roseville TOC <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

MC03 Road Weather Data Collection Sacramento County Maintenance <strong>Plan</strong>ned<br />

Service Center<br />

MC03 Road Weather Data Collection Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

MC03 Road Weather Data Collection Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

MC03 Road Weather Data Collection Weather Information Providers <strong>Plan</strong>ned<br />

MC04 Weather Information Processing Caltrans D3 Data Server<br />

<strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing City of Roseville Police and Fire <strong>Plan</strong>ned<br />

and Distribution<br />

Dispatch<br />

MC04 Weather Information Processing City of Roseville TOC<br />

<strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing City of Sacramento TOC<br />

<strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing Local Print and Broadcast Media <strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing RT Transit Management Center <strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing RTMC-CHP<br />

<strong>Plan</strong>ned<br />

and Distribution<br />

MC04 Weather Information Processing<br />

and Distribution<br />

RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

MC04<br />

MC04<br />

MC04<br />

MC04<br />

Weather Information Processing<br />

and Distribution<br />

Weather Information Processing<br />

and Distribution<br />

Weather Information Processing<br />

and Distribution<br />

Weather Information Processing<br />

and Distribution<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Traffic Operations<br />

Center<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

MC04<br />

MC04<br />

MC04<br />

Market Package Name Element Name Status<br />

Weather Information Processing<br />

and Distribution<br />

Weather Information Processing<br />

and Distribution<br />

Weather Information Processing<br />

and Distribution<br />

Sacramento International Airport TMC<br />

STARNET Server<br />

Weather Information Providers<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

MC05 Roadway Automated Treatment Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

MC05 Roadway Automated Treatment Caltrans Roadside Equipment <strong>Plan</strong>ned<br />

MC06 Winter Maintenance Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

MC06 Winter Maintenance Caltrans D3 Maintenance Vehicles <strong>Plan</strong>ned<br />

MC06 Winter Maintenance Caltrans D3 Storage Facility <strong>Plan</strong>ned<br />

MC06 Winter Maintenance RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

MC06 Winter Maintenance Sacramento County Maintenance <strong>Plan</strong>ned<br />

Service Center<br />

MC06 Winter Maintenance Weather Information Providers <strong>Plan</strong>ned<br />

MC07 Roadway Maintenance and Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

Construction<br />

MC07 Roadway Maintenance and<br />

Construction<br />

Caltrans D3 Maintenance Vehicles <strong>Plan</strong>ned<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Caltrans D3 Pavement Management<br />

System<br />

Citrus Heights Maintenance Dispatch<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

City of Davis Maintenance Dispatch<br />

City of Davis TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Elk Grove TOC<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom TOC<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Roseville Maintenance Dispatch <strong>Plan</strong>ned


Market<br />

Package<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

MC07<br />

Market Package Name Element Name Status<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

Roadway Maintenance and<br />

Construction<br />

City of Roseville TOC<br />

City of Sacramento Maintenance<br />

Dispatch<br />

City of Sacramento Maintenance<br />

Vehicles<br />

City of Sacramento TOC<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Woodland TOC<br />

County Maintenance Dispatch<br />

County Maintenance Vehicles<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Vehicles<br />

Municipal TOCs<br />

Other County TOC<br />

RTMC-D3 - Traffic Operations<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Maintenance<br />

Vehicles<br />

Sacramento County Traffic Operations<br />

Center<br />

Weather Information Providers<br />

Yuba City Maintenance Dispatch<br />

Yuba City TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

MC08 Work Zone Management Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management Caltrans D3 Maintenance Vehicles <strong>Plan</strong>ned<br />

MC08 Work Zone Management Caltrans Roadside Equipment <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

MC08 Work Zone Management Citrus Heights Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management Citrus Heights Roadside Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Davis Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Davis Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Davis TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Elk Grove Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Elk Grove TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Folsom Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Folsom Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Folsom TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Rancho Cordova Field<br />

<strong>Plan</strong>ned<br />

Equipment<br />

MC08 Work Zone Management City of Rancho Cordova Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

MC08 Work Zone Management City of Rancho Cordova TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Roseville Roadside Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Roseville TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

MC08 Work Zone Management City of Sacramento Maintenance <strong>Plan</strong>ned<br />

Vehicles<br />

MC08 Work Zone Management City of Sacramento TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of West Sacramento Maintenance <strong>Plan</strong>ned<br />

Dispatch<br />

MC08 Work Zone Management City of West Sacramento Roadside <strong>Plan</strong>ned<br />

Equipment<br />

MC08 Work Zone Management City of West Sacramento TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Woodland Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management City of Woodland TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management County Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management County Maintenance Vehicles <strong>Plan</strong>ned<br />

MC08 Work Zone Management County Roadside Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management Municipal Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management Municipal Maintenance Dispatch <strong>Plan</strong>ned


Market Market Package Name Element Name Status<br />

Package<br />

MC08 Work Zone Management Municipal Maintenance Vehicles <strong>Plan</strong>ned<br />

MC08 Work Zone Management Municipal TOCs <strong>Plan</strong>ned<br />

MC08 Work Zone Management Other County TOC <strong>Plan</strong>ned<br />

MC08 Work Zone Management RTMC-D3 - Traffic Operations <strong>Plan</strong>ned<br />

MC08 Work Zone Management Sacramento City Roadside Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management Sacramento County Maintenance <strong>Plan</strong>ned<br />

Service Center<br />

MC08 Work Zone Management Sacramento County Maintenance <strong>Plan</strong>ned<br />

Vehicles<br />

MC08 Work Zone Management Sacramento County Roadside <strong>Plan</strong>ned<br />

Equipment<br />

MC08 Work Zone Management Sacramento County Traffic Operations <strong>Plan</strong>ned<br />

Center<br />

MC08 Work Zone Management Sacramento International Airport <strong>Plan</strong>ned<br />

Maintenance Dispatch<br />

MC08 Work Zone Management Yuba City Field Equipment <strong>Plan</strong>ned<br />

MC08 Work Zone Management Yuba City Maintenance Dispatch <strong>Plan</strong>ned<br />

MC08 Work Zone Management Yuba City TOC <strong>Plan</strong>ned<br />

MC09 Work Zone Safety Monitoring Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

MC09 Work Zone Safety Monitoring Caltrans D3 Maintenance Vehicles <strong>Plan</strong>ned<br />

MC09 Work Zone Safety Monitoring Caltrans Roadside Equipment <strong>Plan</strong>ned<br />

MC10 Maintenance and Construction Caltrans D3 Maintenance Dispatch <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction Citrus Heights Maintenance Dispatch <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction Citrus Heights Traffic Operations Center <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction City of Davis Maintenance Dispatch <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction City of Davis TOC<br />

<strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction City of Elk Grove Maintenance Dispatch <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction City of Elk Grove TOC<br />

<strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction City of Folsom Maintenance Dispatch <strong>Plan</strong>ned<br />

Activity Coordination<br />

MC10 Maintenance and Construction<br />

Activity Coordination<br />

City of Folsom TOC<br />

<strong>Plan</strong>ned<br />

MC10<br />

MC10<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

Market Package Name Element Name Status<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

City of Roseville Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Roseville Police and Fire<br />

Dispatch<br />

City of Roseville TOC<br />

City of Sacramento Maintenance<br />

Dispatch<br />

City of Sacramento TOC<br />

City of Sacramento Website<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento TOC<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

City of Woodland Maintenance Dispatch <strong>Plan</strong>ned<br />

City of Woodland TOC<br />

County Maintenance Dispatch<br />

El Dorado Transit Dispatch<br />

e-tran Transit Center<br />

Folsom Stage Lines Transit Dispatch<br />

Local Fire/EMS Dispatch Centers<br />

Local Police Dispatch<br />

Local Print and Broadcast Media<br />

Other Caltrans District Maintenance<br />

Paratransit, Inc.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

RT Transit Management Center<br />

RTMC-CHP<br />

RTMC-D3 - Traffic Operations<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Market<br />

Package<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

MC10<br />

Market Package Name Element Name Status<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Maintenance and Construction<br />

Activity Coordination<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento County Maintenance<br />

Service Center<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Traffic Operations<br />

Center<br />

Sacramento County Website<br />

Sacramento Region 511 Website<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

STARNET ISP<br />

Unitrans Transit Dispatch<br />

Yolo Bus Dispatch Center<br />

Yuba City Maintenance Dispatch<br />

Yuba City TOC<br />

Yuba-Sutter Transit Center<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned<br />

<strong>Plan</strong>ned


Appendix H


ased on<br />

National ITS Architecture Version 5.0


ATMS01 - Network Surveillance<br />

Caltrans District 3<br />

Information Service<br />

Provider<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

traffic flow<br />

traffic images<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

Information Service<br />

Provider<br />

Caltrans D3 Data<br />

Server<br />

+<br />

Caltrans<br />

Performance<br />

Monitoring<br />

System (PeMS)<br />

+<br />

Sacramento<br />

Region 511<br />

Website<br />

road network<br />

conditions<br />

traffic sensor control<br />

video surveillance<br />

control<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

Sacramento County Traffic Operations Center<br />

Roadway Subsystem<br />

Information Service Provider<br />

Private Traveler<br />

Information Service<br />

Providers<br />

+<br />

Sacramento County<br />

Website<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

traffic flow<br />

+<br />

traffic images<br />

video surveillance<br />

control<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

traffic flow<br />

+<br />

traffic images<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

+<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Have a weigh in motion data collection station<br />

Maintain and operate Caltrans signals on ramps


ATMS01 - Network Surveillance<br />

City of Sacramento TOC<br />

Roadway Subsystem<br />

Information Service<br />

Provider<br />

Caltrans D3<br />

Website<br />

+<br />

City of<br />

Sacramento<br />

Website<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of<br />

Sacramento<br />

TOC<br />

traffic flow<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

traffic flow<br />

+<br />

traffic images<br />

Caltrans<br />

Roadside<br />

Equipment<br />

Roadway Subsystem<br />

Sacramento<br />

City Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Operate Caltrans signals.


ATMS01 - Network Surveillance<br />

Citris Heights Traffic Operations Center<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

LEGEND<br />

planned and future flow<br />

Citrus Heights primarily monitors the field devices.<br />

Sacramento County has control under normal<br />

circumstances, although Citrus Heights could have<br />

the capability to control in the future.<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

Roseville TOC<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of West Sacramento TOC<br />

Information Service<br />

Provider<br />

City of West<br />

Sacramento<br />

Website<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of West<br />

Sacramento<br />

TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of West<br />

Sacramento<br />

Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

Sacramento International Airport TMC<br />

Information Service<br />

Provider<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

Sacramento<br />

International<br />

Airport Website<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

Sacramento<br />

International<br />

Airport TMC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

Sacramento<br />

International<br />

Airport<br />

Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

Municipal TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

Municipal TOCs<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

Municipal Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of Davis TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of Davis<br />

TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of Davis<br />

Field Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of Elk Grove TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of Elk<br />

Grove TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of Elk<br />

Grove Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of Folsom TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of Folsom<br />

Field Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of Rancho Cordova TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

City of Woodland TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of<br />

Woodland TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

City of<br />

Woodland Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS01 - Network Surveillance<br />

Yuba City TOC<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Private Traveler<br />

Information<br />

Service Providers<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

Yuba City TOC<br />

traffic flow<br />

+<br />

traffic images<br />

traffic sensor control<br />

+<br />

video surveillance<br />

control<br />

Roadway Subsystem<br />

Yuba City Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS02 - Probe Surveillance<br />

Sacramento County<br />

Traffic Management<br />

vehicle probe data<br />

Roadway Subsystem<br />

request tag data<br />

Vehicle<br />

Municipal TOCs<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

Sacramento County<br />

Roadside<br />

Equipment<br />

vehicle probe data<br />

Vehicles<br />

travel time_ud<br />

Would the City of Sacramento pass traffic time<br />

information to their website or a private website?<br />

Information Service<br />

Provider<br />

Private Traveler<br />

Information Service<br />

Providers<br />

+<br />

Sacramento County<br />

Website<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS02 - Probe Surveillance<br />

Sacramento International Airport<br />

Traffic Management<br />

vehicle probe data<br />

Roadway Subsystem<br />

request tag data<br />

Vehicle<br />

Sacramento<br />

International<br />

Airport TMC<br />

Sacramento<br />

International<br />

Airport Roadside<br />

Equipment<br />

Vehicles<br />

vehicle probe data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Sacramento County TOC (1 of 2)<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

signal control data<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

Roadway Subsystem<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

traffic flow<br />

+<br />

traffic images<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Sacramento County TOC (2 of 2)<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

+<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

traffic flow<br />

+<br />

traffic images<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Sacramento TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

City of<br />

Sacramento<br />

TOC<br />

signal control data<br />

+<br />

video surveillance control<br />

request for right-of-way<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Sacramento<br />

City Roadside<br />

Equipment<br />

field equipment status<br />

signal control status<br />

+<br />

traffic flow<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Citrus Heights TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

signal control data<br />

+<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

LEGEND<br />

planned and future flow<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

signal control data<br />

+<br />

traffic sensor<br />

control<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Roseville TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Municipal TOCs<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

field equipment status<br />

equipment<br />

maintenance status<br />

Traffic Management<br />

Municipal TOCs<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Municipal Field<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Davis TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

City of Davis<br />

TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Davis<br />

Field Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Elk Grove TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Elk<br />

Grove<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

field equipment status<br />

Traffic Management<br />

City of Elk<br />

Grove TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of Elk<br />

Grove Field<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Folsom TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Folsom<br />

Field Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Rancho Cordova TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

field equipment status<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of Woodland TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Woodland<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

field equipment status<br />

Traffic Management<br />

City of<br />

Woodland TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of<br />

Woodland Field<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

City of West Sacramento TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

field equipment status<br />

Traffic Management<br />

City of West<br />

Sacramento<br />

TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of West<br />

Sacramento<br />

Roadside<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Yuba City TOC<br />

Maintenance and<br />

Construction<br />

Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

Yuba City TOC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

traffic flow<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Yuba City Field<br />

Equipment<br />

field equipment status<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS03 - Surface Street Control<br />

Sacramento International Airport TMC<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

International<br />

Airport<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

field equipment status<br />

Traffic Management<br />

Sacramento<br />

International<br />

Airport TMC<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

hov data<br />

+<br />

traffic flow<br />

+<br />

traffic images<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Sacramento<br />

International<br />

Airport<br />

Roadside<br />

Equipment<br />

signal control data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS04 - Freeway Control<br />

Caltrans District 3<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

equipment maintenance<br />

status<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

freeway control data<br />

+<br />

traffic sensor control<br />

+<br />

video surveillance control<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

field equipment status<br />

freeway control status<br />

+<br />

traffic flow<br />

+<br />

traffic images<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Caltrans District 3<br />

Information Service<br />

Provider<br />

STARNET ISP<br />

Information Service Provider<br />

Caltrans D3 Data<br />

Server<br />

+<br />

Caltrans D3 Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

Transit Management<br />

road network<br />

conditions<br />

road network<br />

conditions<br />

road network<br />

conditions<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

road network<br />

conditions_ud<br />

road network<br />

conditions_ud<br />

roadway<br />

information system<br />

status<br />

roadway<br />

information system<br />

data<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

e-tran Transit Center<br />

+<br />

RT Transit<br />

Management Center<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

The providing of road network conditions<br />

to transit will be done through STARNET<br />

in the future. This represents the plan<br />

for transit to get the information.<br />

STARNET will be the physical<br />

connectivity for that to happen<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Sacramento County TOC<br />

Information Service Provider<br />

Sacramento County<br />

Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

roadway<br />

information system<br />

status<br />

Roadway Subsystem<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

Transit Management<br />

e-tran Transit Center<br />

+<br />

Paratransit, Inc.<br />

+<br />

RT Transit<br />

Management Center<br />

road network<br />

conditions<br />

roadway<br />

information system<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

road network<br />

conditions<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Sacramento City TOC<br />

Information Service<br />

Provider<br />

City of Sacramento<br />

Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

road network<br />

conditions<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

roadway information<br />

system status<br />

roadway information<br />

system data<br />

Roadway Subsystem<br />

Sacramento City<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

Media<br />

LEGEND<br />

planned and future flow<br />

Local Print and<br />

Broadcast Media<br />

existing flow<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Citrus Heights TOC<br />

Information Service<br />

Provider<br />

City of Citrus<br />

Heights Website<br />

+<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

roadway information<br />

system data<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

road network<br />

conditions<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Roseville TOC<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

+<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

roadway information<br />

system status<br />

roadway information<br />

system data<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

Media<br />

LEGEND<br />

planned and future flow<br />

Local Print and<br />

Broadcast Media<br />

existing flow<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

Municipal TOCs<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

Municipal TOCs<br />

roadway information<br />

system status<br />

roadway information<br />

system data<br />

Roadway Subsystem<br />

Municipal Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS06 - Traffic Information Dissemination<br />

City of Davis TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Davis<br />

TOC<br />

roadway information<br />

system status<br />

roadway information<br />

system data<br />

Roadway Subsystem<br />

City of Davis Field<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

user defined flow


ATMS06 - Traffic Information Dissemination<br />

City of Elk Grove TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

roadway information<br />

system status<br />

roadway information<br />

system data<br />

Roadway Subsystem<br />

City of Elk Grove<br />

Field Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS06 - Traffic Information Dissemination<br />

City of Folsom TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

City of Folsom<br />

Field Equipment<br />

roadway information<br />

system data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS06 - Traffic Information Dissemination<br />

City of Rancho Cordova TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

roadway information<br />

system data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS06 - Traffic Information Dissemination<br />

City of Woodland TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

City of Woodland<br />

TOC<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

City of Woodland<br />

Field Equipment<br />

roadway information<br />

system data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS06 - Traffic Information Dissemination<br />

Yuba City TOC<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

road network conditions<br />

Traffic Management<br />

Yuba City TOC<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

Yuba City Field<br />

Equipment<br />

roadway information<br />

system data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions<br />

Media<br />

Local Print and<br />

Broadcast Media


ATMS07 - Regional Traffic Control<br />

Caltrans District 3<br />

Traffic Management<br />

Other Caltrans<br />

District TMCs<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

traffic control<br />

coordination<br />

traffic information<br />

coordination<br />

traffic control<br />

coordination<br />

traffic information<br />

coordination<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

traffic control<br />

coordination<br />

traffic information<br />

coordination<br />

traffic control<br />

coordination<br />

traffic information<br />

coordination<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

+<br />

City of Rancho<br />

Cordova TOC<br />

+<br />

City of<br />

Sacramento TOC<br />

CHP has dispatchers, media officers, and Public<br />

Infomration Officers in the RTMC. The CHP<br />

personnel have effective ability to perform control of<br />

Caltrans devices by sitting at a Caltans console.<br />

CHP and Caltrans have two different computer<br />

systems in the same building. At present they do<br />

not communicate, but they may in the future, which<br />

is what the connections on this diagram represent.<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS07 - Regional Traffic Control<br />

STARNET<br />

Traffic Management<br />

Traffic Management<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

STARNET Server<br />

traffic control coordination<br />

traffic information<br />

coordination<br />

traffic control coordination<br />

traffic information<br />

coordination<br />

Citrus Heights Traffic Operations<br />

Center<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

City of West Sacramento TOC<br />

+<br />

Municipal TOCs<br />

+<br />

RTMC-D3 - Traffic Operations<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

+<br />

Sacramento International Airport TMC<br />

user defined flow


ATMS07 - Regional Traffic Control<br />

Sacramento County<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

traffic control coordination<br />

traffic information coordination<br />

traffic control coordination<br />

traffic information coordination<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova<br />

TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

Municipal TOCs<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS07 - Regional Traffic Control<br />

City of Sacramento<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

traffic control coordination<br />

traffic information coordination<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

traffic control coordination<br />

traffic information coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS07 - Regional Traffic Control<br />

Municipalities<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

traffic control coordination<br />

traffic information coordination<br />

Traffic Management<br />

Municipal TOCs<br />

traffic control coordination<br />

traffic information coordination<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

traffic control coordination<br />

traffic information coordination<br />

traffic control coordination<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

+<br />

Municipal TOCs<br />

traffic information coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


Incident Management Overview<br />

ATMS08 Covered<br />

Emergency Management Traffic Management<br />

Emergency Management Maintenance and Construction<br />

Traffic Management Maintenance and Construction<br />

Maintenance and Construction Maintenance and Construction<br />

Event <strong>Plan</strong>s and Weather Traffic Management & Emergency<br />

Management (see MCs for M&C)<br />

ATMS06, 03, 04, etc. Covered<br />

Traffic Management Roadway<br />

ATMS07 Covered<br />

Traffic Management Traffic Management<br />

EM1 Covered<br />

Emergency Management Emergency Management<br />

EM2 Covered<br />

Emergency Vehicle Preemption


ATMS08 - Incident Management<br />

Traffic Management<br />

Emergency Management


ATMS08 - Incident Management<br />

Caltrans District 3 / Sacramento County TOC (TM to EM)<br />

Emergency<br />

Management<br />

RTMC-CHP<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

remote surveillance<br />

control<br />

+<br />

resource request<br />

incident information<br />

+<br />

resource deployment<br />

status<br />

+<br />

traffic images<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

resource request<br />

incident information<br />

+<br />

resource deployment<br />

status<br />

+<br />

traffic images<br />

Emergency Management<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento<br />

County Sheriff<br />

Dept.<br />

Communications<br />

LEGEND<br />

planned and future flow<br />

Emergency Management<br />

RTMC-CHP<br />

incident information<br />

+<br />

incident response status<br />

+<br />

remote surveillance control<br />

+<br />

resource request<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

existing flow<br />

user defined flow<br />

incident information<br />

+<br />

resource deployment status<br />

+<br />

road network conditions<br />

+<br />

traffic images


ATMS08 - Incident Management<br />

City of Sacramento TOC / Citrus Heights Traffic Operations Center (TM to EM)<br />

Emergency Management<br />

Sacramento City<br />

Police Department<br />

Communications<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

incident<br />

information<br />

+<br />

incident response<br />

status<br />

+<br />

remote surveillance<br />

control<br />

+<br />

resource incident request<br />

information<br />

+<br />

resource<br />

deployment status<br />

+<br />

traffic images<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

incident<br />

information<br />

+<br />

traffic images<br />

incident<br />

information<br />

+<br />

incident response<br />

status<br />

+<br />

resource request<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

incident information<br />

incident information<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

incident<br />

information<br />

incident<br />

information<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of West Sacramento TOC / Roseville TOC (TM to EM)<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

remote surveillance<br />

control<br />

+<br />

incident information<br />

resource request<br />

+<br />

resource deployment<br />

status<br />

+<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

incident<br />

information<br />

incident<br />

information<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

Emergency Management<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

resource request<br />

incident information<br />

+<br />

resource deployment<br />

status<br />

+<br />

traffic images<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

incident<br />

information<br />

incident<br />

information<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Sacramento International Airport TMC / Municipal TOCs (TM to EM)<br />

Emergency Management<br />

Airport Dispatch<br />

Center<br />

+<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

resource request<br />

incident information<br />

+<br />

resource deployment<br />

status<br />

+<br />

traffic images<br />

Traffic Management<br />

Sacramento<br />

International<br />

Airport TMC<br />

incident information<br />

incident information<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

Emergency Management<br />

incident information<br />

Traffic Management<br />

incident information<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

incident information<br />

Municipal TOCs<br />

incident information<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Municipality TOCs (TM to EM)<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

incident information<br />

+<br />

incident response<br />

status<br />

+<br />

resource request<br />

incident information<br />

+<br />

resource deployment<br />

status<br />

+<br />

traffic images<br />

Traffic Management<br />

City of Davis TOC<br />

+<br />

City of Elk Grove<br />

TOC<br />

+<br />

City of Folsom<br />

TOC<br />

+<br />

City of Rancho<br />

Cordova TOC<br />

+<br />

City of Woodland<br />

TOC<br />

+<br />

Yuba City TOC<br />

incident information<br />

incident information<br />

Emergency Management<br />

Other Law<br />

Enforcement<br />

Dispatch Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Traffic Management<br />

Maintenance and Construction Management


ATMS08 - Incident Management<br />

Caltrans District 3 (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Sacramento County TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

weather information<br />

Weather Service<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

maint and constr resource<br />

request<br />

maint and constr resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Sacramento TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Citrus Heights TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of West Sacramento TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Roseville TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Davis TOCs (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Davis<br />

TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

maint and constr<br />

resource response<br />

+<br />

roadway maintenance<br />

status<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Elk Grove TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Folsom TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Rancho Cordova TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Woodland TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

City of Woodland<br />

TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Woodland<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Yuba City TOC (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

Yuba City TOC<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Municipal TOCs (TM to MCM)<br />

Event Promoters<br />

Regional Event<br />

Promoters<br />

event plans<br />

Traffic Management<br />

Municipal TOCs<br />

incident information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

Weather Service<br />

weather information<br />

incident information<br />

+<br />

maint and constr<br />

resource response<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Emergency Management<br />

Maintenance and Construction Management


ATMS08 - Incident Management<br />

Sacramento County (EM to MCM)<br />

Emergency Management<br />

Regional Emergency<br />

Operations Center<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource<br />

request<br />

incident information<br />

+<br />

maint and constr resource<br />

response<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of Sacramento / Citrus Heights (EM to MCM)<br />

Emergency Management<br />

Regional<br />

Emergency<br />

Operations Center<br />

+<br />

Sacramento City<br />

Police Department<br />

Communications<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource request<br />

incident information<br />

+<br />

maint and constr resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Regional Emergency<br />

Operations Center<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource<br />

request<br />

incident information<br />

+<br />

maint and constr resource<br />

response<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

City of West Sacramento / Roseville (EM to MCM)<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Regional<br />

Emergency<br />

Operations Center<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource request<br />

incident information<br />

+<br />

maint and constr resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

Emergency Management<br />

Regional Emergency<br />

Operations Center<br />

+<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource<br />

request<br />

incident information<br />

+<br />

maint and constr resource<br />

response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Municipalities (EM to MCM)<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Regional<br />

Emergency<br />

Operations Center<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource request<br />

incident information<br />

+<br />

maint and constr resource response<br />

Maintenance and Construction Management<br />

City of Davis Maintenance<br />

Dispatch<br />

+<br />

City of Elk Grove Maintenance<br />

Dispatch<br />

+<br />

City of Folsom Maintenance<br />

Dispatch<br />

+<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

+<br />

City of Woodland Maintenance<br />

Dispatch<br />

+<br />

Yuba City Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Sacramento International Airport (EM to MCM)<br />

Emergency Management<br />

Airport Dispatch<br />

Center<br />

+<br />

Regional Emergency<br />

Operations Center<br />

incident information<br />

+<br />

incident response status<br />

+<br />

maint and constr resource<br />

request<br />

incident information<br />

+<br />

maint and constr resource<br />

response<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

International<br />

Airport<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Maintenance and Construction Management<br />

Construction Management<br />

Maintenance and


ATMS08 - Incident Management<br />

MCM to Other MCM<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

resource coordination<br />

maint and constr<br />

resource coordination<br />

Maintenance and Construction Management<br />

Citrus Heights Maintenance Dispatch<br />

+<br />

City of Davis Maintenance Dispatch<br />

+<br />

City of Elk Grove Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance Dispatch<br />

+<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

+<br />

City of Sacramento Maintenance Dispatch<br />

+<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

+<br />

City of Woodland Maintenance Dispatch<br />

+<br />

Yuba City Maintenance Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

+<br />

City of Roseville Maintenance Dispatch<br />

+<br />

Sacramento County Maintenance Service<br />

Center<br />

+<br />

Sacramento International Airport<br />

Maintenance Dispatch


ATMS08 - Incident Management<br />

MCM to Other MCM<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

maint and constr resource<br />

coordination<br />

maint and constr resource<br />

coordination<br />

Maintenance and Construction Management<br />

Citrus Heights Maintenance Dispatch<br />

+<br />

City of Elk Grove Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance Dispatch<br />

+<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

+<br />

City of Sacramento Maintenance Dispatch<br />

+<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

+<br />

City of Roseville Maintenance Dispatch<br />

+<br />

Sacramento International Airport<br />

Maintenance Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

MCM to Other MCM<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

maint and constr resource<br />

coordination<br />

maint and constr resource<br />

coordination<br />

Maintenance and Construction Management<br />

City of Davis Maintenance<br />

Dispatch<br />

+<br />

City of Woodland Maintenance<br />

Dispatch<br />

+<br />

Yuba City Maintenance Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Emergency Management<br />

Emergency Vehicles


ATMS08 - Incident Management<br />

(EM to EVS)<br />

Emergency Management<br />

RTMC-CHP<br />

emergency dispatch requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

CHP Vehicles<br />

Emergency Management<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

emergency dispatch requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento County<br />

Sheriff Vehicle<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Emergency Management<br />

Sacramento City<br />

Police Department<br />

Communications<br />

emergency dispatch<br />

requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento City<br />

Fire Vehicles<br />

+<br />

Sacramento City<br />

Police Vehicles


ATMS08 - Incident Management<br />

(EM to EVS)<br />

Emergency Management<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

emergency dispatch requests<br />

incident status<br />

Emergency Vehicle Subsystem<br />

Private/Public<br />

Ambulance Vehicles<br />

+<br />

Sacramento City Fire<br />

Vehicles<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

emergency dispatch<br />

requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

(EM to EVS)<br />

Emergency Management<br />

Local Police Dispatch<br />

emergency dispatch requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Local Law<br />

Enforcement<br />

Vehicles<br />

Emergency Management<br />

Private/Public<br />

Ambulance Dispatch<br />

emergency dispatch requests<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Private/Public<br />

Ambulance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Rail Operations Coordination<br />

Emergency Management<br />

Regional Emergency<br />

Operations Center<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

+<br />

Sacramento Regional Fire/<br />

EMS Comm. Center<br />

incident information<br />

+<br />

incident response status<br />

incident information<br />

+<br />

rail incident response status<br />

Rail Operations<br />

Regional Railroad<br />

Operations<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS08 - Incident Management<br />

Flood Monitoring- Caltrans<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

high water<br />

warning_ud<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

water level<br />

information_ud<br />

Roadway Subsystem<br />

Caltrans Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

high water<br />

warning_ud<br />

Media<br />

high water<br />

warning_ud<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

existing flow<br />

user defined flow<br />

Local Print and<br />

Broadcast Media


ATMS08 - Incident Management<br />

Flood Monitoring- Sacramento County<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

high water<br />

warning_ud<br />

Maintenance and<br />

Construction Management<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

water level<br />

information_ud<br />

Roadway Subsystem<br />

Sacramento County<br />

Roadside Equipment<br />

LEGEND<br />

planned and future flow<br />

high water<br />

warning_ud<br />

Media<br />

high water<br />

warning_ud<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

existing flow<br />

user defined flow<br />

Local Print and<br />

Broadcast Media


ATMS08 - Incident Management<br />

Caltans/ Sacramento County TOC (ISP to TM)<br />

Information Service<br />

Provider<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

+<br />

Sacramento<br />

International Airport<br />

TMC<br />

logged special<br />

vehicle route<br />

road network<br />

conditions<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

Information Service<br />

Provider<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento<br />

International Airport<br />

TMC<br />

logged special<br />

vehicle route<br />

road network<br />

conditions<br />

Traffic Management<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

These flows/ connections are in the current<br />

architecture- should they be there?


ATMS11 - Emissions Monitoring and Management<br />

Sacramento Metrp AQMD (Outputs)<br />

Information Service<br />

Provider<br />

Air Quality Website<br />

+<br />

Private Traveler<br />

Information Service<br />

Providers<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

air quality<br />

information<br />

Emissions Management<br />

Sacramento<br />

Metro AQMD<br />

air quality<br />

information_ud<br />

widearea statistical<br />

pollution information<br />

Other Emissions<br />

Management<br />

County AQMD<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

air quality<br />

information<br />

Media<br />

LEGEND<br />

planned and future flow<br />

Local Print and<br />

Broadcast Media<br />

existing flow<br />

user defined flow


ATMS11 - Emissions Monitoring and Management<br />

Sacramento Metrp AQMD (Inputs)<br />

Emissions Management<br />

City of Roseville<br />

TOC<br />

+<br />

Municipal TOCs<br />

+<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

+<br />

Sacramento<br />

International Airport<br />

TMC<br />

air quality<br />

information_ud<br />

Emissions Management<br />

Sacramento<br />

Metro AQMD<br />

air quality<br />

information_ud<br />

Other Emissions<br />

Management<br />

County AQMD<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS11 - Emissions Monitoring and Management<br />

Data Collection<br />

Roadway<br />

Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

emissions sensor<br />

control<br />

vehicle emissions<br />

data<br />

Emissions<br />

Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

Roadway Subsystem<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

emissions sensor<br />

control<br />

vehicle emissions<br />

data<br />

Emissions<br />

Management<br />

Municipal<br />

TOCs<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

Roadway<br />

Subsystem<br />

City of<br />

Roseville<br />

Roadside<br />

Equipment<br />

emissions sensor<br />

control<br />

vehicle emissions<br />

data<br />

Emissions<br />

Management<br />

City of Roseville<br />

TOC<br />

Roadway Subsystem<br />

Sacramento<br />

International<br />

Airport<br />

Roadside<br />

Equipment<br />

emissions sensor<br />

control<br />

vehicle emissions<br />

data<br />

Emissions<br />

Management<br />

Sacramento<br />

International<br />

Airport TMC<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS13 - Standard Railroad Crossing<br />

Sacramento County / City of Sacramento<br />

Traffic Management<br />

Municipal<br />

TOCs<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

hri operational status<br />

track status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

Traffic Management<br />

City of<br />

Sacramento<br />

TOC<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

Sacramento<br />

City Roadside<br />

Equipment<br />

hri operational status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

track status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS13 - Standard Railroad Crossing<br />

City of Roseville / Sacramento International Airport<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

hri operational status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

track status<br />

Traffic Management<br />

Sacramento<br />

International<br />

Airport TMC<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

Sacramento<br />

International<br />

Airport<br />

Roadside<br />

Equipment<br />

hri operational status<br />

track status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS13 - Standard Railroad Crossing<br />

Caltrans / City of West Sacramento<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

hri operational status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

track status<br />

Traffic Management<br />

City of West<br />

Sacramento<br />

TOC<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

Roadway Subsystem<br />

City of West<br />

Sacramento<br />

Roadside<br />

Equipment<br />

hri operational status<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

track status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS14 - Advanced Railroad Grade Crossing<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

+<br />

intersection blockage<br />

notification<br />

Roadway Subsystem<br />

Sacramento<br />

County<br />

Roadside<br />

Equipment<br />

hri operational<br />

status<br />

+<br />

intersection blockage<br />

notification<br />

arriving train<br />

information<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

railroad advisories<br />

+<br />

railroad schedules<br />

hri advisories<br />

track status<br />

Rail Operations<br />

Regional<br />

Railroad<br />

Operations<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS14 - Advanced Railroad Grade Crossing<br />

Traffic Management<br />

City of<br />

Sacramento<br />

TOC<br />

hri control data<br />

+<br />

hri request<br />

hri status<br />

+<br />

intersection blockage<br />

notification<br />

Roadway Subsystem<br />

Sacramento<br />

City Roadside<br />

Equipment<br />

hri operational<br />

status<br />

+<br />

intersection blockage<br />

notification<br />

arriving train<br />

information<br />

Wayside Equipment<br />

Heavy Rail<br />

Wayside<br />

Equipment<br />

+<br />

RT Wayside<br />

Equipment<br />

railroad advisories<br />

+<br />

railroad schedules<br />

hri advisories<br />

track status<br />

Rail Operations<br />

Regional<br />

Railroad<br />

Operations<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS15 - Railroad Operations Coordination<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

+<br />

Municipal TOCs<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

railroad advisories<br />

+<br />

railroad schedules<br />

hri advisories<br />

Does this market package apply to this<br />

region, and are the interfaces existing or<br />

planned?<br />

Rail Operations<br />

Regional Railroad<br />

Operations<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATMS16 - Parking Facility Management<br />

Light Rail Station Parking Management<br />

Financial Institution<br />

Financial<br />

Institutions<br />

payment request<br />

Parking Management<br />

Light Rail Station<br />

Parking Mgmt.<br />

payment violation<br />

notification<br />

Enforcement Agency<br />

RT Police Services<br />

transaction status<br />

Vehicle<br />

Vehicles<br />

request tag data<br />

+<br />

tag update<br />

parking lot inputs<br />

Traffic Management<br />

STARNET Server<br />

tag data<br />

parking<br />

reservations<br />

request<br />

Information Service Provider<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

parking lot reservation<br />

confirmation<br />

RT Transit<br />

Management Center<br />

+<br />

Sacramento<br />

International Airport<br />

TMC


MC01 - Maintenance and Construction Vehicle and Equipment Tracking<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

maint and constr vehicle location<br />

data<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

maint and constr vehicle location<br />

data<br />

Maintenance and<br />

Construction Vehicle<br />

City of Sacramento<br />

Maintenance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC01 - Maintenance and Construction Vehicle and Equipment Tracking<br />

Municipalities<br />

Maintenance and Construction Management<br />

Citrus Heights Maintenance Dispatch<br />

+<br />

City of Davis Maintenance Dispatch<br />

+<br />

City of Elk Grove Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance Dispatch<br />

+<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

+<br />

City of Roseville Maintenance Dispatch<br />

+<br />

City of Sacramento Maintenance<br />

Dispatch<br />

+<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

+<br />

City of Woodland Maintenance Dispatch<br />

+<br />

Yuba City Maintenance Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

maint and constr<br />

vehicle location data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC01 - Maintenance and Construction Vehicle and Equipment Tracking<br />

County Maintenance<br />

Maintenance and<br />

Construction Management<br />

County<br />

Maintenance<br />

Dispatch<br />

maint and constr vehicle location<br />

data<br />

Maintenance and<br />

Construction Vehicle<br />

County<br />

Maintenance<br />

Vehicles<br />

Maintenance and<br />

Construction Management<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

maint and constr vehicle location<br />

data<br />

Maintenance and<br />

Construction Vehicle<br />

Sacramento County<br />

Maintenance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC02 - Maintenance and Construction Vehicle Maintenance<br />

Caltrans<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

maint and constr vehicle conditions<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

maint and constr<br />

fleet information<br />

maint and constr<br />

equipment repair<br />

status<br />

Equipment Repair<br />

Facility<br />

Caltrans District<br />

Shop<br />

maint and constr<br />

vehicle conditions<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC02 - Maintenance and Construction Vehicle Maintenance<br />

Municipal Maintenance<br />

Maintenance and Construction Management<br />

Citrus Heights Maintenance Dispatch<br />

+<br />

City of Davis Maintenance Dispatch<br />

+<br />

City of Elk Grove Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance Dispatch<br />

+<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

+<br />

City of Roseville Maintenance Dispatch<br />

+<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

+<br />

City of Woodland Maintenance Dispatch<br />

+<br />

Yuba City Maintenance Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

maint and constr vehicle<br />

conditions<br />

maint and constr<br />

equipment repair status<br />

maint and constr fleet<br />

information<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

maint and constr<br />

equipment repair<br />

status<br />

Equipment Repair<br />

Facility<br />

Municipal<br />

Equipment Repair<br />

Facility<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC02 - Maintenance and Construction Vehicle Maintenance<br />

Sacramento County<br />

Maintenance and<br />

Construction Management<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

maint and constr vehicle conditions<br />

Maintenance and<br />

Construction Vehicle<br />

Sacramento County<br />

Maintenance<br />

Vehicles<br />

maint and constr<br />

fleet information<br />

maint and constr<br />

equipment repair<br />

status<br />

Equipment Repair<br />

Facility<br />

Sacramento County<br />

Equipment Repair<br />

Facility<br />

maint and constr<br />

equipment repair<br />

status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC02 - Maintenance and Construction Vehicle Maintenance<br />

City of Sacramento Maintenance<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

maint and constr vehicle conditions<br />

Maintenance and<br />

Construction Vehicle<br />

City of Sacramento<br />

Maintenance<br />

Vehicles<br />

maint and constr<br />

fleet information<br />

maint and constr<br />

equipment repair<br />

status<br />

Equipment Repair<br />

Facility<br />

City of Sacramento<br />

Equipment Shop<br />

maint and constr<br />

equipment repair<br />

status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC03 - Road Weather Data Collection<br />

Weather Service<br />

Weather Information<br />

Providers<br />

environmental<br />

conditions data<br />

weather<br />

information<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

environmental sensors<br />

control<br />

environmental conditions<br />

data<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

environmental<br />

conditions_ud<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC03 - Road Weather Data Collection<br />

Sacramento County<br />

Weather Service<br />

Weather Information<br />

Providers<br />

environmental<br />

conditions data<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

environmental<br />

conditions_ud<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

environmental<br />

conditions data<br />

environmental sensors<br />

control<br />

Roadway Subsystem<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC03 - Road Weather Data Collection<br />

Roseville<br />

Weather Service<br />

Weather Information<br />

Providers<br />

environmental<br />

conditions data<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

environmental sensors<br />

control<br />

environmental conditions<br />

data<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

environmental<br />

conditions_ud<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC04 - Weather Information Processing and Distribution<br />

Caltrans<br />

Maintenance and<br />

Construction<br />

Management<br />

road weather<br />

information<br />

Maintenance and<br />

Construction<br />

Management<br />

road weather information<br />

Weather Service<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

road weather<br />

information<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

weather information<br />

Weather Information<br />

Providers<br />

road weather information<br />

Traffic Management<br />

Information Service<br />

Provider<br />

Caltrans D3<br />

Data Server<br />

LEGEND<br />

planned and future flow<br />

road weather<br />

information<br />

road weather<br />

information<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

City of Sacramento<br />

TOC<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

+<br />

STARNET Server<br />

existing flow<br />

user defined flow


MC04 - Weather Information Processing and Distribution<br />

Sacramento County (1 of 2)<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

+<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento<br />

International<br />

Airport TMC<br />

+<br />

STARNET Server<br />

road weather<br />

information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

road weather<br />

information<br />

weather information<br />

Weather Service<br />

Weather Information<br />

Providers<br />

Maintenance and<br />

Construction<br />

Management<br />

road weather information<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC04 - Weather Information Processing and Distribution<br />

Sacramento County (2 of 2)<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

road weather information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

road weather<br />

information<br />

Emergency Management<br />

Sacramento<br />

County Sheriff<br />

Dept.<br />

Communications<br />

+<br />

Sacramento<br />

County<br />

Telecommunicati<br />

ons Center<br />

(DISPATCH)<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC04 - Weather Information Processing and Distribution<br />

Roseville<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

road weather<br />

information<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

TOC<br />

road weather<br />

information<br />

weather information<br />

Weather Service<br />

Weather Information<br />

Providers<br />

Emergency Management<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

road weather<br />

information<br />

road weather information<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

This could include information from flood sensors.<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC05 - Roadway Automated Treatment<br />

Caltrans<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

roadway treatment<br />

system control<br />

roadway treatment<br />

system status<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC06 - Winter Maintenance<br />

Caltrans<br />

Storage Facility<br />

Caltrans D3 Storage<br />

Facility<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

equipment availability<br />

+<br />

maintenance materials<br />

storage status<br />

storage facility request<br />

roadway maintenance<br />

status<br />

roadway maintenance<br />

status<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

maint and constr dispatch<br />

status<br />

+<br />

maint and constr vehicle<br />

operational data<br />

maint and constr<br />

dispatch information<br />

+<br />

maint and constr<br />

vehicle system control<br />

maint and constr<br />

resource response<br />

+<br />

roadway maintenance<br />

status<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

maint and constr resource<br />

request<br />

+<br />

road network conditions<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

Caltrans Maintenance<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

asset inventory<br />

+<br />

asset restrictions<br />

Asset Management<br />

Caltrans D3<br />

Pavement<br />

Management<br />

System<br />

asset status update


MC07 - Roadway Maintenance and Construction<br />

County Maintenance<br />

Traffic Management<br />

Other County<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

County<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

Sacramento County<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

equipment<br />

maintenance<br />

status<br />

field equipment<br />

status<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

There for Portable CMS.<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

weather information<br />

Maintenance and<br />

Construction Vehicle<br />

Sacramento<br />

County<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

Maintenance and<br />

Construction<br />

Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

LEGEND<br />

planned and future flow<br />

asset inventory<br />

+<br />

asset restrictions<br />

Asset Management<br />

Pavement Management<br />

System,<br />

Sign Inventory, etc..<br />

existing flow<br />

asset status update<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Sacramento<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

City of<br />

Sacramento<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

asset inventory<br />

+<br />

asset restrictions<br />

Asset Management<br />

LEGEND<br />

planned and future flow<br />

Pavement Management<br />

System,<br />

Sign Inventory, etc..<br />

existing flow<br />

asset status update<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Davis<br />

Traffic Management<br />

City of Davis<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Citrus Heights<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Elk Grove<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Folsom<br />

Traffic Management<br />

City of Folsom<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Rancho Cordova<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Roseville<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of West Sacramento<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

City of Woodland<br />

Traffic Management<br />

City of Woodland<br />

TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Woodland<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

Yuba City<br />

Traffic Management<br />

Yuba City TOC<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC07 - Roadway Maintenance and Construction<br />

Municipalities<br />

Traffic Management<br />

Municipal TOCs<br />

field equipment status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

road network conditions<br />

equipment maintenance<br />

status<br />

+<br />

maint and constr<br />

resource response<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

maint and constr<br />

dispatch information<br />

maint and constr<br />

dispatch status<br />

+<br />

maint and constr<br />

vehicle operational data<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

Weather Service<br />

Weather Information<br />

Providers<br />

weather information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

Caltrans<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

roadway information<br />

system status<br />

Roadway Subsystem<br />

Caltrans Roadside<br />

Equipment<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

work zone<br />

information_ud<br />

work zone<br />

information<br />

work zone<br />

information<br />

work zone<br />

information<br />

Maintenance and<br />

Construction Management<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

+<br />

Sacramento<br />

International Airport<br />

Maintenance<br />

Dispatch<br />

Maintenance and<br />

Construction Management<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

Sacramento County<br />

Maintenance and<br />

Construction Vehicle<br />

Sacramento County<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

Traffic Management<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Sacramento<br />

Maintenance and<br />

Construction Vehicle<br />

City of Sacramento<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Sacramento City<br />

Roadside<br />

Equipment<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

Other Counties<br />

Maintenance and<br />

Construction Vehicle<br />

County<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

County Roadside<br />

Equipment<br />

Traffic Management<br />

Other County TOC<br />

work zone<br />

information<br />

LEGEND<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Citrus Heights<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside<br />

Equipment<br />

Traffic Management<br />

Citrus Heights<br />

Traffic Operations<br />

Center<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Davis<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Davis<br />

Field Equipment<br />

Traffic Management<br />

City of Davis TOC<br />

work zone<br />

information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

work zone information<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Elk Grove<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Elk Grove<br />

Field Equipment<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Folsom<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Folsom<br />

Field Equipment<br />

Traffic Management<br />

City of Folsom TOC<br />

work zone<br />

information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

work zone information<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Rancho Cordova<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Rancho<br />

Cordova Field<br />

Equipment<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Roseville<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of West Sacramento<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of West<br />

Sacramento<br />

Roadside<br />

Equipment<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

City of Woodland<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Woodland<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

City of Woodland<br />

Field Equipment<br />

Traffic Management<br />

City of Woodland<br />

TOC<br />

work zone<br />

information<br />

work zone information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

Yuba City<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Yuba City Field<br />

Equipment<br />

Traffic Management<br />

Yuba City TOC<br />

work zone<br />

information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

work zone information<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC08 - Work Zone Management<br />

Municipal Maintenance<br />

Maintenance and<br />

Construction Vehicle<br />

Municipal<br />

Maintenance<br />

Vehicles<br />

work zone status<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

roadway information<br />

system data<br />

+<br />

video surveillance<br />

control<br />

roadway information<br />

system status<br />

+<br />

traffic images<br />

Roadway Subsystem<br />

Municipal Field<br />

Equipment<br />

Traffic Management<br />

work zone<br />

information<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal TOCs<br />

work zone information<br />

County<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC09 - Work Zone Safety Monitoring<br />

Caltrans<br />

Maintenance and<br />

Construction Vehicle<br />

Caltrans D3<br />

Maintenance<br />

Vehicles<br />

work zone warning<br />

status<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

work zone warning<br />

status<br />

Roadway Subsystem<br />

Caltrans<br />

Roadside<br />

Equipment<br />

work zone warning notification<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Caltrans Maintenance (1 of 2)<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

City of Sacramento<br />

Maintenance Dispatch<br />

+<br />

Other Caltrans District<br />

Maintenance<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Caltrans Maintenance (2 of 2)<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

current asset restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

RTMC-CHP<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

current asset restrictions<br />

+<br />

maint and constr work<br />

plans<br />

This is currently done by email<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

+<br />

Yolo Bus<br />

Dispatch Center<br />

maint and constr<br />

work plans<br />

Media<br />

LEGEND<br />

planned and future flow<br />

Local Print and<br />

Broadcast Media<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Sacramento County (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3 Maintenance<br />

Dispatch<br />

+<br />

Citrus Heights Maintenance<br />

Dispatch<br />

+<br />

City of Elk Grove<br />

Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance<br />

Dispatch<br />

+<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Sacramento County (2 of 2)<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

Information Service<br />

Provider<br />

Sacramento<br />

County Website<br />

+<br />

STARNET ISP<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Maintenance and<br />

Construction<br />

Management<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Sacramento<br />

County Sheriff<br />

Dept.<br />

Communications<br />

+<br />

Sacramento<br />

Regional Fire/<br />

EMS Comm.<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Sacramento (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

City of Elk Grove<br />

Maintenance Dispatch<br />

+<br />

City of West<br />

Sacramento<br />

Maintenance Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Sacramento (2 of 2)<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

Information Service<br />

Provider<br />

City of<br />

Sacramento<br />

Website<br />

+<br />

STARNET ISP<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Transit Management<br />

El Dorado Transit Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines Transit<br />

Dispatch<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

Yolo Bus Dispatch Center<br />

+<br />

Yuba-Sutter Transit Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento Regional Fire/<br />

EMS Comm. Center


MC10 - Maintenance and Construction Activity Coordination<br />

City of Citrus Heights (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

City of Folsom<br />

Maintenance Dispatch<br />

+<br />

City of Roseville<br />

Maintenance Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Citrus Heights (2 of 2)<br />

Traffic Management<br />

Citrus Heights<br />

Traffic Operations<br />

Center<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

Citrus Heights<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

RT Transit Management<br />

Center<br />

Information Service<br />

Provider<br />

City of Sacramento<br />

Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Davis (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

County Maintenance<br />

Dispatch<br />

work plan coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Davis (2 of 2)<br />

Traffic Management<br />

City of Davis TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Davis<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

Unitrans Transit<br />

Dispatch<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Elk Grove (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Elk Grove (2 of 2)<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Transit Management<br />

e-tran Transit Center<br />

+<br />

Paratransit, Inc.<br />

+<br />

RT Transit<br />

Management Center<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Folsom (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Citrus Heights<br />

Maintenance Dispatch<br />

+<br />

City of Rancho<br />

Cordova Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Folsom (2 of 2)<br />

Traffic Management<br />

City of Folsom TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Transit Management<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Paratransit, Inc.<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Rancho Cordova (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

City of Folsom<br />

Maintenance Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Rancho Cordova (2 of 2)<br />

Traffic Management<br />

City of Rancho<br />

Cordova TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Rancho<br />

Cordova<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Roseville (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3<br />

Maintenance Dispatch<br />

+<br />

Citrus Heights<br />

Maintenance Dispatch<br />

+<br />

County Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Roseville (2 of 2)<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Emergency Management<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Woodland (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of Woodland<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

+<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of Woodland (2 of 2)<br />

Traffic Management<br />

City of Woodland<br />

TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of Woodland<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of West Sacramento (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

+<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

City of West Sacramento (2 of 2)<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Maintenance and<br />

Construction<br />

Management<br />

City of West<br />

Sacramento<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

RT Transit<br />

Management Center<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr<br />

work plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Yuba City (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

work plan coordination<br />

work plan coordination<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

+<br />

County<br />

Maintenance<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


MC10 - Maintenance and Construction Activity Coordination<br />

Yuba City (2 of 2)<br />

Traffic Management<br />

Yuba City TOC<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Maintenance and<br />

Construction<br />

Management<br />

Yuba City<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Transit Management<br />

Paratransit, Inc.<br />

+<br />

Yuba-Sutter Transit<br />

Center<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Regional Emergency Comm Network (EM to Other EM)<br />

Emergency Management<br />

Airport Dispatch Center<br />

+<br />

City of Roseville Police and Fire Dispatch<br />

+<br />

City of West Sacramento TOC<br />

+<br />

County EOC<br />

+<br />

County Sheriff Communications Centers<br />

+<br />

Light Rail Transit Management Center<br />

+<br />

Local Fire/EMS Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Municipal EOC<br />

+<br />

Other Law Enforcement Dispatch Center<br />

+<br />

RT Police Services<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police Department Communications<br />

+<br />

Sacramento County Sheriff Dept. Communications<br />

+<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

+<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

incident response<br />

coordination<br />

incident report<br />

incident report<br />

incident response coordination<br />

Other Emergency<br />

Management<br />

Regional Emergency<br />

Communications<br />

Network<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Private/Public Ambulance Dispatch<br />

Emergency Management<br />

City of Roseville Police and Fire<br />

Dispatch<br />

+<br />

County Sheriff Communications<br />

Centers<br />

+<br />

Local Fire/EMS Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Other Law Enforcement Dispatch<br />

Center<br />

+<br />

RT Police Services<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police Department<br />

Communications<br />

+<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

+<br />

Sacramento Regional Fire/ EMS<br />

Comm. Center<br />

incident report<br />

incident response<br />

coordination<br />

incident report<br />

incident response<br />

coordination<br />

Emergency<br />

Management<br />

Private/Public<br />

Ambulance<br />

Dispatch<br />

emergency<br />

dispatch response<br />

emergency<br />

dispatch requests<br />

Emergency Vehicle<br />

Subsystem<br />

Private/Public<br />

Ambulance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Local Fire/EMS Dispatch<br />

Emergency<br />

Management<br />

County EOC<br />

+<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Municipal EOC<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

emergency dispatch<br />

requests<br />

emergency dispatch<br />

response<br />

+<br />

incident status<br />

remote surveillance<br />

control<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

Traffic Management<br />

STARNET Server<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Local Police Dispatch<br />

Emergency<br />

Management<br />

County EOC<br />

+<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Municipal EOC<br />

+<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

LEGEND<br />

Emergency Management<br />

Local Police<br />

Dispatch<br />

emergency dispatch<br />

response<br />

emergency dispatch<br />

requests<br />

remote surveillance<br />

control<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Emergency Vehicle<br />

Subsystem<br />

Local Law<br />

Enforcement<br />

Vehicles<br />

Traffic Management<br />

STARNET Server<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

California Highway Patrol<br />

Emergency<br />

Management<br />

California Office of<br />

Emergency Services<br />

Operations Centers<br />

+<br />

County EOC<br />

+<br />

Municipal EOC<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

Emergency<br />

Management<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Management<br />

RTMC-CHP<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

remote surveillance<br />

control<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Vehicle<br />

Subsystem<br />

CHP Vehicles<br />

Traffic Management<br />

STARNET Server<br />

Sacramento Regional<br />

Fire/ EMS Comm. Center<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Sacramento Regional Fire/EMS Comm. Center<br />

Emergency Management<br />

Emergency Management<br />

County EOC<br />

+<br />

Municipal EOC<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City<br />

Police Department<br />

Communications<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

incident report<br />

incident report<br />

incident response<br />

coordination<br />

Sacramento<br />

Regional Fire/<br />

EMS Comm.<br />

Center<br />

remote surveillance<br />

control<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

+<br />

STARNET Server<br />

incident response<br />

coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Sacramento County Sheriff Dept. Communications<br />

Emergency Management<br />

County EOC<br />

+<br />

Sacramento City<br />

Police Department<br />

Communications<br />

+<br />

Sacramento<br />

County<br />

Telecommunicatio<br />

ns Center<br />

(DISPATCH)<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Management<br />

Sacramento<br />

County Sheriff<br />

Dept.<br />

Communications<br />

emergency dispatch<br />

requests<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

remote surveillance<br />

control<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento<br />

County Sheriff<br />

Vehicle<br />

Traffic Management<br />

STARNET Server<br />

LEGEND<br />

planned and future flow<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Sacramento City Police Department Communications<br />

Emergency Management<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Management<br />

Sacramento City<br />

Police<br />

Department<br />

Communications<br />

emergency dispatch<br />

requests<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento City<br />

Police Vehicles<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Emergency<br />

Management<br />

Regional Emergency<br />

Operations Center<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

remote surveillance<br />

control<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

+<br />

STARNET Server<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Sacramento County Telecommunications Center (DISPATCH)<br />

Emergency Management<br />

Emergency<br />

Management<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

emergency dispatch<br />

requests<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

Who does the Telcom Center<br />

dispatch?<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Emergency<br />

Management<br />

County EOC<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

remote surveillance<br />

control<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

Traffic Management<br />

STARNET Server<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

Regional Emergency Operations Center<br />

Traffic Management<br />

STARNET Server<br />

remote surveillance<br />

control<br />

road network<br />

conditions<br />

+<br />

traffic images<br />

LEGEND<br />

Emergency Management<br />

County EOC<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

incident report<br />

+<br />

incident response<br />

coordination<br />

Emergency Management<br />

City of Roseville Police and Fire<br />

Dispatch<br />

+<br />

County Sheriff Communications<br />

Centers<br />

+<br />

Local Fire/EMS Dispatch<br />

Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Other Law Enforcement<br />

Dispatch Center<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police<br />

Department Communications<br />

+<br />

Sacramento County Sheriff<br />

Dept. Communications<br />

+<br />

Sacramento County<br />

Telecommunications Center<br />

(DISPATCH)<br />

+<br />

Sacramento Regional Fire/ EMS<br />

Comm. Center<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM01 - Emergency Call-Taking and Dispatch<br />

STARNET<br />

Traffic Management<br />

Emergency Management<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

STARNET Server<br />

road network conditions<br />

+<br />

traffic images<br />

remote surveillance control<br />

Airport Dispatch Center<br />

+<br />

City of Roseville Police<br />

and Fire Dispatch<br />

+<br />

County Sheriff<br />

Communications Centers<br />

+<br />

Local Fire/EMS Dispatch<br />

Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Other Law Enforcement<br />

Dispatch Center<br />

+<br />

RT Police Services<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

+<br />

Sacramento Regional Fire/<br />

EMS Comm. Center<br />

user defined flow


EM02 - Emergency Routing<br />

Sacramento City Fire (1 of 3)<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Sacramento City<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Sacramento City<br />

Fire Vehicles<br />

LEGEND<br />

planned and future flow<br />

care facility status<br />

request<br />

Care Facility<br />

care facility status<br />

existing flow<br />

user defined flow<br />

care facility status<br />

Regional Medical<br />

Centers<br />

care facility status request<br />

+<br />

patient status


EM02 - Emergency Routing<br />

Sacramento City Fire (2 of 3)<br />

Traffic Management<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Sacramento County<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

+<br />

Sacramento City<br />

Fire Vehicles<br />

LEGEND<br />

planned and future flow<br />

care facility status<br />

request<br />

Care Facility<br />

care facility status<br />

existing flow<br />

user defined flow<br />

care facility status<br />

Regional Medical<br />

Centers<br />

care facility status request<br />

+<br />

patient status


EM02 - Emergency Routing<br />

Sacramento City Fire (3 of 3)<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of West<br />

Sacramento<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

+<br />

Sacramento City<br />

Fire Vehicles<br />

LEGEND<br />

planned and future flow<br />

care facility status<br />

request<br />

Care Facility<br />

care facility status<br />

existing flow<br />

user defined flow<br />

care facility status<br />

Regional Medical<br />

Centers<br />

care facility status request<br />

+<br />

patient status


EM02 - Emergency Routing<br />

Local Law Enforcement (1 of 2)<br />

Traffic Management<br />

City of Elk Grove TOC<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of Elk Grove<br />

Field Equipment<br />

road network<br />

conditions<br />

Elk Grove Police have preemption in Elk Grove<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Local Police Dispatch<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

Emergency Vehicle<br />

Subsystem<br />

Local Law<br />

Enforcement<br />

Vehicles<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

LEGEND<br />

planned and future flow<br />

care facility status<br />

request<br />

Care Facility<br />

care facility status<br />

existing flow<br />

user defined flow<br />

care facility status<br />

Regional Medical<br />

Centers<br />

care facility status request<br />

+<br />

patient status


EM02 - Emergency Routing<br />

Local Law Enforcement (2 of 2)<br />

Traffic Management<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Sacramento County<br />

Roadside<br />

Equipment<br />

road network<br />

conditions<br />

Elk Grove Police have preemption in Sacramento<br />

County.<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Local Police Dispatch<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

Emergency Vehicle<br />

Subsystem<br />

Local Law<br />

Enforcement<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM02 - Emergency Routing<br />

Local Fire / EMS (1 of 3)<br />

Traffic Management<br />

City of West<br />

Sacramento TOC<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of West<br />

Sacramento Roadside<br />

Equipment<br />

road network<br />

conditions<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

local signal<br />

preemption<br />

request<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

care facility status<br />

care facility status<br />

request<br />

Care Facility<br />

Regional Medical<br />

Centers<br />

care facility status<br />

care facility status request<br />

+<br />

patient status


EM02 - Emergency Routing<br />

Local Fire / EMS (2 of 3)<br />

Traffic Management<br />

City of Roseville TOC<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside Equipment<br />

road network<br />

conditions<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM02 - Emergency Routing<br />

Local Fire / EMS (3 of 3)<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

signal control data<br />

request for right-of-way<br />

+<br />

signal control status<br />

Roadway Subsystem<br />

Citrus Heights<br />

Roadside Equipment<br />

road network<br />

conditions<br />

local signal<br />

preemption<br />

request<br />

Emergency Management<br />

Local Fire/EMS<br />

Dispatch Centers<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Local Fire/EMS<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM02 - Emergency Routing<br />

Private EMS Vehicles<br />

Emergency Management<br />

Private/Public<br />

Ambulance<br />

Dispatch<br />

emergency dispatch requests<br />

+<br />

suggested route<br />

emergency dispatch response<br />

+<br />

emergency vehicle tracking data<br />

Emergency Vehicle<br />

Subsystem<br />

Private/Public<br />

Ambulance<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

care facility status<br />

care facility status<br />

request<br />

Care Facility<br />

Regional Medical<br />

Centers<br />

care facility status<br />

care facility status<br />

request<br />

+<br />

patient status<br />

existing flow<br />

user defined flow


EM04 - Roadway Service Patrols<br />

Freeway Service Patrol Vehicles<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

incident information<br />

Emergency Management<br />

RTMC-CHP<br />

emergency dispatch<br />

response<br />

+<br />

emergency vehicle<br />

tracking data<br />

+<br />

incident status<br />

Emergency Vehicle<br />

Subsystem<br />

Freeway Service<br />

Patrol Vehicles<br />

emergency dispatch<br />

requests<br />

incident information<br />

Information Service<br />

Provider<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM05 - Transportation Infrastructure Protection<br />

RT Transit<br />

Emergency Management<br />

RT Police<br />

Services<br />

incident report<br />

+<br />

threat information<br />

coordination<br />

Emergency Management<br />

RT Transit<br />

Management<br />

Center<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

Security Monitoring<br />

Subsystem<br />

RT Security<br />

Monitoring<br />

Equipment<br />

infrastructure monitoring<br />

sensor control<br />

+<br />

secure area sensor control<br />

infrastructure monitoring<br />

sensor data<br />

+<br />

secure area sensor data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

RT has existing cameras for detecting<br />

broken gates. Also cameras at tracks.<br />

user defined flow


EM06 - Wide Area Alert<br />

Amber Alert<br />

Roadway Subsystem<br />

Caltrans Roadside<br />

Equipment<br />

roadway<br />

information system<br />

status<br />

roadway<br />

information system<br />

data<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

alert status<br />

Currently provided by operator to<br />

operator communications<br />

alert notification<br />

Emergency Management<br />

RTMC-CHP<br />

Roadway Subsystem<br />

Sacramento County<br />

Roadside<br />

Equipment<br />

roadway<br />

information system<br />

status<br />

roadway<br />

information system<br />

data<br />

Traffic Management<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

alert status<br />

alert notification<br />

alert<br />

notification_ud<br />

alert notification<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Information Service<br />

Provider<br />

CHP Website<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

user defined flow


EM06 - Wide Area Alert<br />

State EOC (1 of 2)<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

alert status<br />

+<br />

incident information<br />

Emergency Management<br />

California Office<br />

of Emergency<br />

Services<br />

Operations<br />

Centers<br />

alert notification<br />

coordination<br />

+<br />

transportation system<br />

status<br />

Emergency Management<br />

County EOC<br />

+<br />

Municipal EOC<br />

alert notification<br />

alert notification<br />

coordination<br />

+<br />

transportation system<br />

status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM06 - Wide Area Alert<br />

State EOC (2 of 2)<br />

Maintenance and<br />

Construction<br />

Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

alert notification<br />

Emergency Management<br />

California Office<br />

of Emergency<br />

Services<br />

Operations<br />

Centers<br />

alert notification<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

alert status<br />

alert status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM06 - Wide Area Alert<br />

County EOC<br />

Traffic Management<br />

Other County<br />

TOC<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations Center<br />

Information Service<br />

Provider<br />

alert status<br />

+<br />

incident information<br />

alert notification<br />

Emergency Management<br />

County EOC<br />

alert notification<br />

coordination<br />

+<br />

transportation<br />

system status<br />

alert notification<br />

coordination<br />

+<br />

transportation<br />

system status<br />

Emergency Management<br />

California Office of<br />

Emergency Services<br />

Operations Centers<br />

+<br />

Municipal EOC<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

alert notification<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM06 - Wide Area Alert<br />

Municipal EOC<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova<br />

TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

alert status<br />

+<br />

incident<br />

information<br />

alert notification<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Emergency<br />

Management<br />

Municipal EOC<br />

alert notification<br />

alert notification<br />

coordination<br />

+<br />

transportation system<br />

status<br />

alert notification<br />

coordination<br />

+<br />

transportation system<br />

status<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

Emergency Management<br />

California Office<br />

of Emergency<br />

Services<br />

Operations<br />

Centers<br />

+<br />

County EOC<br />

+<br />

Local Fire/EMS<br />

Dispatch<br />

Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento City<br />

Police<br />

Department<br />

Communications<br />

user defined flow


EM07 - Early Warning System<br />

County Emergency Operation Centers<br />

Traffic Management<br />

Citrus Heights Traffic Operations<br />

Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

City of West Sacramento TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

+<br />

Municipal TOCs<br />

+<br />

RTMC-D3 - Traffic Operations<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

threat information<br />

incident<br />

information<br />

Emergency<br />

Management<br />

County EOC<br />

threat information<br />

coordination<br />

threat information<br />

coordination<br />

existing flow<br />

Emergency Management<br />

California Office of<br />

Emergency Services<br />

Operations Centers<br />

+<br />

County Sheriff<br />

Communications Centers<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

LEGEND<br />

planned flow<br />

user defined flow


EM07 - Early Warning System<br />

Weather Warnings<br />

Emergency Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

weather information<br />

Weather Service<br />

Weather Information<br />

Providers<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM08 - Disaster Response and Recovery<br />

County Emergency Operations Centers (1 of 2)<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

emergency plan<br />

coordination<br />

+<br />

incident response<br />

status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

transportation system<br />

status<br />

emergency plan<br />

coordination<br />

+<br />

maint and constr<br />

resource response<br />

+<br />

road network status<br />

assessment<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Emergency<br />

Management<br />

County EOC<br />

emergency plan<br />

coordination<br />

+<br />

incident command<br />

information coordination<br />

+<br />

incident response<br />

coordination<br />

+<br />

resource coordination<br />

+<br />

transportation system<br />

status<br />

emergency plan<br />

coordination<br />

+<br />

incident command<br />

information coordination<br />

+<br />

incident response<br />

coordination<br />

+<br />

resource coordination<br />

+<br />

transportation system<br />

status<br />

Emergency<br />

Management<br />

California Office of<br />

Emergency Services<br />

Operations Centers<br />

+<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Private/Public<br />

Ambulance Dispatch<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center


EM08 - Disaster Response and Recovery<br />

Regional Emergency Operations Center (2 of 2)<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Light Rail Transit<br />

Management Center<br />

+<br />

Local Transit Dispatch<br />

Centers<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

School Bus Dispatch<br />

+<br />

Unitrans Transit Dispatch<br />

+<br />

Yolo Bus Dispatch Center<br />

+<br />

Yuba-Sutter Transit Center<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

schedule<br />

information<br />

+<br />

emergency transit<br />

service response<br />

+<br />

transit system<br />

status assessment<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

service request<br />

+<br />

incident response<br />

status<br />

+<br />

transportation<br />

system status<br />

Emergency Management<br />

County EOC<br />

emergency plan<br />

coordination<br />

+<br />

resource request<br />

+<br />

transportation system<br />

status<br />

emergency plan<br />

coordination<br />

+<br />

resource deployment<br />

status<br />

+<br />

road network status<br />

assessment<br />

Traffic Management<br />

Other County<br />

TOC<br />

+<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM08 - Disaster Response and Recovery<br />

Municipal EOC (1 of 2)<br />

Maintenance and<br />

Construction Management<br />

Citrus Heights Maintenance<br />

Dispatch<br />

+<br />

City of Davis Maintenance<br />

Dispatch<br />

+<br />

City of Elk Grove<br />

Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance<br />

Dispatch<br />

+<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

+<br />

City of Roseville<br />

Maintenance Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance Dispatch<br />

+<br />

City of West Sacramento<br />

Maintenance Dispatch<br />

+<br />

City of Woodland<br />

Maintenance Dispatch<br />

+<br />

Yuba City Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance<br />

Dispatch<br />

emergency plan<br />

coordination<br />

+<br />

incident response<br />

status<br />

+<br />

maint and constr<br />

resource request<br />

+<br />

transportation<br />

system status<br />

emergency plan<br />

coordination<br />

+<br />

maint and constr<br />

resource response<br />

+<br />

road network<br />

status assessment<br />

Emergency<br />

Management<br />

Municipal EOC<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

emergency plan<br />

coordination<br />

+<br />

incident command<br />

information<br />

coordination<br />

+<br />

incident response<br />

coordination<br />

+<br />

resource coordination<br />

+<br />

transportation system<br />

status<br />

emergency plan<br />

coordination<br />

+<br />

incident command<br />

information<br />

coordination<br />

+<br />

incident response<br />

coordination<br />

+<br />

resource coordination<br />

+<br />

transportation system<br />

status<br />

Emergency<br />

Management<br />

California Office of<br />

Emergency Services<br />

Operations Centers<br />

+<br />

City of Roseville Police<br />

and Fire Dispatch<br />

+<br />

County EOC<br />

+<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center


EM08 - Disaster Response and Recovery<br />

Municipal EOC (2 of 2)<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Light Rail Transit<br />

Management Center<br />

+<br />

Local Transit Dispatch<br />

Centers<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

School Bus Dispatch<br />

+<br />

Unitrans Transit Dispatch<br />

+<br />

Yolo Bus Dispatch Center<br />

+<br />

Yuba-Sutter Transit Center<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

schedule<br />

information<br />

+<br />

emergency transit<br />

service response<br />

+<br />

transit system<br />

status assessment<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

service request<br />

+<br />

incident response<br />

status<br />

+<br />

transportation<br />

system status<br />

Emergency Management<br />

Municipal EOC<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

emergency plan<br />

coordination<br />

+<br />

resource request<br />

+<br />

transportation<br />

system status<br />

emergency plan<br />

coordination<br />

+<br />

resource deployment<br />

status<br />

+<br />

road network status<br />

assessment<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova<br />

TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

City of West Sacramento<br />

TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

+<br />

Municipal TOCs


EM09 - Evacuation and Reentry Management<br />

State EOC – County/Muncipal EOC Coordination<br />

Traffic Management<br />

RTMC-D3 - Traffic<br />

Operations<br />

emergency plan<br />

coordination<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

information<br />

Emergency Management<br />

County EOC<br />

+<br />

Municipal EOC<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

emergency plan<br />

coordination<br />

+<br />

emergency traffic<br />

control request<br />

+<br />

evacuation information<br />

emergency plan coordination<br />

+<br />

emergency traffic control information<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

+<br />

resource<br />

coordination<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

+<br />

resource<br />

coordination<br />

Emergency Management<br />

California Office<br />

of Emergency<br />

Services<br />

Operations<br />

Centers


EM09 - Evacuation and Reentry Management<br />

County Emergency Operations Centers<br />

Emergency Management<br />

City of Roseville Police and<br />

Fire Dispatch<br />

+<br />

Local Fire/EMS Dispatch<br />

Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento County Sheriff<br />

Dept. Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

+<br />

Sacramento Regional Fire/<br />

EMS Comm. Center<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

Emergency Management<br />

County EOC<br />

emergency plan<br />

coordination<br />

+<br />

maint and constr<br />

resource response<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction<br />

Management<br />

County Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance Service<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM09 - Evacuation and Reentry Management<br />

County Emergency Operations Centers<br />

Traffic Management<br />

Other County TOC<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

emergency plan<br />

coordination<br />

+<br />

emergency traffic<br />

control information<br />

emergency plan<br />

coordination<br />

+<br />

emergency traffic<br />

control request<br />

+<br />

evacuation information<br />

Emergency Management<br />

County EOC<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

service request<br />

+<br />

evacuation information<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

schedule information<br />

+<br />

emergency transit<br />

service response<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

School Bus Dispatch<br />

+<br />

Unitrans Transit<br />

Dispatch<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


EM09 - Evacuation and Reentry Management<br />

Municipal EOC<br />

Emergency Management<br />

Emergency Management<br />

Transit Management<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

+<br />

County EOC<br />

+<br />

Local Fire/EMS<br />

Dispatch Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Private/Public<br />

Ambulance<br />

Dispatch<br />

+<br />

Sacramento City<br />

Police Department<br />

Communications<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

coordination<br />

Municipal EOC<br />

LEGEND<br />

planned and future flow<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

service request<br />

+<br />

evacuation information<br />

emergency plan<br />

coordination<br />

+<br />

emergency transit<br />

schedule information<br />

+<br />

emergency transit<br />

service response<br />

El Dorado Transit<br />

Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Local Transit Dispatch<br />

Centers<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

School Bus Dispatch<br />

+<br />

Unitrans Transit<br />

Dispatch<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

+<br />

Yuba-Sutter Transit<br />

Center<br />

existing flow<br />

user defined flow


EM09 - Evacuation and Reentry Management<br />

Municipal EOC<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho<br />

Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

+<br />

Municipal TOCs<br />

emergency plan<br />

coordination<br />

+<br />

emergency traffic<br />

control information<br />

emergency plan<br />

coordination<br />

+<br />

emergency traffic<br />

control request<br />

+<br />

evacuation<br />

information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Emergency<br />

Management<br />

Municipal EOC<br />

emergency plan<br />

coordination<br />

+<br />

maint and constr<br />

resource response<br />

emergency plan<br />

coordination<br />

+<br />

evacuation<br />

information<br />

+<br />

maint and constr<br />

resource request<br />

Maintenance and<br />

Construction Management<br />

Citrus Heights Maintenance<br />

Dispatch<br />

+<br />

City of Davis Maintenance<br />

Dispatch<br />

+<br />

City of Elk Grove<br />

Maintenance Dispatch<br />

+<br />

City of Folsom Maintenance<br />

Dispatch<br />

+<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

+<br />

City of Roseville<br />

Maintenance Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance Dispatch<br />

+<br />

City of West Sacramento<br />

Maintenance Dispatch<br />

+<br />

City of Woodland<br />

Maintenance Dispatch<br />

+<br />

Yuba City Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance<br />

Dispatch<br />

user defined flow


EM10 - Disaster Traveler Information<br />

Emergency Management<br />

County EOC<br />

+<br />

Municipal EOC<br />

evacuation<br />

information<br />

+<br />

incident<br />

information<br />

+<br />

transportation<br />

system status<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

emergency traveler<br />

information<br />

Personal Information<br />

Access<br />

School Bus<br />

Dispatch<br />

incident<br />

information for<br />

media<br />

Media<br />

emergency traveler<br />

information_ud<br />

Local Print and<br />

Broadcast Media<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


AD1 - ITS Data Mart<br />

Statewide Crash Records Information System<br />

Emergency Management<br />

City of Roseville Police and<br />

Fire Dispatch<br />

+<br />

County Sheriff<br />

Communications Centers<br />

+<br />

Local Police Dispatch<br />

+<br />

RTMC-CHP<br />

+<br />

Sacramento City Police<br />

Department<br />

Communications<br />

+<br />

Sacramento County Sheriff<br />

Dept. Communications<br />

emergency archive data<br />

archive requests<br />

+<br />

archive status<br />

Archived Data<br />

Management Subsystem<br />

Statewide<br />

Integrated<br />

Reporting<br />

System (SWITRS)<br />

LEGEND<br />

planned flow<br />

existing flow<br />

Are there regional or local crash<br />

databases?<br />

user defined flow


AD1 - ITS Data Mart<br />

Traffic Operations Data<br />

Archived Data<br />

Management Subsystem<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

maint and constr archive<br />

data<br />

archive coordination<br />

Archived Data<br />

Management Subsystem<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

archive requests<br />

+<br />

archive status<br />

traveler archive data<br />

traffic archive data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

RTMC providing archive intormation to<br />

Sacramento County<br />

user defined flow


AD1 - ITS Data Mart<br />

Traffic Operations Data<br />

Archived Data<br />

Management Subsystem<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

maint and constr<br />

archive data<br />

archive coordination<br />

Archived Data<br />

Management Subsystem<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

archive requests<br />

+<br />

archive status<br />

traveler archive data<br />

traffic archive data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Sacramento County providing archive<br />

information to RTMC<br />

user defined flow


AD1 - ITS Data Mart<br />

Statewide Data Collection Systems (HPMS, PeMS, and TASAS)<br />

Traffic Management<br />

RTMC-D3 -<br />

Traffic<br />

Operations<br />

traffic archive data<br />

archive requests<br />

+<br />

archive status<br />

Archived Data<br />

Management Subsystem<br />

California HPMS<br />

+<br />

Caltrans<br />

Performance<br />

Monitoring<br />

System (PeMS)<br />

+<br />

Traffic Accident<br />

and Surveillance<br />

Analysis System<br />

(TASAS)<br />

archived data products<br />

archived data product<br />

requests<br />

Archived Data User<br />

Systems<br />

Archive Data User<br />

Systems<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


AD1 - ITS Data Mart<br />

Regional Traffic Counts<br />

Roadway Subsystem<br />

Sacramento City<br />

Roadside<br />

Equipment<br />

+<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

roadside archive data<br />

data collection and<br />

monitoring control<br />

Archived Data<br />

Management Subsystem<br />

Regional Traffic<br />

Count Archive<br />

traffic archive data<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

archive requests<br />

+<br />

archive status<br />

Is there such a thing as a Regional Traffic<br />

Count Archive? Who owns? Who inputs?<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Archived Data User<br />

Systems<br />

Archive Data User<br />

Systems<br />

archived data<br />

products<br />

archived data<br />

product requests


AD1 - ITS Data Mart<br />

RT Transit Management Center<br />

Parking Management<br />

Light Rail Station<br />

Parking Mgmt.<br />

Maintenance and<br />

Construction<br />

Management<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento<br />

County<br />

Maintenance<br />

Service Center<br />

parking archive data<br />

archive requests<br />

+<br />

archive status<br />

archive requests<br />

+<br />

archive status<br />

maint and constr<br />

archive data<br />

Archived Data<br />

Management Subsystem<br />

RT Transit<br />

Management<br />

Center<br />

emergency archive<br />

data<br />

transit archive data<br />

archive requests<br />

+<br />

archive status<br />

Emergency Management<br />

RT Police<br />

Services<br />

Transit Management<br />

Capitol Corridor<br />

Train Stations<br />

+<br />

Light Rail Transit<br />

Management<br />

Center<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

archive requests<br />

+<br />

archive status


AD2 - ITS Data Warehouse<br />

SACOG<br />

Traffic Management<br />

Citrus Heights Traffic Operations<br />

Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

City of West Sacramento TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

+<br />

Municipal TOCs<br />

+<br />

Other County TOC<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

+<br />

Sacramento International Airport<br />

TMC<br />

+<br />

STARNET Server<br />

traffic archive data<br />

archive requests<br />

+<br />

archive status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

Archived Data<br />

Management<br />

Subsystem<br />

SACOG Data<br />

Repository<br />

archived data<br />

products<br />

archived data<br />

product requests<br />

transit archive data<br />

archive requests<br />

+<br />

archive status<br />

Archived Data User<br />

Systems<br />

Archive Data User<br />

Systems<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Local Transit Dispatch<br />

Centers<br />

+<br />

Paratransit, Inc.<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit Management<br />

Center<br />

+<br />

Unitrans Transit Dispatch<br />

+<br />

Yolo Bus Dispatch Center<br />

+<br />

Yuba-Sutter Transit Center


AD3 - ITS Virtual Data Warehouse<br />

SACOG Data Repository<br />

Archived Data<br />

Management<br />

Subsystem<br />

archive coordination<br />

Archived Data<br />

Management Subsystem<br />

SACOG Data<br />

Repository<br />

archive coordination<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Are there any other archives that the Data<br />

Repository might coordinate information<br />

with?<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Regional Transit<br />

Traffic Management<br />

City of<br />

Sacramento<br />

TOC<br />

+<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

transit vehicle location<br />

data_ud<br />

transit and fare<br />

schedules<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

Information Service<br />

Provider<br />

RT Website<br />

Transit Management<br />

Light Rail Transit<br />

Management<br />

Center<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Yolo County Bus<br />

Traffic Management<br />

City of Davis TOC<br />

+<br />

City of<br />

Sacramento TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

+<br />

City of Woodland<br />

TOC<br />

+<br />

Other County TOC<br />

transit system data<br />

Transit Management<br />

Yolo Bus<br />

Dispatch Center<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Roseville Transit<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

Traffic Management<br />

Citrus Heights<br />

Traffic<br />

Operations<br />

Center<br />

+<br />

City of Roseville<br />

TOC<br />

transit vehicle location<br />

data_ud<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle<br />

schedule performance<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Independent School District<br />

Transit Management<br />

School Bus<br />

Dispatch<br />

Transit Vehicle Subsystem<br />

School Buses<br />

transit vehicle location data<br />

+<br />

transit vehicle schedule<br />

performance<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Paratransit, Inc.<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova<br />

TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

transit vehicle<br />

location data_ud<br />

Transit Management<br />

Paratransit, Inc.<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle<br />

schedule performance<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Transit Vehicle<br />

Subsystem<br />

Paratransit Vehicle<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

LEGEND<br />

planned and future flow<br />

Data sent to Sac County and City of Sacramento<br />

and all municipalities in Sac County.<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Local Transit Systems<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Local Transit<br />

Dispatch Centers<br />

Transit Vehicle<br />

Subsystem<br />

Local Transit<br />

Vehicles<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle<br />

schedule performance<br />

transit information<br />

request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Capital Corridor Trains<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Capital Corridor<br />

Train Operations<br />

Center<br />

Transit Vehicle<br />

Subsystem<br />

Capital Corridor<br />

Trains<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle<br />

schedule performance<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

El Dorado Transit<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

transit and fare<br />

schedules<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

Transit Vehicle<br />

Subsystem<br />

El Dorado Transit<br />

Vehicles<br />

Traffic Management<br />

Other County<br />

TOC<br />

transit vehicle location<br />

data_ud<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle<br />

schedule performance<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

e-tran Transit<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Sacramento<br />

Region 511<br />

Website<br />

Traffic Management<br />

transit and fare<br />

schedules<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

e-tran Transit<br />

Vehicles<br />

City of Elk Grove<br />

TOC<br />

transit vehicle location<br />

data_ud<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Folsom Stage Lines Transit<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

+<br />

Sacramento<br />

Region 511<br />

Website<br />

Traffic Management<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Folsom Stage<br />

Lines Transit<br />

Dispatch<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Folsom Stage<br />

Line Vehicles<br />

City of Folsom<br />

TOC<br />

transit vehicle location<br />

data_ud<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Unitrans Transit<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Unitrans Transit<br />

Dispatch<br />

Transit Vehicle<br />

Subsystem<br />

Unitrans<br />

Transit<br />

Vehicles<br />

Traffic Management<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

City of Davis<br />

TOC<br />

transit vehicle location<br />

data_ud<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS1 - Transit Vehicle Tracking<br />

Yuba-Sutter Transit<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

transit and fare<br />

schedules<br />

Transit Management<br />

Yuba-Sutter<br />

Transit Center<br />

Transit Vehicle<br />

Subsystem<br />

Yuba-Sutter<br />

Transit<br />

Vehicles<br />

Traffic Management<br />

transit vehicle location<br />

data<br />

+<br />

transit vehicle schedule<br />

performance<br />

Yuba City TOC<br />

transit vehicle location<br />

data_ud<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Regional Transit<br />

Traffic Management<br />

Transit Vehicle Subsystem<br />

City of Sacramento<br />

TOC<br />

road network<br />

conditions<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit vehicle<br />

operator<br />

instructions<br />

transit vehicle<br />

schedule<br />

performance<br />

Regional Transit<br />

Bus Vehicle<br />

Maintenance and<br />

Construction Management<br />

Caltrans D3<br />

Maintenance<br />

Dispatch<br />

+<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

current asset<br />

restrictions<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

LEGEND<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Light Rail Transit<br />

Transit Management<br />

Light Rail Transit<br />

Management<br />

Center<br />

transit vehicle<br />

operator<br />

instructions<br />

transit vehicle<br />

schedule<br />

performance<br />

Transit Vehicle Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Roseville Transit<br />

Traffic Management<br />

Transit Vehicle Subsystem<br />

City of Roseville TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

transit vehicle<br />

operator<br />

instructions<br />

transit vehicle<br />

schedule<br />

performance<br />

Roseville Transit<br />

Vehicles<br />

Maintenance and Construction<br />

Management<br />

City of Roseville<br />

Maintenance Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Yolo County Bus<br />

Traffic Management<br />

Municipal TOCs<br />

road network<br />

conditions<br />

Transit Management<br />

Yolo Bus<br />

Dispatch Center<br />

transit vehicle operator<br />

instructions<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

congestion<br />

information_ud<br />

transit vehicle schedule<br />

performance<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

+<br />

Yolo County Bus<br />

Website<br />

LEGEND<br />

transit and fare<br />

schedules<br />

transit information<br />

request<br />

current asset<br />

restrictions<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

Maintenance and<br />

Construction<br />

Management<br />

County<br />

Maintenance<br />

Dispatch<br />

+<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Local Transit<br />

Traffic Management<br />

Transit Vehicle Subsystem<br />

Municipal TOCs<br />

road network<br />

conditions<br />

Transit Management<br />

Local Transit<br />

Dispatch Centers<br />

transit vehicle<br />

operator<br />

instructions<br />

Local Transit<br />

Vehicles<br />

transit vehicle<br />

schedule<br />

performance<br />

Maintenance and Construction<br />

Management<br />

Municipal Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Independent School Districts<br />

Traffic Management<br />

Transit Vehicle Subsystem<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Davis TOC<br />

+<br />

City of Elk Grove TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento TOC<br />

+<br />

City of West Sacramento TOC<br />

+<br />

City of Woodland TOC<br />

+<br />

Yuba City TOC<br />

+<br />

Municipal TOCs<br />

+<br />

Sacramento County Traffic<br />

Operations Center<br />

road network<br />

conditions<br />

Transit Management<br />

School Bus<br />

Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

transit vehicle<br />

operator<br />

instructions<br />

transit vehicle<br />

schedule<br />

performance<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

School Buses<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance<br />

Service Center


APTS2 - Transit Fixed-Route Operations<br />

El Dorado Transit<br />

Traffic Management<br />

Transit Vehicle Subsystem<br />

Municipal TOCs<br />

+<br />

Other County TOC<br />

road network<br />

conditions<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

transit vehicle<br />

operator<br />

instructions<br />

El Dorado Transit<br />

Vehicles<br />

transit vehicle<br />

schedule<br />

performance<br />

Maintenance and Construction<br />

Management<br />

County Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

e-tran Transit<br />

Traffic Management<br />

City of Elk Grove TOC<br />

road network<br />

conditions<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

transit vehicle<br />

operator<br />

instructions<br />

Transit Vehicle Subsystem<br />

e-tran Transit<br />

Vehicles<br />

transit vehicle<br />

schedule<br />

performance<br />

Maintenance and Construction<br />

Management<br />

City of Elk Grove<br />

Maintenance Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Folsom Stage Lines Transit<br />

Traffic Management<br />

City of Folsom TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Folsom Stage<br />

Lines Transit<br />

Dispatch<br />

transit vehicle<br />

operator<br />

instructions<br />

transit vehicle<br />

schedule<br />

performance<br />

Transit Vehicle Subsystem<br />

Folsom Stage Line<br />

Vehicles<br />

Maintenance and Construction<br />

Management<br />

City of Folsom<br />

Maintenance Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Unitrans Transit<br />

Traffic Management<br />

City of Davis TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Unitrans Transit<br />

Dispatch<br />

transit vehicle<br />

operator<br />

instructions<br />

Transit Vehicle Subsystem<br />

Unitrans Transit<br />

Vehicles<br />

transit vehicle<br />

schedule<br />

performance<br />

Maintenance and Construction<br />

Management<br />

City of Davis<br />

Maintenance Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS2 - Transit Fixed-Route Operations<br />

Yuba-Sutter Transit<br />

Traffic Management<br />

Municipal TOCs<br />

+<br />

Other County TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Yuba-Sutter<br />

Transit Center<br />

transit vehicle<br />

operator<br />

instructions<br />

Transit Vehicle Subsystem<br />

Yuba-Sutter Transit<br />

Vehicles<br />

transit vehicle<br />

schedule<br />

performance<br />

Maintenance and Construction<br />

Management<br />

County Maintenance<br />

Dispatch<br />

+<br />

Municipal Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

transit information<br />

request<br />

transit and fare<br />

schedules<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS3 - Demand Response Transit Operations<br />

Regional Transit<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

road network<br />

conditions<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit vehicle operator<br />

instructions<br />

transit vehicle<br />

passenger and use data<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

LEGEND<br />

planned and future flow<br />

current asset<br />

restrictions<br />

+<br />

work zone<br />

information<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

demand responsive transit<br />

request<br />

+<br />

selected routes<br />

+<br />

transit information request<br />

Information Service<br />

Provider<br />

Sacramento<br />

Region 511<br />

Website<br />

+<br />

STARNET ISP<br />

existing flow<br />

user defined flow


APTS3 - Demand Response Transit Operations<br />

Paratransit, Inc.<br />

Traffic Management<br />

City of Sacramento<br />

TOC<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

+<br />

STARNET Server<br />

road network<br />

conditions<br />

Transit Management<br />

Paratransit, Inc.<br />

transit vehicle operator<br />

instructions<br />

transit vehicle<br />

passenger and use data<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

Transit Vehicle<br />

Subsystem<br />

Paratransit<br />

Vehicle<br />

Information Service<br />

Provider<br />

Maintenance and<br />

Construction Management<br />

City of Sacramento<br />

Maintenance<br />

Dispatch<br />

+<br />

Sacramento County<br />

Maintenance<br />

Service Center<br />

current asset<br />

restrictions<br />

+<br />

work zone<br />

information<br />

LEGEND<br />

demand responsive<br />

transit request<br />

+<br />

selected routes<br />

+<br />

transit information<br />

request<br />

Private Traveler<br />

Information<br />

Service<br />

Providers<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS3 - Demand Response<br />

Roseville Transit<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

transit vehicle operator<br />

instructions<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

transit vehicle<br />

passenger and use data<br />

Maintenance and<br />

Construction Management<br />

City of Roseville<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway<br />

maintenance status<br />

+<br />

work zone<br />

information<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

demand responsive<br />

transit request<br />

+<br />

transit information<br />

request<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS3 - Demand Response<br />

El Dorado Transit Transit<br />

Traffic Management<br />

Municipal TOCs<br />

+<br />

Other County TOC<br />

road network<br />

conditions<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

transit vehicle operator<br />

instructions<br />

Transit Vehicle<br />

Subsystem<br />

El Dorado Transit<br />

Vehicles<br />

transit vehicle<br />

passenger and use<br />

data<br />

Maintenance and<br />

Construction Management<br />

County<br />

Maintenance<br />

Dispatch<br />

+<br />

Municipal<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

demand responsive<br />

transit request<br />

+<br />

transit information<br />

request<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS3 - Demand Response<br />

e-tran Transit Transit<br />

Traffic Management<br />

City of Elk Grove<br />

TOC<br />

road network<br />

conditions<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

transit vehicle operator<br />

instructions<br />

Transit Vehicle<br />

Subsystem<br />

e-tran Transit<br />

Vehicles<br />

transit vehicle<br />

passenger and use<br />

data<br />

Maintenance and<br />

Construction Management<br />

City of Elk Grove<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

demand responsive<br />

transit request<br />

+<br />

transit information<br />

request<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS3 - Demand Response<br />

Folsom Stage Lines Transit<br />

Traffic Management<br />

City of Folsom TOC<br />

road network<br />

conditions<br />

Transit Management<br />

Folsom Stage<br />

Lines Transit<br />

Dispatch<br />

transit vehicle operator<br />

instructions<br />

Transit Vehicle<br />

Subsystem<br />

Folsom Stage<br />

Line Vehicles<br />

transit vehicle<br />

passenger and use<br />

data<br />

Maintenance and<br />

Construction Management<br />

City of Folsom<br />

Maintenance<br />

Dispatch<br />

current asset<br />

restrictions<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

demand responsive<br />

transit plan<br />

+<br />

transit and fare<br />

schedules<br />

demand responsive<br />

transit request<br />

+<br />

transit information<br />

request<br />

Information Service<br />

Provider<br />

Municipal<br />

Websites<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS4 - Transit Passenger and Fare Management<br />

Regional Transit<br />

Financial Institution<br />

Financial<br />

Institutions<br />

payment request<br />

transaction status<br />

payment violation<br />

notification<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

fare and payment<br />

status<br />

+<br />

request for bad tag list<br />

+<br />

transit vehicle<br />

passenger and use data<br />

bad tag list<br />

+<br />

fare management<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

+<br />

Regional Transit<br />

LRT Vehicle<br />

Enforcement Agency<br />

RT Police Services<br />

transit fare<br />

information<br />

transit fare and<br />

passenger status<br />

payment<br />

request for<br />

payment<br />

Remote Traveler<br />

Support<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

RT Transit<br />

Kiosks<br />

request for payment<br />

payment<br />

Traveler Card<br />

Sacramento<br />

Regional Traveler<br />

Card


APTS4 - Transit Passenger and Fare Management<br />

Paratransit, Inc.<br />

Financial Institution<br />

Financial<br />

Institutions<br />

payment request<br />

transaction status<br />

Transit Management<br />

Paratransit, Inc.<br />

fare and payment<br />

status<br />

+<br />

request for bad tag list<br />

+<br />

transit vehicle<br />

passenger and use data<br />

bad tag list<br />

+<br />

fare management<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Paratransit<br />

Vehicle<br />

transit fare<br />

information<br />

transit fare and<br />

passenger status<br />

payment<br />

request for<br />

payment<br />

Remote Traveler<br />

Support<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

RT Transit<br />

Kiosks<br />

request for payment<br />

payment<br />

Traveler Card<br />

Sacramento<br />

Regional Traveler<br />

Card


APTS4 - Transit Passenger and Fare Management<br />

Yolo Bus Dispatch<br />

Financial Institution<br />

Financial<br />

Institutions<br />

payment request<br />

transaction status<br />

Transit Management<br />

Yolo Bus<br />

Dispatch Center<br />

fare and payment<br />

status<br />

+<br />

request for bad tag list<br />

+<br />

transit vehicle<br />

passenger and use data<br />

bad tag list<br />

+<br />

fare management<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

transit fare<br />

information<br />

transit fare and<br />

passenger status<br />

payment<br />

request for<br />

payment<br />

Remote Traveler<br />

Support<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

RT Transit<br />

Kiosks<br />

request for payment<br />

payment<br />

Traveler Card<br />

Sacramento<br />

Regional Traveler<br />

Card


APTS5 - Transit Security<br />

Regional Transit<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

emergency acknowledge<br />

Emergency Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

emergency<br />

acknowledge<br />

Remote Traveler<br />

Support<br />

RT Transit<br />

Kiosks<br />

emergency notification<br />

emergency notification<br />

secure area surveillance<br />

data<br />

secure area<br />

surveillance control<br />

secure area surveillance<br />

control<br />

secure area<br />

surveillance data<br />

Emergency Management<br />

RT Police<br />

Services<br />

transit emergency data<br />

incident response status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Light Rail Tranist<br />

Emergency Management<br />

RT Police<br />

Services<br />

transit emergency data<br />

Transit Management<br />

Light Rail Transit<br />

Management<br />

Center<br />

emergency<br />

acknowledge<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

incident response status<br />

emergency notification<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

County School Districts<br />

Emergency Management<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Police<br />

Dispatch<br />

+<br />

Sacramento City<br />

Police Department<br />

Communications<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

transit emergency<br />

data<br />

incident response<br />

status<br />

Transit Management<br />

Sacramento<br />

Metro AQMD<br />

emergency<br />

acknowledge<br />

emergency notification<br />

Transit Vehicle<br />

Subsystem<br />

County AQMD<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

El Dorado Transit<br />

Emergency Management<br />

County Sheriff<br />

Communications<br />

Centers<br />

transit emergency data<br />

Transit Emergency Management<br />

Management<br />

El Dorado Transit<br />

Dispatch El Dorado<br />

Transit<br />

Dispatch<br />

emergency<br />

acknowledge<br />

emergency notification<br />

Transit Vehicle<br />

Subsystem<br />

El Dorado Transit<br />

Vehicles<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

e-tran Transit<br />

Emergency Management<br />

Local Police<br />

Dispatch<br />

transit emergency data<br />

Transit Emergency Management<br />

Management<br />

e-tran Transit<br />

e-tran Center Transit<br />

Center<br />

emergency<br />

acknowledge<br />

Transit Vehicle<br />

Subsystem<br />

e-tran Transit<br />

Vehicles<br />

emergency notification<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Folsom Stage Lines Transit<br />

Emergency Management<br />

Local Police<br />

Dispatch<br />

transit emergency data<br />

Transit Emergency Management<br />

Management<br />

Folsom Stage<br />

Lines Folsom Transit Stage<br />

Lines Dispatch Transit<br />

Dispatch<br />

emergency<br />

acknowledge<br />

emergency notification<br />

Transit Vehicle<br />

Subsystem<br />

Folsom Stage<br />

Line Vehicles<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Roseville Transit<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

emergency acknowledge<br />

Emergency Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

emergency<br />

acknowledge<br />

Remote Traveler<br />

Support<br />

emergency notification<br />

emergency notification<br />

secure area surveillance<br />

data<br />

secure area<br />

surveillance control<br />

secure area sensor<br />

control<br />

secure area<br />

surveillance data<br />

Emergency Management<br />

transit emergency data<br />

City of Roseville<br />

Police and Fire<br />

Dispatch<br />

incident response status<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Folsom Stage Lines Transit<br />

Emergency Management<br />

Local Police<br />

Dispatch<br />

transit emergency data<br />

Transit Emergency Management<br />

Management<br />

Unitrans Transit<br />

Unitrans Dispatch Transit<br />

Dispatch<br />

emergency<br />

acknowledge<br />

Transit Vehicle<br />

Subsystem<br />

Unitrans Transit<br />

Vehicles<br />

emergency notification<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Yolo County Bus<br />

Emergency Management<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Police<br />

Dispatch<br />

transit emergency data<br />

Transit Emergency Management<br />

Management<br />

Yolo Bus<br />

Dispatch Yolo Bus Center<br />

Dispatch Center<br />

emergency<br />

acknowledge<br />

emergency notification<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS5 - Transit Security<br />

Yuba-Sutter Transit<br />

Emergency Management<br />

County Sheriff<br />

Communications<br />

Centers<br />

+<br />

Local Police<br />

Dispatch<br />

transit emergency data<br />

Emergency Transit Management<br />

Yuba-Sutter<br />

Transit Center<br />

emergency<br />

acknowledge<br />

emergency notification<br />

Transit Vehicle<br />

Subsystem<br />

Yuba-Sutter<br />

Transit Vehicles<br />

incident response<br />

status<br />

secure area surveillance<br />

control<br />

secure area surveillance<br />

data<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

Regional Transit<br />

Transit Management<br />

Light Rail Transit<br />

Management<br />

Center<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

County School Districts<br />

Transit Management<br />

School Bus<br />

Dispatch<br />

request for vehicle measures<br />

Transit Vehicle<br />

Subsystem<br />

School Buses<br />

transit vehicle conditions<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

Roseville Transit<br />

Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

El Dorado/ Yuba-Sutter Transit<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

El Dorado Transit<br />

Vehicles<br />

Transit Management<br />

Yuba-Sutter<br />

Transit Center<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Yuba-Sutter<br />

Transit Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

e-tran/ Folsom Stage Lines Transit<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

e-tran Transit<br />

Vehicles<br />

Transit Management<br />

Folsom Stage<br />

Lines Transit<br />

Dispatch<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Folsom Stage<br />

Line Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS6 - Transit Maintenance<br />

Unitrans/ Yolo County Bus<br />

Transit Management<br />

Yolo Bus<br />

Dispatch Center<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

Transit Management<br />

Unitrans Transit<br />

Dispatch<br />

request for vehicle measures<br />

transit vehicle conditions<br />

Transit Vehicle<br />

Subsystem<br />

Unitrans Transit<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Regional Transit<br />

Transit Management<br />

Capital Corridor Train<br />

Operations Center<br />

+<br />

e-tran Transit Center<br />

+<br />

Light Rail Transit<br />

Management Center<br />

+<br />

Paratransit, Inc.<br />

+<br />

Private Transit Provider<br />

Dispatch<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

Taxi Dispatch<br />

+<br />

Yolo Bus Dispatch Center<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

multimodal service<br />

data<br />

transit multimodal<br />

information<br />

Multimodal<br />

Transportation Service<br />

Provider<br />

Sacramento<br />

International Airport<br />

TMC<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Regional Transit<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

traffic control<br />

priority request<br />

+<br />

transit system data<br />

traffic control<br />

priority status<br />

local signal priority<br />

request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Traffic Management<br />

City of<br />

Sacramento TOC<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

Roadway Subsystem<br />

Sacramento City<br />

Roadside<br />

Equipment<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Regional Transit<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

traffic control<br />

priority request<br />

+<br />

transit system data<br />

traffic control<br />

priority status<br />

local signal priority<br />

request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

Roadway Subsystem<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Light Rail Transit<br />

Transit Management<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Local Transit<br />

Dispatch Centers<br />

+<br />

RT Transit<br />

Management<br />

Center<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

Light Rail Transit<br />

Management<br />

Center<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

parking lot data request<br />

Parking Management<br />

Light Rail Station<br />

Parking Mgmt.<br />

parking information<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

traffic control<br />

priority request<br />

+<br />

transit system data<br />

Traffic Management<br />

Sacramento<br />

County Traffic<br />

Operations<br />

Center<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

local signal priority<br />

request<br />

Roadway Subsystem<br />

Sacramento<br />

County Roadside<br />

Equipment<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Roseville Transit<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

+<br />

Taxi Dispatch<br />

transit service<br />

coordination<br />

Transit Management<br />

Roseville Transit<br />

Management<br />

Center (Dispatch)<br />

transit vehicle schedule<br />

performance<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

transit service<br />

coordination<br />

Do they coordinate transit<br />

service with any other transit<br />

agencies?<br />

traffic control<br />

priority request<br />

+<br />

transit system data<br />

local signal priority<br />

request<br />

LEGEND<br />

planned and future flow<br />

Traffic Management<br />

City of Roseville<br />

TOC<br />

request for right-of-way<br />

+<br />

signal control status<br />

signal control data<br />

Roadway Subsystem<br />

City of Roseville<br />

Roadside<br />

Equipment<br />

existing flow<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Yuba Sutter/ Yolo Bus Transit<br />

Transit Management<br />

Yolo Bus<br />

Dispatch Center<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

+<br />

Yuba-Sutter Transit<br />

Center<br />

Transit Management<br />

Yuba-Sutter<br />

Transit Center<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

+<br />

Yolo Bus Dispatch<br />

Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

Capital Corridor Train Operations<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit service<br />

coordination<br />

Transit Management<br />

Capital Corridor<br />

Train Operations<br />

Center<br />

transit service<br />

coordination<br />

Any Other Transit Agencies that they should<br />

coordinate with?<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS7 - Multi-modal Coordination<br />

e-tran / Folsom Stage Lines<br />

Transit Management<br />

RT Transit<br />

Management<br />

Center<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

Any Transit Agencies that they should coordinate<br />

with?<br />

Transit Management<br />

transit service<br />

coordination<br />

transit service<br />

coordination<br />

Transit Management<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Regional Transit<br />

Information Service<br />

Provider<br />

RT Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

RT Transit<br />

Management Center<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

Bus Vehicle<br />

Personal Information<br />

Access<br />

personal transit<br />

information<br />

transit traveler<br />

request<br />

User Personal<br />

Computing<br />

Devices<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

transit information user<br />

request<br />

transit traveler<br />

information<br />

transit information user<br />

request<br />

Remote Traveler Support<br />

RT Passenger<br />

Information Signs<br />

+<br />

RT Transit Kiosks<br />

+<br />

RT Transit<br />

Monitors<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Light Rail Transit<br />

Information Service<br />

Provider<br />

RT Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

Light Rail Transit<br />

Management Center<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

Regional Transit<br />

LRT Vehicle<br />

Personal Information<br />

Access<br />

personal transit<br />

information<br />

traveler information<br />

Remote Traveler<br />

Support<br />

User Personal<br />

Computing<br />

Devices<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

transit information user<br />

request<br />

LEGEND<br />

traveler request<br />

RT Passenger<br />

Information<br />

Signs<br />

+<br />

RT Transit<br />

Kiosks<br />

+<br />

RT Transit<br />

Monitors


APTS8 - Transit Traveler Information<br />

Paratransit, Inc.<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

Transit Management<br />

Paratransit, Inc.<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Paratransit<br />

Vehicle<br />

transit information<br />

request<br />

transit traveler request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

El Dorado Transit<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

El Dorado Transit<br />

Dispatch<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

El Dorado Transit<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

e-tran Transit<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

e-tran Transit<br />

Center<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

e-tran Transit<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Roseville<br />

Information Service<br />

Provider<br />

City of Roseville<br />

Website<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

Roseville Transit<br />

Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Folsom Transit<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

Folsom Stage<br />

Line Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Yolo County Bus<br />

Information Service<br />

Provider<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

Transit Management<br />

Yolo Bus Dispatch<br />

Center<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

Transit Vehicle<br />

Subsystem<br />

Yolo County<br />

Buses<br />

transit information<br />

request<br />

transit traveler request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APTS8 - Transit Traveler Information<br />

Yuba-Sutter Transit<br />

Information Service<br />

Provider<br />

Municipal Websites<br />

+<br />

Sacramento Region<br />

511 Website<br />

+<br />

STARNET ISP<br />

transit and fare<br />

schedules<br />

+<br />

transit request<br />

confirmation<br />

transit information<br />

request<br />

Transit Management<br />

Yuba-Sutter Transit<br />

Center<br />

transit schedule<br />

information<br />

+<br />

transit traveler<br />

information<br />

transit traveler request<br />

Transit Vehicle<br />

Subsystem<br />

Yuba-Sutter<br />

Transit Vehicles<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATIS1 - Broadcast Traveler Information<br />

STARNET(Inputs) (1 of 2)<br />

Maintenance and Construction<br />

Management<br />

Caltrans D3 Maintenance<br />

Dispatch<br />

+<br />

Citrus Heights Maintenance<br />

Dispatch<br />

+<br />

City of Elk Grove Maintenance<br />

Dispatch<br />

+<br />

City of Folsom Maintenance<br />

Dispatch<br />

+<br />

City of Rancho Cordova<br />

Maintenance Dispatch<br />

+<br />

City of Roseville Maintenance<br />

Dispatch<br />

+<br />

City of Sacramento Maintenance<br />

Dispatch<br />

+<br />

City of West Sacramento<br />

Maintenance Dispatch<br />

+<br />

Municipal Maintenance Dispatch<br />

+<br />

Sacramento County Maintenance<br />

Service Center<br />

+<br />

Sacramento International Airport<br />

Maintenance Dispatch<br />

current asset<br />

restrictions<br />

+<br />

maint and constr work<br />

plans<br />

+<br />

roadway maintenance<br />

status<br />

+<br />

work zone information<br />

Traffic<br />

Management<br />

STARNET<br />

Server<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow<br />

road network<br />

conditions_ud<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Elk Grove<br />

TOC<br />

+<br />

City of Folsom TOC<br />

+<br />

City of Rancho<br />

Cordova TOC<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

City of West<br />

Sacramento TOC<br />

+<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

+<br />

Sacramento<br />

International Airport<br />

TMC


ATIS1 - Broadcast Traveler Information<br />

STARNET (Inputs) (2 of 2)<br />

Emergency Management<br />

Traffic Management<br />

Transit Management<br />

RTMC-CHP<br />

+<br />

Sacramento<br />

County<br />

Telecommunicatio<br />

ns Center<br />

(DISPATCH)<br />

+<br />

Sacramento<br />

Regional Fire/ EMS<br />

Comm. Center<br />

incident information<br />

STARNET Server<br />

transit system data<br />

Capitol Corridor<br />

Train Stations<br />

+<br />

e-tran Transit Center<br />

+<br />

Folsom Stage Lines<br />

Transit Dispatch<br />

+<br />

Light Rail Transit<br />

Management Center<br />

+<br />

Roseville Transit<br />

Management Center<br />

(Dispatch)<br />

+<br />

RT Transit<br />

Management Center<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATIS1 - Broadcast Traveler Information<br />

STARNET (Outputs)<br />

Traffic Management<br />

STARNET Server<br />

road network<br />

conditions<br />

Information Service<br />

Provider<br />

Private Traveler<br />

Information Service<br />

Providers<br />

+<br />

STARNET ISP<br />

broadcast information<br />

Personal Information<br />

Access<br />

User Personal<br />

Computing<br />

Devices<br />

Media<br />

traveler<br />

information for<br />

media<br />

LEGEND<br />

planned and future flow<br />

Local Print and<br />

Broadcast Media<br />

existing flow<br />

user defined flow


ATIS1 - Broadcast Traveler Information<br />

Website (Outputs)<br />

Information Service Provider<br />

Caltrans D3 Website<br />

+<br />

City of Citrus Heights Website<br />

+<br />

City of Roseville Website<br />

+<br />

City of Sacramento Website<br />

+<br />

City of West Sacramento Website<br />

+<br />

Municipal Websites<br />

+<br />

Sacramento County Website<br />

+<br />

Sacramento International Airport Website<br />

broadcast information<br />

Personal Information<br />

Access<br />

User Personal<br />

Computing<br />

Devices<br />

Media<br />

Local Print and<br />

Broadcast Media<br />

traveler<br />

information for<br />

media<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATIS2 - Interactive Traveler Information<br />

Personal Information<br />

Access<br />

User Personal<br />

Computing<br />

Devices<br />

Remote Traveler<br />

Support<br />

RT Transit<br />

Kiosks<br />

LEGEND<br />

traveler information<br />

traveler profile<br />

+<br />

traveler request<br />

traveler information<br />

traveler request<br />

Information Service<br />

Provider<br />

STARNET ISP<br />

request fare and<br />

price information<br />

fare and price<br />

information<br />

Traffic Management<br />

Citrus Heights Traffic<br />

Operations Center<br />

+<br />

City of Roseville TOC<br />

+<br />

City of Sacramento<br />

TOC<br />

+<br />

Municipal TOCs<br />

+<br />

RTMC-D3 - Traffic<br />

Operations<br />

+<br />

Sacramento County<br />

Traffic Operations<br />

Center<br />

+<br />

Sacramento<br />

International Airport<br />

TMC<br />

planned and future flow<br />

existing flow<br />

user defined flow


ATIS8 – Dynamic RideSharing<br />

Personal Information<br />

Access<br />

User Personal<br />

Computing<br />

Devices<br />

trip confirmation<br />

+<br />

trip request<br />

Information Service<br />

Provider<br />

STARNET ISP<br />

trip plan<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

What other elements would be involved in this<br />

ridesharing?<br />

user defined flow


CVO10 - HAZMAT Management<br />

Commercial Vehicles<br />

Fleet and Freight<br />

Management<br />

Commercial<br />

Vehicle Fleet<br />

Dispatch<br />

Systems<br />

hazmat information<br />

hazmat information<br />

request<br />

Emergency Management<br />

RTMC-CHP<br />

+<br />

Sacramento County<br />

Sheriff Dept.<br />

Communications<br />

+<br />

Sacramento County<br />

Telecommunications<br />

Center (DISPATCH)<br />

+<br />

Sacramento Regional<br />

Fire/ EMS Comm.<br />

Center<br />

hazmat spill<br />

notification<br />

emergency<br />

notification<br />

commercial vehicle<br />

data request<br />

+<br />

vehicle location<br />

Commercial Vehicle<br />

Subsystem<br />

Commercial<br />

Vehicles<br />

commercial vehicle<br />

data<br />

Vehicle<br />

Vehicles<br />

emergency<br />

acknowledge<br />

+<br />

emergency data<br />

request<br />

LEGEND<br />

planned and future flow<br />

existing flow<br />

user defined flow


APPENDIX I: EQUIPMENT PACKAGES ASSIGNED TO ELEMENTS:<br />

This appendix contains two tables. The first is the mapping of equipment packages (or functions) to<br />

elements. The second is the definition of each of the equipment packages identified in the first table.<br />

Equipment Packages Selections by Element<br />

Element<br />

Air Quality Website<br />

Airport Dispatch Center<br />

Airport Dispatch Center<br />

Airport Dispatch Center<br />

California HPMS<br />

California HPMS<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

Caltrans D3 Data Server<br />

Caltrans D3 Data Server<br />

Caltrans D3 Data Server<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Website<br />

Caltrans D3 Website<br />

Equipment Package<br />

Basic Information Broadcast<br />

Emergency Dispatch<br />

Emergency Response Management<br />

Incident Command<br />

Government Reporting Systems Support<br />

ITS Data Repository<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

ISP Data Collection<br />

MCM Automated Treatment System Control<br />

MCM Environmental Information Collection<br />

MCM Environmental Information Processing<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Winter Maintenance Management<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

MCM Work Zone Safety Management<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Vehicle Location Tracking<br />

MCV Vehicle Safety Monitoring<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Winter Maintenance<br />

MCV Work Zone Support<br />

Basic Information Broadcast<br />

ISP Emergency Traveler Information


Element<br />

Caltrans Performance Monitoring System (PeMS)<br />

Caltrans Performance Monitoring System (PeMS)<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Capital Corridor Train Operations Center<br />

Capital Corridor Train Operations Center<br />

Capital Corridor Train Operations Center<br />

Capital Corridor Train Operations Center<br />

Capital Corridor Train Operations Center<br />

Capital Corridor Trains<br />

Capital Corridor Trains<br />

Capital Corridor Trains<br />

Capitol Corridor Train Stations<br />

CHP Vehicles<br />

CHP Vehicles<br />

CHP Website<br />

CHP Website<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Equipment Package<br />

Government Reporting Systems Support<br />

ITS Data Repository<br />

Roadway Basic Surveillance<br />

Roadway Emissions Monitoring<br />

Roadway Equipment Coordination<br />

Roadway Freeway Control<br />

Roadway HOV Control<br />

Roadway Incident Detection<br />

Roadway Probe Beacons<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Safety<br />

Roadway Work Zone Traffic Control<br />

Standard Rail Crossing<br />

Transit Center Fixed­Route Operations<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Transit Data Collection<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Basic Information Broadcast<br />

ISP Emergency Traveler Information<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control


Element<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

City of Citrus Heights Website<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

Equipment Package<br />

Collect Traffic Surveillance<br />

Rail Operations Coordination<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control


Element<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Folsom Field Equipment<br />

City of Folsom Field Equipment<br />

City of Folsom Field Equipment<br />

City of Folsom Field Equipment<br />

City of Folsom Field Equipment<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

Equipment Package<br />

Standard Rail Crossing<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance


Element<br />

City of Rancho Cordova Field Equipment<br />

City of Rancho Cordova Field Equipment<br />

City of Rancho Cordova Field Equipment<br />

City of Rancho Cordova Field Equipment<br />

City of Rancho Cordova Field Equipment<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova Maintenance Dispatch<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

Equipment Package<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

MCM Environmental Information Collection<br />

MCM Environmental Information Processing<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Center Secure Area Alarm Support<br />

Center Secure Area Sensor Management<br />

Center Secure Area Surveillance<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Environmental Monitoring<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing


Element<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville Website<br />

City of Roseville Website<br />

City of Roseville Website<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento TOC<br />

Equipment Package<br />

Incident Command<br />

Roadway Basic Surveillance<br />

Roadway Environmental Monitoring<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Probe Beacons<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

Standard Rail Crossing<br />

Collect Traffic Surveillance<br />

HRI Traffic Management<br />

MCM Environmental Information Collection<br />

MCM Environmental Information Processing<br />

Rail Operations Coordination<br />

TMC Environmental Monitoring<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Multimodal Coordination<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

MCM Incident Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Vehicle Location Tracking<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Work Zone Support<br />

Collect Traffic Surveillance


Element<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento Website<br />

City of Sacramento Website<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Maintenance Dispatch<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento Roadside Equipment<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento Website<br />

Equipment Package<br />

HRI Traffic Management<br />

Rail Operations Coordination<br />

TMC Environmental Monitoring<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Multimodal Coordination<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast<br />

ISP Emergency Traveler Information<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Work Zone Traffic Control<br />

Standard Rail Crossing<br />

Collect Traffic Surveillance<br />

HRI Traffic Management<br />

Rail Operations Coordination<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast


Element<br />

City of West Sacramento Website<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

Commercial Vehicle Fleet Dispatch Systems<br />

Commercial Vehicles<br />

County AQMD<br />

County EOC<br />

County EOC<br />

County EOC<br />

County EOC<br />

County EOC<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Vehicles<br />

County Maintenance Vehicles<br />

County Maintenance Vehicles<br />

County Roadside Equipment<br />

County Sheriff Communications Centers<br />

Equipment Package<br />

ISP Emergency Traveler Information<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Fleet HAZMAT Management<br />

On­board Cargo Monitoring<br />

Emissions Data Management<br />

Emergency Data Collection<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

MCM Incident Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Vehicle Location Tracking<br />

MCV Work Zone Support<br />

Roadway Work Zone Traffic Control<br />

Center Secure Area Alarm Support


Element<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Dispatch<br />

El Dorado Transit Vehicles<br />

El Dorado Transit Vehicles<br />

El Dorado Transit Vehicles<br />

El Dorado Transit Vehicles<br />

El Dorado Transit Vehicles<br />

El Dorado Transit Vehicles<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Center<br />

e­tran Transit Vehicles<br />

e­tran Transit Vehicles<br />

e­tran Transit Vehicles<br />

e­tran Transit Vehicles<br />

Equipment Package<br />

Center Secure Area Sensor Management<br />

Center Secure Area Surveillance<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Environmental Monitoring<br />

Emergency Response Management<br />

Emergency Routing<br />

Incident Command<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Paratransit Operations<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Center Secure Area Alarm Support<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Paratransit Operations<br />

On­board Transit Information Services


Element<br />

e­tran Transit Vehicles<br />

e­tran Transit Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Line Vehicles<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Folsom Stage Lines Transit Dispatch<br />

Freeway Service Patrol Vehicles<br />

Freeway Service Patrol Vehicles<br />

Light Rail Station Parking Mgmt.<br />

Light Rail Station Parking Mgmt.<br />

Light Rail Station Parking Mgmt.<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Light Rail Transit Management Center<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Dispatch Centers<br />

Local Fire/EMS Vehicles<br />

Local Fire/EMS Vehicles<br />

Equipment Package<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Paratransit Operations<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Center Secure Area Alarm Support<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Parking Electronic Payment<br />

Parking Management<br />

Parking Surveillance<br />

Emergency Response Management<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

Emergency Call­Taking<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing<br />

Incident Command<br />

On­board EV En Route Support<br />

On­board EV Incident Management


Element<br />

Local Law Enforcement Vehicles<br />

Local Law Enforcement Vehicles<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Police Dispatch<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Dispatch Centers<br />

Local Transit Vehicles<br />

Local Transit Vehicles<br />

Municipal EOC<br />

Municipal EOC<br />

Municipal EOC<br />

Municipal EOC<br />

Municipal EOC<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Vehicles<br />

Equipment Package<br />

Communication<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Center Secure Area Alarm Support<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing<br />

Incident Command<br />

Emergency Response Management<br />

Transit Center Fixed­Route Operations<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Transit Trip Monitoring<br />

Emergency Data Collection<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

Roadway Basic Surveillance<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Data Collection<br />

MCM Incident Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

MCV Roadway Maintenance and<br />

Construction


Element<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal Websites<br />

Municipal Websites<br />

Paratransit Vehicle<br />

Paratransit Vehicle<br />

Paratransit Vehicle<br />

Paratransit Vehicle<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Paratransit, Inc.<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Dispatch<br />

Private/Public Ambulance Vehicles<br />

Private/Public Ambulance Vehicles<br />

Regional Emergency Operations Center<br />

Regional Emergency Operations Center<br />

Regional Emergency Operations Center<br />

Regional Emergency Operations Center<br />

Regional Emergency Operations Center<br />

Regional Traffic Count Archive<br />

Equipment Package<br />

MCV Vehicle Location Tracking<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Work Zone Support<br />

Collect Traffic Surveillance<br />

HRI Traffic Management<br />

Rail Operations Coordination<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

On­board Paratransit Operations<br />

On­board Transit Fare and Load<br />

Management<br />

On­board Transit Information Services<br />

On­board Transit Trip Monitoring<br />

Transit Center Fare and Load Management<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Operations<br />

Emergency Dispatch<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Emergency Data Collection<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

Government Reporting Systems Support


Element<br />

Regional Traffic Count Archive<br />

Regional Traffic Count Archive<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit Bus Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Regional Transit LRT Vehicle<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Management Center (Dispatch)<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

Roseville Transit Vehicles<br />

RT Passenger Information Signs<br />

RT Police Services<br />

RT Police Services<br />

RT Police Services<br />

RT Police Services<br />

RT Security Monitoring Equipment<br />

Equipment Package<br />

ITS Data Repository<br />

Traffic and Roadside Data Archival<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Paratransit Operations<br />

On­board Transit Fare and Load<br />

Management<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Signal Priority<br />

On­board Transit Trip Monitoring<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Transit Fare and Load<br />

Management<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Signal Priority<br />

On­board Transit Trip Monitoring<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Paratransit Operations<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Signal Priority<br />

On­board Transit Trip Monitoring<br />

Remote Transit Information Services<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Response Management<br />

Incident Command<br />

Field Secure Area Surveillance


Element<br />

RT Transit Kiosks<br />

RT Transit Kiosks<br />

RT Transit Kiosks<br />

RT Transit Kiosks<br />

RT Transit Kiosks<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Management Center<br />

RT Transit Monitors<br />

RT Website<br />

RT Website<br />

RT Website<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­CHP<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

Equipment Package<br />

Remote Interactive Information Reception<br />

Remote Transit Fare Management<br />

Remote Transit Information Services<br />

Remote Traveler Security<br />

Traveler Secure Area Surveillance<br />

Center Secure Area Alarm Support<br />

Center Secure Area Surveillance<br />

Transit Center Fare and Load Management<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

Remote Transit Information Services<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Environmental Monitoring<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

Mayday Support<br />

Service Patrol Management<br />

TMC Regional Traffic Control<br />

Basic Information Broadcast<br />

Collect Traffic Surveillance<br />

Government Reporting Systems Support<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

ITS Data Repository<br />

MCM Environmental Information Collection<br />

MCM Environmental Information Processing<br />

TMC Environmental Monitoring<br />

TMC Evacuation Support<br />

TMC Freeway Management


Element<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

SACOG Data Repository<br />

SACOG Data Repository<br />

SACOG Data Repository<br />

SACOG Data Repository<br />

Sacramento City Fire Vehicles<br />

Sacramento City Fire Vehicles<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Vehicles<br />

Sacramento City Police Vehicles<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Equipment Package<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Regional Traffic Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic and Roadside Data Archival<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Government Reporting Systems Support<br />

ITS Data Repository<br />

On­Line Analysis and Mining<br />

Traffic and Roadside Data Archival<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Advanced Rail Crossing<br />

Roadway Basic Surveillance<br />

Roadway Data Collection<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

Standard Rail Crossing<br />

MCM Data Collection<br />

MCM Environmental Information Processing<br />

MCM Incident Management<br />

MCM Maintenance Decision Support


Element<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Service Center<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County Telecommunications Center<br />

Equipment Package<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Winter Maintenance Management<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Vehicle Location Tracking<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Work Zone Support<br />

Advanced Rail Crossing<br />

Roadway Basic Surveillance<br />

Roadway Data Collection<br />

Roadway Environmental Monitoring<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Probe Beacons<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

Standard Rail Crossing<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing<br />

Incident Command<br />

Mayday Support<br />

On­board EV En Route Support<br />

On­board EV Incident Management<br />

Communication<br />

Emergency Call­Taking


Element<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Telecommunications Center<br />

(DISPATCH)<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Traffic Operations Center<br />

Sacramento County Website<br />

Sacramento County Website<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Roadside<br />

Equipment Package<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Incident Command<br />

Mayday Support<br />

MCM Environmental Information Processing<br />

Basic Information Broadcast<br />

Collect Traffic Surveillance<br />

Government Reporting Systems Support<br />

HRI Traffic Management<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

ITS Data Repository<br />

MCM Environmental Information Collection<br />

MCM Environmental Information Processing<br />

On­Line Analysis and Mining<br />

Rail Operations Coordination<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Multimodal Coordination<br />

TMC Probe Information Collection<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

Traffic and Roadside Data Archival<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

MCM Incident Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Work Zone Management<br />

Roadway Basic Surveillance


Element<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport Website<br />

Sacramento International Airport Website<br />

Sacramento Metro AQMD<br />

Sacramento Metro AQMD<br />

Sacramento Region 511 Website<br />

Sacramento Region 511 Website<br />

Sacramento Region 511 Website<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

Sacramento Regional Fire/ EMS Comm. Center<br />

School Bus Dispatch<br />

School Bus Dispatch<br />

School Bus Dispatch<br />

School Bus Dispatch<br />

School Bus Dispatch<br />

School Bus Dispatch<br />

School Buses<br />

School Buses<br />

School Buses<br />

School Buses<br />

STARNET ISP<br />

STARNET ISP<br />

STARNET ISP<br />

Equipment Package<br />

Roadway Incident Detection<br />

Roadway Probe Beacons<br />

Basic Information Broadcast<br />

Collect Traffic Surveillance<br />

Interactive Infrastructure Information<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Multimodal Coordination<br />

TMC Probe Information Collection<br />

TMC Regional Traffic Control<br />

TMC Toll/Parking Coordination<br />

Traffic Data Collection<br />

Basic Information Broadcast<br />

Interactive Infrastructure Information<br />

Emissions Data Collection<br />

Emissions Data Management<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

Traveler Telephone Information<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Evacuation Support<br />

Emergency Response Management<br />

Emergency Routing<br />

Incident Command<br />

Mayday Support<br />

Transit Center Fixed­Route Operations<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Basic Information Broadcast<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

Infrastructure Provided Route Selection


Element<br />

STARNET ISP<br />

STARNET ISP<br />

STARNET ISP<br />

STARNET Server<br />

STARNET Server<br />

STARNET Server<br />

STARNET Server<br />

STARNET Server<br />

Statewide Integrated Reporting System (SWITRS)<br />

Statewide Integrated Reporting System (SWITRS)<br />

Statewide Integrated Reporting System (SWITRS)<br />

Taxi Dispatch<br />

Traffic Accident and Surveillance Analysis System<br />

(TASAS)<br />

Traffic Accident and Surveillance Analysis System<br />

(TASAS)<br />

Traffic Accident and Surveillance Analysis System<br />

(TASAS)<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Dispatch<br />

Unitrans Transit Vehicles<br />

Unitrans Transit Vehicles<br />

Unitrans Transit Vehicles<br />

Unitrans Transit Vehicles<br />

User Personal Computing Devices<br />

User Personal Computing Devices<br />

Vehicles<br />

Vehicles<br />

Vehicles<br />

Vehicles<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Equipment Package<br />

Interactive Infrastructure Information<br />

ISP Emergency Traveler Information<br />

Traveler Telephone Information<br />

ITS Data Repository<br />

TMC Environmental Monitoring<br />

TMC Regional Traffic Control<br />

Traffic and Roadside Data Archival<br />

Traffic Data Collection<br />

Government Reporting Systems Support<br />

ITS Data Repository<br />

Traffic and Roadside Data Archival<br />

Transit Center Multi­Modal Coordination<br />

Government Reporting Systems Support<br />

ITS Data Repository<br />

Traffic and Roadside Data Archival<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Personal Basic Information Reception<br />

Personal Interactive Information Reception<br />

Vehicle Location Determination<br />

Vehicle Mayday I/F<br />

Vehicle Probe Support<br />

Vehicle Toll/Parking Interface<br />

Center Secure Area Surveillance<br />

Transit Center Fare and Load Management<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch


Element<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo Bus Dispatch Center<br />

Yolo County Bus Website<br />

Yolo County Buses<br />

Yolo County Buses<br />

Yolo County Buses<br />

Yolo County Buses<br />

Yolo County Buses<br />

Yolo County Buses<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Equipment Package<br />

Transit Data Collection<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

Basic Information Broadcast<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Transit Fare and Load<br />

Management<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring<br />

Roadway Basic Surveillance<br />

Roadway Data Collection<br />

Roadway Equipment Coordination<br />

Roadway Incident Detection<br />

Roadway Signal Controls<br />

Roadway Traffic Information Dissemination<br />

Roadway Work Zone Traffic Control<br />

MCM Incident Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Vehicle and Equipment Maintenance<br />

Management<br />

MCM Vehicle Tracking<br />

MCM Work Activity Coordination<br />

MCM Work Zone Management<br />

Collect Traffic Surveillance<br />

Rail Operations Coordination<br />

TMC Evacuation Support<br />

TMC Incident Detection<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Signal Control<br />

TMC Traffic Information Dissemination<br />

TMC Work Zone Traffic Management<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Center Secure Area Surveillance<br />

Transit Center Fixed­Route Operations<br />

Transit Center Information Services<br />

Transit Center Multi­Modal Coordination<br />

Transit Center Security<br />

Transit Center Tracking and Dispatch<br />

Transit Data Collection


Element<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Center<br />

Yuba­Sutter Transit Vehicles<br />

Yuba­Sutter Transit Vehicles<br />

Yuba­Sutter Transit Vehicles<br />

Yuba­Sutter Transit Vehicles<br />

Yuba­Sutter Transit Vehicles<br />

Equipment Package<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

On­board Fixed Route Schedule<br />

Management<br />

On­board Maintenance<br />

On­board Transit Information Services<br />

On­board Transit Security<br />

On­board Transit Trip Monitoring


Equipment Package Definitions<br />

Equipment Package<br />

Advanced Rail Crossing<br />

Basic Information Broadcast<br />

Center Secure Area Alarm<br />

Support<br />

Center Secure Area Sensor<br />

Management<br />

Center Secure Area<br />

Surveillance<br />

Collect Traffic Surveillance<br />

Emergency Call­Taking<br />

Emergency Data Collection<br />

Emergency Dispatch<br />

Emergency Early Warning<br />

System<br />

Emergency Environmental<br />

Monitoring<br />

Equipment Package Description<br />

Field elements at highway­rail intersections (HRIs) where operational<br />

requirements demand advanced features (e.g., where rail operational<br />

speeds are greater than 80 miles per hour). Capabilities from the Standard<br />

Rail Crossing plus systems which preclude entrance into the intersection<br />

when the barriers are activated, additional arriving train information, and<br />

detection of blocked intersections.<br />

Collection, processing, storage, and broadcast dissemination of traffic,<br />

transit, maintenance and construction, event, and weather information to<br />

traveler interface systems and vehicles.<br />

Collection and response to silent and audible alarms received from<br />

travelers in secure areas (such as transit stops, rest areas, park­and­ride<br />

lots) and from on­board transit vehicles.<br />

Management of security sensors, analysis of sensor data, correlation with<br />

surveillance data and alerts from other agencies to detect potential<br />

threats, and dissemination of threat information to other agencies.<br />

Sensors may be placed in areas such as transit stops, transit stations, rest<br />

areas, park and ride lots, modal interchange facilities, on­board a transit<br />

vehicle, etc.<br />

Management of security surveillance devices and analysis of that data to<br />

detect potential threats. Areas under surveillance may include transit<br />

stops, transit stations, rest areas, park and ride lots, modal interchange<br />

facilities, on­board a transit vehicle, etc.<br />

Management of traffic sensors and surveillance (CCTV) equipment, and<br />

distribution of the collected information to other centers and operators.<br />

Provides interface to the emergency call­taking systems such as the<br />

Emergency Telecommunications System (e.g., 911) that correlate call<br />

information with emergencies reported by transit agencies, commercial<br />

vehicle operators, or other public safety agencies. Allows the operator to<br />

verify the incident and forward the information to the responding<br />

agencies.<br />

Collection and storage of information related to Emergency<br />

Management. For use by operations personnel or data archives in the<br />

region.<br />

Dispatch emergency vehicles to incidents, tracking their location and<br />

status. Pertinent incident information is gathered and relayed to the<br />

responding units; includes requests for signal preemption.<br />

Monitors alerting and advisory systems, information collected by ITS<br />

surveillance and sensors, and reports from other agencies in order to<br />

identify potential, imminent, or in­progress major incidents or disasters.<br />

Notification is provided to other ITS centers to notify the traveling<br />

public. Includes support for Child Abduction notices.<br />

Current and forecast road and weather information assimilated from<br />

weather service providers and emergency vehicles equipped with<br />

environmental sensors; used by the operator to more effectively manage<br />

incidents.


Equipment Package<br />

Emergency Evacuation<br />

Support<br />

Emergency Response<br />

Management<br />

Emergency Routing<br />

Emissions Data Collection<br />

Emissions Data Management<br />

Field Secure Area Sensor<br />

Monitoring<br />

Field Secure Area Surveillance<br />

Fleet HAZMAT Management<br />

Government Reporting<br />

Systems Support<br />

HRI Traffic Management<br />

Incident Command<br />

Infrastructure Provided<br />

Dynamic Ridesharing<br />

Infrastructure Provided Route<br />

Selection<br />

Interactive Infrastructure<br />

Information<br />

Equipment Package Description<br />

Evacuation planning and coordination to manage evacuation and reentry<br />

of a population in the vicinity of a disaster or other emergency that poses<br />

a risk to public safety.<br />

<strong>Strategic</strong> emergency planning and response capabilities and broad interagency<br />

interfaces to support large­scale incidents and disasters,<br />

commonly associated with Emergency Operations Centers.<br />

Routing of emergency vehicles to facilitate the quickest/safest arrival.<br />

Routes may be determined based on real­time traffic information and<br />

road conditions or routes may be provided by Traffic Management on<br />

request.<br />

Collection and storage of air quality and emissions management<br />

information. For use by operations personnel or data archives in the<br />

region.<br />

Assimilation and storage of air quality measures and roadside collected<br />

emissions data; distribution for general traveler information or for use in<br />

demand management programs.<br />

Security sensors monitoring facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, and<br />

transit railways or guideways) for environmental threats, intrusion and<br />

motion, object detection, and infrastructure integrity.<br />

Security surveillance devices (audio/video) that monitor facilities (e.g.<br />

transit yards) and transportation infrastructure (e.g. bridges, tunnels,<br />

interchanges, and transit railways or guideways).<br />

Notification of hazardous materials (HAZMAT) shipments to emergency<br />

management centers for commercial vehicles managed by the center ­<br />

includes information on the nature of the cargo, the vehicle, and its<br />

expected route.<br />

Selects and formats data residing in an ITS archive to facilitate local,<br />

state, and federal government data reporting requirements.<br />

Remotely monitor and control highway­rail intersection (HRI)<br />

equipment, includes standard speed active warning systems and high<br />

speed systems which provide additional information on approaching<br />

trains and detect and report on obstructions in the HRI.<br />

Tactical decision support, resource coordination, and communications<br />

integration among emergency management agencies for Incident<br />

Commands that are established by first responders to support local<br />

management of an incident.<br />

Dynamic rideshare matching, including traveler eligibility, preference<br />

information, connections to transit or other multimodal services,<br />

confirmation, and payment of rideshare matching services.<br />

Generation of pre­trip and enroute trip plans for travelers (and vehicles)<br />

based on current traffic conditions, work zones, weather, and travelers<br />

constraints and preferences. Includes end­to­end trips using multiple<br />

modes, such as bicycle, transit, etc.<br />

Collection, processing, storage, and personalized dissemination of traffic,<br />

transit, maintenance and construction, multimodal, event, and weather<br />

information to traveler interface systems and vehicles, upon request.


Equipment Package<br />

ISP Data Collection<br />

ISP Emergency Traveler<br />

Information<br />

ISP Probe Information<br />

Collection<br />

ITS Data Repository<br />

Mayday Support<br />

MCM Automated Treatment<br />

System Control<br />

MCM Data Collection<br />

MCM Environmental<br />

Information Collection<br />

MCM Environmental<br />

Information Processing<br />

MCM Incident Management<br />

MCM Maintenance Decision<br />

Support<br />

MCM Roadway Maintenance<br />

and Construction<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle Tracking<br />

MCM Winter Maintenance<br />

Management<br />

Equipment Package Description<br />

Collection and storage of information supporting the operations of<br />

traveler information service providers. For use by operations personnel<br />

or data archives in the region.<br />

Collection and distribution of emergency information to the traveler<br />

public, including evacuation information and wide­area alerts.<br />

Collection and aggregation of vehicle probe data, including calculation<br />

and dissemination of route travel times and usage. Includes<br />

environmental probe data collection, aggregation and dissemination.<br />

Collect and maintain data and data catalogs from one or more data<br />

sources. May include quality checks, error notification, and archive<br />

coordination.<br />

Collection and response to Mayday messages received from vehicles and<br />

drivers.<br />

Remotely controls automated roadway treatment systems (to disperse<br />

anti­icing chemicals, etc.) directly, or via control of the environmental<br />

sensors that activate the treatment systems automatically in the field.<br />

Collection and storage of maintenance and construction information. For<br />

use by operations personnel or data archives in the region.<br />

Remotely controls environmental sensors and assimilates collected data<br />

with other current and forecast road conditions and surface weather<br />

information from weather service providers and transportation<br />

operations.<br />

Processes current and forecast weather data, road condition information,<br />

local environmental data, and uses internal models to develop specialized<br />

detailed forecasts of local weather and surface conditions. Disseminates<br />

road weather information to other agencies and centers.<br />

Supports coordinated response to incidents ­ share incident notifications,<br />

manage incident response resources, and coordinate overall incident<br />

situation and response among allied response organizations.<br />

Maintenance Decision Support Systems recommend courses of action<br />

based on current and forecast environmental and road conditions (filtered<br />

and fused for specific time horizons) and additional application specific<br />

information. Recommendations and dispatch instructions are generated<br />

based on this integrated information.<br />

Overall management and support for routine maintenance on the roadway<br />

or right­of­way. Includes landscape maintenance, hazard removal<br />

(roadway debris, dead animals), routine maintenance activities (roadway<br />

cleaning, grass cutting), and repair and maintenance of both ITS and non­<br />

ITS equipment.<br />

Monitors vehicle and equipment condition, tracks maintenance history,<br />

and schedules routine and corrective maintenance.<br />

Remotely tracks the location of maintenance and construction vehicles<br />

and other equipment; presented to the center personnel.<br />

Manages winter road maintenance, tracking and controlling snow plow<br />

operations, roadway treatment (e.g., salt spraying and other material<br />

applications) based on weather information.


Equipment Package<br />

MCM Work Activity<br />

Coordination<br />

MCM Work Zone<br />

Management<br />

MCM Work Zone Safety<br />

Management<br />

MCV Infrastructure<br />

Monitoring<br />

MCV Roadway Maintenance<br />

and Construction<br />

MCV Vehicle Location<br />

Tracking<br />

MCV Vehicle Safety<br />

Monitoring<br />

MCV Vehicle System<br />

Monitoring and Diagnostics<br />

MCV Winter Maintenance<br />

MCV Work Zone Support<br />

On­board Cargo Monitoring<br />

On­board EV En Route<br />

Support<br />

On­board EV Incident<br />

Management Communication<br />

Equipment Package Description<br />

Disseminates work activity schedules to other agencies. Work schedules<br />

are coordinated, factoring in the needs and activities of other agencies<br />

and adjacent jurisdictions.<br />

Remotely monitors and supports work zone activities, controlling traffic<br />

through portable dynamic message signs (DMS) and informing other<br />

groups of activity (e.g., traveler information systems, traffic management<br />

centers, other maintenance and construction centers).<br />

Remotely monitors work zone safety systems that detect vehicle<br />

intrusions in work zones and warns crew workers and drivers of<br />

imminent encroachment. Crew movements are also monitored so that the<br />

crew can be warned of movement beyond the designated safe zone.<br />

On­board systems to monitor the condition of pavement, bridges, tunnels,<br />

associated hardware, and other transportation­related infrastructure (e.g.,<br />

culverts). Includes vehicle­based sensors and communications with<br />

roadway­based infrastructure monitoring sensors.<br />

On­board systems that support routine non­winter maintenance on the<br />

roadway or right­of­way. Includes landscape maintenance, hazard<br />

removal (roadway debris, dead animals), routine maintenance activities<br />

(roadway cleaning, grass cutting), and repair and maintenance of<br />

equipment on the roadway.<br />

On­board systems to track vehicle location and reports the position and<br />

timestamp information to the dispatch center.<br />

On­board systems to detect vehicle intrusions and warn crew workers<br />

and drivers of imminent encroachment. Crew movements are monitored<br />

so that the crew can be warned of movement beyond the designated safe<br />

zone. Used for stationary work zones or in mobile applications where a<br />

safe zone is maintained around the moving vehicle.<br />

On­board sensors capable of monitoring the condition of each of the<br />

vehicle systems and diagnostics that can be used to support vehicle<br />

maintenance.<br />

On­board systems that support snow plow operations and other roadway<br />

treatments (e.g., salt spraying and other material applications). Supports<br />

platooning of snow plows.<br />

On­board systems that provide communications and support for local<br />

management of a work zone.<br />

On­board systems monitoring the location and status of the commercial<br />

vehicle and its cargo. Sends the data on to appropriate centers and<br />

roadside facilities, including emergency management in the case of<br />

HAZMAT incidents.<br />

On­board systems for gathering of dispatch and routing information for<br />

emergency vehicle personnel, vehicle tracking, communications with<br />

care facilities, and signal preemption via short range communication<br />

directly with traffic control equipment at the roadside.<br />

On­board systems providing the direct interface between the emergency<br />

vehicle and incident management personnel at the incident site.


Equipment Package<br />

On­board Fixed Route<br />

Schedule Management<br />

On­board Maintenance<br />

On­board Paratransit<br />

Operations<br />

On­board Transit Fare and<br />

Load Management<br />

On­board Transit Information<br />

Services<br />

On­board Transit Security<br />

On­board Transit Signal<br />

Priority<br />

On­board Transit Trip<br />

Monitoring<br />

On­Line Analysis and Mining<br />

Parking Data Collection<br />

Parking Electronic Payment<br />

Parking Management<br />

Parking Surveillance<br />

Personal Basic Information<br />

Reception<br />

Equipment Package Description<br />

Collecting of data for schedule generation and adjustment on­board a<br />

transit vehicle. Supports communication between the vehicle, operator,<br />

and center.<br />

On­board systems to collect and process transit vehicle maintenance data<br />

including mileage and vehicle operating conditions for use in scheduling<br />

future vehicle maintenance.<br />

On­board systems to manage paratransit and flexible­route dispatch<br />

requests, including multi­stop runs. Inputs based on the transit vehicle’s<br />

type and passenger capacity.<br />

On­board systems provide variable and flexible fare collection using a<br />

travelers fare medium (stored value cards or other payment instrument).<br />

Collect data required to determine accurate ridership levels and fare<br />

statistics.<br />

On­board systems to furnish next­stop annunciation as well as interactive<br />

travel­related information, including routes, schedules, transfer options,<br />

fares, real­time schedule adherence, current incidents, weather<br />

conditions, non­motorized transportation services, and special events.<br />

On­board video/audio surveillance systems, threat sensors, and object<br />

detection sensors to enhance security and safety on­board a transit<br />

vehicles. Also includes silent alarms activated by transit user or vehicle<br />

operator, operator authentication, and remote vehicle disabling.<br />

On­board systems to provides request signal priority through short range<br />

communication directly with traffic control equipment at the roadside<br />

(intersections, crossings, ramp meters, etc.).<br />

Support fleet management with automatic vehicle location (AVL) and<br />

automated mileage and fuel reporting and auditing.<br />

Advanced data analysis and mining features to support discovery of<br />

information, patterns, and correlations in large ITS archives.<br />

Collection and storage of parking management information. For use by<br />

operations personnel or data archives in the region.<br />

Parking payment collection using in­vehicle equipment (tags) or contact<br />

or proximity traveler cards used for electronic payment. Includes field<br />

elements and back­office functionality.<br />

Maintain and distribute parking lot information including static (spaces,<br />

hours, charges, etc.) and dynamic (availability, open/closed, etc.) data.<br />

Interface to traffic, transit, and traveler information providers.<br />

Field elements that detect and classify vehicles entering and exiting a<br />

parking facility.<br />

Personal traveler interface that provides formatted traffic advisories,<br />

transit, event, and other traveler information, as well as broadcast alerts.<br />

Devices include desktop computers at home, work, or at major trip<br />

generation sites, plus personal portable devices such as PDAs and pagers.


Equipment Package<br />

Personal Interactive<br />

Information Reception<br />

Equipment Package Description<br />

Personal traveler interface that provides traffic, transit, yellow pages,<br />

event, and trip planning information, as well as payment services for<br />

tolls, parking, and other personalized traveler information services upon<br />

request. Devices include desktop computers at home, work, or at major<br />

trip generation sites, plus personal portable devices such as PDAs and<br />

pagers.<br />

Rail Operations Coordination Coordination between rail operations and traffic management centers ­<br />

exchanging train schedules, maintenance schedules, as well as incidents<br />

and priority messages which result in highway­rail intersection (HRI).<br />

Supports advanced traffic control strategies and enhanced traveler<br />

information.<br />

Remote Interactive<br />

Information Reception<br />

Remote Transit Fare<br />

Management<br />

Remote Transit Information<br />

Services<br />

Remote Traveler Security<br />

Roadway Basic Surveillance<br />

Roadway Data Collection<br />

Roadway Emissions<br />

Monitoring<br />

Roadway Environmental<br />

Monitoring<br />

Roadway Equipment<br />

Coordination<br />

Roadway Freeway Control<br />

Roadway HOV Control<br />

Public traveler interface, such as a kiosk, that provides traffic, transit,<br />

yellow pages, event, and trip planning information, as well as payment<br />

services for tolls, parking, and other personalized traveler information<br />

services upon request.<br />

Public traveler interface, such as a kiosk, that provides the capability for<br />

the traveler to use a common fare medium for transit fares, tolls, and/or<br />

parking lot charges, to calculate the amount due and identify payment<br />

problems.<br />

Public traveler interface that provides real­time travel­related information<br />

at transit stops and multi­modal transfer points, including general<br />

annunciation, display of imminent arrival information, the latest available<br />

information on transit routes, schedules, transfer options, bicycle<br />

accessibility, fares, real­time schedule adherence, current incidents,<br />

weather conditions, and special events<br />

Public traveler interface that provides the capability for travelers to report<br />

an emergency or activate a panic button to summon assistance in areas<br />

such as transit stops, park­and­ride areas, etc.<br />

Field elements that monitor traffic conditions using loop detectors and<br />

CCTV cameras.<br />

Field elements to collect traffic, road, and environmental conditions<br />

information for use in transportation planning, research, and other offline<br />

applications. Includes the sensors, supporting roadside infrastructure,<br />

and communications equipment.<br />

Emissions and air quality sensors that collect vehicular emissions and<br />

area­wide air quality data.<br />

Environmental sensors, surface and sub­surface, that collect weather and<br />

road surface information. Weather conditions measured include<br />

temperature, wind, humidity, precipitation, and visibility. Sensors<br />

measure road surface temperature, moisture, icing, salinity, etc.<br />

Field elements that control and send data to other field elements (such as<br />

environmental sensors that send data to a DMS or coordination between<br />

traffic controllers on adjacent intersections), without center control.<br />

Freeway control equipment including ramp meters, mainline metering,<br />

and lane control equipment which controls traffic on freeways, including<br />

indicators to drivers.<br />

HOV lane usage traffic sensors and display equipment to notify users of<br />

HOV lane status for control of traffic in HOV lanes on freeways.


Equipment Package<br />

Roadway Incident Detection<br />

Roadway Probe Beacons<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Work Zone Safety<br />

Roadway Work Zone Traffic<br />

Control<br />

Service Patrol Management<br />

Standard Rail Crossing<br />

TMC Environmental<br />

Monitoring<br />

TMC Evacuation Support<br />

TMC Freeway Management<br />

TMC HOV Lane Management<br />

TMC Incident Detection<br />

Equipment Package Description<br />

Field elements that provide video images of traffic conditions, including<br />

advanced CCTV cameras with built­in incident detection algorithms.<br />

Field elements to collect traffic and road conditions from passing<br />

vehicles; both anonymous toll/parking tag readings for link time<br />

calculations and smart probe data supported.<br />

Field elements including traffic signal controllers for use at major<br />

intersections and on main highways for urban areas; also supports<br />

pedestrian crossings.<br />

Field elements that provide the capability to receive vehicle signal<br />

priority requests and control traffic signals accordingly.<br />

Driver information systems, such as dynamic message signs and<br />

Highway Advisory Radio (HAR).<br />

Work zone intrusion detection devices (to detect vehicle intrusion upon a<br />

work zone or crew worker movement across a work zone boundary) and<br />

intrusion alerting devices that provide alerts to crew and drivers.<br />

Field elements in a work zone that manage traffic conditions using<br />

CCTV cameras and driver information systems (such as DMS) to provide<br />

information directly to drivers affected by the work zone activity.<br />

Dispatch and communication with roadway service patrol vehicles that<br />

monitor roads to aid motorists, offering rapid response to minor<br />

incidents.<br />

Field elements at highway­rail intersections (HRIs) where operational<br />

requirements do not dictate advanced features (e.g., where rail<br />

operational speeds are less than 80 miles per hour). Includes traditional<br />

HRI warning systems augmented with other standard traffic management<br />

devices.<br />

Management of environmental sensors and assimilation of collected data<br />

with other current and forecast road conditions and surface weather<br />

information from weather service providers and roadway maintenance<br />

operations.<br />

Development, coordination, and execution of special traffic management<br />

strategies during evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or major emergency. Interfaces with emergency<br />

management and other traffic management centers.<br />

Remotely controls ramp meters, mainline metering, and lane controls on<br />

freeways based on upstream and downstream traffic flow and ramp<br />

queue length algorithms.<br />

Remotely controls high­occupancy vehicle (HOV) lane sensors, driver<br />

information systems, and ramp meters to manage use of HOV or High<br />

Occupancy Toll (HOT) lanes; also detects HOV violators and notifies<br />

enforcement agencies.<br />

Remotely controls traffic and video sensors to support incident detection<br />

and verification; exchange information with other agencies including<br />

emergency management, maintenance and construction, alerting and<br />

advisory systems, event promoters, intermodal freight depots, and<br />

traveler information systems.


Equipment Package<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Multimodal<br />

Coordination<br />

TMC Probe Information<br />

Collection<br />

TMC Regional Traffic Control<br />

TMC Signal Control<br />

TMC Toll/Parking<br />

Coordination<br />

TMC Traffic Information<br />

Dissemination<br />

TMC Work Zone Traffic<br />

Management<br />

Traffic and Roadside Data<br />

Archival<br />

Traffic Data Collection<br />

Traffic Maintenance<br />

Transit Center Fare and Load<br />

Management<br />

Transit Center Fixed­Route<br />

Operations<br />

Equipment Package Description<br />

Center­based capability to formulate an incident response that takes into<br />

account the incident potential, incident impacts, and/or resources<br />

required for incident management including proposing and facilitating<br />

the dispatch of emergency response and service vehicles as well as<br />

coordinating response with all appropriate cooperating agencies.<br />

Provides traffic signal priority for transit vehicles based on center­tocenter<br />

communications with the transit management center; also<br />

exchange traffic and transit information.<br />

Collects, assimilates, and disseminates vehicle probe data collected from<br />

roadside beacons and centers controlling transit vehicles, emergency<br />

vehicles, toll collection points, and route­guided vehicles.<br />

Coordination between traffic management centers in order to share traffic<br />

information between centers as well as control of traffic management<br />

field equipment. This may be used during incidents and special events<br />

and during day­to­day operations.<br />

Remotely controls traffic signal controllers to implement traffic<br />

management strategies at major intersections and on main highways for<br />

urban areas, based on traffic conditions, incidents, emergency vehicle<br />

preemptions, pedestrian crossings, etc.<br />

Provides the capability to gather information on regional toll, parking,<br />

and transit usage and request changes to enable dynamic pricing for<br />

demand management.<br />

Controls dissemination of traffic­related data to other centers, the media,<br />

and travelers via the driver information systems (DMS, HAR) that it<br />

operates.<br />

Coordination with maintenance systems using work zone images and<br />

traveler information systems (such as DMS), and distribution of work<br />

plans so that work zones are established that have minimum traffic<br />

impact.<br />

Collects and archives traffic and environmental information directly from<br />

the roadside for use in off­line planning, research, and analysis.<br />

Collection and storage of traffic management data. For use by operations<br />

personnel or data archives in the region.<br />

Monitoring and remote diagnostics of field equipment ­ detect failures,<br />

issue problem reports, and track the repair or replacement of the failed<br />

equipment.<br />

Management of fare collection at the center ­ includes setting and<br />

distributing fare information, central processing of fares for transit as<br />

well as other ITS services, links to financial institutions and enforcement<br />

agencies.<br />

<strong>Plan</strong>ning and scheduling associated with fixed and flexible route transit<br />

services, automatically updates customer service operator systems, and<br />

provides current vehicle schedule adherence and optimum scenarios for<br />

schedule adjustment.


Equipment Package<br />

Transit Center Information<br />

Services<br />

Transit Center Multi­Modal<br />

Coordination<br />

Transit Center Paratransit<br />

Operations<br />

Transit Center Security<br />

Transit Center Tracking and<br />

Dispatch<br />

Transit Data Collection<br />

Transit Environmental<br />

Monitoring<br />

Transit Evacuation Support<br />

Transit Garage Maintenance<br />

Transit Garage Operations<br />

Traveler Secure Area Sensor<br />

Monitoring<br />

Traveler Secure Area<br />

Surveillance<br />

Traveler Telephone<br />

Information<br />

Vehicle Location<br />

Determination<br />

Vehicle Mayday I/F<br />

Equipment Package Description<br />

Provide interactive traveler information to travelers (on­board transit<br />

vehicles, at stops/stations, using personal devices), traveler information<br />

service providers, media, and other transit organizations. Includes routes,<br />

schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, yellow pages, and special events.<br />

Generate requests for transit priority on routes and at certain<br />

intersections. Coordinate schedules with other agencies and modes,<br />

including transit transfer cluster and transfer point information.<br />

<strong>Plan</strong>ning and scheduling of demand responsive transit (i.e. paratransit)<br />

services, includes automatic operator assignment and monitoring.<br />

Monitor transit vehicle operator or traveler activated alarms; authenticate<br />

transit vehicle operators; remotely disable a transit vehicle; alert<br />

operators, travelers, and police to potential incidents identified by these<br />

security features.<br />

Monitoring transit vehicle locations via interactions with on­board<br />

systems and determining vehicle schedule adherence. Furnish users with<br />

real­time transit related information and maintain interface with digital<br />

map providers.<br />

Collection and storage of transit management data. For use by operations<br />

personnel or data archives in the region.<br />

Current and forecast road and weather information assimilated from<br />

weather service providers and vehicle probes. The information is<br />

monitored and forwarded to other agencies to more effectively manage<br />

transit operations.<br />

Support evacuation and subsequent reentry of a population in the vicinity<br />

of a disaster or other emergency. Coordinate regional evacuation plans<br />

and resources including transit and school bus fleets.<br />

Collect operational and maintenance data from transit vehicles, manage<br />

vehicle service histories, automatically generate preventative<br />

maintenance schedules, and provide information to service personnel.<br />

Assignment of transit vehicles and operators to routes or service areas in<br />

a fair manner while minimizing labor and overtime services, considering<br />

operator preferences, qualifications, accumulated work hours, and other<br />

information about each operator.<br />

Security sensors monitoring traveler­frequented areas such as transit<br />

stops, park­and­ride lots, and rest stops for environmental threats,<br />

intrusion and motion, and object detection.<br />

Security surveillance devices that monitor traveler­frequented areas such<br />

as transit stops and rest stops.<br />

Collection and distribution of traveler information and wide­area alerts to<br />

traveler telephone information systems such as 511, based on voicebased<br />

traveler requests.<br />

Determines current location of the vehicle using GPS or similar location<br />

referencing and provides this information to other in­vehicle functions.<br />

In­vehicle capability for drivers or collision detection sensors onboard a<br />

vehicle to report an emergency and summon assistance.


Equipment Package<br />

Vehicle Probe Support<br />

Vehicle Toll/Parking Interface<br />

Virtual Data Warehouse<br />

Services<br />

Equipment Package Description<br />

On­board systems that identify location, measure traffic conditions such<br />

as link travel time and speed and transmit data to a center or roadside<br />

beacons.<br />

On­board systems to support paying toll without stopping and pay for<br />

parking without the use of cash through the use of an active tag interface<br />

and debit/credit card interface.<br />

Provides access to data from geographically dispersed archives and<br />

coordinates information exchange with a local data warehouse. Also<br />

provides the specialized publishing, directory services, and transaction<br />

management functions associated with coordinating remote archives.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Air Quality Website Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

Air Quality Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Airport Dispatch Center Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

Airport Dispatch Center Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

Airport Dispatch Center Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

Airport Dispatch Center Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

Airport Dispatch Center Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

Airport Dispatch Center Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

Airport Dispatch Center Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

Airport Dispatch Center Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Airport Dispatch Center Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

Airport Dispatch Center Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Airport Dispatch Center Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Airport Dispatch Center Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Airport Dispatch Center Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Airport Dispatch Center Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Airport Dispatch Center Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Airport Dispatch Center Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Airport Dispatch Center Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Airport Dispatch Center Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

Airport Dispatch Center Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

Airport Dispatch Center Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

Airport Dispatch Center Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

Airport Dispatch Center Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

Archive Data User Systems TBD TBD<br />

California DMV Licensing and Registration TBD<br />

TBD<br />

Division<br />

California HPMS ITS Data Repository The center shall collect data to be archived from one or more data sources.<br />

California HPMS ITS Data Repository The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

California HPMS ITS Data Repository The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

California HPMS ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.<br />

California HPMS ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.<br />

California HPMS ITS Data Repository The center shall include capabilities for archive to archive coordination.<br />

California HPMS ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

California HPMS ITS Data Repository The center shall perform quality checks on received data.<br />

California HPMS ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

California HPMS ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

California HPMS ITS Data Repository When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

California HPMS ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

California HPMS<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

California HPMS<br />

California HPMS<br />

California HPMS<br />

California HPMS<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

California Office of Emergency Services<br />

Operations Centers<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

The center shall provide strategic emergency response capabilities such as that of an Emergency Operations Center for<br />

large­scale incidents and disasters.<br />

The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.<br />

The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

The center shall receive event scheduling information from Event Promoters.<br />

The center shall receive hazardous materials incident information from commercial fleet operators.<br />

The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

The center shall provide information to the media concerning the status of an emergency response.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

California Office of Emergency Services Incident Command<br />

Operations Centers<br />

California Office of Emergency Services Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

Operations Centers<br />

process and reentry.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Operations Centers<br />

California Office of Emergency Services Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

Operations Centers<br />

present the operator with other agenciesÆ plans.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Operations Centers<br />

Cross) in the region.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

Operations Centers<br />

emergency management centers as needed.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

Operations Centers<br />

California Office of Emergency Services Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

Operations Centers<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

Operations Centers<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

Operations Centers<br />

during the incident, with allied agencies.<br />

California Office of Emergency Services Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

Operations Centers<br />

California Office of Emergency Services Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

Operations Centers<br />

services or fee collection during an evacuation.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Caltrans D3 Data Server Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Caltrans D3 Data Server Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Caltrans D3 Data Server ISP Data Collection The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle<br />

probe data, and other data from traveler information system operations.<br />

Caltrans D3 Data Server ISP Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Caltrans D3 Data Server ISP Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or<br />

for the data itself.<br />

Caltrans D3 Data Server ISP Data Collection The center shall be able to produce sample products of the data available.<br />

Caltrans D3 Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

Caltrans D3 Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

Caltrans D3 Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from traffic, emergency, and transit management, traveler information providers, and<br />

environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and<br />

construction vehicles.<br />

The center shall provide weather and road condition information to weather service providers and center personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall collect operational status for the roadside and vehicle­based environmental sensor equipment.<br />

The center shall collect fault data for the roadside and vehicle­based environmental sensor equipment for repair.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

and predicted road weather and road conditions.<br />

The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

treatment information that supports forecasts for road conditions.<br />

The center shall remotely control automated roadway treatment systems. Treatments can be in the form of fog<br />

dispersion, anti­icing chemicals, etc.<br />

The center shall remotely control the environmental sensors that upon detecting changes in environmental or<br />

atmospheric conditions, automatically activate roadway treatment systems.<br />

The center shall collect automated roadway treatment system and associated environmental sensor operational status.<br />

Caltrans D3 Maintenance Dispatch MCM Environmental Information<br />

Processing<br />

Caltrans D3 Maintenance Dispatch MCM Automated Treatment System<br />

Control<br />

Caltrans D3 Maintenance Dispatch MCM Automated Treatment System<br />

Control<br />

Caltrans D3 Maintenance Dispatch MCM Automated Treatment System<br />

Control<br />

Caltrans D3 Maintenance Dispatch MCM Automated Treatment System The center shall collect automated roadway treatment system and associated environmental sensor fault data and<br />

Control<br />

request repair.<br />

Caltrans D3 Maintenance Dispatch MCM Automated Treatment System The center shall accept requests for automated roadway treatment system activation from center personnel.<br />

Control<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Caltrans D3 Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Caltrans D3 Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

Caltrans D3 Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

Caltrans D3 Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

Caltrans D3 Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other winter roadway maintenance.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall exchange information with administrative systems to support the planning and scheduling of winter<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall provide status information about scheduled winter maintenance activities including anticipated closures<br />

and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided<br />

to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance<br />

centers, and the media.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of winter maintenance activities.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of winter maintenance<br />

activities.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall dispatch and route winter maintenance vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall determine the need for roadway treatment based on current and forecasted weather information, current<br />

usage of treatments and materials, available resources, requests for action from other agencies, and recommendations<br />

from the Maintenance Decision Support system, specifically under winter conditions. This supports winter maintenance<br />

such as plowing, treating, anti­icing, etc.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall provide dispatch instructions for vehicle operators based on input parameters from center personnel,<br />

specifically for winter conditions. This could include a treatment route, treatment application rates, start and end times,<br />

and other treatment instructions.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall support remote control of on­board maintenance and construction vehicle systems and field equipment<br />

that is remotely controlled by the vehicle such as adjusting material application rates and spread patterns.<br />

Caltrans D3 Maintenance Dispatch MCM Winter Maintenance Management The center shall assess the current status of all winter maintenance activities, including actual work activities performed,<br />

current locations and operational conditions of vehicles, materials and equipment inventories, field equipment status,<br />

environmental information, etc.<br />

Caltrans D3 Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

Caltrans D3 Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

Caltrans D3 Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

Caltrans D3 Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

Caltrans D3 Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Safety Management The center shall provide remote monitoring and control of work zone safety devices ­ including intrusion detection devices<br />

that have been installed in work zones or maintenance areas.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Safety Management The center shall provide remote monitoring and control of intrusion alert devices that have been installed in work zones or<br />

maintenance areas.<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Safety Management The center shall collect status information of work zone safety device status from field equipment or the maintenance and<br />

construction vehicles.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Caltrans D3 Maintenance Dispatch MCM Work Zone Safety Management The center shall collect and store work zone data collected from work zone monitoring devices (such as intrusion<br />

detection or alert devices and speed monitoring devices) on­board the vehicle and at the roadside.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

Caltrans D3 Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle<br />

location determination function.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

The maintenance and construction vehicle shall collect vehicle diagnostics and operating status data from the<br />

maintenance vehicle platform including engine temperature, mileage, tire wear, brake wear, belt wear, and other<br />

operational status measures as well as the status of maintenance and construction­specific systems on the vehicle.<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

The maintenance and construction vehicle shall use the diagnostic and status information to support scheduling vehicle<br />

maintenance, monitoring safety status, and informing the vehicle operator of the conditions.<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

The maintenance and construction vehicle shall the vehicle diagnostic and safety information to an equipment repair<br />

facility.<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

The maintenance and construction vehicle shall send the vehicle diagnostic and safety information to the controlling<br />

maintenance center.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include winter maintenance equipment for plowing, treating, and antiicing.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

Caltrans D3 Maintenance Vehicles MCV Winter Maintenance The maintenance and construction vehicle shall exchange operational and environmental data with other maintenance<br />

and construction vehicles. Operational data includes operational state of the maintenance equipment (e.g., blade<br />

up/down, spreader pattern, equipment configuration) and a record of the actual work performed while the environmentatl<br />

data includes environmental sensor data collected on­board a maintenance and construction vehicle, either raw or<br />

processed data.<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

Caltrans D3 Maintenance Vehicles<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include routine maintenance equipment for cutting, repairs, hazard<br />

removal, etc.<br />

The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.<br />

The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

Caltrans D3 Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall monitor, operate, and control work zone devices located at or alongside<br />

the roadway. The devices operated on board the vehicle include driver information devices (e.g. dynamic message signs)<br />

and work zone intrusion detection and alert devices.<br />

Caltrans D3 Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone<br />

activities.<br />

Caltrans D3 Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on­board<br />

the maintenance and construction vehicle and send them to the controlling center.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Safety Monitoring The maintenance and construction vehicle shall detect that a vehicle has intruded upon the boundary of a work zone. The<br />

boundary of the work zone represents an area around the maintenance and construction vehicle, which may be stationary<br />

or moving.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Safety Monitoring The maintenance and construction vehicle shall receive work zone warnings from the field equipment at the roadside,<br />

other maintenance and construction vehicles.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Safety Monitoring The maintenance and construction vehicle shall present work zone warnings to the field personnel using direct warning<br />

signals or in­vehicle signage functions.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Safety Monitoring The maintenance and construction vehicle shall monitor the crew movements to identify when a crew member is crossing<br />

the boundary between a work zone and vehicle traffic and issue an alert to the crew member.<br />

Caltrans D3 Maintenance Vehicles MCV Vehicle Safety Monitoring The maintenance and construction vehicle shall provide status of the work zone warning systems to the center.<br />

Caltrans D3 Pavement Management System TBD TBD<br />

Caltrans D3 Storage Facility TBD TBD<br />

Caltrans D3 Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Caltrans D3 Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Caltrans D3 Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Caltrans D3 Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Caltrans D3 Website Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

Caltrans D3 Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Caltrans D3 Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Caltrans D3 Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

Caltrans D3 Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Caltrans D3 Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

Caltrans D3 Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

Caltrans District Shop<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

ITS Data Repository<br />

The center shall collect data to be archived from one or more data sources.<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

ITS Data Repository<br />

The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

The center shall include capabilities for performing quality checks on the incoming archived data.<br />

The center shall include capabilities for error notification on the incoming archived data.<br />

The center shall include capabilities for archive to archive coordination.<br />

The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

The center shall perform quality checks on received data.<br />

The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

ITS Data Repository<br />

When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

ITS Data Repository<br />

For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

TBD<br />

TBD<br />

Caltrans Performance Monitoring System<br />

(PeMS)<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Caltrans Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall use toll and parking tags on passing vehicles for traffic data link time calculations and send to the<br />

controlling center; tag identities will be removed to ensure anonymity.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors traffic conditions (e.g., average speed) by communicating with<br />

passing vehicles equipped with a transponder or other short range communications device; also called smart probes.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors road conditions by communicating with passing vehicles<br />

equipped with a transponder or other short range communications device; also called smart probes.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall aggregate, format, and store collected vehicle smart probe data (traffic and road conditions data),<br />

calculate link travel times and processed road condition data, and send to future passing vehicles.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment operational status to the center.<br />

Caltrans Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment fault indication to the center for repair.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Caltrans Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall include ramp metering controllers, mainline meters, and lane controls for use on freeways, under<br />

center control.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall monitor operation of ramp meter, mainline meters, and lane control indicators and report to the<br />

center any instances in which the indicator response does not match that expected from the indicator control information.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall monitor operation of ramp meter, mainline meters, and lane control indicators and report to the<br />

center any instances in which the indicator response does not match that expected from known indicator preemptions.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall return ramp metering controller, mainline meters, and lane control operational status to the<br />

controlling center.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall return ramp metering controller, mainline meters, and lane control fault data to the maintenance<br />

center for repair.<br />

Caltrans Roadside Equipment Roadway Freeway Control The field element shall provide indications to the driver that a freeway ramp or a lane is available for use, with possible<br />

usage data for the freeway lanes they are entering.<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall include sensors to detect high­occupancy vehicle (HOV) lane usage, under center control.<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall include driver information systems to notify users of lane status for lanes that become HOV or<br />

High Occupancy Toll (HOT) lanes during certain times of the day on freeways, under center control.<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall include freeway control devices, such as ramp signals and mainline metering and other systems<br />

associated with freeway operations that control use of HOV lanes, under center control.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall provide traffic flow measures and information regarding vehicle occupancy (i.e., lane usage) in<br />

HOV lanes to the center.<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall return operational status for the HOV lane sensors to the controlling center.<br />

Caltrans Roadside Equipment Roadway HOV Control The field element shall return fault data for the HOV lane sensors to the center for repair.<br />

Caltrans Roadside Equipment<br />

Caltrans Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Caltrans Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Caltrans Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Caltrans Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Caltrans Roadside Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Caltrans Roadside Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Caltrans Roadside Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Caltrans Roadside Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

Caltrans Roadside Equipment Standard Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

Caltrans Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

Caltrans Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Caltrans Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

Caltrans Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall include emissions sensors that detect levels of emissions from individual vehicles, under center<br />

control.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall include air quality sensors, often distributed geographically, that detect area­wide levels of<br />

pollution, under center control.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall analyze collected vehicle emissions data against reference data to determine whether or not a<br />

vehicle is violating the acceptable levels of emissions, and shall return this analysis to a center for possible enforcement<br />

action.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring If the emissions level detected by the emissions sensor indicates a vehicle is violating the acceptable levels of emissions,<br />

the field element shall provide the capability to display summary emissions information or warnings to passing drivers via<br />

a driver information system (such as portable messages signs, etc.).<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall provide emissions sensor equipment operational status to the center.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall provide emissions sensor equipment fault indication to the center for repair.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall provide area­wide pollution sensor equipment operational status to the center.<br />

Caltrans Roadside Equipment Roadway Emissions Monitoring The field element shall provide area­wide pollution sensor equipment fault indication to the center for repair.<br />

Caltrans Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Caltrans Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Caltrans Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Caltrans Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Caltrans Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall include work zone intrusion detection devices that detect when a vehicle has intruded upon the<br />

boundary of a work zone, under center control.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall include work zone intrusion detection devices that detect when crew workers have crossed the<br />

boundary between the work zone and vehicle traffic, under center control.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall include work zone intrusion alerting devices that alert crew workers of a work zone emergency or<br />

safety issue such as the intrusion of a vehicle into the work zone area or movement of field crew into the travel lanes.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall include work zone intrusion alerting devices that notify crew via maintenance vehicles of a work<br />

zone emergency or safety issue such as the intrusion of a vehicle into the work zone area or movement of field crew into<br />

the travel lanes.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall include work zone intrusion alerting devices that alert drivers that they have intruded upon the<br />

perimeter of the work zone, or are about to do so; may provide alerts to drivers directly or via in­vehicle signing.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall provide operational status for the work zone intrusion detection devices to the maintenance<br />

center.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall provide fault data for the work zone intrusion detection devices to the maintenance center for<br />

repair.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall provide operational status for the work zone intrusion alerting devices to the maintenance center.<br />

Caltrans Roadside Equipment Roadway Work Zone Safety The field element shall provide fault data for the work zone intrusion alerting devices to the maintenance center for repair.<br />

Capital Corridor Train Operations Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Capital Corridor Train Operations Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Capital Corridor Train Operations Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Capital Corridor Train Operations Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Capital Corridor Train Operations Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Capital Corridor Train Operations Center Transit Center Fixed­Route Operations The center shall generate train routes and schedules based on such factors as parameters input by the system operator,<br />

operational data on current routes and schedules, and digitized map data.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

Capital Corridor Train Operations Center Transit Center Security The center shall provide support to remotely disable (or reset the disabling of) a transit vehicle in service.<br />

Capital Corridor Train Operations Center Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

Capital Corridor Train Operations Center Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Capital Corridor Train Operations Center Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Capital Corridor Train Operations Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Capital Corridor Train Operations Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Capital Corridor Train Operations Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Capital Corridor Train Operations Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Capital Corridor Trains On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Capital Corridor Trains On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Capital Corridor Trains On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Capital Corridor Trains On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Capital Corridor Trains On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Capital Corridor Trains<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall detect potential threats via sensors for chemical agents, toxic industrial chemicals, biological<br />

agents, explosives, and radiation.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall detect potential threats via object detection sensors(e.g. metal detectors).<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed sensor information to the<br />

center along with the vehicleÆs current location.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall accept sensor control data to allow remote control of the sensors.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall output reported emergencies to the center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or<br />

authentic inputs from the transit vehicle operator.<br />

Capital Corridor Trains On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Capitol Corridor Train Stations Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Capitol Corridor Train Stations Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Capitol Corridor Train Stations Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Capitol Corridor Train Stations Transit Data Collection The center shall be able to produce sample products of the data available.<br />

ChemTrec Information System (Terminator) TBD TBD<br />

CHP Vehicles On­board EV En Route Support TBD<br />

CHP Vehicles<br />

CHP Vehicles<br />

CHP Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

CHP Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

CHP Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

CHP Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

CHP Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

CHP Website Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

CHP Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

CHP Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

CHP Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

CHP Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

CHP Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

CHP Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

Citrus Heights Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

Citrus Heights Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

Citrus Heights Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

Citrus Heights Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Citrus Heights Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

Citrus Heights Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

Citrus Heights Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

Citrus Heights Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

Citrus Heights Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Citrus Heights Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

Citrus Heights Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

Citrus Heights Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

Citrus Heights Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

Citrus Heights Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

Citrus Heights Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

Citrus Heights Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

Citrus Heights Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

Citrus Heights Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

Citrus Heights Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

Citrus Heights Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Citrus Heights Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Citrus Heights Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Citrus Heights Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

Citrus Heights Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) priority requests from transit vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

Citrus Heights Roadside Equipment Roadway Signal Priority The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Citrus Heights Roadside Equipment<br />

Citrus Heights Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Citrus Heights Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Citrus Heights Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Citrus Heights Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Citrus Heights Roadside Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Citrus Heights Roadside Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Citrus Heights Roadside Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Citrus Heights Roadside Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Citrus Heights Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

Citrus Heights Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Citrus Heights Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

Citrus Heights Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Citrus Heights Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Citrus Heights Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Citrus Heights Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Citrus Heights Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Citrus Heights Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

Citrus Heights Traffic Operations Center Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

Citrus Heights Traffic Operations Center TMC Signal Control The center shall remotely control traffic signal controllers.<br />

Citrus Heights Traffic Operations Center TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

Citrus Heights Traffic Operations Center TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

Citrus Heights Traffic Operations Center TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

Citrus Heights Traffic Operations Center TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

Citrus Heights Traffic Operations Center TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

Citrus Heights Traffic Operations Center TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

Citrus Heights Traffic Operations Center TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

Citrus Heights Traffic Operations Center TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

Citrus Heights Traffic Operations Center<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

Citrus Heights Traffic Operations Center<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

Citrus Heights Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Citrus Heights Traffic Operations Center TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

Citrus Heights Traffic Operations Center TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

Citrus Heights Traffic Operations Center TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

Citrus Heights Traffic Operations Center TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

Citrus Heights Traffic Operations Center Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

Citrus Heights Traffic Operations Center Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

Citrus Heights Traffic Operations Center Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect environmental sensor operational status.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

Citrus Heights Traffic Operations Center Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

Citrus Heights Traffic Operations Center TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

Citrus Heights Traffic Operations Center Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

Citrus Heights Traffic Operations Center Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Citrus Heights Traffic Operations Center Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

Citrus Heights Traffic Operations Center Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

City of Citrus Heights Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Davis Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

City of Davis Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Davis Field Equipment<br />

City of Davis Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Davis Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Davis Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Davis Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Davis Field Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Davis Field Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

City of Davis Field Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

City of Davis Field Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

City of Davis Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of Davis Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Davis Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Davis Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Davis Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Davis Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of Davis Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Davis Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Davis Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Davis Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Davis Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Davis Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of Davis Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Davis Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Davis Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

City of Davis Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

City of Davis Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

City of Davis Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

City of Davis Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

City of Davis Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Davis Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Davis Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Davis Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Davis Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Davis Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

City of Davis Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Davis Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Davis Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Davis Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Davis TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Davis TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Davis TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Davis TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Davis TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Davis TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Davis TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Davis TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Davis TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Davis TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Davis TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Davis TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Davis TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Davis TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Davis TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Davis TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Davis TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Davis TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Davis TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Davis TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Davis TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Davis TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Davis TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

City of Davis TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Davis TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Davis TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Davis TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Davis TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Davis TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Davis TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Davis TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Davis TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Davis TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Davis TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Davis TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Davis TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Davis TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Davis TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Davis TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Davis TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Davis TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Davis TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Elk Grove Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

City of Elk Grove Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Elk Grove Field Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

City of Elk Grove Field Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) priority requests from transit vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

City of Elk Grove Field Equipment Roadway Signal Priority The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.<br />

City of Elk Grove Field Equipment<br />

City of Elk Grove Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Elk Grove Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Elk Grove Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Elk Grove Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Elk Grove Field Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Elk Grove Field Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

City of Elk Grove Field Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

City of Elk Grove Field Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

City of Elk Grove Field Equipment Standard Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

City of Elk Grove Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of Elk Grove Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Elk Grove Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Elk Grove Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Elk Grove Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Elk Grove Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Elk Grove Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Elk Grove Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Elk Grove Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Elk Grove Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Elk Grove Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Elk Grove Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of Elk Grove Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Elk Grove Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Elk Grove Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

City of Elk Grove Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

City of Elk Grove Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

City of Elk Grove Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

City of Elk Grove Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

City of Elk Grove Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Elk Grove Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Elk Grove Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Elk Grove Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Elk Grove Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Elk Grove Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Elk Grove Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Elk Grove Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Elk Grove Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Elk Grove Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Elk Grove TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Elk Grove TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Elk Grove TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Elk Grove TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Elk Grove TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Elk Grove TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Elk Grove TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Elk Grove TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of Elk Grove TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

City of Elk Grove TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Elk Grove TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Elk Grove TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Elk Grove TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Elk Grove TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Elk Grove TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Elk Grove TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

City of Elk Grove TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Elk Grove TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Elk Grove TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Elk Grove TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Elk Grove TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Elk Grove TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Elk Grove TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Elk Grove TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Elk Grove TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Elk Grove TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Elk Grove TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Elk Grove TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Elk Grove TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Elk Grove TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Folsom Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

City of Folsom Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Folsom Field Equipment<br />

City of Folsom Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Folsom Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Folsom Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Folsom Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Folsom Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Folsom Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Folsom Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Folsom Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Folsom Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Folsom Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of Folsom Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Folsom Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Folsom Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Folsom Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Folsom Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Folsom Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of Folsom Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Folsom Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Folsom Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

City of Folsom Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

City of Folsom Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

City of Folsom Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

City of Folsom Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Folsom Maintenance Dispatch<br />

City of Folsom Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Folsom Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Folsom Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Folsom Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Folsom Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Folsom Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

City of Folsom Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Folsom Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Folsom Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Folsom Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Folsom TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Folsom TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Folsom TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Folsom TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Folsom TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Folsom TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Folsom TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Folsom TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of Folsom TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

City of Folsom TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Folsom TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Folsom TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Folsom TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Folsom TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Folsom TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Folsom TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Folsom TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

City of Folsom TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Folsom TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Folsom TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Folsom TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Folsom TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Folsom TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Folsom TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Folsom TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Folsom TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Folsom TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Folsom TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Folsom TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Folsom TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Folsom TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Folsom TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Folsom TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Folsom TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Folsom TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Folsom TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Rancho Cordova Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Rancho Cordova Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Rancho Cordova Field Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

City of Rancho Cordova Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Rancho Cordova Field Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Rancho Cordova Field Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Rancho Cordova Field Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Rancho Cordova Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of Rancho Cordova Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Rancho Cordova Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Rancho Cordova Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Rancho Cordova Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Rancho Cordova Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of Rancho Cordova Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Rancho Cordova Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Rancho Cordova Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

City of Rancho Cordova Maintenance<br />

Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Rancho Cordova Maintenance MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

Dispatch<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Rancho Cordova TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Rancho Cordova TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Rancho Cordova TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Rancho Cordova TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Rancho Cordova TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Rancho Cordova TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Rancho Cordova TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Rancho Cordova TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of Rancho Cordova TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Rancho Cordova TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Rancho Cordova TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

City of Rancho Cordova TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Rancho Cordova TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Rancho Cordova TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Rancho Cordova TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Rancho Cordova TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Rancho Cordova TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Rancho Cordova TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Rancho Cordova TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Rancho Cordova TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Rancho Cordova TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Rancho Cordova TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Rancho Cordova TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Roseville Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Roseville Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Roseville Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

The center shall remotely control environmental sensors on­board maintenance and construction vehicles that measure<br />

road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and<br />

other measures.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from traffic, emergency, and transit management, traveler information providers, and<br />

environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and<br />

construction vehicles.<br />

The center shall provide weather and road condition information to weather service providers and center personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall collect operational status for the roadside and vehicle­based environmental sensor equipment.<br />

The center shall collect fault data for the roadside and vehicle­based environmental sensor equipment for repair.<br />

City of Roseville Maintenance Dispatch<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

City of Roseville Maintenance Dispatch<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

City of Roseville Maintenance Dispatch MCM Environmental Information The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

Processing<br />

and predicted road weather and road conditions.<br />

City of Roseville Maintenance Dispatch MCM Environmental Information The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

Processing<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

City of Roseville Maintenance Dispatch MCM Environmental Information The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

Processing<br />

treatment information that supports forecasts for road conditions.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Roseville Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Roseville Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

City of Roseville Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

City of Roseville Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

City of Roseville Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

City of Roseville Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

City of Roseville Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Roseville Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Roseville Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Roseville Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Roseville Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Roseville Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

City of Roseville Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Roseville Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Roseville Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Roseville Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall update the incident information log once the emergency system operator has verified the incident.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Call­Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

City of Roseville Police and Fire Dispatch Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

City of Roseville Police and Fire Dispatch Emergency Routing The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

City of Roseville Police and Fire Dispatch Emergency Routing The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Police and Fire Dispatch Emergency Routing The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

City of Roseville Police and Fire Dispatch Emergency Routing In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

City of Roseville Police and Fire Dispatch Emergency Routing The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

City of Roseville Police and Fire Dispatch Emergency Routing Once the route is calculated the route shall be provided to the dispatch function.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

City of Roseville Police and Fire Dispatch Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

City of Roseville Police and Fire Dispatch Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

City of Roseville Police and Fire Dispatch Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

City of Roseville Police and Fire Dispatch Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

City of Roseville Police and Fire Dispatch Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

City of Roseville Police and Fire Dispatch Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

City of Roseville Police and Fire Dispatch Emergency Environmental Monitoring The center shall collect current and forecast road and weather information from weather service providers (such as the<br />

National Weather Service and value­added sector specific meteorological services).<br />

City of Roseville Police and Fire Dispatch Emergency Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information to support incident<br />

management.<br />

City of Roseville Police and Fire Dispatch Emergency Environmental Monitoring The center shall present the current and forecast road and weather information to the emergency system operator.<br />

City of Roseville Police and Fire Dispatch Emergency Environmental Monitoring The center shall provide aggregated or processed environmental probe information from its fleet of emergency vehicles to<br />

traffic management and maintenance centers.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which<br />

include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g.,<br />

emergency pull­off areas and travel information centers). The data may be raw or pre­processed in the field.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations,<br />

transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and<br />

travel information centers).<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall match traveler video images against a database from the Alerting and Advisory Systems of known<br />

images that may represent criminals and terrorists.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

City of Roseville Police and Fire Dispatch<br />

City of Roseville Police and Fire Dispatch<br />

Center Secure Area Sensor<br />

Management<br />

Center Secure Area Sensor<br />

Management<br />

The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g.<br />

transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit<br />

railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic<br />

industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and<br />

motion, and object detection sensors. The data may be raw or pre­processed in the field.<br />

The center shall remotely monitor and control security sensor data collected in traveler secure areas, which include transit<br />

stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off<br />

areas and travel information centers). The types of security sensor data include environmental threat (e.g. chemical<br />

agent, toxic industrial chemical, biological, explosives, and radiological sensors), intrusion and motion, and object<br />

detection sensors. The data may be raw or pre­processed in the field.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Police and Fire Dispatch<br />

Center Secure Area Sensor<br />

Management<br />

The center shall remotely monitor and control security sensor data collected on­board transit vehicles. The types of<br />

security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives,<br />

and radiological sensors) and object detection sensors. The data may be raw or pre­processed in the field.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

The center shall exchange security sensor data with other emergency centers.<br />

Management<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

The center shall identify potential security threats based on collected security sensor data.<br />

Management<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

The center shall verify potential security threats by correlating security sensor data from multiple sources.<br />

Management<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

The center shall perform threat analysis based on correlations of security sensor and surveillance data.<br />

Management<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

Management<br />

The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat<br />

analysis processing.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

Management<br />

The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations,<br />

and other emergency management centers.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Sensor<br />

Management<br />

The center shall respond to control data from center personnel regarding security sensor data collection, processing,<br />

threat detection, and threat analysis.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest<br />

areas, park and ride lots, modal interchange facilities).<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

City of Roseville Police and Fire Dispatch Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

City of Roseville Police and Fire Dispatch Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

City of Roseville Police and Fire Dispatch Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Roseville Police and Fire Dispatch Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

City of Roseville Police and Fire Dispatch Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Roseville Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall use toll and parking tags on passing vehicles for traffic data link time calculations and send to the<br />

controlling center; tag identities will be removed to ensure anonymity.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors traffic conditions (e.g., average speed) by communicating with<br />

passing vehicles equipped with a transponder or other short range communications device; also called smart probes.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors road conditions by communicating with passing vehicles<br />

equipped with a transponder or other short range communications device; also called smart probes.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall aggregate, format, and store collected vehicle smart probe data (traffic and road conditions data),<br />

calculate link travel times and processed road condition data, and send to future passing vehicles.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment operational status to the center.<br />

City of Roseville Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment fault indication to the center for repair.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

City of Roseville Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Roseville Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

City of Roseville Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) priority requests from transit vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

City of Roseville Roadside Equipment Roadway Signal Priority The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.<br />

City of Roseville Roadside Equipment<br />

City of Roseville Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Roseville Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Roseville Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Roseville Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Roseville Roadside Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Roseville Roadside Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

City of Roseville Roadside Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

City of Roseville Roadside Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

City of Roseville Roadside Equipment Standard Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

City of Roseville Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of Roseville Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Roseville Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Roseville Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall include surface and sub­surface environmental sensors that measure road surface temperature,<br />

moisture, icing, salinity, and other measures.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall include environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a maintenance center.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a traffic management center.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by weather service providers such as the National<br />

Weather Service or value­added sector specific meteorological services.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a maintenance and construction vehicle.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall provide environmental sensor equipment operational status to the controlling center or<br />

maintenance vehicle.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall provide environmental sensor equipment fault indication to the controlling center or maintenance<br />

vehicle.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall remotely aggregate environmental sensor data with environmental data collected from<br />

maintenance and construction vehicles.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall provide weather and road surface condition data to centers.<br />

City of Roseville Roadside Equipment Roadway Environmental Monitoring The field element shall provide weather and road surface condition data to maintenance and construction vehicles.<br />

City of Roseville Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Roseville Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of Roseville Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Roseville Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Roseville Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Roseville TOC TBD TBD<br />

City of Roseville TOC TBD TBD<br />

City of Roseville TOC<br />

MCM Environmental Information<br />

Collection<br />

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

City of Roseville TOC<br />

MCM Environmental Information<br />

Collection<br />

The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

The center shall remotely control environmental sensors on­board maintenance and construction vehicles that measure<br />

road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and<br />

other measures.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from traffic, emergency, and transit management, traveler information providers, and<br />

environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and<br />

construction vehicles.<br />

The center shall provide weather and road condition information to weather service providers and center personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall collect operational status for the roadside and vehicle­based environmental sensor equipment.<br />

The center shall collect fault data for the roadside and vehicle­based environmental sensor equipment for repair.<br />

City of Roseville TOC<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

City of Roseville TOC<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

City of Roseville TOC<br />

MCM Environmental Information The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

Processing<br />

and predicted road weather and road conditions.<br />

City of Roseville TOC<br />

MCM Environmental Information The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

Processing<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

City of Roseville TOC<br />

MCM Environmental Information The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

Processing<br />

treatment information that supports forecasts for road conditions.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Roseville TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Roseville TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Roseville TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Roseville TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Roseville TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Roseville TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Roseville TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Roseville TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of Roseville TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

City of Roseville TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Roseville TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Roseville TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Roseville TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Roseville TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Roseville TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Roseville TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Roseville TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

City of Roseville TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Roseville TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Roseville TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Roseville TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Roseville TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Roseville TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Roseville TOC TMC Environmental Monitoring The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

City of Roseville TOC TMC Environmental Monitoring The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville TOC TMC Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from roadway maintenance operations, and environmental data collected from sensors<br />

deployed on and about the roadway.<br />

City of Roseville TOC TMC Environmental Monitoring The center shall provide weather and road condition information to weather service providers and center personnel.<br />

City of Roseville TOC TMC Environmental Monitoring The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

City of Roseville TOC HRI Traffic Management The center shall remotely control highway­rail intersection (HRI) equipment located in the field.<br />

City of Roseville TOC HRI Traffic Management The center shall accept collect highway­rail intersection (HRI) advisory or alert data from rail operations centers.<br />

City of Roseville TOC HRI Traffic Management The center shall collect highway­rail intersection (HRI) equipment operational status and compare against the control<br />

information sent by the center.<br />

City of Roseville TOC HRI Traffic Management The center shall provide the highway­rail intersection (HRI) equipment operational status to rail operations centers.<br />

City of Roseville TOC HRI Traffic Management The center shall collect incident information related to a highway­rail intersection (HRI), such as intersection blockages or<br />

crashes or equipment malfunctions.<br />

City of Roseville TOC HRI Traffic Management The center shall implement control plans to coordinate signalized intersections around highway­rail intersections (HRI),<br />

under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents,<br />

equipment faults, pedestrian crossings, etc.<br />

City of Roseville TOC Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

City of Roseville TOC Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

City of Roseville TOC Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

City of Roseville TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Roseville TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Roseville TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Roseville TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Roseville TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Roseville TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Roseville TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Roseville TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Roseville TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Roseville TOC TMC Multimodal Coordination The center shall respond to requests from transit management centers for signal priority at one or more intersections<br />

along a particular transit route.<br />

City of Roseville TOC TMC Multimodal Coordination The center shall exchange information with transit management centers including details current transit routes, the level<br />

of service on each route, and the progress of individual vehicles along their routes.<br />

City of Roseville TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Roseville TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Roseville TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Roseville TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

City of Roseville Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

City of Roseville Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

City of Roseville Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

City of Roseville Website Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

City of Roseville Website Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

City of Roseville Website Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

City of Roseville Website Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

City of Roseville Website Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

City of Roseville Website Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

City of Roseville Website Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

City of Roseville Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Roseville Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

City of Roseville Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

City of Roseville Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

City of Sacramento Equipment Shop TBD TBD<br />

City of Sacramento Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Sacramento Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Sacramento Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of Sacramento Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Sacramento Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Sacramento Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

City of Sacramento Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Sacramento Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Sacramento Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Sacramento Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Sacramento Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Sacramento Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

City of Sacramento Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Sacramento Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Sacramento Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Sacramento Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Sacramento Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle<br />

location determination function.<br />

City of Sacramento Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

City of Sacramento Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall collect vehicle diagnostics and operating status data from the<br />

maintenance vehicle platform including engine temperature, mileage, tire wear, brake wear, belt wear, and other<br />

operational status measures as well as the status of maintenance and construction­specific systems on the vehicle.<br />

The maintenance and construction vehicle shall use the diagnostic and status information to support scheduling vehicle<br />

maintenance, monitoring safety status, and informing the vehicle operator of the conditions.<br />

The maintenance and construction vehicle shall the vehicle diagnostic and safety information to an equipment repair<br />

facility.<br />

The maintenance and construction vehicle shall send the vehicle diagnostic and safety information to the controlling<br />

maintenance center.<br />

The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include routine maintenance equipment for cutting, repairs, hazard<br />

removal, etc.<br />

The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.<br />

The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

City of Sacramento Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall monitor, operate, and control work zone devices located at or alongside<br />

the roadway. The devices operated on board the vehicle include driver information devices (e.g. dynamic message signs)<br />

and work zone intrusion detection and alert devices.<br />

City of Sacramento Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone<br />

activities.<br />

City of Sacramento Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on­board<br />

the maintenance and construction vehicle and send them to the controlling center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Sacramento TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Sacramento TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Sacramento TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Sacramento TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Sacramento TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Sacramento TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Sacramento TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Sacramento TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of Sacramento TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Sacramento TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Sacramento TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Sacramento TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Sacramento TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Sacramento TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Sacramento TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Sacramento TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

City of Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of Sacramento TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Sacramento TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Sacramento TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Sacramento TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Sacramento TOC TMC Environmental Monitoring The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

City of Sacramento TOC TMC Environmental Monitoring The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

City of Sacramento TOC TMC Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from roadway maintenance operations, and environmental data collected from sensors<br />

deployed on and about the roadway.<br />

City of Sacramento TOC TMC Environmental Monitoring The center shall provide weather and road condition information to weather service providers and center personnel.<br />

City of Sacramento TOC TMC Environmental Monitoring The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

City of Sacramento TOC HRI Traffic Management The center shall remotely control highway­rail intersection (HRI) equipment located in the field.<br />

City of Sacramento TOC HRI Traffic Management The center shall accept collect highway­rail intersection (HRI) advisory or alert data from rail operations centers.<br />

City of Sacramento TOC HRI Traffic Management The center shall collect highway­rail intersection (HRI) equipment operational status and compare against the control<br />

information sent by the center.<br />

City of Sacramento TOC HRI Traffic Management The center shall provide the highway­rail intersection (HRI) equipment operational status to rail operations centers.<br />

City of Sacramento TOC HRI Traffic Management The center shall collect incident information related to a highway­rail intersection (HRI), such as intersection blockages or<br />

crashes or equipment malfunctions.<br />

City of Sacramento TOC HRI Traffic Management The center shall implement control plans to coordinate signalized intersections around highway­rail intersections (HRI),<br />

under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents,<br />

equipment faults, pedestrian crossings, etc.<br />

City of Sacramento TOC Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

City of Sacramento TOC Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

City of Sacramento TOC Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Sacramento TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Sacramento TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Sacramento TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Sacramento TOC TMC Multimodal Coordination The center shall respond to requests from transit management centers for signal priority at one or more intersections<br />

along a particular transit route.<br />

City of Sacramento TOC TMC Multimodal Coordination The center shall exchange information with transit management centers including details current transit routes, the level<br />

of service on each route, and the progress of individual vehicles along their routes.<br />

City of Sacramento TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Sacramento TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Sacramento TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Sacramento TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

City of Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

City of Sacramento Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

City of Sacramento Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

City of Sacramento Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

City of Sacramento Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

City of Sacramento Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

City of Sacramento Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

MCM Vehicle Tracking<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Maintenance<br />

Dispatch<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Controls<br />

Roadway Signal Priority<br />

Roadway Signal Priority<br />

Roadway Incident Detection<br />

Roadway Incident Detection<br />

Roadway Incident Detection<br />

Roadway Incident Detection<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

The center shall exchange rail schedules and work plans with rail operations centers.<br />

The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

The field element shall return sensor and CCTV system operational status to the controlling center.<br />

The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

The field element shall return traffic signal controller operational status to the controlling center.<br />

The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.<br />

The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

The field element's video devices shall be remotely controlled by a traffic management center.<br />

The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of West Sacramento Roadside<br />

Equipment<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

Standard Rail Crossing<br />

The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Standard Rail Crossing<br />

The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of West Sacramento Roadside<br />

Equipment<br />

Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of West Sacramento TOC TBD TBD<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of West Sacramento TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of West Sacramento TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of West Sacramento TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of West Sacramento TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of West Sacramento TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of West Sacramento TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of West Sacramento TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of West Sacramento TOC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

City of West Sacramento TOC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

City of West Sacramento TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of West Sacramento TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of West Sacramento TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of West Sacramento TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of West Sacramento TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of West Sacramento TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of West Sacramento TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of West Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

City of West Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of West Sacramento TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

City of West Sacramento TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of West Sacramento TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of West Sacramento TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of West Sacramento TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of West Sacramento TOC HRI Traffic Management The center shall remotely control highway­rail intersection (HRI) equipment located in the field.<br />

City of West Sacramento TOC HRI Traffic Management The center shall accept collect highway­rail intersection (HRI) advisory or alert data from rail operations centers.<br />

City of West Sacramento TOC HRI Traffic Management The center shall collect highway­rail intersection (HRI) equipment operational status and compare against the control<br />

information sent by the center.<br />

City of West Sacramento TOC HRI Traffic Management The center shall provide the highway­rail intersection (HRI) equipment operational status to rail operations centers.<br />

City of West Sacramento TOC HRI Traffic Management The center shall collect incident information related to a highway­rail intersection (HRI), such as intersection blockages or<br />

crashes or equipment malfunctions.<br />

City of West Sacramento TOC HRI Traffic Management The center shall implement control plans to coordinate signalized intersections around highway­rail intersections (HRI),<br />

under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents,<br />

equipment faults, pedestrian crossings, etc.<br />

City of West Sacramento TOC Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

City of West Sacramento TOC Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

City of West Sacramento TOC Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of West Sacramento TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of West Sacramento TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of West Sacramento TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of West Sacramento TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of West Sacramento TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of West Sacramento TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of West Sacramento TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of West Sacramento TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

City of West Sacramento Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

City of West Sacramento Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

City of West Sacramento Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

City of West Sacramento Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

City of West Sacramento Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

City of West Sacramento Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

City of West Sacramento Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

City of Woodland Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

City of Woodland Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

City of Woodland Field Equipment<br />

City of Woodland Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

City of Woodland Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

City of Woodland Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

City of Woodland Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

City of Woodland Field Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

City of Woodland Field Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

City of Woodland Field Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

City of Woodland Field Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

City of Woodland Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

City of Woodland Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

City of Woodland Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

City of Woodland Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

City of Woodland Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

City of Woodland Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

City of Woodland Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

City of Woodland Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

City of Woodland Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

City of Woodland Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

City of Woodland Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

City of Woodland Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Woodland Maintenance Dispatch MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Woodland Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

City of Woodland Maintenance Dispatch MCM Maintenance Decision Support The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

City of Woodland Maintenance Dispatch MCM Maintenance Decision Support The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

City of Woodland Maintenance Dispatch MCM Maintenance Decision Support The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

City of Woodland Maintenance Dispatch MCM Maintenance Decision Support The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

City of Woodland Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

City of Woodland Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

City of Woodland Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

City of Woodland Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

City of Woodland Maintenance Dispatch MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

City of Woodland Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

City of Woodland Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

City of Woodland Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

City of Woodland Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

City of Woodland Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

City of Woodland Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

City of Woodland TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

City of Woodland TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

City of Woodland TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

City of Woodland TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

City of Woodland TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

City of Woodland TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

City of Woodland TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

City of Woodland TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

City of Woodland TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

City of Woodland TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

City of Woodland TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

City of Woodland TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

City of Woodland TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

City of Woodland TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

City of Woodland TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

City of Woodland TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

City of Woodland TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

City of Woodland TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

City of Woodland TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

City of Woodland TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

City of Woodland TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

City of Woodland TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

City of Woodland TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

City of Woodland TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

City of Woodland TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

City of Woodland TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

City of Woodland TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

City of Woodland TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

City of Woodland TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

City of Woodland TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

City of Woodland TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

City of Woodland TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

City of Woodland TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

City/County Animal Control<br />

Commercial Vehicle Fleet Dispatch Systems Fleet HAZMAT Management The center shall track the routing and cargo information, including the manifest data plus the chemical characteristics of a<br />

hazardous materials (HAZMAT) load being carried by its fleet of commercial vehicles.<br />

Commercial Vehicle Fleet Dispatch Systems Fleet HAZMAT Management The center shall provide information concerning commercial vehicles carrying hazardous materials (HAZMAT) upon<br />

request from an emergency management center. The information includes the nature of the cargo being carried, identity<br />

of the vehicle and unloading instructions.<br />

Commercial Vehicles On­board Cargo Monitoring The commercial vehicle shall compute the location of the commercial vehicle and its freight equipment based on inputs<br />

from a vehicle location determination function.<br />

Commercial Vehicles On­board Cargo Monitoring The commercial vehicle shall monitor on­board systems and record measures such as weight, vehicle security status,<br />

vehicle safety status, vehicle identity, driver status, driver safety status, distance traveled, and brake condition.<br />

Commercial Vehicles On­board Cargo Monitoring The commercial vehicle shall monitor information concerning the freight equipment including cargo type, HAZMAT<br />

designation (if any) for the cargo, cargo weight, the type of container in which the cargo is held, safety condition of the<br />

cargo, etc.<br />

Commercial Vehicles On­board Cargo Monitoring The commercial vehicle shall forward information concerning the freight equipment on to its fleet and freight management<br />

center as well as the roadside check facility.<br />

Commercial Vehicles On­board Cargo Monitoring The commercial vehicle shall send notification of a hazmat spill to appropriate emergency management center in case of<br />

an incident including the information from cargo sensors, vehicle location, and the carrier identification.<br />

County AQMD Emissions Data Management The center shall collect, analyze, and store vehicle emissions data collected from roadside sensors.<br />

County AQMD Emissions Data Management The center shall collect, analyze, and store wide area pollution data collected from sensors that may the general (wide<br />

area) environment.<br />

County AQMD Emissions Data Management The center shall configure and control emissions and air quality sensors located in the field.<br />

County AQMD Emissions Data Management The center shall maintain a database of pollution reference data including acceptable and tolerable emissions and<br />

pollution levels for the area served by the center.<br />

County AQMD Emissions Data Management The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for emissions.<br />

County AQMD Emissions Data Management The center shall establish violation parameters, detect emissions violators, obtain the vehicle registration data from the<br />

appropriate State Department of Motor Vehicles (DMV) office, and then provide the capability to send violation information<br />

to a law enforcement agency.<br />

County AQMD Emissions Data Management The center shall distribute air quality information to the media, traveler information service providers, and traffic<br />

management centers. This information may be used for information to travelers or part of demand management<br />

programs.<br />

County AQMD<br />

County EOC Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

County EOC Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

County EOC Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

County EOC Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

County EOC Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

County EOC Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

County EOC Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

County EOC Emergency Response Management The center shall provide strategic emergency response capabilities such as that of an Emergency Operations Center for<br />

large­scale incidents and disasters.<br />

County EOC Emergency Response Management The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.<br />

County EOC Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

County EOC Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

County EOC Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

County EOC Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

County EOC Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

County EOC Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

County EOC Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

County EOC Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

County EOC Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

County EOC Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

County EOC Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

County EOC Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

County EOC Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

County EOC Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

County EOC Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

County EOC Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

County EOC Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

County EOC Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

County EOC Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

County EOC Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

County EOC Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

County EOC Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

County EOC Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

County EOC Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

County EOC Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

County EOC Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

County EOC Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

County EOC Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

County EOC Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

County EOC Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

County EOC Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

County EOC Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

County Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

County Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

County Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

County Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

County Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

County Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

County Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

County Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

County Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

County Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

County Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

County Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

County Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

County Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

County Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

County Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

County Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

County Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

County Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

County Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

County Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

County Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

County Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle<br />

location determination function.<br />

County Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.<br />

County Maintenance Vehicles<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

County Maintenance Vehicles<br />

County Maintenance Vehicles<br />

County Maintenance Vehicles<br />

County Maintenance Vehicles<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include routine maintenance equipment for cutting, repairs, hazard<br />

removal, etc.<br />

The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.<br />

The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall monitor, operate, and control work zone devices located at or alongside<br />

the roadway. The devices operated on board the vehicle include driver information devices (e.g. dynamic message signs)<br />

and work zone intrusion detection and alert devices.<br />

County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone<br />

activities.<br />

County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on­board<br />

the maintenance and construction vehicle and send them to the controlling center.<br />

County Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

County Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

County Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

County Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

County Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall update the incident information log once the emergency system operator has verified the incident.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Call­Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

County Sheriff Communications Centers Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

County Sheriff Communications Centers Emergency Routing The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

County Sheriff Communications Centers Emergency Routing The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

County Sheriff Communications Centers Emergency Routing The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

County Sheriff Communications Centers Emergency Routing In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

County Sheriff Communications Centers Emergency Routing The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

County Sheriff Communications Centers Emergency Routing Once the route is calculated the route shall be provided to the dispatch function.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

County Sheriff Communications Centers Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

County Sheriff Communications Centers Emergency Response Management The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

County Sheriff Communications Centers Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

County Sheriff Communications Centers Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

County Sheriff Communications Centers Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

County Sheriff Communications Centers Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

County Sheriff Communications Centers Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

County Sheriff Communications Centers Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

County Sheriff Communications Centers Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

County Sheriff Communications Centers Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

County Sheriff Communications Centers Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

County Sheriff Communications Centers Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

County Sheriff Communications Centers Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

County Sheriff Communications Centers Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

County Sheriff Communications Centers Emergency Environmental Monitoring The center shall collect current and forecast road and weather information from weather service providers (such as the<br />

National Weather Service and value­added sector specific meteorological services).<br />

County Sheriff Communications Centers Emergency Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information to support incident<br />

management.<br />

County Sheriff Communications Centers Emergency Environmental Monitoring The center shall present the current and forecast road and weather information to the emergency system operator.<br />

County Sheriff Communications Centers Emergency Environmental Monitoring The center shall provide aggregated or processed environmental probe information from its fleet of emergency vehicles to<br />

traffic management and maintenance centers.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall match traveler video images against a database from the Alerting and Advisory Systems of known<br />

images that may represent criminals and terrorists.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

County Sheriff Communications Centers Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

County Sheriff Communications Centers<br />

Center Secure Area Sensor<br />

Management<br />

Center Secure Area Sensor<br />

Management<br />

Center Secure Area Sensor<br />

Management<br />

The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g.<br />

transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit<br />

railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic<br />

industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and<br />

motion, and object detection sensors. The data may be raw or pre­processed in the field.<br />

The center shall remotely monitor and control security sensor data collected in traveler secure areas, which include transit<br />

stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off<br />

areas and travel information centers). The types of security sensor data include environmental threat (e.g. chemical<br />

agent, toxic industrial chemical, biological, explosives, and radiological sensors), intrusion and motion, and object<br />

detection sensors. The data may be raw or pre­processed in the field.<br />

The center shall remotely monitor and control security sensor data collected on­board transit vehicles. The types of<br />

security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives,<br />

and radiological sensors) and object detection sensors. The data may be raw or pre­processed in the field.<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

The center shall exchange security sensor data with other emergency centers.<br />

Management<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

The center shall identify potential security threats based on collected security sensor data.<br />

Management<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

The center shall verify potential security threats by correlating security sensor data from multiple sources.<br />

Management<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

The center shall perform threat analysis based on correlations of security sensor and surveillance data.<br />

Management<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

Management<br />

The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat<br />

analysis processing.<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

Management<br />

The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations,<br />

and other emergency management centers.<br />

County Sheriff Communications Centers Center Secure Area Sensor<br />

Management<br />

The center shall respond to control data from center personnel regarding security sensor data collection, processing,<br />

threat detection, and threat analysis.<br />

County Sheriff Communications Centers Center Secure Area Alarm Support The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest<br />

areas, park and ride lots, modal interchange facilities).<br />

County Sheriff Communications Centers Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

County Sheriff Communications Centers Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.<br />

County Sheriff Communications Centers Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

County Sheriff Communications Centers Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

County Sheriff Communications Centers Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

County Sheriff Communications Centers Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

County Sheriff Communications Centers Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

County Sheriff Communications Centers Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

County Sheriff Communications Centers Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

Driver TBD TBD<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

El Dorado Transit Dispatch Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

El Dorado Transit Dispatch Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

El Dorado Transit Dispatch Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

El Dorado Transit Dispatch Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

El Dorado Transit Dispatch Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

El Dorado Transit Dispatch Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

El Dorado Transit Dispatch Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

El Dorado Transit Dispatch Transit Center Paratransit Operations The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

El Dorado Transit Dispatch Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

El Dorado Transit Dispatch Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

El Dorado Transit Dispatch Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

El Dorado Transit Dispatch Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

El Dorado Transit Dispatch Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

El Dorado Transit Dispatch Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

El Dorado Transit Dispatch Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

El Dorado Transit Dispatch Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

El Dorado Transit Dispatch Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

El Dorado Transit Dispatch Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

El Dorado Transit Dispatch Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

El Dorado Transit Dispatch Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

El Dorado Transit Dispatch Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

El Dorado Transit Dispatch Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

El Dorado Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

El Dorado Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall send requests for priority along routes or at intersections to traffic management.<br />

El Dorado Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

El Dorado Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

El Dorado Transit Dispatch Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

El Dorado Transit Dispatch Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

El Dorado Transit Dispatch Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

El Dorado Transit Dispatch Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

El Dorado Transit Dispatch Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

El Dorado Transit Dispatch Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

El Dorado Transit Dispatch Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

El Dorado Transit Dispatch Transit Data Collection The center shall be able to produce sample products of the data available.<br />

El Dorado Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

El Dorado Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

El Dorado Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

El Dorado Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

El Dorado Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

El Dorado Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

El Dorado Transit Vehicles On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

El Dorado Transit Vehicles On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

El Dorado Transit Vehicles On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed sensor information to the<br />

center along with the vehicleÆs current location.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

El Dorado Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

El Dorado Transit Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

El Dorado Transit Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

El Dorado Transit Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

El Dorado Transit Vehicles On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

e­tran Transit Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which<br />

include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g.,<br />

emergency pull­off areas and travel information centers). The data may be raw or pre­processed in the field.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

e­tran Transit Center Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

e­tran Transit Center Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

e­tran Transit Center Center Secure Area Alarm Support The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest<br />

areas, park and ride lots, modal interchange facilities).<br />

e­tran Transit Center Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

e­tran Transit Center Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.<br />

e­tran Transit Center Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

e­tran Transit Center Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

e­tran Transit Center Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

e­tran Transit Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

e­tran Transit Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

e­tran Transit Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

e­tran Transit Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

e­tran Transit Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

e­tran Transit Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

e­tran Transit Center Transit Center Paratransit Operations The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

e­tran Transit Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

e­tran Transit Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

e­tran Transit Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

e­tran Transit Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

e­tran Transit Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

e­tran Transit Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

e­tran Transit Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

e­tran Transit Center Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

e­tran Transit Center Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

e­tran Transit Center Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

e­tran Transit Center Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

e­tran Transit Center Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

e­tran Transit Center Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

e­tran Transit Center Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

e­tran Transit Center Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

e­tran Transit Center Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

e­tran Transit Center Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

e­tran Transit Center Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

e­tran Transit Center Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

e­tran Transit Center Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

e­tran Transit Center Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

e­tran Transit Center Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

e­tran Transit Center Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

e­tran Transit Center Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

e­tran Transit Center Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

e­tran Transit Center<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

e­tran Transit Center<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

e­tran Transit Center Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

e­tran Transit Center Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

e­tran Transit Center Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

e­tran Transit Center Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

e­tran Transit Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

e­tran Transit Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

e­tran Transit Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

e­tran Transit Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

e­tran Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

e­tran Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

e­tran Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

e­tran Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

e­tran Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

e­tran Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

e­tran Transit Vehicles On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

e­tran Transit Vehicles On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

e­tran Transit Vehicles On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

e­tran Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

e­tran Transit Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

e­tran Transit Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

e­tran Transit Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

e­tran Transit Vehicles On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Financial Institutions TBD TBD<br />

Folsom Stage Line Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Folsom Stage Line Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Folsom Stage Line Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Folsom Stage Line Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Folsom Stage Line Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Folsom Stage Line Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Folsom Stage Line Vehicles On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

Folsom Stage Line Vehicles On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

Folsom Stage Line Vehicles On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Folsom Stage Line Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Folsom Stage Line Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Folsom Stage Line Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Folsom Stage Line Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Folsom Stage Line Vehicles On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations,<br />

transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and<br />

travel information centers).<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

Folsom Stage Lines Transit Dispatch Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

Folsom Stage Lines Transit Dispatch Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Folsom Stage Lines Transit Dispatch Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Folsom Stage Lines Transit Dispatch Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Folsom Stage Lines Transit Dispatch Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Folsom Stage Lines Transit Dispatch Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Folsom Stage Lines Transit Dispatch Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Folsom Stage Lines Transit Dispatch Transit Center Paratransit Operations The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Folsom Stage Lines Transit Dispatch Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

Folsom Stage Lines Transit Dispatch Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Folsom Stage Lines Transit Dispatch Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Folsom Stage Lines Transit Dispatch Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Folsom Stage Lines Transit Dispatch Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Folsom Stage Lines Transit Dispatch Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Folsom Stage Lines Transit Dispatch Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Folsom Stage Lines Transit Dispatch Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Folsom Stage Lines Transit Dispatch Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Folsom Stage Lines Transit Dispatch Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Folsom Stage Lines Transit Dispatch Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Folsom Stage Lines Transit Dispatch Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Folsom Stage Lines Transit Dispatch Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Freeway Service Patrol Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Freeway Service Patrol Vehicles<br />

Freeway Service Patrol Vehicles<br />

Freeway Service Patrol Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

Heavy Rail Wayside Equipment TBD TBD<br />

Light Rail Station Parking Mgmt. Parking Surveillance The parking element shall provide the capability to detect and classify vehicles entering and exiting a parking facility<br />

(vehicle size, type, identifiable features, etc.).<br />

Light Rail Station Parking Mgmt. Parking Management The parking element shall maintain parking lot information including static information such as hours of operation, rates,<br />

location, entrance locations, capacity, type, and constraints; as well as dynamic information such as current state of the<br />

lot, occupancy, arrival rates, and departure rates.<br />

Light Rail Station Parking Mgmt. Parking Management The parking element shall distribute parking lot information upon request to traffic management centers, transit<br />

management centers for park and ride facilities, and to traveler information providers.<br />

Light Rail Station Parking Mgmt. Parking Management The parking element manage local dynamic message signs that display messages to travelers such as the parking lot<br />

state, number of spaces available, location of entrances, and current charges.<br />

Light Rail Station Parking Mgmt. Parking Management The parking element shall support requests for parking reservations.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall detect and classify vehicles entering and exiting a parking facility (vehicle size, type, identifiable<br />

features, etc.).<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall read data from the traveler card / payment instrument carried on­board the vehicle (tag) or by<br />

the traveler.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall provide an interface to the driver informing them of the success or failure of the financial<br />

transaction. This may involve a request for the driver to pull aside so the operator can resolve an issue.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall collect data on payment violations and send the data, including images of the violator and the<br />

vehicle registration data obtained from the Department of Motor Vehicles (DMV) office, to the appropriate enforcement<br />

agency.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall manage the parking lot charges, considering such factors as location, vehicle types, and times<br />

of day.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall process the financial requests and manage an interface to a Financial Institution.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall support the payment of parking lot transactions using data provided by the traveler cards /<br />

payment instruments.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall process requests for parking lot charges to be paid in advance.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall process requests for the advanced payment of tolls and transit fares as well as other nontransportation<br />

services, e.g. yellow­pages services.<br />

Light Rail Station Parking Mgmt. Parking Electronic Payment The parking element shall maintain a list of invalid traveler credit identities, or bad tag lists.<br />

Light Rail Transit Management Center Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Light Rail Transit Management Center Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Light Rail Transit Management Center Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Light Rail Transit Management Center Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Light Rail Transit Management Center Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Light Rail Transit Management Center Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Light Rail Transit Management Center Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Light Rail Transit Management Center Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Light Rail Transit Management Center Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Light Rail Transit Management Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Light Rail Transit Management Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Light Rail Transit Management Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Light Rail Transit Management Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Light Rail Transit Management Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Light Rail Transit Management Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Light Rail Transit Management Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Light Rail Transit Management Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Light Rail Transit Management Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Light Rail Transit Management Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Light Rail Transit Management Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Light Rail Transit Management Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Light Rail Transit Management Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Light Rail Transit Management Center Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

Light Rail Transit Management Center Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Light Rail Transit Management Center Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Light Rail Transit Management Center Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Light Rail Transit Management Center Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

Light Rail Transit Management Center Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

Light Rail Transit Management Center Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Light Rail Transit Management Center Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

Light Rail Transit Management Center Transit Center Multi­Modal Coordination The center shall send requests for priority along routes or at intersections to traffic management.<br />

Light Rail Transit Management Center Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Light Rail Transit Management Center Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Light Rail Transit Management Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Light Rail Transit Management Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Light Rail Transit Management Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Light Rail Transit Management Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall update the incident information log once the emergency system operator has verified the incident.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Call­Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

Local Fire/EMS Dispatch Centers Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

Local Fire/EMS Dispatch Centers Emergency Routing The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

Local Fire/EMS Dispatch Centers Emergency Routing The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

Local Fire/EMS Dispatch Centers Emergency Routing The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

Local Fire/EMS Dispatch Centers Emergency Routing In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

Local Fire/EMS Dispatch Centers Emergency Routing The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

Local Fire/EMS Dispatch Centers Emergency Routing Once the route is calculated the route shall be provided to the dispatch function.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

Local Fire/EMS Dispatch Centers Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Local Fire/EMS Dispatch Centers Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Local Fire/EMS Dispatch Centers Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

Local Fire/EMS Dispatch Centers Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

Local Fire/EMS Dispatch Centers Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

Local Fire/EMS Dispatch Centers Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

Local Fire/EMS Dispatch Centers Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

Local Fire/EMS Dispatch Centers Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Local Fire/EMS Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Local Fire/EMS Vehicles<br />

Local Fire/EMS Vehicles<br />

Local Fire/EMS Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Local Law Enforcement Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Local Law Enforcement Vehicles<br />

Local Law Enforcement Vehicles<br />

Local Law Enforcement Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

Local Police Dispatch Emergency Call­Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

Local Police Dispatch Emergency Call­Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

Local Police Dispatch Emergency Call­Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

Local Police Dispatch Emergency Call­Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

Local Police Dispatch Emergency Call­Taking The center shall update the incident information log once the emergency system operator has verified the incident.<br />

Local Police Dispatch Emergency Call­Taking The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

Local Police Dispatch Emergency Call­Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

Local Police Dispatch Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

Local Police Dispatch Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

Local Police Dispatch Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

Local Police Dispatch Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

Local Police Dispatch Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

Local Police Dispatch Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

Local Police Dispatch Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

Local Police Dispatch Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

Local Police Dispatch Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

Local Police Dispatch Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Local Police Dispatch Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

Local Police Dispatch Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

Local Police Dispatch Emergency Routing The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

Local Police Dispatch Emergency Routing The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

Local Police Dispatch Emergency Routing The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

Local Police Dispatch Emergency Routing In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

Local Police Dispatch Emergency Routing The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

Local Police Dispatch Emergency Routing Once the route is calculated the route shall be provided to the dispatch function.<br />

Local Police Dispatch Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

Local Police Dispatch Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Local Police Dispatch Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

Local Police Dispatch Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

Local Police Dispatch Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

Local Police Dispatch Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

Local Police Dispatch Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

Local Police Dispatch Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Local Police Dispatch Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Local Police Dispatch Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Local Police Dispatch Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Local Police Dispatch Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Local Police Dispatch Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Local Police Dispatch Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

Local Police Dispatch Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

Local Police Dispatch Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Local Police Dispatch Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Local Police Dispatch Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Local Police Dispatch Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Local Police Dispatch Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

Local Police Dispatch Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

Local Police Dispatch Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

Local Police Dispatch Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

Local Police Dispatch Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

Local Police Dispatch Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

Local Police Dispatch Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Local Police Dispatch Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

Local Police Dispatch Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

Local Police Dispatch Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

Local Police Dispatch Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

Local Police Dispatch Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

Local Police Dispatch Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

Local Police Dispatch Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

Local Police Dispatch Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

Local Police Dispatch Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

Local Police Dispatch Center Secure Area Alarm Support The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest<br />

areas, park and ride lots, modal interchange facilities).<br />

Local Police Dispatch Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

Local Police Dispatch Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.<br />

Local Police Dispatch Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

Local Police Dispatch Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

Local Police Dispatch Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

Local Police Dispatch Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

Local Police Dispatch Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Local Police Dispatch Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Local Police Dispatch Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

Local Print and Broadcast Media TBD TBD<br />

Local Transit Dispatch Centers Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Local Transit Dispatch Centers Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Local Transit Dispatch Centers Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Local Transit Dispatch Centers Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Local Transit Dispatch Centers Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Local Transit Dispatch Centers Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Local Transit Dispatch Centers Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Local Transit Dispatch Centers Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Local Transit Dispatch Centers Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Local Transit Dispatch Centers Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Local Transit Dispatch Centers Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Local Transit Dispatch Centers Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Local Transit Dispatch Centers Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Local Transit Dispatch Centers Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Local Transit Dispatch Centers Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Local Transit Dispatch Centers Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

Local Transit Dispatch Centers Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Local Transit Dispatch Centers Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Local Transit Dispatch Centers Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Local Transit Dispatch Centers Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Local Transit Dispatch Centers<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Local Transit Dispatch Centers<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Local Transit Dispatch Centers Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Local Transit Dispatch Centers Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Local Transit Dispatch Centers Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Local Transit Dispatch Centers Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Local Transit Dispatch Centers Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Local Transit Dispatch Centers Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Local Transit Dispatch Centers Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Local Transit Dispatch Centers Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Local Transit Dispatch Centers TBD TBD<br />

Local Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Local Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Local Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Local Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Local Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Local Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Municipal EOC Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

Municipal EOC Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Municipal EOC Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

Municipal EOC Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

Municipal EOC Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

Municipal EOC Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

Municipal EOC Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

Municipal EOC Emergency Response Management The center shall provide strategic emergency response capabilities such as that of an Emergency Operations Center for<br />

large­scale incidents and disasters.<br />

Municipal EOC Emergency Response Management The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Municipal EOC Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Municipal EOC Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Municipal EOC Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Municipal EOC Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Municipal EOC Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Municipal EOC Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Municipal EOC Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

Municipal EOC Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Municipal EOC Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Municipal EOC Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Municipal EOC Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Municipal EOC Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

Municipal EOC Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

Municipal EOC Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

Municipal EOC Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

Municipal EOC Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

Municipal EOC Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

Municipal EOC Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Municipal EOC Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

Municipal EOC Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

Municipal EOC Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

Municipal EOC Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

Municipal EOC Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

Municipal EOC Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

Municipal EOC Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

Municipal EOC Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

Municipal EOC Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

Municipal EOC Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

Municipal EOC Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Municipal EOC Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Municipal EOC Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

Municipal Equipment Repair Facility TBD TBD<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Municipal Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Municipal Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Municipal Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Municipal Field Equipment<br />

Municipal Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Municipal Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Municipal Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Municipal Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Municipal Field Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Municipal Field Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Municipal Field Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Municipal Field Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Municipal Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Municipal Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Municipal Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

Municipal Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Municipal Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Municipal Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Municipal Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Municipal Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Municipal Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Municipal Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

Municipal Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

Municipal Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

Municipal Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Municipal Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

Municipal Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

Municipal Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Municipal Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

Municipal Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

Municipal Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

Municipal Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

Municipal Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

Municipal Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

Municipal Maintenance Dispatch MCM Data Collection The center shall collect maintenance and construction data (such as field equipment status, infrastructure status,<br />

maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction<br />

sources.<br />

Municipal Maintenance Dispatch MCM Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Municipal Maintenance Dispatch MCM Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and<br />

construction data or for the data itself.<br />

Municipal Maintenance Dispatch MCM Data Collection The center shall be able to produce sample products of the data available.<br />

Municipal Maintenance Dispatch MCM Data Collection The center shall provide data to Asset Management to be used in updating the status of assets in the inventory.<br />

Municipal Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle<br />

location determination function.<br />

Municipal Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

Municipal Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall collect vehicle diagnostics and operating status data from the<br />

maintenance vehicle platform including engine temperature, mileage, tire wear, brake wear, belt wear, and other<br />

operational status measures as well as the status of maintenance and construction­specific systems on the vehicle.<br />

The maintenance and construction vehicle shall use the diagnostic and status information to support scheduling vehicle<br />

maintenance, monitoring safety status, and informing the vehicle operator of the conditions.<br />

The maintenance and construction vehicle shall the vehicle diagnostic and safety information to an equipment repair<br />

facility.<br />

The maintenance and construction vehicle shall send the vehicle diagnostic and safety information to the controlling<br />

maintenance center.<br />

The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include routine maintenance equipment for cutting, repairs, hazard<br />

removal, etc.<br />

The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.<br />

The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

Municipal Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall monitor, operate, and control work zone devices located at or alongside<br />

the roadway. The devices operated on board the vehicle include driver information devices (e.g. dynamic message signs)<br />

and work zone intrusion detection and alert devices.<br />

Municipal Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone<br />

activities.<br />

Municipal Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on­board<br />

the maintenance and construction vehicle and send them to the controlling center.<br />

Municipal TOCs TBD TBD<br />

Municipal TOCs Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

Municipal TOCs Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

Municipal TOCs Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

Municipal TOCs Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

Municipal TOCs Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

Municipal TOCs Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

Municipal TOCs Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

Municipal TOCs Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

Municipal TOCs Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

Municipal TOCs TMC Signal Control The center shall remotely control traffic signal controllers.<br />

Municipal TOCs TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

Municipal TOCs TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

Municipal TOCs TMC Signal Control The center shall collect traffic signal controller fault data from the field.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Municipal TOCs TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

Municipal TOCs TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

Municipal TOCs TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

Municipal TOCs TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

Municipal TOCs TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Municipal TOCs TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

Municipal TOCs TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

Municipal TOCs TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Municipal TOCs TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

Municipal TOCs TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

Municipal TOCs TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

Municipal TOCs<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

Municipal TOCs<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

Municipal TOCs<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

Municipal TOCs TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

Municipal TOCs TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

Municipal TOCs TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

Municipal TOCs TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

Municipal TOCs HRI Traffic Management The center shall remotely control highway­rail intersection (HRI) equipment located in the field.<br />

Municipal TOCs HRI Traffic Management The center shall accept collect highway­rail intersection (HRI) advisory or alert data from rail operations centers.<br />

Municipal TOCs HRI Traffic Management The center shall collect highway­rail intersection (HRI) equipment operational status and compare against the control<br />

information sent by the center.<br />

Municipal TOCs HRI Traffic Management The center shall provide the highway­rail intersection (HRI) equipment operational status to rail operations centers.<br />

Municipal TOCs HRI Traffic Management The center shall collect incident information related to a highway­rail intersection (HRI), such as intersection blockages or<br />

crashes or equipment malfunctions.<br />

Municipal TOCs HRI Traffic Management The center shall implement control plans to coordinate signalized intersections around highway­rail intersections (HRI),<br />

under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents,<br />

equipment faults, pedestrian crossings, etc.<br />

Municipal TOCs Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

Municipal TOCs Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

Municipal TOCs Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

Municipal TOCs Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

Municipal TOCs Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Municipal TOCs Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

Municipal TOCs Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

Municipal TOCs Traffic Maintenance The center shall collect environmental sensor operational status.<br />

Municipal TOCs Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

Municipal TOCs Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

Municipal TOCs Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

Municipal TOCs Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

Municipal TOCs Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Municipal TOCs Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

Municipal TOCs Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Municipal Websites Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Municipal Websites Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Municipal Websites Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Municipal Websites Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

Municipal Websites Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Municipal Websites Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Municipal Websites Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Municipal Websites Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Municipal Websites Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Municipal Websites Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Other County TOC TBD TBD<br />

Other Caltrans District Maintenance TBD TBD<br />

Other Caltrans District Maintenance TBD TBD<br />

Other Caltrans District TMCs TBD TBD<br />

Other Caltrans District TMCs TBD TBD<br />

Other Law Enforcement Dispatch Center TBD TBD<br />

Paratransit Vehicle On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Paratransit Vehicle On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Paratransit Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Paratransit Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Paratransit Vehicle On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Paratransit Vehicle On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

Paratransit Vehicle On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

Paratransit Vehicle On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall detect embarking travelers on­board a transit vehicle and read data from the traveler card /<br />

payment instrument that they are carrying.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not<br />

have a traveler card / payment instrument or whose transit fare transaction fails.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the<br />

traveler's destination.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well<br />

as factors such as the transit routing, transit fare category, traveler history, and route­specific information.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available<br />

to the traveler.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.<br />

Management<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall include a database on­board the transit vehicle for use in fare processing from which the fares for<br />

all possible trips within the transit operational network can be determined.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during<br />

disasters, states of emergency or evacuations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares<br />

via the traveler card / payment instrument.<br />

Paratransit Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide passenger loading and fare statistics data to the center.<br />

Management<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Paratransit Vehicle On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Paratransit, Inc. Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Paratransit, Inc. Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Paratransit, Inc. Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Paratransit, Inc. Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Paratransit, Inc. Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Paratransit, Inc. Transit Center Paratransit Operations The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

Paratransit, Inc.<br />

Transit Center Fare and Load<br />

Management<br />

The center shall be capable of establishing emergency fare structures to override all other fares during disasters, states<br />

of emergency, or evacuations.<br />

Paratransit, Inc.<br />

Transit Center Fare and Load The center shall collect passenger loading and fare statistics data to implement variable and flexible fare structures.<br />

Management<br />

Paratransit, Inc.<br />

Transit Center Fare and Load The center shall provide transit fare information to other centers, including traveler information providers upon request.<br />

Management<br />

Paratransit, Inc. Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Paratransit, Inc. Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Paratransit, Inc. Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Paratransit, Inc. Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Paratransit, Inc. Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Paratransit, Inc. Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Paratransit, Inc. Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

Paratransit, Inc. Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Paratransit, Inc. Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Paratransit, Inc. Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Paratransit, Inc. Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Paratransit, Inc. Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Paratransit, Inc. Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

Paratransit, Inc. Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

Paratransit, Inc. Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

Paratransit, Inc. Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

Paratransit, Inc. Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Paratransit, Inc.<br />

Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

Paratransit, Inc.<br />

Transit Center Multi­Modal Coordination The center shall send requests for priority along routes or at intersections to traffic management.<br />

Paratransit, Inc.<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Paratransit, Inc.<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Paratransit, Inc. Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Paratransit, Inc. Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Paratransit, Inc. Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Paratransit, Inc. Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Paratransit, Inc. Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Paratransit, Inc. Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Paratransit, Inc. Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Paratransit, Inc. Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Pedestrian TBD TBD<br />

Private Transit Provider Dispatch TBD TBD<br />

Private Traveler Information Service Providers TBD<br />

TBD<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

Private/Public Ambulance Dispatch Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

Private/Public Ambulance Dispatch Emergency Routing The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

Private/Public Ambulance Dispatch Emergency Routing The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

Private/Public Ambulance Dispatch Emergency Routing The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

Private/Public Ambulance Dispatch Emergency Routing In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

Private/Public Ambulance Dispatch Emergency Routing The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

Private/Public Ambulance Dispatch Emergency Routing Once the route is calculated the route shall be provided to the dispatch function.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Private/Public Ambulance Dispatch Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Private/Public Ambulance Dispatch Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Private/Public Ambulance Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Private/Public Ambulance Vehicles<br />

Private/Public Ambulance Vehicles<br />

Private/Public Ambulance Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

TBD<br />

Regional Emergency Communications TBD<br />

Network<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

Regional Emergency Operations Center Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide strategic emergency response capabilities such as that of an Emergency Operations Center for<br />

large­scale incidents and disasters.<br />

Regional Emergency Operations Center Emergency Response Management The center shall manage coordinated inter­agency responses to and recovery from large­scale emergencies. Such<br />

agencies include traffic management, transit, maintenance and construction management, rail operations, and other<br />

emergency management agencies.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide the capability to implement response plans and track progress through the incident by<br />

exchanging incident information and distributing response status to allied agencies.<br />

Regional Emergency Operations Center Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

Regional Emergency Operations Center Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

Regional Emergency Operations Center Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

Regional Emergency Operations Center Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

Regional Emergency Operations Center Emergency Response Management The center shall receive hazardous materials incident information from commercial fleet operators.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

Regional Emergency Operations Center Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

Regional Emergency Operations Center Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

Regional Emergency Operations Center Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

Regional Emergency Operations Center Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

Regional Emergency Operations Center Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

Regional Emergency Operations Center Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

Regional Emergency Operations Center Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

Regional Emergency Operations Center Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

Regional Emergency Operations Center Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

Regional Emergency Operations Center Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Regional Emergency Operations Center Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Regional Emergency Operations Center Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

Regional Event Promoters TBD TBD<br />

Regional Medical Centers TBD TBD<br />

Regional Railroad Operations TBD TBD<br />

Regional Traffic Count Archive ITS Data Repository The center shall collect data to be archived from one or more data sources.<br />

Regional Traffic Count Archive ITS Data Repository The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

Regional Traffic Count Archive ITS Data Repository The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

Regional Traffic Count Archive ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.<br />

Regional Traffic Count Archive ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.<br />

Regional Traffic Count Archive ITS Data Repository The center shall include capabilities for archive to archive coordination.<br />

Regional Traffic Count Archive ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

Regional Traffic Count Archive ITS Data Repository The center shall perform quality checks on received data.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Regional Traffic Count Archive ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

Regional Traffic Count Archive ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

Regional Traffic Count Archive ITS Data Repository When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

Regional Traffic Count Archive ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall collect traffic sensor information from roadside devices.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall collect environmental sensor information that from roadside devices.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall record the status about the imported traffic and roadside data.<br />

Regional Traffic Count Archive Traffic and Roadside Data Archival The center shall use the status information to adjust the collection of traffic and roadside data.<br />

Regional Traffic Count Archive<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

Regional Traffic Count Archive<br />

Regional Traffic Count Archive<br />

Regional Traffic Count Archive<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Regional Traffic Count Archive<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

Regional Transit Bus Vehicle On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Regional Transit Bus Vehicle On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Regional Transit Bus Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Regional Transit Bus Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Regional Transit Bus Vehicle On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Regional Transit Bus Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Regional Transit Bus Vehicle On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

Regional Transit Bus Vehicle On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

Regional Transit Bus Vehicle On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall detect embarking travelers on­board a transit vehicle and read data from the traveler card /<br />

payment instrument that they are carrying.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not<br />

have a traveler card / payment instrument or whose transit fare transaction fails.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the<br />

traveler's destination.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well<br />

as factors such as the transit routing, transit fare category, traveler history, and route­specific information.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available<br />

to the traveler.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.<br />

Management<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall include a database on­board the transit vehicle for use in fare processing from which the fares for<br />

all possible trips within the transit operational network can be determined.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during<br />

disasters, states of emergency or evacuations.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares<br />

via the traveler card / payment instrument.<br />

Regional Transit Bus Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide passenger loading and fare statistics data to the center.<br />

Management<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Regional Transit Bus Vehicle On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Regional Transit Bus Vehicle On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Regional Transit Bus Vehicle On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Regional Transit Bus Vehicle On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Regional Transit Bus Vehicle On­board Transit Signal Priority The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.<br />

Regional Transit Bus Vehicle On­board Transit Signal Priority The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and<br />

multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle<br />

schedule deviation to be corrected.<br />

Regional Transit Bus Vehicle On­board Transit Signal Priority The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Regional Transit Bus Vehicle On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Regional Transit LRT Vehicle On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Regional Transit LRT Vehicle On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Regional Transit LRT Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Regional Transit LRT Vehicle On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Regional Transit LRT Vehicle On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Regional Transit LRT Vehicle<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall detect embarking travelers on­board a transit vehicle and read data from the traveler card /<br />

payment instrument that they are carrying.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not<br />

have a traveler card / payment instrument or whose transit fare transaction fails.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the<br />

traveler's destination.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well<br />

as factors such as the transit routing, transit fare category, traveler history, and route­specific information.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available<br />

to the traveler.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.<br />

Management<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall include a database on­board the transit vehicle for use in fare processing from which the fares for<br />

all possible trips within the transit operational network can be determined.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during<br />

disasters, states of emergency or evacuations.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares<br />

via the traveler card / payment instrument.<br />

Regional Transit LRT Vehicle<br />

On­board Transit Fare and Load The transit vehicle shall provide passenger loading and fare statistics data to the center.<br />

Management<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Regional Transit LRT Vehicle On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Regional Transit LRT Vehicle On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Regional Transit LRT Vehicle On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Regional Transit LRT Vehicle On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

Regional Transit LRT Vehicle On­board Transit Signal Priority The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.<br />

Regional Transit LRT Vehicle On­board Transit Signal Priority The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and<br />

multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle<br />

schedule deviation to be corrected.<br />

Regional Transit LRT Vehicle On­board Transit Signal Priority The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator.<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Regional Transit LRT Vehicle On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

Roseville Transit Management Center Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

(Dispatch)<br />

Roseville Transit Management Center Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Center Secure Area Surveillance<br />

Center Secure Area Surveillance<br />

Center Secure Area Surveillance<br />

Center Secure Area Surveillance<br />

Center Secure Area Surveillance<br />

Transit Center Tracking and Dispatch<br />

Transit Center Tracking and Dispatch<br />

Transit Center Tracking and Dispatch<br />

Transit Center Tracking and Dispatch<br />

The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations,<br />

transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and<br />

travel information centers).<br />

The center shall remotely control security surveillance devices on­board transit vehicles.<br />

The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

The center shall monitor the locations of all transit vehicles within its network.<br />

The center shall determine adherence of transit vehicles to their assigned schedule.<br />

The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

The center shall provide transit operational data to traveler information service providers.<br />

Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Transit Center Paratransit Operations<br />

Transit Center Paratransit Operations<br />

Transit Center Paratransit Operations<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Center Security<br />

Transit Garage Operations<br />

Transit Garage Operations<br />

Transit Garage Operations<br />

The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

The center shall exchange transit incident information along with other service data with other transit agencies.<br />

The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

The center shall provide support to remotely disable (or reset the disabling of) a transit vehicle in service.<br />

The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Transit Garage Operations<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Garage Maintenance<br />

Transit Center Information Services<br />

Transit Center Information Services<br />

Transit Center Information Services<br />

Transit Center Information Services<br />

Transit Center Information Services<br />

The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

The center shall collect operational and maintenance data from transit vehicles.<br />

The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

Transit Center Multi­Modal Coordination The center shall send requests for priority along routes or at intersections to traffic management.<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Transit Evacuation Support<br />

The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Transit Evacuation Support<br />

The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Transit Evacuation Support<br />

The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Transit Evacuation Support<br />

The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Transit Data Collection<br />

The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Transit Data Collection<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Roseville Transit Management Center<br />

(Dispatch)<br />

Transit Data Collection<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Roseville Transit Management Center Transit Data Collection<br />

The center shall be able to produce sample products of the data available.<br />

(Dispatch)<br />

Roseville Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Roseville Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Roseville Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Roseville Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Roseville Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Roseville Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Roseville Transit Vehicles On­board Paratransit Operations The transit vehicle shall manage data input to sensor(s) on­board a transit vehicle to determine the vehicle's availability<br />

for use in demand responsive and flexible­route transit services based on identity, type, and passenger capacity.<br />

Roseville Transit Vehicles On­board Paratransit Operations The transit vehicle shall receive the status of demand responsive or flexible­route transit schedules and passenger<br />

loading from the transit vehicle operator.<br />

Roseville Transit Vehicles On­board Paratransit Operations The transit vehicle shall provide the transit vehicle operator instructions about the demand responsive or flexible­route<br />

transit schedule that has been confirmed from the center.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or<br />

authentic inputs from the transit vehicle operator.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Roseville Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Roseville Transit Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Roseville Transit Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Roseville Transit Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

Roseville Transit Vehicles On­board Transit Signal Priority The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.<br />

Roseville Transit Vehicles On­board Transit Signal Priority The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and<br />

multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle<br />

schedule deviation to be corrected.<br />

Roseville Transit Vehicles On­board Transit Signal Priority The transit vehicle shall send the schedule deviation data and status of priority requests to the transit vehicle operator.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Roseville Transit Vehicles On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

RT Passenger Information Signs Remote Transit Information Services The public interface for travelers shall collect and provide real­time travel­related information at transit stops, multi­modal<br />

transfer points, and other public transportation areas.<br />

RT Passenger Information Signs Remote Transit Information Services The public interface for travelers shall collect and present to the transit traveler information on transit routes, schedules,<br />

and real­time schedule adherence.<br />

RT Passenger Information Signs Remote Transit Information Services The public interface for travelers shall provide support for general annunciation and/or display of imminent arrival<br />

information and other information of general interest to transit users.<br />

RT Passenger Information Signs Remote Transit Information Services The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical<br />

disabilities.<br />

RT Police Services Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

RT Police Services Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

RT Police Services Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

RT Police Services Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

RT Police Services Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

RT Police Services Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

RT Police Services Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

RT Police Services Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

RT Police Services Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

RT Police Services Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

RT Police Services Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

RT Police Services Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

RT Police Services Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

RT Police Services Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

RT Police Services Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

RT Police Services Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

RT Police Services Emergency Response Management The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials<br />

incident.<br />

RT Police Services Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

RT Police Services Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

RT Police Services Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

RT Police Services Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

RT Police Services Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

RT Police Services Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

RT Police Services Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

RT Police Services Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

RT Police Services Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

RT Police Services Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

RT Police Services Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

RT Police Services Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

RT Police Services Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

RT Police Services Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

RT Police Services TBD TBD<br />

RT Security Monitoring Equipment Field Secure Area Surveillance The field element shall include video and/or audio surveillance of secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RT Security Monitoring Equipment Field Secure Area Surveillance The field element shall be remotely controlled by a center.<br />

RT Security Monitoring Equipment Field Secure Area Surveillance The field element shall provide equipment status and fault indication of surveillance equipment to a center.<br />

RT Security Monitoring Equipment Field Secure Area Surveillance The field element shall provide raw video or audio data.<br />

RT Security Monitoring Equipment Field Secure Area Surveillance The field element shall remotely process video and audio data and provide an indication of potential incidents or threats<br />

to a center.<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall receive traffic information from a center and present it to the traveler upon request.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall receive transit information from a center and present it to the traveler upon request.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall receive yellow pages information (such as lodging, restaurants, theaters, bicycle<br />

facilities, and other tourist activities) from a center and present it to the traveler upon request.<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall receive event information from a center and present it to the traveler upon request.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall receive evacuation information from a center and present it to the traveler.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall receive wide­area alerts and present it to the traveler.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall accept reservations for confirmed trip plans.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall support payment for services, such as confirmed trip plans, confirmed yellow pages<br />

services, tolls, transit fares, parking lot charges, and advanced payment for tolls.<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall provide an interface through which credit identities and stored credit values may be<br />

collected from tags, traveler cards, or payment instruments used by travelers.<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall base requests from the traveler on the traveler's current location or a specific<br />

location identified by the traveler, and filter the provided information accordingly.<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall provide digitized map data to act as the background to the information presented<br />

to the traveler.<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall support traveler input in audio or manual form.<br />

Reception<br />

RT Transit Kiosks<br />

Remote Interactive Information<br />

Reception<br />

The public interface for travelers shall present information to the traveler in audible or visual forms consistent with a kiosk,<br />

including those that are suitable for travelers with hearing or vision physical disabilities.<br />

RT Transit Kiosks<br />

Remote Interactive Information The public interface for travelers shall be able to store frequently requested data.<br />

Reception<br />

RT Transit Kiosks Traveler Secure Area Surveillance The field element shall include video and/or audio surveillance of traveler secure areas including transit stations, transit<br />

stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and traveler<br />

information centers).<br />

RT Transit Kiosks Traveler Secure Area Surveillance The field element shall be remotely controlled by a center.<br />

RT Transit Kiosks Traveler Secure Area Surveillance The field element shall provide equipment status and fault indication of surveillance equipment to a center.<br />

RT Transit Kiosks Traveler Secure Area Surveillance The field element shall provide raw video or audio data.<br />

RT Transit Kiosks Traveler Secure Area Surveillance The field element shall remotely process video and audio data and provide an indication of potential incidents or threats<br />

to a center.<br />

RT Transit Kiosks Remote Traveler Security The public interface for travelers shall provide the capability for a traveler to report an emergency and summon<br />

assistance from secure areas such as transit stops, transit stations, modal transfer facilities, rest stops, park­and­ride<br />

areas, travel information areas, and emergency pull off areas.<br />

RT Transit Kiosks Remote Traveler Security When initiated by a traveler, the public interface for travelers shall forward a request for assistance to an emergency<br />

management function and acknowledge the request.<br />

RT Transit Kiosks Remote Traveler Security The public interface for travelers shall provide the capability to broadcast a message to advise or warn a traveler.<br />

RT Transit Kiosks Remote Traveler Security The public interface for travelers shall accept input and provide information to the traveler in a form suitable for travelers<br />

with physical disabilities.<br />

RT Transit Kiosks Remote Transit Information Services The public interface for travelers shall collect and provide real­time travel­related information at transit stops, multi­modal<br />

transfer points, and other public transportation areas.<br />

RT Transit Kiosks Remote Transit Information Services The public interface for travelers shall collect and present to the transit traveler information on transit routes, schedules,<br />

and real­time schedule adherence.<br />

RT Transit Kiosks Remote Transit Information Services The public interface for travelers shall provide support for general annunciation and/or display of imminent arrival<br />

information and other information of general interest to transit users.<br />

RT Transit Kiosks Remote Transit Information Services The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical<br />

disabilities.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall accept and process current transit passenger fare collection information.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall calculate a fare based on the origin and destination provided by the traveler, in<br />

conjunction with transit routing, transit fare category, and transit user history.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall provide an interface to a transit user traveler card in support of payment for transit<br />

fares, tolls, and/or parking lot charges. The stored credit value data from the card shall be collected and updated based<br />

on the fare or other charges, or the credit identity shall be collected.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall provide information to the center for financial authorization and transaction<br />

processing.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall provide an image of all travelers purchasing rides or services to be used for<br />

violation processing.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall determine the routing based on the traveler's destination and the location of the<br />

closest transit stop from which a route request is being made.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall create passenger loading and fare statistics data based upon data collected at a<br />

transit stop.<br />

RT Transit Kiosks Remote Transit Fare Management The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical<br />

disabilities.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which<br />

include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g.,<br />

emergency pull­off areas and travel information centers). The data may be raw or pre­processed in the field.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations,<br />

transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and<br />

travel information centers).<br />

RT Transit Management Center Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

RT Transit Management Center Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

RT Transit Management Center Center Secure Area Alarm Support The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest<br />

areas, park and ride lots, modal interchange facilities).<br />

RT Transit Management Center Center Secure Area Alarm Support The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit<br />

vehicle operator.<br />

RT Transit Management Center Center Secure Area Alarm Support After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RT Transit Management Center Center Secure Area Alarm Support After the alarm message becomes a verified incident, the center shall determine the appropriate response.<br />

RT Transit Management Center Center Secure Area Alarm Support The center shall determine whether the alarm message indicates an emergency that requires the attention of public<br />

safety agencies, and forward alarm message data to the appropriate agency as necessary.<br />

RT Transit Management Center Center Secure Area Alarm Support The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as<br />

directed by the personnel.<br />

RT Transit Management Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

RT Transit Management Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

RT Transit Management Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

RT Transit Management Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

RT Transit Management Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

RT Transit Management Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall process trip requests for demand responsive transit services, i.e. paratransit. Sources of the requests<br />

may include traveler information service providers.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall track the location and availability of transit vehicles for use in demand responsive transit (paratransit)<br />

operations.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall generate demand responsive transit (paratransit) routes and schedules based on such factors as<br />

parameters input by the system operator, what other demand responsive transit schedules have been planned, the<br />

availability and location of vehicles, the relevance of any fixed transit routes and schedules, and road network information.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall assign transit vehicle operators for confirmed demand responsive transit (paratransit) trips based on<br />

factors such as eligibility, route preferences, seniority, and transit vehicle availability.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

RT Transit Management Center Transit Center Paratransit Operations The center shall disseminate up­to­date schedules and route information to other centers for demand responsive transit<br />

services (paratransit).<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall manage the actual value of transit fares for each segment of each regular transit route, including the<br />

transmission of the information to transit vehicles and transit stops or stations.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall provide the capability for a system operator to manage the transit fares and control the exchange of<br />

transit fare information.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall process the financial requests from the transit vehicles or roadside and manage an interface to a<br />

Financial Institution.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall support the payment of transit fare transactions using data provided by the traveler cards / payment<br />

instruments.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall collect data on fare payment violations and send the data, including images of the violator, to the<br />

appropriate enforcement agency.<br />

RT Transit Management Center<br />

Transit Center Fare and Load The center shall process requests for transit fares to be paid in advance.<br />

Management<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall process requests for the advanced payment of tolls and parking lot charges as well as other nontransportation<br />

services, e.g. yellow­pages services.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall be capable of establishing emergency fare structures to override all other fares during disasters, states<br />

of emergency, or evacuations.<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall maintain a list of invalid traveler credit identities, or bad tag lists that can be forwarded to transit vehicles<br />

and transit stops or stations.<br />

RT Transit Management Center<br />

Transit Center Fare and Load The center shall collect passenger loading and fare statistics data to implement variable and flexible fare structures.<br />

Management<br />

RT Transit Management Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall exchange fare and load information with other transit management centers, including potential<br />

Centralized Payments facilities.<br />

RT Transit Management Center<br />

Transit Center Fare and Load The center shall provide transit fare information to other centers, including traveler information providers upon request.<br />

Management<br />

RT Transit Management Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

RT Transit Management Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

RT Transit Management Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

RT Transit Management Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

RT Transit Management Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

RT Transit Management Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

RT Transit Management Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

RT Transit Management Center Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

RT Transit Management Center Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

RT Transit Management Center Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

RT Transit Management Center Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

RT Transit Management Center Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

RT Transit Management Center Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RT Transit Management Center Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

RT Transit Management Center Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

RT Transit Management Center Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

RT Transit Management Center Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

RT Transit Management Center Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

RT Transit Management Center Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

RT Transit Management Center Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

RT Transit Management Center Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

RT Transit Management Center Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

RT Transit Management Center Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

RT Transit Management Center Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

RT Transit Management Center Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

RT Transit Management Center Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

RT Transit Management Center<br />

Transit Center Multi­Modal Coordination The center shall analyze transit vehicle schedule performance to determine the need for priority along certain routes or at<br />

certain intersections.<br />

RT Transit Management Center<br />

Transit Center Multi­Modal Coordination The center shall send requests for priority along routes or at intersections to traffic management.<br />

RT Transit Management Center<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

RT Transit Management Center<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

RT Transit Management Center Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

RT Transit Management Center Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

RT Transit Management Center Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

RT Transit Management Center Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

RT Transit Management Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

RT Transit Management Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

RT Transit Management Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

RT Transit Management Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

RT Transit Management Center TBD TBD<br />

RT Transit Monitors Remote Transit Information Services The public interface for travelers shall collect and provide real­time travel­related information at transit stops, multi­modal<br />

transfer points, and other public transportation areas.<br />

RT Transit Monitors Remote Transit Information Services The public interface for travelers shall collect and present to the transit traveler information on transit routes, schedules,<br />

and real­time schedule adherence.<br />

RT Transit Monitors Remote Transit Information Services The public interface for travelers shall provide support for general annunciation and/or display of imminent arrival<br />

information and other information of general interest to transit users.<br />

RT Transit Monitors Remote Transit Information Services The public interface for travelers shall present information to the traveler in a form suitable for travelers with physical<br />

disabilities.<br />

RT Wayside Equipment TBD TBD<br />

RT Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

RT Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

RT Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

RT Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

RT Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

RT Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

RT Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

RT Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

RT Website Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

RT Website Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

RT Website Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

RT Website Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

RT Website Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

RT Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

RT Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

RT Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

RT Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

RTMC­CHP Emergency Call­Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

RTMC­CHP Emergency Call­Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

RTMC­CHP Emergency Call­Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

RTMC­CHP Emergency Call­Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

RTMC­CHP Emergency Call­Taking The center shall update the incident information log once the emergency system operator has verified the incident.<br />

RTMC­CHP Emergency Call­Taking The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

RTMC­CHP Emergency Call­Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

RTMC­CHP Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

RTMC­CHP Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

RTMC­CHP Emergency Dispatch The center shall relay location and incident details to the responding vehicles.<br />

RTMC­CHP Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

RTMC­CHP Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

RTMC­CHP Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

RTMC­CHP Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.<br />

RTMC­CHP Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

RTMC­CHP Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

RTMC­CHP Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

RTMC­CHP Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

RTMC­CHP Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

RTMC­CHP Emergency Early Warning System The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

RTMC­CHP Emergency Early Warning System The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

RTMC­CHP Emergency Early Warning System The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

RTMC­CHP Emergency Early Warning System The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

RTMC­CHP Emergency Early Warning System The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

RTMC­CHP Emergency Early Warning System The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

RTMC­CHP Emergency Early Warning System The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

RTMC­CHP Emergency Response Management The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

RTMC­CHP Emergency Response Management The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

RTMC­CHP Emergency Response Management The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

RTMC­CHP Emergency Response Management The center shall receive event scheduling information from Event Promoters.<br />

RTMC­CHP Emergency Response Management The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

RTMC­CHP Emergency Response Management The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

RTMC­CHP Emergency Response Management The center shall provide information to the media concerning the status of an emergency response.<br />

RTMC­CHP Emergency Response Management The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

RTMC­CHP Emergency Response Management The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

RTMC­CHP Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

RTMC­CHP Incident Command The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

RTMC­CHP Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

RTMC­CHP Incident Command The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

RTMC­CHP Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RTMC­CHP Emergency Evacuation Support The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

RTMC­CHP Emergency Evacuation Support The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

RTMC­CHP Emergency Evacuation Support The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

RTMC­CHP Emergency Evacuation Support The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

RTMC­CHP Emergency Evacuation Support The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

RTMC­CHP Emergency Evacuation Support The center shall request resources from transit agencies as needed to support the evacuation.<br />

RTMC­CHP Emergency Evacuation Support The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

RTMC­CHP Emergency Evacuation Support The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

RTMC­CHP Emergency Evacuation Support The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

RTMC­CHP Emergency Evacuation Support The center shall monitor the progress of the reentry process.<br />

RTMC­CHP Emergency Evacuation Support The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

RTMC­CHP Emergency Environmental Monitoring The center shall collect current and forecast road and weather information from weather service providers (such as the<br />

National Weather Service and value­added sector specific meteorological services).<br />

RTMC­CHP Emergency Environmental Monitoring The center shall collect current road and weather information from roadway maintenance operations.<br />

RTMC­CHP Emergency Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information to support incident<br />

management.<br />

RTMC­CHP Emergency Environmental Monitoring The center shall present the current and forecast road and weather information to the emergency system operator.<br />

RTMC­CHP Emergency Environmental Monitoring The center shall provide aggregated or processed environmental probe information from its fleet of emergency vehicles to<br />

traffic management and maintenance centers.<br />

RTMC­CHP Mayday Support The center shall collect mayday messages from vehicles and drivers.<br />

RTMC­CHP Mayday Support The center shall collect mayday messages from travelers via personal handheld devices.<br />

RTMC­CHP Mayday Support The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by<br />

the vehicle's safety systems, or by a traveler via a personal handheld device.<br />

RTMC­CHP Mayday Support After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday<br />

message.<br />

RTMC­CHP Mayday Support The center shall determine whether the mayday message indicates an emergency that requires the attention of public<br />

safety agencies, and forward mayday emergency data to the appropriate agency as necessary.<br />

RTMC­CHP Mayday Support The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock<br />

doors.<br />

RTMC­CHP Mayday Support The center shall request additional emergency details from or issue commands to the vehicle's security systems or<br />

vehicle driver if needed.<br />

RTMC­CHP Mayday Support The center shall maintain a log of all mayday signals received from vehicles.<br />

RTMC­CHP Mayday Support The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the<br />

portable handheld device as directed by the personnel.<br />

RTMC­CHP Service Patrol Management The center shall dispatch roadway service patrol vehicles to identified incident locations.<br />

RTMC­CHP Service Patrol Management The center shall store the current status of all service patrol vehicles available for dispatch and those that have been<br />

dispatched.<br />

RTMC­CHP Service Patrol Management The center shall share incident information collected by the service patrol with traffic, maintenance and construction, and<br />

traveler information centers for incident management, incident notification to travelers, and incident cleanup.<br />

RTMC­CHP Service Patrol Management The center shall track the location and status of service patrol vehicles.<br />

RTMC­CHP Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

RTMC­CHP Emergency Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

RTMC­CHP Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

RTMC­CHP Emergency Data Collection The center shall be able to produce sample products of the data available.<br />

RTMC­CHP TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

RTMC­CHP TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall collect data to be archived from one or more data sources.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall include capabilities for archive to archive coordination.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall perform quality checks on received data.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

RTMC­D3 ­ Traffic Operations ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall collect traffic sensor information from roadside devices.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall collect environmental sensor information that from roadside devices.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall record the status about the imported traffic and roadside data.<br />

RTMC­D3 ­ Traffic Operations Traffic and Roadside Data Archival The center shall use the status information to adjust the collection of traffic and roadside data.<br />

RTMC­D3 ­ Traffic Operations<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RTMC­D3 ­ Traffic Operations<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

RTMC­D3 ­ Traffic Operations TBD TBD<br />

RTMC­D3 ­ Traffic Operations TBD TBD<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

RTMC­D3 ­ Traffic Operations Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

RTMC­D3 ­ Traffic Operations Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

RTMC­D3 ­ Traffic Operations ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

RTMC­D3 ­ Traffic Operations ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

RTMC­D3 ­ Traffic Operations ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

RTMC­D3 ­ Traffic Operations ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information<br />

Collection<br />

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information<br />

Collection<br />

The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Collection<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

The center shall remotely control environmental sensors on­board maintenance and construction vehicles that measure<br />

road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and<br />

other measures.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from traffic, emergency, and transit management, traveler information providers, and<br />

environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and<br />

construction vehicles.<br />

The center shall provide weather and road condition information to weather service providers and center personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall collect operational status for the roadside and vehicle­based environmental sensor equipment.<br />

The center shall collect fault data for the roadside and vehicle­based environmental sensor equipment for repair.<br />

RTMC­D3 ­ Traffic Operations<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

RTMC­D3 ­ Traffic Operations<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

Processing<br />

and predicted road weather and road conditions.<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

Processing<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

RTMC­D3 ­ Traffic Operations<br />

MCM Environmental Information The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

Processing<br />

treatment information that supports forecasts for road conditions.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

RTMC­D3 ­ Traffic Operations Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

RTMC­D3 ­ Traffic Operations TMC Freeway Management The center shall remotely control systems to manage use of the freeways, including ramp meters, mainline metering, and<br />

lane controls.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RTMC­D3 ­ Traffic Operations TMC Freeway Management The center shall collect operational status from ramp meters, mainline metering, and lane controls and compare against<br />

the control information sent by the center.<br />

RTMC­D3 ­ Traffic Operations TMC Freeway Management The center shall collect fault data from ramp meters, mainline metering, and lane controls.<br />

RTMC­D3 ­ Traffic Operations TMC Freeway Management The center shall implement control strategies, under control of center personnel, on some or all of the freeway network<br />

devices (e.g. ramp meters, mainline metering, and lane controls), based on data from sensors monitoring traffic<br />

conditions upstream, downstream, and queue data on the ramps themselves.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

RTMC­D3 ­ Traffic Operations TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

RTMC­D3 ­ Traffic Operations TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

RTMC­D3 ­ Traffic Operations TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

RTMC­D3 ­ Traffic Operations TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

RTMC­D3 ­ Traffic Operations<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

RTMC­D3 ­ Traffic Operations<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

RTMC­D3 ­ Traffic Operations<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

RTMC­D3 ­ Traffic Operations TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

RTMC­D3 ­ Traffic Operations TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

RTMC­D3 ­ Traffic Operations TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

RTMC­D3 ­ Traffic Operations TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

RTMC­D3 ­ Traffic Operations TMC Environmental Monitoring The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

RTMC­D3 ­ Traffic Operations TMC Environmental Monitoring The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

RTMC­D3 ­ Traffic Operations TMC Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from roadway maintenance operations, and environmental data collected from sensors<br />

deployed on and about the roadway.<br />

RTMC­D3 ­ Traffic Operations TMC Environmental Monitoring The center shall provide weather and road condition information to weather service providers and center personnel.<br />

RTMC­D3 ­ Traffic Operations TMC Environmental Monitoring The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect environmental sensor operational status.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

RTMC­D3 ­ Traffic Operations Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

RTMC­D3 ­ Traffic Operations TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

RTMC­D3 ­ Traffic Operations Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

RTMC­D3 ­ Traffic Operations Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

RTMC­D3 ­ Traffic Operations Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

RTMC­D3 ­ Traffic Operations Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

SACOG Data Repository ITS Data Repository The center shall collect data to be archived from one or more data sources.<br />

SACOG Data Repository ITS Data Repository The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

SACOG Data Repository ITS Data Repository The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

SACOG Data Repository ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.<br />

SACOG Data Repository ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.<br />

SACOG Data Repository ITS Data Repository The center shall include capabilities for archive to archive coordination.<br />

SACOG Data Repository ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

SACOG Data Repository ITS Data Repository The center shall perform quality checks on received data.<br />

SACOG Data Repository ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

SACOG Data Repository ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

SACOG Data Repository ITS Data Repository When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

SACOG Data Repository ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall collect traffic sensor information from roadside devices.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall collect environmental sensor information that from roadside devices.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall record the status about the imported traffic and roadside data.<br />

SACOG Data Repository Traffic and Roadside Data Archival The center shall use the status information to adjust the collection of traffic and roadside data.<br />

SACOG Data Repository<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

SACOG Data Repository<br />

SACOG Data Repository<br />

SACOG Data Repository<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

SACOG Data Repository<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

SACOG Data Repository On­Line Analysis and Mining The center shall support the interface with Archive Data User Systems for requests for analysis of the archive data.<br />

SACOG Data Repository On­Line Analysis and Mining The center shall provide the capability to perform activities such as data mining, data fusion, summarizations,<br />

aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and<br />

expansion of data details, and many other advanced analysis services.<br />

SACOG Data Repository On­Line Analysis and Mining The center shall receive the userÆs systems requests and develop the request to retrieve the data from the archive.<br />

SACOG Data Repository On­Line Analysis and Mining The center shall respond to users systems requests for a catalog of the archived data analysis products available.<br />

SACOG Data Repository On­Line Analysis and Mining For archive analysis and data mining products requiring financial payment the center shall process the financial requests<br />

and manage an interface to a Financial Institution.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Sacramento City Fire Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Sacramento City Fire Vehicles<br />

Sacramento City Fire Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

Sacramento City Fire Vehicles<br />

Sacramento City Police Department<br />

Communications<br />

On­board EV Incident Management<br />

Communication<br />

Emergency Call­Taking<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

The center shall update the incident information log once the emergency system operator has verified the incident.<br />

The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

The center shall relay location and incident details to the responding vehicles.<br />

The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

The center shall store and maintain the emergency service responses in an action log.<br />

The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

The center shall receive event scheduling information from Event Promoters.<br />

The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

The center shall provide information to the media concerning the status of an emergency response.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Sacramento City Police Department<br />

Communications<br />

Emergency Response Management<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Data Collection<br />

Emergency Data Collection<br />

The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

The center shall request resources from transit agencies as needed to support the evacuation.<br />

The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

The center shall monitor the progress of the reentry process.<br />

The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento City Police Department<br />

Communications<br />

Emergency Data Collection<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Sacramento City Police Department Emergency Data Collection<br />

The center shall be able to produce sample products of the data available.<br />

Communications<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Sacramento City Police Vehicles On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Sacramento City Police Vehicles<br />

Sacramento City Police Vehicles<br />

Sacramento City Police Vehicles<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Sacramento City Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Sacramento City Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Sacramento City Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

Sacramento City Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) priority requests from transit vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento City Roadside Equipment Roadway Signal Priority The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.<br />

Sacramento City Roadside Equipment<br />

Sacramento City Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Sacramento City Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Sacramento City Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Sacramento City Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Sacramento City Roadside Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Sacramento City Roadside Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Sacramento City Roadside Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Sacramento City Roadside Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

Sacramento City Roadside Equipment Standard Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall determine whether the highway­rail intersection (HRI) is blocked by traffic in the roadway or some<br />

other obstruction.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall notify the traffic management center and the rail wayside equipment of any intersection blockages,<br />

including trapped vehicles or other obstructions.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall receive track status and arriving train information from the rail wayside equipment that can be<br />

passed on to the traffic management center. This may include the current status of the tracks and when a train is<br />

expected and/or how long the crossing will be closed.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching with enough time for traffic to<br />

safely clear the crossing using gates, lights/signs, barriers, and traffic control signals.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

Sacramento City Roadside Equipment Advanced Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

Sacramento City Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

Sacramento City Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Sacramento City Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

Sacramento City Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Sacramento City Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Sacramento City Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Sacramento City Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Sacramento City Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Sacramento City Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Sacramento City Roadside Equipment Roadway Data Collection The field element shall collect traffic, road, and environmental conditions information.<br />

Sacramento City Roadside Equipment Roadway Data Collection The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road,<br />

and environmental conditions information to a center for archival.<br />

Sacramento City Roadside Equipment Roadway Data Collection The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the<br />

recorded data to a center for archival.<br />

Sacramento County Equipment Repair Facility TBD<br />

TBD<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Vehicle Tracking<br />

MCM Vehicle Tracking<br />

The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Vehicle Tracking<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

MCM Incident Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

and predicted road weather and road conditions.<br />

The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

treatment information that supports forecasts for road conditions.<br />

The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Incident Management<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Maintenance Decision Support<br />

MCM Winter Maintenance Management<br />

MCM Winter Maintenance Management<br />

MCM Winter Maintenance Management<br />

MCM Winter Maintenance Management<br />

MCM Winter Maintenance Management<br />

MCM Winter Maintenance Management<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

The center shall provide the center personnel with tailored external information, including weather or road condition<br />

observations, forecasted weather information or road conditions, current usage of treatments and materials, available<br />

resources, equipment and vehicle availability, road network information, and source reliability information.<br />

The center shall tailor the decision support information to include filtering (selection from a large amount of external<br />

information), error reduction ('smoothing' the information), fusion (combination of disparate information to match the<br />

decision needs), and analysis (creating the decision).<br />

The center shall provide an interface to the center personnel to input control parameters for the decision support process<br />

and receive decisions or information presentation.<br />

The center shall provide dispatch information to maintenance and construction vehicles based on the outputs of the<br />

decision support system, including recommended roadway treatment actions.<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other winter roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of winter<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide status information about scheduled winter maintenance activities including anticipated closures<br />

and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided<br />

to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance<br />

centers, and the media.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of winter maintenance activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of winter maintenance<br />

activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

MCM Winter Maintenance Management The center shall dispatch and route winter maintenance vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

MCM Winter Maintenance Management The center shall determine the need for roadway treatment based on current and forecasted weather information, current<br />

usage of treatments and materials, available resources, requests for action from other agencies, and recommendations<br />

from the Maintenance Decision Support system, specifically under winter conditions. This supports winter maintenance<br />

such as plowing, treating, anti­icing, etc.<br />

MCM Winter Maintenance Management The center shall provide dispatch instructions for vehicle operators based on input parameters from center personnel,<br />

specifically for winter conditions. This could include a treatment route, treatment application rates, start and end times,<br />

and other treatment instructions.<br />

MCM Winter Maintenance Management The center shall support remote control of on­board maintenance and construction vehicle systems and field equipment<br />

that is remotely controlled by the vehicle such as adjusting material application rates and spread patterns.<br />

MCM Winter Maintenance Management<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall assess the current status of all winter maintenance activities, including actual work activities performed,<br />

current locations and operational conditions of vehicles, materials and equipment inventories, field equipment status,<br />

environmental information, etc.<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Zone Management<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Work Activity Coordination<br />

MCM Data Collection<br />

MCM Data Collection<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

The center shall exchange rail schedules and work plans with rail operations centers.<br />

The center shall collect maintenance and construction data (such as field equipment status, infrastructure status,<br />

maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction<br />

sources.<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento County Maintenance Service<br />

Center<br />

MCM Data Collection<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and<br />

construction data or for the data itself.<br />

Sacramento County Maintenance Service MCM Data Collection<br />

The center shall be able to produce sample products of the data available.<br />

Center<br />

Sacramento County Maintenance Service MCM Data Collection<br />

The center shall provide data to Asset Management to be used in updating the status of assets in the inventory.<br />

Center<br />

Sacramento County Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle<br />

location determination function.<br />

Sacramento County Maintenance Vehicles MCV Vehicle Location Tracking The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.<br />

Sacramento County Maintenance Vehicles MCV Vehicle System Monitoring and<br />

Diagnostics<br />

The maintenance and construction vehicle shall collect vehicle diagnostics and operating status data from the<br />

maintenance vehicle platform including engine temperature, mileage, tire wear, brake wear, belt wear, and other<br />

operational status measures as well as the status of maintenance and construction­specific systems on the vehicle.<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

Sacramento County Maintenance Vehicles<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Vehicle System Monitoring and<br />

Diagnostics<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall use the diagnostic and status information to support scheduling vehicle<br />

maintenance, monitoring safety status, and informing the vehicle operator of the conditions.<br />

The maintenance and construction vehicle shall the vehicle diagnostic and safety information to an equipment repair<br />

facility.<br />

The maintenance and construction vehicle shall send the vehicle diagnostic and safety information to the controlling<br />

maintenance center.<br />

The maintenance and construction vehicle shall track the location and status of safety systems on­board the vehicle.<br />

The maintenance and construction vehicle shall respond to control information from the center to allow remote operation<br />

of the on­board vehicle systems. These systems include routine maintenance equipment for cutting, repairs, hazard<br />

removal, etc.<br />

The maintenance and construction vehicle shall monitor materials information including remaining quantity and current<br />

application rate of materials on the vehicle.<br />

The maintenance and construction vehicle shall respond to dispatch information from the center, presented to the vehicle<br />

operator for acknowledgement and returning status.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Maintenance Vehicles<br />

MCV Roadway Maintenance and<br />

Construction<br />

The maintenance and construction vehicle shall send operational data to the center including the operational state of the<br />

maintenance equipment (e.g., blade up/down, spreader pattern), types and quantities of materials used for construction<br />

and maintenance activities, and a record of the actual work performed.<br />

Sacramento County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall monitor, operate, and control work zone devices located at or alongside<br />

the roadway. The devices operated on board the vehicle include driver information devices (e.g. dynamic message signs)<br />

and work zone intrusion detection and alert devices.<br />

Sacramento County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall provide an interface for field personnel to input status of their work zone<br />

activities.<br />

Sacramento County Maintenance Vehicles MCV Work Zone Support The maintenance and construction vehicle shall collect inputs from field personnel and from work zone devices on­board<br />

the maintenance and construction vehicle and send them to the controlling center.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Sacramento County Roadside Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall use toll and parking tags on passing vehicles for traffic data link time calculations and send to the<br />

controlling center; tag identities will be removed to ensure anonymity.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors traffic conditions (e.g., average speed) by communicating with<br />

passing vehicles equipped with a transponder or other short range communications device; also called smart probes.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall include equipment that monitors road conditions by communicating with passing vehicles<br />

equipped with a transponder or other short range communications device; also called smart probes.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall aggregate, format, and store collected vehicle smart probe data (traffic and road conditions data),<br />

calculate link travel times and processed road condition data, and send to future passing vehicles.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment operational status to the center.<br />

Sacramento County Roadside Equipment Roadway Probe Beacons The field element shall provide roadside beacon equipment fault indication to the center for repair.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Sacramento County Roadside Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Sacramento County Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) preemption requests from emergency vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

Sacramento County Roadside Equipment Roadway Signal Priority The field element shall respond to requests for indicator (e.g., signal) priority requests from transit vehicles at<br />

intersections, pedestrian crossings, and multimodal crossings.<br />

Sacramento County Roadside Equipment Roadway Signal Priority The field element shall notify controlling traffic management center and maintenance center that the signal timing has<br />

changed based on a signal preemption/priority request to help those centers determine whether a fault detected at the<br />

signal is a true malfunction or due to a signal override.<br />

Sacramento County Roadside Equipment<br />

Sacramento County Roadside Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Sacramento County Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Sacramento County Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Sacramento County Roadside Equipment Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Sacramento County Roadside Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Sacramento County Roadside Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Sacramento County Roadside Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Sacramento County Roadside Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall receive track status from the rail wayside equipment that can be passed on to the traffic<br />

management center. This may include the current status of the tracks and whether a train is approaching.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching using gates, lights/signs,<br />

barriers, and traffic control signals.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

Sacramento County Roadside Equipment Standard Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall collect and process, traffic sensor data in the vicinity of a highway­rail intersection (HRI).<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall determine whether the highway­rail intersection (HRI) is blocked by traffic in the roadway or some<br />

other obstruction.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall notify the traffic management center and the rail wayside equipment of any intersection blockages,<br />

including trapped vehicles or other obstructions.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the traffic management center.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall monitor the status of the highway­rail intersection (HRI) equipment, including both the current<br />

state and mode of operation and the current equipment condition, to be forwarded on to the rail wayside equipment.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall receive track status and arriving train information from the rail wayside equipment that can be<br />

passed on to the traffic management center. This may include the current status of the tracks and when a train is<br />

expected and/or how long the crossing will be closed.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall control the dynamic message signs (DMS) in the vicinity of a highway­rail intersection (HRI) to<br />

advise drivers, cyclists, and pedestrians of approaching trains.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall close the highway­rail intersection (HRI) when a train is approaching with enough time for traffic to<br />

safely clear the crossing using gates, lights/signs, barriers, and traffic control signals.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall support the integrated control of adjacent traffic signals to clear an area in advance of an<br />

approaching train and to manage traffic around the intersection.<br />

Sacramento County Roadside Equipment Advanced Rail Crossing The field element shall forward rail traffic advisories received from the Wayside Equipment to the traffic management<br />

center.<br />

Sacramento County Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

Sacramento County Roadside Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Sacramento County Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.<br />

Sacramento County Roadside Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall include surface and sub­surface environmental sensors that measure road surface temperature,<br />

moisture, icing, salinity, and other measures.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall include environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a maintenance center.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a traffic management center.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by weather service providers such as the National<br />

Weather Service or value­added sector specific meteorological services.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element's environmental sensors shall be remotely controlled by a maintenance and construction vehicle.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall provide environmental sensor equipment operational status to the controlling center or<br />

maintenance vehicle.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall provide environmental sensor equipment fault indication to the controlling center or maintenance<br />

vehicle.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall remotely aggregate environmental sensor data with environmental data collected from<br />

maintenance and construction vehicles.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall provide weather and road surface condition data to centers.<br />

Sacramento County Roadside Equipment Roadway Environmental Monitoring The field element shall provide weather and road surface condition data to maintenance and construction vehicles.<br />

Sacramento County Roadside Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Sacramento County Roadside Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Sacramento County Roadside Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Sacramento County Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Sacramento County Roadside Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Sacramento County Roadside Equipment Roadway Data Collection The field element shall collect traffic, road, and environmental conditions information.<br />

Sacramento County Roadside Equipment Roadway Data Collection The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road,<br />

and environmental conditions information to a center for archival.<br />

Sacramento County Roadside Equipment Roadway Data Collection The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the<br />

recorded data to a center for archival.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

The center shall update the incident information log once the emergency system operator has verified the incident.<br />

The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

The center shall relay location and incident details to the responding vehicles.<br />

The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

The center shall receive status information from care facilities to determine the appropriate facility and its location.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

The center shall store and maintain the emergency service responses in an action log.<br />

The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

Once the route is calculated the route shall be provided to the dispatch function.<br />

The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

The center shall receive event scheduling information from Event Promoters.<br />

The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

The center shall provide information to the media concerning the status of an emergency response.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Emergency Data Collection<br />

Emergency Data Collection<br />

The center shall request resources from transit agencies as needed to support the evacuation.<br />

The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

The center shall monitor the progress of the reentry process.<br />

The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

The center shall collect mayday messages from vehicles and drivers.<br />

The center shall collect mayday messages from travelers via personal handheld devices.<br />

The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by<br />

the vehicle's safety systems, or by a traveler via a personal handheld device.<br />

After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday<br />

message.<br />

The center shall determine whether the mayday message indicates an emergency that requires the attention of public<br />

safety agencies, and forward mayday emergency data to the appropriate agency as necessary.<br />

The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock<br />

doors.<br />

The center shall request additional emergency details from or issue commands to the vehicle's security systems or<br />

vehicle driver if needed.<br />

The center shall maintain a log of all mayday signals received from vehicles.<br />

The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the<br />

portable handheld device as directed by the personnel.<br />

The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento County Sheriff Dept.<br />

Communications<br />

Emergency Data Collection<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Sacramento County Sheriff Dept.<br />

Emergency Data Collection<br />

The center shall be able to produce sample products of the data available.<br />

Communications<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall compute the location of the emergency vehicle based on<br />

inputs from a vehicle location determination function.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the<br />

center for emergency management and dispatch.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when<br />

dispatched to a scene.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for<br />

emergency dispatch updates.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle shall provide the personnel on­board with dispatch information, including incident type and<br />

location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle shall send patient status information to the care facility along with a request for further<br />

information.<br />

Sacramento County Sheriff Vehicle On­board EV En Route Support The emergency vehicle shall forward care facility status information to emergency vehicle personnel, including the<br />

location, specialized services, quality of care, waiting time, number of rooms available, and emergency room status of<br />

hospitals or emergency care providers.<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County Sheriff Vehicle<br />

On­board EV Incident Management<br />

Communication<br />

On­board EV Incident Management<br />

Communication<br />

The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to<br />

implement an effective incident response. It includes local traffic, road, and weather conditions, hazardous material<br />

information, and the current status of resources that have been allocated to an incident.<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.<br />

Sacramento County Sheriff Vehicle<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

On­board EV Incident Management<br />

Communication<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the<br />

current incident response status such as the identification of the resources on site, site management strategies in effect,<br />

and current clearance status.<br />

The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

The center shall update the incident information log once the emergency system operator has verified the incident.<br />

The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

The center shall relay location and incident details to the responding vehicles.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Early Warning System<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

The center shall store and maintain the emergency service responses in an action log.<br />

The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

The center shall monitor information from Alerting and Advisory Systems such as the Information Sharing and Analysis<br />

Centers (ISACs), the National Infrastructure Protection Center (NIPC), the Homeland Security Advisory System (HSAS),<br />

etc. The information may include assessments (general incident and vulnerability awareness information), advisories<br />

(identification of threats or recommendations to increase preparedness levels), or alerts (information on imminent or inprogress<br />

emergencies).<br />

The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and<br />

surveillance data.<br />

The center shall broadcast wide­area alerts and advisories to traffic management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to transit management centers for emergency situations such<br />

as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other<br />

situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to toll administration centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to traveler information service providers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to maintenance centers for emergency situations such as<br />

severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations<br />

that pose a threat to life and property.<br />

The center shall broadcast wide­area alerts and advisories to other emergency management centers for emergency<br />

situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities,<br />

and other situations that pose a threat to life and property.<br />

The center shall process status information from each of the centers that have been sent the wide­area alert.<br />

The center shall coordinate the broadcast of wide­area alerts and advisories with other emergency management centers.<br />

The center shall receive incident information from other transportation management centers to support the early warning<br />

system.<br />

The center shall present the alert and advisory information and the status of the actions taken in response to the alert by<br />

the other centers to the emergency system operator as received from other system inputs.<br />

The center shall support the entry of alert and advisory information directly from the emergency system operator.<br />

The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

The center shall receive event scheduling information from Event Promoters.<br />

The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

The center shall provide information to the media concerning the status of an emergency response.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.<br />

The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

The center shall request resources from transit agencies as needed to support the evacuation.<br />

The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Sacramento County Telecommunications<br />

Center (DISPATCH)<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

MCM Environmental Information<br />

Processing<br />

MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

The center shall monitor the progress of the reentry process.<br />

The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

The center shall collect mayday messages from vehicles and drivers.<br />

The center shall collect mayday messages from travelers via personal handheld devices.<br />

The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by<br />

the vehicle's safety systems, or by a traveler via a personal handheld device.<br />

After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday<br />

message.<br />

The center shall determine whether the mayday message indicates an emergency that requires the attention of public<br />

safety agencies, and forward mayday emergency data to the appropriate agency as necessary.<br />

The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock<br />

doors.<br />

The center shall request additional emergency details from or issue commands to the vehicle's security systems or<br />

vehicle driver if needed.<br />

The center shall maintain a log of all mayday signals received from vehicles.<br />

The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the<br />

portable handheld device as directed by the personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

The center shall collect data to be archived from one or more data sources.<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center ITS Data Repository<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

Sacramento County Traffic Operations Center Traffic and Roadside Data Archival<br />

The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

The center shall include capabilities for performing quality checks on the incoming archived data.<br />

The center shall include capabilities for error notification on the incoming archived data.<br />

The center shall include capabilities for archive to archive coordination.<br />

The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

The center shall perform quality checks on received data.<br />

The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

The center shall collect traffic sensor information from roadside devices.<br />

The center shall collect environmental sensor information that from roadside devices.<br />

The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

The center shall record the status about the imported traffic and roadside data.<br />

The center shall use the status information to adjust the collection of traffic and roadside data.<br />

Sacramento County Traffic Operations Center Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

Sacramento County Traffic Operations Center Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Sacramento County Traffic Operations Center Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Sacramento County Traffic Operations Center Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Sacramento County Traffic Operations Center Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

Sacramento County Traffic Operations Center On­Line Analysis and Mining<br />

The center shall support the interface with Archive Data User Systems for requests for analysis of the archive data.<br />

Sacramento County Traffic Operations Center On­Line Analysis and Mining<br />

Sacramento County Traffic Operations Center On­Line Analysis and Mining<br />

Sacramento County Traffic Operations Center On­Line Analysis and Mining<br />

Sacramento County Traffic Operations Center On­Line Analysis and Mining<br />

Sacramento County Traffic Operations Center TBD<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

The center shall provide the capability to perform activities such as data mining, data fusion, summarizations,<br />

aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and<br />

expansion of data details, and many other advanced analysis services.<br />

The center shall receive the userÆs systems requests and develop the request to retrieve the data from the archive.<br />

The center shall respond to users systems requests for a catalog of the archived data analysis products available.<br />

For archive analysis and data mining products requiring financial payment the center shall process the financial requests<br />

and manage an interface to a Financial Institution.<br />

TBD<br />

The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

The center shall collect, process, store, and disseminate toll fee information to travelers.<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Basic Information Broadcast<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center Interactive Infrastructure Information<br />

Sacramento County Traffic Operations Center ISP Emergency Traveler Information<br />

Sacramento County Traffic Operations Center ISP Emergency Traveler Information<br />

Sacramento County Traffic Operations Center ISP Emergency Traveler Information<br />

Sacramento County Traffic Operations Center ISP Emergency Traveler Information<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Collection<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center MCM Environmental Information<br />

Processing<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

The center shall collect, process, store, and disseminate weather information to travelers.<br />

The center shall collect, process, store, and disseminate event information to travelers.<br />

The center shall collect, process, store, and disseminate air quality information to travelers.<br />

The center shall provide the capability to support requests from the media for traffic and incident data.<br />

The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

The center shall collect, process, store, and disseminate customized toll fee information to travelers upon request.<br />

The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

The center shall provide the capability to support requests from the media for traffic and incident data.<br />

The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

The center shall provide evacuation information to shelter providers.<br />

The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

The center shall remotely control environmental sensors on­board maintenance and construction vehicles that measure<br />

road and weather conditions including air and surface temperatures, wind speed, humidity, precipitation, visibility and<br />

other measures.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from traffic, emergency, and transit management, traveler information providers, and<br />

environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and<br />

construction vehicles.<br />

The center shall provide weather and road condition information to weather service providers and center personnel.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall collect operational status for the roadside and vehicle­based environmental sensor equipment.<br />

The center shall collect fault data for the roadside and vehicle­based environmental sensor equipment for repair.<br />

The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services) and local environmental sensor data.<br />

The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current<br />

and predicted road weather and road conditions.<br />

The center shall disseminate current and forecasted road weather and road condition information to weather service<br />

providers (such as the National Weather Service and value­added sector specific meteorological services) as well as<br />

other agencies including traffic, emergency, and transit management, traveler information providers, rail operations<br />

centers, media, and other maintenance management centers.<br />

The center shall provide value­added sector specific meteorological services with information on basic road facility and<br />

treatment information that supports forecasts for road conditions.<br />

The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center Collect Traffic Surveillance<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Probe Information Collection<br />

Sacramento County Traffic Operations Center TMC Signal Control<br />

Sacramento County Traffic Operations Center TMC Signal Control<br />

Sacramento County Traffic Operations Center TMC Signal Control<br />

Sacramento County Traffic Operations Center TMC Signal Control<br />

Sacramento County Traffic Operations Center TMC Signal Control<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Traffic Information Dissemination<br />

Sacramento County Traffic Operations Center TMC Regional Traffic Control<br />

Sacramento County Traffic Operations Center TMC Regional Traffic Control<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Detection<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

The center shall collect probe data including traffic and road conditions from vehicles via roadside beacon field elements;<br />

the data may be aggregated and initial link time calculations performed in the field.<br />

The center shall collect road condition data from probe­equipped transit vehicles via transit management centers; the<br />

data may be aggregated and preliminarily processed at the sending center.<br />

The center shall collect traffic data from probe­equipped emergency vehicles via emergency management centers; the<br />

data may be aggregated and initial link time calculations performed at the sending center.<br />

The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the<br />

data may be aggregated and initial link time calculations performed at the sending center.<br />

The center shall collect traffic data from toll administrative centers containing journey times between toll collection points<br />

for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending<br />

center.<br />

The center shall assimilate current and forecast traffic and road conditions based on collected probe data and distribute<br />

to other centers for dissemination to travelers.<br />

The center shall collect operational status for the roadside probe data collection equipment.<br />

The center shall collect fault data for the roadside probe data collection equipment for repair.<br />

The center shall remotely control traffic signal controllers.<br />

The center shall accept notifications of right­of­way requests from pedestrians.<br />

The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

The center shall collect traffic signal controller fault data from the field.<br />

The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento County Traffic Operations Center TMC Evacuation Support<br />

Sacramento County Traffic Operations Center TMC Evacuation Support<br />

Sacramento County Traffic Operations Center TMC Evacuation Support<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

Sacramento County Traffic Operations Center TMC Evacuation Support<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center HRI Traffic Management<br />

Sacramento County Traffic Operations Center Rail Operations Coordination<br />

Sacramento County Traffic Operations Center Rail Operations Coordination<br />

Sacramento County Traffic Operations Center Rail Operations Coordination<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center Traffic Maintenance<br />

Sacramento County Traffic Operations Center TMC Multimodal Coordination<br />

Sacramento County Traffic Operations Center TMC Multimodal Coordination<br />

Sacramento County Traffic Operations Center Traffic Data Collection<br />

Sacramento County Traffic Operations Center Traffic Data Collection<br />

Sacramento County Traffic Operations Center Traffic Data Collection<br />

Sacramento County Traffic Operations Center Traffic Data Collection<br />

The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

The center shall remotely control highway­rail intersection (HRI) equipment located in the field.<br />

The center shall accept collect highway­rail intersection (HRI) advisory or alert data from rail operations centers.<br />

The center shall collect highway­rail intersection (HRI) equipment operational status and compare against the control<br />

information sent by the center.<br />

The center shall provide the highway­rail intersection (HRI) equipment operational status to rail operations centers.<br />

The center shall collect incident information related to a highway­rail intersection (HRI), such as intersection blockages or<br />

crashes or equipment malfunctions.<br />

The center shall implement control plans to coordinate signalized intersections around highway­rail intersections (HRI),<br />

under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents,<br />

equipment faults, pedestrian crossings, etc.<br />

The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

The center shall collect environmental sensor operational status.<br />

The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

The center shall respond to requests from transit management centers for signal priority at one or more intersections<br />

along a particular transit route.<br />

The center shall exchange information with transit management centers including details current transit routes, the level<br />

of service on each route, and the progress of individual vehicles along their routes.<br />

The center shall collect traffic management data such as operational data, event logs, etc.<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

The center shall be able to produce sample products of the data available.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Sacramento County Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Sacramento County Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento County Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento County Website Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Sacramento County Website Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

Sacramento County Website Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Sacramento County Website Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Sacramento County Website Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Sacramento County Website Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Sacramento County Website Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento County Website Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

MCM Incident Management<br />

The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

MCM Incident Management<br />

MCM Incident Management<br />

Sacramento International Airport Maintenance MCM Incident Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Incident Management<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

MCM Incident Management<br />

MCM Incident Management<br />

Sacramento International Airport Maintenance MCM Incident Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance<br />

Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Roadway Maintenance and<br />

Dispatch<br />

Construction<br />

Sacramento International Airport Maintenance MCM Work Zone Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Work Zone Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Work Zone Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Work Zone Management<br />

Dispatch<br />

Sacramento International Airport Maintenance MCM Work Zone Management<br />

Dispatch<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.<br />

The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Basic Surveillance<br />

Roadway Basic Surveillance<br />

Roadway Probe Beacons<br />

Roadway Probe Beacons<br />

The field element shall return sensor and CCTV system operational status to the controlling center.<br />

The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

The field element shall use toll and parking tags on passing vehicles for traffic data link time calculations and send to the<br />

controlling center; tag identities will be removed to ensure anonymity.<br />

The field element shall include equipment that monitors traffic conditions (e.g., average speed) by communicating with<br />

passing vehicles equipped with a transponder or other short range communications device; also called smart probes.<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Probe Beacons<br />

The field element shall include equipment that monitors road conditions by communicating with passing vehicles<br />

equipped with a transponder or other short range communications device; also called smart probes.<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Probe Beacons<br />

The field element shall aggregate, format, and store collected vehicle smart probe data (traffic and road conditions data),<br />

calculate link travel times and processed road condition data, and send to future passing vehicles.<br />

Sacramento International Airport Roadside Roadway Probe Beacons<br />

The field element shall provide roadside beacon equipment operational status to the center.<br />

Equipment<br />

Sacramento International Airport Roadside Roadway Probe Beacons<br />

The field element shall provide roadside beacon equipment fault indication to the center for repair.<br />

Equipment<br />

Sacramento International Airport Roadside Roadway Incident Detection<br />

The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Incident Detection<br />

The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Sacramento International Airport Roadside Roadway Incident Detection<br />

The field element's video devices shall be remotely controlled by a traffic management center.<br />

Equipment<br />

Sacramento International Airport Roadside<br />

Equipment<br />

Roadway Incident Detection<br />

The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Sacramento International Airport TMC TBD TBD<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate toll fee information to travelers.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento International Airport TMC Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized toll fee information to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento International Airport TMC Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

Sacramento International Airport TMC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect probe data including traffic and road conditions from vehicles via roadside beacon field elements;<br />

the data may be aggregated and initial link time calculations performed in the field.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect road condition data from probe­equipped transit vehicles via transit management centers; the<br />

data may be aggregated and preliminarily processed at the sending center.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect traffic data from probe­equipped emergency vehicles via emergency management centers; the<br />

data may be aggregated and initial link time calculations performed at the sending center.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the<br />

data may be aggregated and initial link time calculations performed at the sending center.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect traffic data from toll administrative centers containing journey times between toll collection points<br />

for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending<br />

center.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall assimilate current and forecast traffic and road conditions based on collected probe data and distribute<br />

to other centers for dissemination to travelers.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect operational status for the roadside probe data collection equipment.<br />

Sacramento International Airport TMC TMC Probe Information Collection The center shall collect fault data for the roadside probe data collection equipment for repair.<br />

Sacramento International Airport TMC TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

Sacramento International Airport TMC TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

Sacramento International Airport TMC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

Sacramento International Airport TMC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

Sacramento International Airport TMC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

Sacramento International Airport TMC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

Sacramento International Airport TMC TMC Incident Dispatch<br />

Coordination/Communication<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall collect and store toll pricing data from toll administration centers, including the price for each road<br />

segment to which a toll applies, with the time and date for when it applies.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall collect and store parking information from parking management providers including lot locations, features<br />

(e.g. ability to handle oversized vehicles), capacity, type, hours of operation and rates.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall collect and store transit fare and schedule information from transit management centers.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall collect and store current transit, parking, and toll fee schedule information provided by regional traveler<br />

information systems.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall send requests to toll administration centers to change pricing, modify restrictions, or modify operations of<br />

a toll road facility.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall send requests to parking management providers to change the current parking lot charging structure.<br />

Sacramento International Airport TMC TMC Toll/Parking Coordination The center shall send requests to transit management centers to change the current transit services ­ schedules or fares<br />

of the transit services including park­and­ride lots.<br />

Sacramento International Airport TMC TMC Multimodal Coordination The center shall respond to requests from transit management centers for signal priority at one or more intersections<br />

along a particular transit route.<br />

Sacramento International Airport TMC TMC Multimodal Coordination The center shall exchange information with transit management centers including details current transit routes, the level<br />

of service on each route, and the progress of individual vehicles along their routes.<br />

Sacramento International Airport TMC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

Sacramento International Airport TMC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento International Airport TMC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

Sacramento International Airport TMC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

Sacramento International Airport TMC TBD TBD<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento International Airport Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento International Airport Website Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Sacramento Metro AQMD Emissions Data Management The center shall collect, analyze, and store vehicle emissions data collected from roadside sensors.<br />

Sacramento Metro AQMD Emissions Data Management The center shall collect, analyze, and store wide area pollution data collected from sensors that may the general (wide<br />

area) environment.<br />

Sacramento Metro AQMD Emissions Data Management The center shall configure and control emissions and air quality sensors located in the field.<br />

Sacramento Metro AQMD Emissions Data Management The center shall maintain a database of pollution reference data including acceptable and tolerable emissions and<br />

pollution levels for the area served by the center.<br />

Sacramento Metro AQMD Emissions Data Management The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for emissions.<br />

Sacramento Metro AQMD Emissions Data Management The center shall establish violation parameters, detect emissions violators, obtain the vehicle registration data from the<br />

appropriate State Department of Motor Vehicles (DMV) office, and then provide the capability to send violation information<br />

to a law enforcement agency.<br />

Sacramento Metro AQMD Emissions Data Management The center shall distribute air quality information to the media, traveler information service providers, and traffic<br />

management centers. This information may be used for information to travelers or part of demand management<br />

programs.<br />

Sacramento Metro AQMD Emissions Data Collection The center shall collect air quality and emissions management data from various sources, including emissions sensors<br />

distributed along the roadside and wide­area sensors detecting pollution over a larger geographical area.<br />

Sacramento Metro AQMD Emissions Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento Metro AQMD Emissions Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emissions management<br />

data or for the data itself.<br />

Sacramento Metro AQMD Emissions Data Collection The center shall be able to produce sample products of the data available.<br />

Sacramento Metro AQMD TBD TBD<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized toll fee information to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Sacramento Region 511 Website Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall provide the capability to process voice­formatted requests for traveler information from a traveler<br />

telephone information system, and return the information in the requested format.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall provide the capability to process dual­tone multifrequency (DTMF)­based requests (touch­tone) for<br />

traveler information from a traveler telephone information system.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall provide the capability to process traveler information requests from a traveler telephone information<br />

system.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide information on traffic conditions in the requested voice format and for the requested<br />

location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide work zone and roadway maintenance information in the requested voice format and<br />

for the requested location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide roadway environment conditions information in the requested voice format and for the<br />

requested location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide weather and event information in the requested voice format and for the requested<br />

location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide transit service information in the requested voice format and for the requested<br />

location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide yellow pages services information in the requested voice format and for the<br />

requested location.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall collect and provide current ferry and rail schedule and airport status information in the requested voice<br />

format and for the requested location.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall provide the capability to support both specific caller requests as well as bulk upload of regional traveler<br />

information.<br />

Sacramento Region 511 Website Traveler Telephone Information The center shall receive and forward region­specific wide­area alert and advisory information to the traveler telephone<br />

information system, including major emergencies such as a natural or man­made disaster, civil emergency, child<br />

abductions, severe weather watches and warnings, military activities, and law enforcement warnings.<br />

Sacramento Region 511 Website ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

Sacramento Region 511 Website ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

Sacramento Region 511 Website ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

Sacramento Region 511 Website ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7­digit call routing) to<br />

receive emergency notification information and provide it to the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from 911 services and present the possible incident information to<br />

the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from motorist call­boxes and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency call information from mayday service providers and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from other public safety agencies and present the possible<br />

incident information to the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from public transit systems and present the possible incident<br />

information to the emergency system operator.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations,<br />

or commercial fleet operators and present the possible incident information to the emergency system operator. This may<br />

include detection of non­permitted transport of security sensitive hazmat, hazardous cargo spills, etc.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Call­Taking<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Dispatch<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Routing<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

Emergency Response Management<br />

The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for<br />

incidents involving potential hazardous materials.<br />

The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls<br />

and internal analysis of security sensor and surveillance data, and assign each a level of confidence.<br />

The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify<br />

the reported incident.<br />

The center shall update the incident information log once the emergency system operator has verified the incident.<br />

The center shall provide the capability for digitized map data to act as the background to the emergency information<br />

presented to the emergency system operator.<br />

The center shall forward the verified emergency information to the responding agency based on the location and nature of<br />

the emergency.<br />

The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under<br />

center personnel control.<br />

The center shall store the current status of all emergency vehicles available for dispatch and those that have been<br />

dispatched.<br />

The center shall relay location and incident details to the responding vehicles.<br />

The center shall provide the capability to request traffic control measures from traffic management centers such as signal<br />

preemption, traffic barriers and road closures.<br />

The center shall track the location and status of emergency vehicles responding to an emergency and update the incident<br />

status based on information from the emergency vehicle.<br />

The center shall receive status information from care facilities to determine the appropriate facility and its location.<br />

The center shall store and maintain the emergency service responses in an action log.<br />

The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate<br />

emergency resources.<br />

The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.<br />

The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate<br />

resources are dispatched and utilized.<br />

The center shall collect current traffic and road condition information from traffic management centers for emergency<br />

vehicle route calculation.<br />

The center shall receive inputs from traffic management and maintenance centers on the location and status of traffic<br />

control equipment and work zones along potential emergency routes.<br />

The center shall calculate emergency vehicle routes based on information from traffic management and maintenance<br />

centers.<br />

In special circumstances such as during disasters and evacuations when normal routes are not available, the center shall<br />

request a route from the traffic management center.<br />

The center shall provide the capability to request special traffic control measures from the traffic management center to<br />

facilitate emergency vehicle progress along the suggested route.<br />

Once the route is calculated the route shall be provided to the dispatch function.<br />

The center shall develop, coordinate with other agencies, and store emergency response plans.<br />

The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional<br />

resources from traffic, maintenance, or other emergency centers if needed.<br />

The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and<br />

shall provide the capability to override the current allocation to suit the special needs of a current incident.<br />

The center shall receive event scheduling information from Event Promoters.<br />

The center shall provide the capability to request transit resource availability from transit centers for use during disaster<br />

and evacuation operations.<br />

The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and<br />

systems to create an overall transportation system status, and disseminate to each of these centers and the traveling<br />

public via traveler information providers.<br />

The center shall provide information to the media concerning the status of an emergency response.<br />

The center shall provide the capability for digitized map data to act as the background to the information presented to the<br />

emergency system operator.<br />

The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters<br />

and evacuations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Incident Command<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Emergency Evacuation Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Mayday Support<br />

Emergency Data Collection<br />

Emergency Data Collection<br />

The center shall provide tactical decision support, resource coordination, and communications integration for Incident<br />

Commands that are established by first responders to support local management of an incident.<br />

The center shall provide incident command communications with public safety, emergency management, transportation,<br />

and other allied response agency centers.<br />

The center shall track and maintain resource information and action plans pertaining to the incident command.<br />

The center shall share incident command information with other public safety agencies including resource deployment<br />

status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather<br />

conditions.<br />

The center shall assess the status of responding emergency vehicles as part of an incident command.<br />

The center shall manage inter­agency coordination of evacuation operations, from initial planning through the evacuation<br />

process and reentry.<br />

The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.<br />

The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and<br />

present the operator with other agenciesÆ plans.<br />

The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red<br />

Cross) in the region.<br />

The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other<br />

emergency management centers as needed.<br />

The center shall request resources from transit agencies as needed to support the evacuation.<br />

The center shall request traffic management agencies to implement special traffic control strategies and to control<br />

evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.<br />

The center shall provide traveler information systems with evacuation guidance including basic information to assist<br />

potential evacuees in determining whether evacuation is necessary and when it is safe to return.<br />

The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared<br />

during the incident, with allied agencies.<br />

The center shall monitor the progress of the reentry process.<br />

The center shall submit evacuation information to toll administration centers along with requests for changes in the toll<br />

services or fee collection during an evacuation.<br />

The center shall collect mayday messages from vehicles and drivers.<br />

The center shall collect mayday messages from travelers via personal handheld devices.<br />

The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by<br />

the vehicle's safety systems, or by a traveler via a personal handheld device.<br />

After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday<br />

message.<br />

The center shall determine whether the mayday message indicates an emergency that requires the attention of public<br />

safety agencies, and forward mayday emergency data to the appropriate agency as necessary.<br />

The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock<br />

doors.<br />

The center shall request additional emergency details from or issue commands to the vehicle's security systems or<br />

vehicle driver if needed.<br />

The center shall maintain a log of all mayday signals received from vehicles.<br />

The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the<br />

portable handheld device as directed by the personnel.<br />

The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor<br />

and surveillance data, threat data, and incident data.<br />

The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Sacramento Regional Fire/ EMS Comm.<br />

Center<br />

Emergency Data Collection<br />

The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management<br />

data or for the data itself.<br />

Sacramento Regional Fire/ EMS Comm. Emergency Data Collection<br />

The center shall be able to produce sample products of the data available.<br />

Center<br />

Sacramento Regional Traveler Card TBD TBD<br />

School Bus Dispatch TBD TBD<br />

School Bus Dispatch Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

School Bus Dispatch Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

School Bus Dispatch Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

School Bus Dispatch Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

School Bus Dispatch Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

School Bus Dispatch Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

School Bus Dispatch Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

School Bus Dispatch Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

School Bus Dispatch Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

School Bus Dispatch Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

School Bus Dispatch Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

School Bus Dispatch Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

School Bus Dispatch Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

School Bus Dispatch Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.<br />

School Bus Dispatch Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

School Bus Dispatch Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

School Bus Dispatch Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

School Bus Dispatch Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

School Bus Dispatch Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

School Bus Dispatch Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

School Bus Dispatch Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

School Bus Dispatch Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

School Bus Dispatch Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

School Bus Dispatch Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

School Bus Dispatch Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

School Bus Dispatch Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

School Bus Dispatch Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

School Bus Dispatch Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

School Bus Dispatch Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

School Bus Dispatch Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

School Buses On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

School Buses On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

School Buses On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

School Buses On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

School Buses On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

School Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

School Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

School Buses<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

School Buses<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

School Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

School Buses<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

School Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

School Buses On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

School Buses On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

School Buses On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

School Buses On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

School Buses On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

School Buses On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

School Buses On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

School Buses On­board Transit Security The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or<br />

authentic inputs from the transit vehicle operator.<br />

School Buses On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

School Buses On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

School Buses On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

School Buses On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

School Buses On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

School Buses On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

STARNET ISP TBD TBD<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including<br />

incident information, detours and road closures, event information, recommended routes, and current speeds on specific<br />

routes.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including<br />

scheduled maintenance and construction work activities and work zone activities.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate toll fee information to travelers.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

STARNET ISP Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.<br />

STARNET ISP Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

STARNET ISP Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized traffic and highway condition information to<br />

travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific<br />

routes upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized maintenance and construction information to<br />

travelers, including scheduled maintenance and construction work activities and work zone activities upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer<br />

options, transit fares, and real­time schedule adherence information to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized parking information to travelers, including location,<br />

availability, and fees upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized toll fee information to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized weather information to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized multimodal transportation service information (for<br />

example, from ferry and airline operators), including transfer points and other information, to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized event information to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall provide all traveler information based on the traveler's current location or a specific location identified by<br />

the traveler, and filter or customize the provided information accordingly.<br />

STARNET ISP Interactive Infrastructure Information The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.<br />

STARNET ISP Interactive Infrastructure Information The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and<br />

advanced payment for tolls, and provide transaction success or failure details.<br />

STARNET ISP Interactive Infrastructure Information The center shall support requests for traveler information and advanced payment for traveler services from commercial<br />

fleet operators.<br />

STARNET ISP Interactive Infrastructure Information The center shall provide the capability to exchange information with another traveler information service provider current<br />

or predicted data for road links that are outside the area served by the local supplier.<br />

STARNET ISP Interactive Infrastructure Information The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.<br />

STARNET ISP Interactive Infrastructure Information The center shall provide the capability to support requests from the media for traffic and incident data.<br />

STARNET ISP Interactive Infrastructure Information The center shall provide the capability for a system operator to control the type and update frequency of traveler<br />

information.<br />

STARNET ISP Traveler Telephone Information The center shall provide the capability to process voice­formatted requests for traveler information from a traveler<br />

telephone information system, and return the information in the requested format.<br />

STARNET ISP Traveler Telephone Information The center shall provide the capability to process dual­tone multifrequency (DTMF)­based requests (touch­tone) for<br />

traveler information from a traveler telephone information system.<br />

STARNET ISP Traveler Telephone Information The center shall provide the capability to process traveler information requests from a traveler telephone information<br />

system.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide information on traffic conditions in the requested voice format and for the requested<br />

location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide work zone and roadway maintenance information in the requested voice format and<br />

for the requested location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide roadway environment conditions information in the requested voice format and for the<br />

requested location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide weather and event information in the requested voice format and for the requested<br />

location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide transit service information in the requested voice format and for the requested<br />

location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide yellow pages services information in the requested voice format and for the<br />

requested location.<br />

STARNET ISP Traveler Telephone Information The center shall collect and provide current ferry and rail schedule and airport status information in the requested voice<br />

format and for the requested location.<br />

STARNET ISP Traveler Telephone Information The center shall provide the capability to support both specific caller requests as well as bulk upload of regional traveler<br />

information.<br />

STARNET ISP Traveler Telephone Information The center shall receive and forward region­specific wide­area alert and advisory information to the traveler telephone<br />

information system, including major emergencies such as a natural or man­made disaster, civil emergency, child<br />

abductions, severe weather watches and warnings, military activities, and law enforcement warnings.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall provide the capability to provide specific pre­trip and enroute directions to travelers (and drivers),<br />

including costs, arrival times, and transfer points.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall include bicycle routes, walkways, skyways, and multi­use trails in the pre­trip and enroute directions it<br />

provides to travelers.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall support on­line route guidance for travelers using personal devices (such as PDAs).<br />

STARNET ISP Infrastructure Provided Route Selection The center shall support on­line route guidance for drivers in vehicles.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall support on­line route guidance for specialty vehicles, such as commercial vehicles.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate route plans based on current and/or predicted conditions of the road network, scheduled<br />

maintenance and construction work activities, and work zone activities.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate route plans based on transit services, including fares, schedules, and requirements for<br />

travelers with special needs.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate route plans based on current asset restrictions, such as height and weight restrictions on<br />

tunnels or bridges.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate route plans based on current or forecasted weather.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate route plans based on ferry, rail, air, or other multimodal transportation data.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall exchange route segment information with other centers outside the area served by the local center.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall generate trips based on the use of more than one mode of transport.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall use the preferences and constraints specified by the traveler in the trip request to select the most<br />

appropriate mode of transport.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall provide the capability for the traveler to confirm the proposed trip plan.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall log route plans, particularly for special vehicles such as those containing hazardous materials, over­sized<br />

vehicles, or motorcades, with a traffic center.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used to determine vehicle and non­vehicle routes, trip planning, and<br />

on­line vehicle guidance.<br />

STARNET ISP Infrastructure Provided Route Selection The center shall provide the capability for center personnel to control route calculation parameters.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

STARNET ISP<br />

STARNET ISP<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

The center shall accept requests from traveler interface systems for ridesharing as part of a trip plan request.<br />

The center shall provide a rideshare match based on origin and destination of the traveler's proposed trip, any routing<br />

constraints, preferences specified by the traveler, compatibility of this rideshare with rideshares confirmed by other<br />

travelers, the requesting traveler's eligibility data, and traffic data.<br />

The center shall process rideshare requests by balancing the relative benefits of the rideshare to each rideshare<br />

participant.<br />

The center shall arrange connections to transit or other multimodal services for portions of a multi­segment trip that<br />

includes ridesharing.<br />

The center shall provide a confirmation of the traveler's rideshare match and provide the capability to support a payment<br />

transaction for the rideshare service.<br />

The center shall store all rideshare matches and traveler eligibility data.<br />

STARNET ISP<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

STARNET ISP<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

STARNET ISP<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

STARNET ISP<br />

Infrastructure Provided Dynamic<br />

Ridesharing<br />

STARNET ISP ISP Emergency Traveler Information The center shall collect and provide to the traveler interface systems emergency evacuation information, including<br />

evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit<br />

services, and traffic and road conditions at the origin, destination, and along the evacuation routes.<br />

STARNET ISP ISP Emergency Traveler Information The center shall provide evacuation information to shelter providers.<br />

STARNET ISP ISP Emergency Traveler Information The center shall collect and provide wide­area alert information to the traveler interface system with region­specific data,<br />

including major emergencies such as a natural or man­made disaster, civil emergency, child abductions, severe weather<br />

watches and warnings, military activities, and law enforcement warnings.<br />

STARNET ISP ISP Emergency Traveler Information The center shall provide the capability for a system operator to control the type and update frequency of emergency and<br />

wide­area alert information distributed to travelers.<br />

STARNET Server ITS Data Repository The center shall collect data to be archived from one or more data sources.<br />

STARNET Server ITS Data Repository The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

STARNET Server ITS Data Repository The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

STARNET Server ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.<br />

STARNET Server ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.<br />

STARNET Server ITS Data Repository The center shall include capabilities for archive to archive coordination.<br />

STARNET Server ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

STARNET Server ITS Data Repository The center shall perform quality checks on received data.<br />

STARNET Server ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

STARNET Server ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

STARNET Server ITS Data Repository When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

STARNET Server ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

STARNET Server Traffic and Roadside Data Archival The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

STARNET Server Traffic and Roadside Data Archival The center shall collect traffic sensor information from roadside devices.<br />

STARNET Server Traffic and Roadside Data Archival The center shall collect environmental sensor information that from roadside devices.<br />

STARNET Server Traffic and Roadside Data Archival The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

STARNET Server Traffic and Roadside Data Archival The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

STARNET Server Traffic and Roadside Data Archival The center shall record the status about the imported traffic and roadside data.<br />

STARNET Server Traffic and Roadside Data Archival The center shall use the status information to adjust the collection of traffic and roadside data.<br />

STARNET Server TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information,<br />

congestion data, traffic data, signal timing plans, and real­time signal control information.<br />

STARNET Server TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring<br />

and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).<br />

STARNET Server TMC Environmental Monitoring The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity,<br />

and other measures.<br />

STARNET Server TMC Environmental Monitoring The center shall remotely control environmental sensors that measure weather conditions including temperature, wind,<br />

humidity, precipitation, and visibility.<br />

STARNET Server TMC Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information using a combination of<br />

weather service provider information (such as the National Weather Service and value­added sector specific<br />

meteorological services), data from roadway maintenance operations, and environmental data collected from sensors<br />

deployed on and about the roadway.<br />

STARNET Server TMC Environmental Monitoring The center shall provide weather and road condition information to weather service providers and center personnel.<br />

STARNET Server TMC Environmental Monitoring The center shall respond to control data from center personnel regarding environmental sensor control and weather data<br />

collection and processing.<br />

STARNET Server Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

STARNET Server Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

STARNET Server Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

STARNET Server Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

ITS Data Repository<br />

The center shall collect data to be archived from one or more data sources.<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

ITS Data Repository<br />

The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

The center shall include capabilities for performing quality checks on the incoming archived data.<br />

The center shall include capabilities for error notification on the incoming archived data.<br />

The center shall include capabilities for archive to archive coordination.<br />

The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

The center shall perform quality checks on received data.<br />

The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Statewide Integrated Reporting System<br />

(SWITRS)<br />

Taxi Dispatch<br />

Taxi Dispatch<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

ITS Data Repository<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

The center shall collect traffic sensor information from roadside devices.<br />

The center shall collect environmental sensor information that from roadside devices.<br />

The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

The center shall record the status about the imported traffic and roadside data.<br />

The center shall use the status information to adjust the collection of traffic and roadside data.<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

ITS Data Repository<br />

The center shall collect data to be archived from one or more data sources.<br />

ITS Data Repository<br />

The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the<br />

collection of archived data and may include descriptions of the schema or structure of the data, a description of the<br />

contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

The center shall store the archived data in a focused repository that is suited to a particular set of ITS data users.<br />

The center shall include capabilities for performing quality checks on the incoming archived data.<br />

The center shall include capabilities for error notification on the incoming archived data.<br />

The center shall include capabilities for archive to archive coordination.<br />

The center shall support a broad range of archived data management implementations, ranging from simple data marts<br />

that collect a focused set of data and serve a particular user community to large­scale data warehouses that collect,<br />

integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

Traffic Accident and Surveillance Analysis<br />

System (TASAS)<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

ITS Data Repository<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

Traffic and Roadside Data Archival<br />

The center shall perform quality checks on received data.<br />

The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations,<br />

aggregations, or transformations applied to the data before it is stored in the archive.<br />

The center shall respond to requests from the administrator interface function to maintain the archive data.<br />

When data or a catalog of data is received from the archive, the center shall generate the requested data product for the<br />

users systems.<br />

For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a<br />

Financial Institution.<br />

The center shall manage the collection of archive data directly from collection equipment located at the roadside.<br />

The center shall collect traffic sensor information from roadside devices.<br />

The center shall collect environmental sensor information that from roadside devices.<br />

The center shall respond to requests from the Archive Data Administer to input the parameters that control the collection<br />

process.<br />

The center shall send the request for data and control parameters to the field equipment where the information is<br />

collected and returned.<br />

The center shall record the status about the imported traffic and roadside data.<br />

The center shall use the status information to adjust the collection of traffic and roadside data.<br />

Government Reporting Systems Support The center shall provide data from an ITS archive to federal, state, or local government reporting systems.<br />

Government Reporting Systems Support The center shall provide the capability to select data from an ITS archive for use in government reports.<br />

Government Reporting Systems Support The center shall provide the capability to format data from an ITS archive suitable for input into government reports.<br />

Government Reporting Systems Support The center shall support requests for ITS archived data from Government Reporting Systems.<br />

Government Reporting Systems Support The center shall provide the applicable meta­data for any ITS archived data to satisfy government reporting system<br />

requests. Meta­data may include attributes that describe the source and quality of the data and the conditions<br />

surrounding the collection of the data.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in traveler secure areas, which<br />

include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g.,<br />

emergency pull­off areas and travel information centers). The data may be raw or pre­processed in the field.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations,<br />

transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull­off areas and<br />

travel information centers).<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

Unitrans Transit Dispatch Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

Unitrans Transit Dispatch Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Unitrans Transit Dispatch Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Unitrans Transit Dispatch Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Unitrans Transit Dispatch Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Unitrans Transit Dispatch Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Unitrans Transit Dispatch Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Unitrans Transit Dispatch Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Unitrans Transit Dispatch Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Unitrans Transit Dispatch Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Unitrans Transit Dispatch Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Unitrans Transit Dispatch Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Unitrans Transit Dispatch Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Unitrans Transit Dispatch Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Unitrans Transit Dispatch Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Unitrans Transit Dispatch Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Unitrans Transit Dispatch Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Unitrans Transit Dispatch Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

Unitrans Transit Dispatch Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

Unitrans Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Unitrans Transit Dispatch<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Unitrans Transit Dispatch Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Unitrans Transit Dispatch Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Unitrans Transit Dispatch Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Unitrans Transit Dispatch Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Unitrans Transit Dispatch Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Unitrans Transit Dispatch Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Unitrans Transit Dispatch Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Unitrans Transit Dispatch Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Unitrans Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Unitrans Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Unitrans Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Unitrans Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Unitrans Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Unitrans Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Unitrans Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Unitrans Transit Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Unitrans Transit Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Unitrans Transit Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall receive traffic information from a center and present it to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall receive transit information from a center and present it to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall receive event information from a center and present it to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall receive evacuation information from a center and present it to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall receive wide­area alerts and present it to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall provide the capability for digitized map data to act as the background to the<br />

information presented to the traveler.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall support traveler input in audio or manual form.<br />

User Personal Computing Devices Personal Basic Information Reception The personal traveler interface shall present information to the traveler in audible or visual forms, consistent with a<br />

personal device.<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall receive traffic information from a center and present it to the traveler upon request.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall receive transit information from a center and present it to the traveler upon request.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall receive yellow pages information (such as lodging, restaurants, theaters, bicycle<br />

facilities, and other tourist activities) from a center and present it to the traveler upon request.<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall receive event information from a center and present it to the traveler upon request.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall receive evacuation information from a center and present it to the traveler.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall receive wide­area alerts and present it to the traveler.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall accept reservations for confirmed trip plans.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall support payment for services, such as confirmed trip plans, tolls, transit fares,<br />

parking lot charges, map updates, and advanced payment for tolls.<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall provide an interface through which credit identity, stored credit value, or traveler<br />

information may be collected from a traveler card being used by a traveler with a personal device.<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall base requests from the traveler on the traveler's current location or a specific<br />

location identified by the traveler, and filter the provided information accordingly.<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall provide digitized map data to act as the background to the information presented to<br />

the traveler.<br />

User Personal Computing Devices<br />

Personal Interactive Information The personal traveler interface shall support traveler input in audio or manual form.<br />

Reception<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall present information to the traveler in audible or visual forms consistent with a<br />

personal device, and suitable for travelers with hearing and vision physical disabilities.<br />

User Personal Computing Devices<br />

Personal Interactive Information<br />

Reception<br />

The personal traveler interface shall be able to store frequently requested or used data, including the traveler's identity,<br />

home and work locations, etc.<br />

Utilities Dispatch TBD TBD<br />

Vehicles Vehicle Location Determination The vehicle shall provide the vehicle's current location to other in­vehicle functions.<br />

Vehicles Vehicle Location Determination The vehicle shall calculate the location from one or more sources of position data. These location referencing systems<br />

include position systems such as GPS, DGPS, odometer and differential odometers.<br />

Vehicles Vehicle Location Determination The vehicle shall refine its calculations as required by other in­vehicle functions.<br />

Vehicles Vehicle Toll/Parking Interface The vehicle shall respond to requests from toll collection equipment for tag information including credit identity, stored<br />

value card cash, etc.<br />

Vehicles Vehicle Toll/Parking Interface The vehicle shall respond to request from parking field equipment for tag information including credit identity, stored value<br />

card cash, etc.<br />

Vehicles Vehicle Toll/Parking Interface The vehicle shall provide an interface to the driver to make requests for advance payments of tolls, parking, and transit<br />

fares and present the status of electronic payment transactions.<br />

Vehicles Vehicle Toll/Parking Interface The vehicle shall provide an interface with the traveler card / payment instrument carried on­board the vehicle (tag) ­ to<br />

exchange identity information and payment transactions.<br />

Vehicles Vehicle Toll/Parking Interface The vehicle shall present information to the driver in audible or visual forms without impairing the driver's ability to control<br />

the vehicle in a safe manner.<br />

Vehicles Vehicle Probe Support The vehicle shall collect and process traffic conditions data, including location, speed, and link travel times.<br />

Vehicles Vehicle Probe Support The vehicle shall transmit data to the center upon request including speed, link travel times, location and timestamp<br />

information.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Vehicles Vehicle Probe Support The vehicle shall transmit data to field equipment located along the roadway upon request including speed, link travel<br />

times, location and timestamp information.<br />

Vehicles Vehicle Mayday I/F The vehicle shall provide the capability for a driver to report an emergency and summon assistance.<br />

Vehicles Vehicle Mayday I/F The vehicle shall provide the capability to accept input from a driver via a panic button or some other functionally similar<br />

form of input device provided as part of the in­vehicle equipment.<br />

Vehicles Vehicle Mayday I/F The vehicle shall provide the capability to automatically identify that a collision has occurred using equipment such as<br />

collision detection sensors with an interface to mayday type equipment that would automatically detect vehicle problems<br />

and send appropriate distress signals to a center.<br />

Vehicles Vehicle Mayday I/F The vehicle shall forward a request for assistance to a center containing the driver's current location, its identity and basic<br />

vehicle data relevant to its current condition, as well as any other data, such as personal medical history, vehicle<br />

orientation, etc., that may be developed in­vehicle by other systems.<br />

Vehicles Vehicle Mayday I/F The vehicle shall acknowledge the driver's request for emergency assistance.<br />

Vehicles Vehicle Mayday I/F The vehicle shall provide further details about the emergency to the center upon request from that function.<br />

Vehicles TBD TBD<br />

Weather Information Providers TBD TBD<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

Yolo Bus Dispatch Center Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

Yolo Bus Dispatch Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Yolo Bus Dispatch Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Yolo Bus Dispatch Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Yolo Bus Dispatch Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Yolo Bus Dispatch Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Yolo Bus Dispatch Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall manage the actual value of transit fares for each segment of each regular transit route, including the<br />

transmission of the information to transit vehicles and transit stops or stations.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall provide the capability for a system operator to manage the transit fares and control the exchange of<br />

transit fare information.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall process the financial requests from the transit vehicles or roadside and manage an interface to a<br />

Financial Institution.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall support the payment of transit fare transactions using data provided by the traveler cards / payment<br />

instruments.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall collect data on fare payment violations and send the data, including images of the violator, to the<br />

appropriate enforcement agency.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load The center shall process requests for transit fares to be paid in advance.<br />

Management<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall process requests for the advanced payment of tolls and parking lot charges as well as other nontransportation<br />

services, e.g. yellow­pages services.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall be capable of establishing emergency fare structures to override all other fares during disasters, states<br />

of emergency, or evacuations.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall maintain a list of invalid traveler credit identities, or bad tag lists that can be forwarded to transit vehicles<br />

and transit stops or stations.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load The center shall collect passenger loading and fare statistics data to implement variable and flexible fare structures.<br />

Management<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load<br />

Management<br />

The center shall exchange fare and load information with other transit management centers, including potential<br />

Centralized Payments facilities.<br />

Yolo Bus Dispatch Center<br />

Transit Center Fare and Load The center shall provide transit fare information to other centers, including traveler information providers upon request.<br />

Management<br />

Yolo Bus Dispatch Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Yolo Bus Dispatch Center Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yolo Bus Dispatch Center Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Yolo Bus Dispatch Center Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Yolo Bus Dispatch Center Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Yolo Bus Dispatch Center Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

Yolo Bus Dispatch Center Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

Yolo Bus Dispatch Center Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Yolo Bus Dispatch Center<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Yolo Bus Dispatch Center<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Yolo Bus Dispatch Center Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Yolo Bus Dispatch Center Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Yolo Bus Dispatch Center Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Yolo Bus Dispatch Center Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Yolo Bus Dispatch Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Yolo Bus Dispatch Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Yolo Bus Dispatch Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Yolo Bus Dispatch Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Yolo County Bus Website Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transit transfer options, transit<br />

fares, and real­time schedule adherence information to travelers.<br />

Yolo County Bus Website Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability,<br />

and fees.<br />

Yolo County Bus Website Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.<br />

Yolo County Bus Website Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.<br />

Yolo County Bus Website Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast<br />

traveler information.<br />

Yolo County Buses On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Yolo County Buses On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Yolo County Buses On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Yolo County Buses On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Yolo County Buses On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Yolo County Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.<br />

Yolo County Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Yolo County Buses<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Yolo County Buses<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Yolo County Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Yolo County Buses<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Yolo County Buses<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall detect embarking travelers on­board a transit vehicle and read data from the traveler card /<br />

payment instrument that they are carrying.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall provide an image of all travelers which shall be used for violation processing of those who do not<br />

have a traveler card / payment instrument or whose transit fare transaction fails.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall determine the traveler's travel routing based on the transit vehicle's current location and the<br />

traveler's destination.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall calculate the traveler's fare based on the origin and destination provided by the traveler as well<br />

as factors such as the transit routing, transit fare category, traveler history, and route­specific information.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall have access to the complete range of transit services (routes and schedules) that are available<br />

to the traveler.<br />

Yolo County Buses<br />

On­board Transit Fare and Load The transit vehicle shall provide a transit fare payment interface that is suitable for travelers with physical disabilities.<br />

Management<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall include a database on­board the transit vehicle for use in fare processing from which the fares for<br />

all possible trips within the transit operational network can be determined.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support an emergency fare structure overriding all other fares that can be activated during<br />

disasters, states of emergency or evacuations.<br />

Yolo County Buses<br />

On­board Transit Fare and Load<br />

Management<br />

The transit vehicle shall support the support advanced payments for tolls, and/or parking lot charges, and/or transit fares<br />

via the traveler card / payment instrument.<br />

Yolo County Buses<br />

On­board Transit Fare and Load The transit vehicle shall provide passenger loading and fare statistics data to the center.<br />

Management<br />

Yolo County Buses On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Yolo County Buses On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or<br />

authentic inputs from the transit vehicle operator.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Yolo County Buses On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Yolo County Buses On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Yolo County Buses On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Yolo County Buses On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Yolo County Buses On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the<br />

center for further analysis and storage, under center control.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor<br />

data to the center for further analysis and storage.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.<br />

Yuba City Field Equipment Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall control traffic signals at intersections and on main highways for urban and rural areas, under<br />

center control.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall collect pedestrian images and pedestrian sensor data, and respond to pedestrian crossing<br />

requests via display, audio signal, or other manner.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall provide the capability to notify the traffic management center that a pedestrian has requested rightof­way<br />

and when the request was or will be granted (request for right­of­way).<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from the indicator control information.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall monitor operation of traffic signal controllers and report to the center any instances in which the<br />

indicator response does not match that expected from known indicator preemptions.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall return traffic signal controller operational status to the controlling center.<br />

Yuba City Field Equipment Roadway Signal Controls The field element shall return traffic signal controller fault data to the maintenance center for repair.<br />

Yuba City Field Equipment<br />

Yuba City Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers,<br />

under center control; the DMS may be either those that display variable text messages, or those that have fixed format<br />

display(s) (e.g. vehicle restrictions, or lane open/close).<br />

The field element shall include driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.<br />

Yuba City Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a<br />

potential hazard, or providing mandatory instructions as to the availability of pedestrian access).<br />

Yuba City Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the<br />

center.<br />

Yuba City Field Equipment<br />

Roadway Traffic Information<br />

Dissemination<br />

The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for<br />

repair.<br />

Yuba City Field Equipment Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.<br />

Yuba City Field Equipment Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic<br />

management center.<br />

Yuba City Field Equipment Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.<br />

Yuba City Field Equipment Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic<br />

management center.<br />

Yuba City Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic<br />

signals, work zone intrusion alert systems), without center control.<br />

Yuba City Field Equipment Roadway Equipment Coordination The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that<br />

receive control information from other field element devices, without center control.<br />

Yuba City Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data<br />

and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent<br />

intersections), without center control.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yuba City Field Equipment Roadway Equipment Coordination The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems,<br />

barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive<br />

control information from other field element devices, without center control.<br />

Yuba City Field Equipment Roadway Work Zone Traffic Control The field element shall collect, process, and send work zone images to the center for further analysis and distribution,<br />

under center control.<br />

Yuba City Field Equipment Roadway Work Zone Traffic Control Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic<br />

messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are<br />

currently passing.<br />

Yuba City Field Equipment Roadway Work Zone Traffic Control Under the control of field personnel within maintenance vehicles, the field element shall include driver information<br />

systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around a work<br />

zone through which they are currently passing.<br />

Yuba City Field Equipment Roadway Work Zone Traffic Control The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work<br />

zones to the maintenance center.<br />

Yuba City Field Equipment Roadway Work Zone Traffic Control The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to<br />

the maintenance center for repair.<br />

Yuba City Field Equipment Roadway Data Collection The field element shall collect traffic, road, and environmental conditions information.<br />

Yuba City Field Equipment Roadway Data Collection The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road,<br />

and environmental conditions information to a center for archival.<br />

Yuba City Field Equipment Roadway Data Collection The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the<br />

recorded data to a center for archival.<br />

Yuba City Maintenance Dispatch MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its<br />

jurisdiction.<br />

Yuba City Maintenance Dispatch MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and<br />

other equipment.<br />

Yuba City Maintenance Dispatch MCM Vehicle Tracking The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for maintenance and construction vehicle<br />

tracking.<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall collect and analyze vehicle diagnostics information from maintenance and construction vehicles. The<br />

information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms<br />

concerning the operational condition of the vehicle and ancillary equipment.<br />

The center shall exchange information with equipment repair facilities including status and history of repairs concerning<br />

maintenance and construction vehicles. This information includes vehicle status and diagnostic information, vehicle<br />

utilization, and coordination of when vehicles will be available for preventative and corrective maintenance.<br />

Yuba City Maintenance Dispatch<br />

MCM Vehicle and Equipment<br />

Maintenance Management<br />

The center shall schedule preventive and corrective vehicle maintenance with the equipment repair facility based on fleet<br />

health reports, maintenance records, vehicle utilization and vehicle availability schedules.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction. The<br />

information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency,<br />

the effective time period, etc.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic<br />

management centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources<br />

to implement response plans, assist in clean up, verify an incident, etc. This may also involve coordination with traffic<br />

management centers and other maintenance centers.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic<br />

management centers including an assessment of damage sustained by the road network including location and extent of<br />

the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame<br />

for repair and recovery.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Yuba City Maintenance Dispatch MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial<br />

surveillance, field reports, inspections, tests, and analyses to support incident management.<br />

Yuba City Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs<br />

and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials<br />

information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

Yuba City Maintenance Dispatch<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

MCM Roadway Maintenance and<br />

Construction<br />

The center shall respond to requests from emergency management and traffic management centers for hazard removal,<br />

field equipment repair, and other roadway maintenance.<br />

The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance activities. This information includes: equipment and consumables resupply purchase request status,<br />

personnel qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

The center shall provide emergency management and traffic management centers with information about scheduled<br />

maintenance and construction work activities including anticipated closures and impact to the roadway, alternate routes,<br />

anticipated delays, closure times, and durations.<br />

The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and<br />

environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure,<br />

and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems,<br />

barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors<br />

and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.<br />

The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway<br />

infrastructure or on maintenance and construction vehicles.<br />

The center shall receive equipment availability and materials storage status information from storage facilities to support<br />

the scheduling of roadway maintenance and construction activities.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for the scheduling of roadway maintenance and<br />

construction activities.<br />

The center shall collect current and forecast traffic and weather information from traffic management centers and weather<br />

service providers (such as the National Weather Service and value­added sector specific meteorological services).<br />

The center shall dispatch and route maintenance and construction vehicle drivers and support them with route­ specific<br />

environmental, incident, advisory, threat, alert, and traffic congestion information.<br />

The center shall manage an interface with center personnel to accept vehicle systems control information and remotely<br />

control maintenance and construction vehicle on­board equipment.<br />

The center shall track the status of roadway maintenance and construction activities by monioring collected data from the<br />

dispatched vehicles and equipment.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yuba City Maintenance Dispatch MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles,<br />

maintenance and construction operators, and for information coordination purposes.<br />

Yuba City Maintenance Dispatch MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or<br />

near the work zone.<br />

Yuba City Maintenance Dispatch MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency<br />

management centers, other maintenance centers, traveler information providers, and the media.<br />

Yuba City Maintenance Dispatch MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory<br />

radio systems located in or near the work zone.<br />

Yuba City Maintenance Dispatch MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone<br />

activities. This information includes: equipment and consumables resupply purchase request status, personnel<br />

qualifications including training and special certifications, environmental regulations and rules that may impact<br />

maintenance activities, and requests and project requirements from contract administration.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall provide work zone activities affecting the road network including the nature of the maintenance or<br />

construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays,<br />

alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual<br />

indication of current work zone status and traffic impacts.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall provide status information about scheduled maintenance and construction activities including anticipated<br />

closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is<br />

provided to other management centers such as traffic, emergency, transit, traveler information providers, other<br />

maintenance centers, multimodal transportation providers, rail operations, and the media.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with<br />

other management centers such as traffic, emergency, transit, and rail operations.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall collect and disseminate asset restriction information levied on transportation asset usage based on<br />

infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight<br />

restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed<br />

during maintenance and construction.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall exchange information with administrative systems to support the planning and scheduling of<br />

maintenance and construction activities. This information includes: equipment and consumables resupply purchase<br />

request status, personnel qualifications including training and special certifications, environmental regulations and rules<br />

that may impact maintenance activities, and requests and project requirements from contract administration.<br />

Yuba City Maintenance Dispatch MCM Work Activity Coordination The center shall exchange rail schedules and work plans with rail operations centers.<br />

Yuba City TOC Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements<br />

under remote control of the center.<br />

Yuba City TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.<br />

Yuba City TOC Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of<br />

the center.<br />

Yuba City TOC Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the<br />

center.<br />

Yuba City TOC Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data<br />

under remote control of the center.<br />

Yuba City TOC Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways,<br />

e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each<br />

link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.<br />

Yuba City TOC Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic data.<br />

Yuba City TOC Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic<br />

sensor and surveillance data to other centers.<br />

Yuba City TOC Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection,<br />

analysis, storage, and distribution.<br />

Yuba City TOC TMC Signal Control The center shall remotely control traffic signal controllers.<br />

Yuba City TOC TMC Signal Control The center shall accept notifications of right­of­way requests from pedestrians.<br />

Yuba City TOC TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the<br />

center.<br />

Yuba City TOC TMC Signal Control The center shall collect traffic signal controller fault data from the field.<br />

Yuba City TOC TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based<br />

on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the<br />

passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio<br />

(such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and<br />

weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special<br />

traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management<br />

centers, and traveler information providers.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall distribute traffic data to the media upon request; the capability to provide the information in both data<br />

stream and graphical display shall be supported.<br />

Yuba City TOC TMC Traffic Information Dissemination The center shall provide the capability for center personnel to control the nature of the data that is available to non­traffic<br />

operations centers and the media.<br />

Yuba City TOC TMC Incident Detection The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe<br />

weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.<br />

Yuba City TOC TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.<br />

Yuba City TOC TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, and intermodal freight depots.<br />

Yuba City TOC TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

Yuba City TOC TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field.<br />

Yuba City TOC TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the<br />

detection, verification, and classification of incidents.<br />

Yuba City TOC TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.<br />

Yuba City TOC<br />

Yuba City TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall exchange alert information and status with emergency management centers. The information includes<br />

notification of a major emergency such as a natural or man­made disaster, civil emergency, or child abduction for<br />

distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic<br />

area affected by the emergency, the effective time period, and information and instructions necessary for the public to<br />

respond to the alert. This may also identify specific information that should not be released to the public.<br />

The center shall coordinate planning for incidents with emergency management centers ­ including pre­planning activities<br />

for disaster response, evacuation, and recovery operations.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

Yuba City TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

The center shall support requests from emergency management centers to remotely control sensor and surveillance<br />

equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency<br />

vehicles with signal preemption.<br />

The center shall exchange incident and threat information with emergency management centers as well as maintenance<br />

and construction centers; including notification of existence of incident and expected severity, location, time and nature of<br />

incident.<br />

The center shall respond to requests from emergency management to provide traffic management resources to<br />

implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination<br />

with maintenance centers.<br />

The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters,<br />

traveler information service providers, media, and rail operations centers.<br />

The center shall provide road network conditions and traffic images to emergency management centers, maintenance<br />

and construction centers, and traveler information service providers.<br />

The center shall exchange road network status assessment information with emergency management and maintance<br />

centers including an assessment of damage sustained by the road network including location and extent of the damage,<br />

estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and<br />

recovery.<br />

The center shall coordinate information and controls with other traffic management centers.<br />

The center shall receive inputs from emergency management and transit management centers to develop an overall<br />

status of the transportation system including emergency transit schedules in effect and current status and condition of the<br />

transportation infrastructure.<br />

The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic incident management.<br />

Yuba City TOC<br />

TMC Incident Dispatch<br />

Coordination/Communication<br />

Yuba City TOC TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers ­ including pre­planning<br />

activities such as establishing routes, areas to be evacuated, timing, etc.<br />

Yuba City TOC TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy,<br />

activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver<br />

information systems to support evacuation traffic control plans.<br />

Yuba City TOC TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.<br />

Yuba City TOC TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers ­ including activities<br />

such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.<br />

Yuba City TOC Rail Operations Coordination The center shall exchange highway­rail intersection (HRI) information with rail operations centers. This information may<br />

include event schedules, requests for information from the Rail Operators, incident notification based on rail operations<br />

messages, and priority messages like notifications of a HAZMAT spill, equipment failure, or an intersection blockage.<br />

Yuba City TOC Rail Operations Coordination The center shall receive highway­rail intersection (HRI) maintenance schedules, train schedules, and incident notifications<br />

from rail operations centers.<br />

Yuba City TOC Rail Operations Coordination The center shall use the rail operations information to develop forecast HRI closure times and durations which may be<br />

applied in advanced traffic control strategies or delivered as enhanced traveler information.<br />

Yuba City TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.<br />

Yuba City TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.<br />

Yuba City TOC Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance<br />

center for repair.<br />

Yuba City TOC Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance<br />

center for repair.<br />

Yuba City TOC Traffic Maintenance The center shall collect environmental sensor operational status.<br />

Yuba City TOC Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.<br />

Yuba City TOC Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the<br />

schedule/status of their repair. Information exchanged includes details of new equipment faults, and clearances when the<br />

faults are cleared.<br />

Yuba City TOC Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for traffic maintenance data.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall receive work zone images from a maintenance center.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall analyze work zone images for indications of a possible incident.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios)<br />

to advise drivers of activity around a work zone.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall collect operational status for the driver information systems equipment in work zones.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall collect fault data for the driver information systems equipment in work zones for repair.<br />

Yuba City TOC TMC Work Zone Traffic Management The center shall receive proposed maintenance and construction work plans, analyze the activity as a possible incident,<br />

and provide work plan feedback to the sending center.<br />

Yuba City TOC Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.<br />

Yuba City TOC Traffic Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Yuba City TOC Traffic Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traffic data or for the data<br />

itself.<br />

Yuba City TOC Traffic Data Collection The center shall be able to produce sample products of the data available.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities<br />

(e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and<br />

transit railways or guideways). The data may be raw or pre­processed in the field.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall remotely monitor video images and audio surveillance data collected on­board transit vehicles. The data<br />

may be raw or pre­processed in the field.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall exchange surveillance data with other emergency centers.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall identify potential security threats based on collected security surveillance data.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall verify potential security threats by correlating security surveillance data from multiple sources.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and<br />

transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or<br />

guideways).<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall remotely control security surveillance devices on­board transit vehicles.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall exchange traveler images with other emergency management centers to support traveler image<br />

matching.<br />

Yuba­Sutter Transit Center Center Secure Area Surveillance The center shall respond to control data from center personnel regarding security surveillance data collection, processing,<br />

threat detection, and image matching.<br />

Yuba­Sutter Transit Center Transit Center Tracking and Dispatch The center shall monitor the locations of all transit vehicles within its network.<br />

Yuba­Sutter Transit Center Transit Center Tracking and Dispatch The center shall determine adherence of transit vehicles to their assigned schedule.<br />

Yuba­Sutter Transit Center Transit Center Tracking and Dispatch The center shall collect trip monitoring data from on­board systems including transit vehicle mileage, fuel usage,<br />

passenger loading, availability, etc.<br />

Yuba­Sutter Transit Center Transit Center Tracking and Dispatch The center shall provide transit operational data to traveler information service providers.<br />

Yuba­Sutter Transit Center Transit Center Tracking and Dispatch The center shall support an interface with a map update provider, or other appropriate data sources, through which<br />

updates of digitized map data can be obtained and used as a background for transit tracking and dispatch.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall generate transit routes and schedules based on such factors as parameters input by the system<br />

operator, road network conditions, operational data on current routes and schedules, and digitized map data.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall provide the interface to the system operator to control the generation of new routes and schedules<br />

(transit services) including the ability to review and update the parameters used by the routes and schedules generation<br />

processes and to initiate these processes<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall be able to generate special routes and schedules to support an incident, disaster, evacuation, or other<br />

emergency.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall accept requests from traffic management to change routes and schedules as part of the implementation<br />

of demand management strategies.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall collect transit operational data for use in the generation of routes and schedules.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall assign transit vehicle operators based on factors such as eligibility, route preferences, seniority, and<br />

transit vehicle availability.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall manage large deviations of individual transit vehicles, deviations in rural areas, and deviations of large<br />

numbers of vehicles.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall generate the necessary corrective actions which may involve more than the vehicles concerned and<br />

more far reaching action, such as, the introduction of extra vehicles, wide area signal priority by traffic management, the<br />

premature termination of some services, etc.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall exchange information with Maintenance and Construction Operations concerning work zones, roadway<br />

conditions, asset restrictions, work plans, etc.<br />

Yuba­Sutter Transit Center Transit Center Fixed­Route Operations The center shall disseminate up­to­date schedules and route information to other centers for fixed and flexible route<br />

services.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall monitor transit vehicle operational data to determine if the transit vehicle is off­route and assess whether<br />

a security incident is occurring.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall receive reports of emergencies on­board transit vehicles entered directly be the transit vehicle operator<br />

or from a traveler through interfaces such as panic buttons or alarm switches.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall support the back­office portion of functionality to authenticate transit vehicle operators.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall receive information pertaining to a wide­area alert such as weather alerts, disaster situations, or child<br />

abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall send wide­area alert information to travelers (on­board transit vehicles or at stations/stops) and transit<br />

vehicle operators.<br />

Yuba­Sutter Transit Center Transit Center Security The center shall coordinate the response to security incidents involving transit with other agencies including Emergency<br />

Management, other transit agencies, media, traffic management, and traveler information service providers.<br />

Yuba­Sutter Transit Center Transit Garage Operations The center shall maintain records of a transit vehicle operator's performance. This may be done utilizing standardized<br />

performance evaluation criteria set forth by governmental regulations and transit operating company policies, assessing<br />

the transit vehicle operator's driving history, and assessing comments from the transit vehicle operator's supervisor(s) as<br />

well as noting any moving violations or accidents, supervisor comments, government regulations, and company policies.<br />

Yuba­Sutter Transit Center Transit Garage Operations The center shall assess the transit vehicle operator's availability based on previous work assignments, accumulated<br />

hours, plus health and vacation commitments.<br />

Yuba­Sutter Transit Center Transit Garage Operations The center shall assign transit vehicle operators to transit schedules based on their eligibility, route preferences, seniority,<br />

and transit vehicle availability.<br />

Yuba­Sutter Transit Center Transit Garage Operations The center shall provide an interface through which the transit vehicle operator information can be maintained ­ either<br />

from the transit vehicle operator, a transit system operator (i.e. center personnel), or other functions.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall collect operational and maintenance data from transit vehicles.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall monitor the condition of a transit vehicle to analyze brake, drive train, sensors, fuel, steering, tire,<br />

processor, communications equipment, and transit vehicle mileage to identify mileage based maintenance, out­ofspecification<br />

or imminent failure conditions.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall generate transit vehicle maintenance schedules, includes what and when the maintenance or repair is to<br />

be performed.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall generate transit vehicle availability listings, current and forecast, to support transit vehicle assignment<br />

planning based, in part, on the transit vehicle maintenance schedule.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall assign technicians to a transit vehicle maintenance schedule, based upon such factors as personnel<br />

eligibility, work assignments, preferences and seniority.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall verify that the transit vehicle maintenance activities were performed correctly, using the transit vehicle's<br />

status, the maintenance personnel's work assignment, and the transit maintenance schedules.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall generate a time­stamped maintenance log of all maintenance activities performed on a transit vehicle.<br />

Yuba­Sutter Transit Center Transit Garage Maintenance The center shall provide the transit system operator with the capability to update transit vehicle maintenance information<br />

and receive reports on all transit vehicle operations data.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall provide travelers using public transportation with traffic and advisory information upon request. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall provide transit information to the media including details of deviations from schedule of regular transit<br />

services.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall exchange transit schedules, real­time arrival information, fare schedules, and general transit service<br />

information with other transit organizations to support transit traveler information systems.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall provide transit service information to traveler information service providers including routes, schedules,<br />

schedule adherence, and fare information as well as transit service information during evacuation.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall enable yellow pages (including non­motorized transportation) information to be output to the traveler.<br />

Yuba­Sutter Transit Center Transit Center Information Services The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man<br />

made disasters.<br />

Yuba­Sutter Transit Center<br />

Transit Center Multi­Modal Coordination The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and<br />

construction operations, parking management, and other surface or air transportation modes.<br />

Yuba­Sutter Transit Center<br />

Transit Center Multi­Modal Coordination The center shall share transfer cluster and transfer point information with multimodal transportation service providers,<br />

other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or<br />

terminals where transfers can be made conveniently.<br />

Yuba­Sutter Transit Center Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the<br />

vicinity of a disaster or other emergency.<br />

Yuba­Sutter Transit Center Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management ­ identifying the transit role in an<br />

evacuation and the transit resources that would be used.<br />

Yuba­Sutter Transit Center Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those<br />

with special needs and the general population.<br />

Yuba­Sutter Transit Center Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as<br />

they coordinate evacuations.<br />

Yuba­Sutter Transit Center Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit<br />

operations, transit vehicle maintenance data, etc.<br />

Yuba­Sutter Transit Center Transit Data Collection The center shall assign quality control metrics and meta­data to be stored along with the data. Meta­data may include<br />

attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.<br />

Yuba­Sutter Transit Center Transit Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the transit data or for the data<br />

itself.<br />

Yuba­Sutter Transit Center Transit Data Collection The center shall be able to produce sample products of the data available.<br />

Yuba­Sutter Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall compute the location of the transit vehicle based on inputs from a vehicle location determination<br />

function.<br />

Yuba­Sutter Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall support the computation of the location of a transit vehicle using on­board sensors to augment<br />

the location determination function. This may include proximity to the transit stops or other known reference points as<br />

well as recording trip length.<br />

Yuba­Sutter Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including vehicle mileage and fuel usage.<br />

Yuba­Sutter Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall record transit trip monitoring data including operational status information such as doors<br />

open/closed, passenger loading, running times, etc.<br />

Yuba­Sutter Transit Vehicles On­board Transit Trip Monitoring The transit vehicle shall send the transit vehicle trip monitoring data to center­based trip monitoring functions.<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall receive transit route information for its assigned route including transit service instructions, traffic<br />

information, road conditions, and other information for the operator.


APPENDIX J: FUNCTIONAL REQUIREMENTS<br />

Functional Requirements by Element<br />

Element Name Functional Area Requirement<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall use the route information and its current location to determine the deviation from the<br />

predetermined schedule.<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall calculate the estimated times of arrival (ETA) at transit stops.<br />

Management<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall determine scenarios to correct the schedule deviation.<br />

Management<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall provide the schedule deviations and instructions for schedule corrections to the transit vehicle<br />

operator if the deviation is small, or the transit vehicle is operating in an urban area.<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule The transit vehicle shall send the schedule deviation and estimated arrival time information to the center.<br />

Management<br />

Yuba­Sutter Transit Vehicles<br />

On­board Fixed Route Schedule<br />

Management<br />

The transit vehicle shall support the operations of a flexible route service. This may include requests for route deviations<br />

that would then lead to schedule corrective actions.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data<br />

for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local<br />

storage (e.g., in an event recorder).<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles,<br />

and identify potential incidents or threats based on received processing parameters.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information<br />

to the center along with the vehicleÆs current location.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such<br />

interfaces as panic buttons, silent or audible alarms, etc.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall output reported emergencies to the center.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall receive acknowledgments of the emergency request from the center and output this<br />

acknowledgment to the transit vehicle operator or to the travelers.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit<br />

vehicle operator.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or<br />

authentic inputs from the transit vehicle operator.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall perform authentication of the transit vehicle operator.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall output an indication of potential incidents or threats to the center along with the vehicleÆs<br />

current location.<br />

Yuba­Sutter Transit Vehicles On­board Transit Security The transit vehicle shall monitor and output surveillance equipment status and fault indications.<br />

Yuba­Sutter Transit Vehicles On­board Maintenance The transit vehicle shall collect and process vehicle mileage data available to sensors on­board.<br />

Yuba­Sutter Transit Vehicles On­board Maintenance The transit vehicle shall collect and process the transit vehicle's operating conditions such as engine temperature, oil<br />

pressure, brake wear, internal lighting, environmental controls, etc.<br />

Yuba­Sutter Transit Vehicles On­board Maintenance The transit vehicle shall transmit vehicle maintenance data to the center to be used for scheduling future vehicle<br />

maintenance.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall enable traffic and travel advisory information to be requested and output to the traveler. Such<br />

information may include transit routes, schedules, transfer options, fares, real­time schedule adherence, current<br />

incidents, weather conditions, and special events.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall enable yellow pages (including non­motorized transportation) information to be requested and<br />

output to the traveler.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall broadcast advisories about the imminent arrival of the transit vehicle at the next stop via an onboard<br />

automated annunciation system.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall support input and output forms that are suitable for travelers with physical disabilities.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall gather transit advisory data, including alerts and advisories pertaining to major emergencies, or<br />

man made disasters.<br />

Yuba­Sutter Transit Vehicles On­board Transit Information Services The transit vehicle shall tailor the output of the request traveler information based on the current location of the transit<br />

vehicle.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!