appendix a1: bibliography...72. texas transportation institute, guidelines for developing its data...

091783000 California ITS Architecture and System Plan Appendix A1 - Bibliography 1 Appendix A1: Bibliography

APPENDIX A1: BIBLIOGRAPHY

1. USDOT, Regional ITS Architecture Guidance: Developing, Using, and Maintaining an ITS Architecture for Your Region, October 12, 2001

2. USDOT, National ITS Architecture, version 5.0, October, 2003

3. FHWA/FTA, ITS Architecture and Standards Final Rule/ Policy (23 CFR Parts 655 and 940 Intelligent

Transportation System Architecture and Standards), effective April, 2001 4. Advanced Transportation Systems Program Plan – 1996 Update: Framework for a California

Partnership, December 1998

5. Advanced Transportation Systems Program Plan, October 1995

6. BayArea Regional Intelligent Transportation Systems Plan Project Deliverable 9: Architecture Maintenance, April 2004

7. California Commercial Vehicle Operations Strategic Business Plan, November 1999

8. California Department of Transportation, Director’s Traveler Information Task Force, Traveler

Information Implementation Plan (document not dated)

9. California Department of Transportation, Director’s Traveler Information Task Force, Meeting Record, August 1, 2001

10. California Department of Transportation, Director’s Traveler Information Task Force, Proposed Traveler

Information Strategy for Caltrans and California, Memorandum from Jeff Morales to Janet Friedl and Russell Snyder, March 5, 2001

11. California Department of Transportation, Division of New Technology and Research, Intelligent

Transportation Systems Deployment Plan Strategic Evaluation, June 2002 12. California Department of Transportation, Division of New Technology and Research, Inventory,

Compliance, and Deployment Document, October 2000

13. California Department of Transportation, Division of New Technology and Research, Inventory, Compliance and Deployment Appendices, October 2000

14. California Department of Transportation, Division of New Technology and Research, New Directions:

An Action Summary for Southern California ITS Priority Corridor, February 2000

15. California Department of Transportation, Division of New Technology and Research, New Directions: A Strategic Deployment Guide for the Southern California ITS Priority Corridor, May 2000

16. California Department of Transportation, Traffic Operations Program, TMC Master Plan, Revised

December 1997

17. California ITS Deployment Initiatives, February 2000

18. California ITS Developing the Business – Final Report, 1998

19. California ITS System Architecture, Final Deliverable, July 1999.


20. California Transportation Plan 2025, August 2003

21. California/Oregon Advanced Transportation Systems – Regional Architecture, December 2000

22. California’s National Parks Service Needs Assessment (still being developed), January 2003

23. California State Rail Plan, January 2002

24. California Statewide Rail Transportation Assessment, September 2002

25. Central Coast ITS Strategic Deployment Plan, Executive Summary, June 2000

26. Central Coast: ITS Project Documentation, Volume Three, June 2000

27. Central Coast: ITS Project Implementation Guide, Volume Two, June 2000

28. Central Coast: ITS Strategic Plan, Volume One, June 2000

29. Connecting Californians: California Transportation Plan 2025, August 2002

30. Global Gateways Development Program - Final Report, January 2002 31. Inland Empire Regional Intelligent Transportation Systems (ITS) Architecture, July 2003

32. ITS/CVO and CVISN: Implications for Security and Commercial Freight Mobility. Presentation at 2003

CAATS Annual Meeting, San Diego, December 2003.

33. ITS Deployment Plan Strategic Evaluation, June 2002

34. ITS Standards Program Update, April 2002

35. Los Angeles and Ventura Region Intelligent Transportation Systems Strategic Deployment Plan, October 1998

36. Los Angeles County MTA, Regional Integration of Intelligent Transportation System (RIITS), Los

Angeles County ITS Integration Master Plan, October 2002

37. Los Angeles County Regional ITS Architecture, April 2004

38. Los Angeles MTA (RIITS), Regional ITS Architecture, October 2002

39. Los Angeles Spread Spectrum Radio Traffic Signal Interconnect, Practical Lessons Learned Evaluation Report, June 1999

40. Metropolitan Transportation Commission (MTC), ITS Early Deployment Plan, 1996

41. Metropolitan Transportation Commission (MTC), Assessment Plan, June 2002

42. Metropolitan Transportation Commission (MTC), ITS Inventory Design Plan, May 2002

43. Metropolitan Transportation Commission (MTC), State of ITS in the San Francisco Bay Area, November

2002


44. Oak Ridge National Laboratory, Cross-Cutting Studies and State-of-the-Practice Reviews: Archive and Use of ITS-Generated Data, April 30, 2002

45. Orange County Transportation Authority, ITS Study Update, 1996

46. Orange County Transportation Authority, ITS Master Plan Update (Final Draft), August 1998

47. Oregon ITS Strategic Plan, 1997-2017, October 1998

48. Rural California and Oregon Advanced Transportation Systems (COATS): Regional Architecture,

December 2000

49. Rural California and Oregon Advanced Transportation Systems (COATS): ITS Strategic Deployment Plan, May 2001

50. Sacramento Area Council of Governments, ITS Early Deployment Plan, 1996

51. Sacramento Area Council of Governments, Project Report, Sacramento ITS Deployment Partnership:

Proposals for a Sacramento Transportation Area-Wide Network and Smart Corridor Development, June 1999

52. Sacramento Area Council of Governments, Sacramento Regional ITS Architecture – Executive Summary

and Final Report, July 2001

53. STARNET System Needs Assessment, Nov. 2001

54. San Diego Region Intelligent Transportation Systems Architecture: Detailed Document, Feb 2003

55. San Diego Region System Architecture Summary, August 2002

56. San Joaquin Valley Intelligent Transportation System (ITS) Strategic Deployment Plan-Final, September 2001

57. Sierra Nevada ITS Strategic Deployment Plan, June 2002

58. Smart Card Alliance, Transit and Retail Payment: Opportunities for Collaboration and Convergence,

October 2003

59. Southern California ITS Priority Corridor Strategic Deployment Plan, Interim Report, August 1998

60. Southern California Priority Corridor Intermodal Transportation Management and Information System (SHOWCASE) High Level Design, Showcase Kernel Network System Impact Document, March 2000

61. Statewide Goods Movement ITS Action Plan: Task 1 ITS Inventory Report, May 2002

62. Statewide Goods Movement ITS Action Plan: Task 5 Final Report, May 2002

63. Strategic Plan – Intelligent Transportation Systems (Riverside County Transportation Commission, San

Bernardino Associated Governments), April 2000

64. Status of California ITS Transportation Systems, March 1999.

65. Tahoe Basin ITS Strategic Plan Working Paper #2: ITS Vision for the Tahoe Basin, Revised November 2000


66. Tahoe Basin ITS Strategic Plan, Report #1: Market Packages and Functional Requirements, November

2001

67. Tahoe Basin ITS Strategic Plan, Working Paper #1: System Inventory Deficiencies, and Opportunities Assessment, November 2002

68. Tahoe Basin ITS Strategic Plan, Working Paper #3: ITS Project Funding Sources, February 2002

69. Tahoe Basin ITS Strategic Plan, Working Paper #4: Functional Areas and Technology Options, May

2002

70. Tahoe Gateway Counties ITS Strategic Deployment Plan, Report #1: Market Package and Functional Requirements, January 2002

71. Tahoe Gateway Counties ITS Strategic Deployment Plan, Report #2: Regional Architecture and

Implementation Plan, May 2002

72. Texas Transportation Institute, Guidelines for Developing ITS Data Archiving Systems, September 2001

73. Texas Transportation Institute, Guidelines for The National Intelligent Transportation Systems Program Plan: A Ten Year Vision, January 2002

74. Transit Communication Interface Profile, August 2002

75. Transit ITS Standards Program Update, April 2002

76. Transportation Management Systems (TMS) Arterial Signalization Business Plan, December 2002

77. Transportation Management Systems (TMS) Baseline Inventory, February 2002

78. Transportation Management Systems (TMS) Detection Plan, December 2002

79. Transportation Management Systems (TMS) Incident Management Business Plan, December 2002

80. Transportation Management Systems (TMS) Ramp Metering Business Plan, December 2002

81. Transportation Management Systems (TMS) Transportation Management Centers: Development

Considerations and Constraints, December 2002

82. Transportation Management Systems (TMS) Traveler Information Business Plan, December 2002

83. Transportation Research Board, TCRP Report 94: Fare Policies, Structures and Technologies: Update, 2003

84. Transportation System Performance Measures, October 2000

85. United States Department of Transportation, Federal Highway Administration, Evaluation Strategy,

December 1997

86. United States Department of Transportation, Maritime Administration, Intermodal Access to US Ports, Report on Survey Findings, August 2002


87. Ventura County Transportation Commission, Using Technology to Help Move People and Products: A Strategy for Ventura County, September 2001

091783000 California ITS Architecture and System Plan Appendix A2 - Final Inventory 1 Appendix A2: Final Inventory

APPENDIX A2: FINAL INVENTORY Element Name Stakeholder Name Element Description Status Amtrak Schedule Operations AMTRAK This is the operational entity that provides static and real-time Amtrak schedule

information. Existing

Archive Data User Systems Archive Data Users Systems that access archive data. Planned Arizona DOT TMCs Arizona DOT Represents Traffic Management Centers operated by State of Arizona. Existing ASPEN California Highway Patrol

(CHP) A laptop based system to conduct roadside safety inspections. Planned

Baja Transportation Management Center

Mexican Transportation Agency

Planned transportation management center in Baja Mexico. Planned

BART Fleet Management System

BART Operations and dispatch of BART fleet. Existing

Bay Area Transit Administration

Bay Area Transit Agencies Administration functions of Bay Area transit agencies. Includes electronic fare reconciliation between agencies.

Existing

Bay Area Transit Stations and Stops

Bay Area Transit Agencies Transit stations and transfer points of Bay Area transit systems. Existing

Bay Area Transit Vehicles Bay Area Transit Agencies Transit vehicles of central California transit agencies. Existing BCBP Offices BCBP Bureau of Customs and Border Protection Offices. Existing Broadcast and Print Media Local Media Local media that includes traveler information with entertainment, general news and

other topical information. In contrast to other traveler information inventory items, this entry represents the analog TV, radio and print media intended for human, rather than system, processing and interpretation.

Existing

CA CVIEW California Highway Patrol (CHP)

Commercial Vehicle Information Exchange Window. Collects snapshots for interstate and intrastate carriers, vehicles, and drivers. Interfaces with SAFER for interstate snapshot exchange. Also distributed snapshots to other states.

Existing

CA DMV Enforcement Vehicles

California DMV Represents DMV's enforcement vehicles. Planned

California Commercial Vehicle Inspection System (CCVIS)

California Highway Patrol (CHP)

This system allows electronic collection of inspection data while an inspection is being performed. Information is electronically forwarded to a CHP headquarters database and then to SAFETYNET, a federal commercial vehicle information system database. The CHP currently conducts 70 percent of its inspections using CCVIS. The system has improved accuracy, timeliness of reporting, and has significantly reduced data entry time. Future expansions or improvements may include

Existing


Element Name Stakeholder Name Element Description Status modifications for mobile road enforcement officer use.

California Highway Information Network(CHIN)

Caltrans HQ The California Highway Information Network provides daily adverse travel conditions and work plan information. Information is made available by telephone (1-800-427-ROAD) and Internet (http://www.dot.ca.gov/hq/roadinfo/).

Existing

California Highway Information Web Page

Caltrans HQ This interactive Web-based service (http://www.dot.ca.gov/hq/roadinfo) provides key road construction, detour and closure information based on user-specified route numbers.

Existing

Caltrans HQ California HPMS Highway performance monitoring system. Existing California National Parks and National Forests

National Park Service/U.S. Forest Service

Visitors information for park access, parking, and trip planning at National Parks and National Forests within the state.

Planned

California Office of Emergency Services Operations Centers

State Office of Emergency Services

The OES Warning Center is staffed 24 hours a day, 365 days a year. From this center, warning controllers speak with county OESs and the National Warning Center in Berryville, Virginia on a daily basis. OES also maintains a 24-hour toll-free toxic release hotline, and relays spill reports to a number of other state and federal response and regulatory agencies, as well as local governments. During emergencies, OES activates the State Operations Center (SOC) in Sacramento and the Regional Emergency Operations Centers (REOCs) in impacted areas to receive and process local requests for assistance.

Existing

California Transit Data Archive

Caltrans Represents statewide archive of transit data. Existing

Caltrain Operations Center Caltrain Managing of Caltrain system including managing of Automated Passenger Counters (APC) which is integrated with AVL system.

Planned

Caltrans District 1 Transportation Management Center

Caltrans, District 1 This TMC, called ARTIC (Advanced Rural Technology Integration Center) in the COATS architecture plays a central role in managing and monitoring the transportation system in Del Norte, Humboldt, Mendocino and Lake Counties. It is a Tier 3 Satellite Operation Center connected to the Oakland Regional TMC.

Existing


Caltrans, District 10 Provides traffic management, information dissemination, and incident management for state owned highways in District 10. Located in Stockton.

Existing

Caltrans District 11 Intermodal Transportation Management Center

Caltrans, District 11 Caltrans transportation management center for District 11. Interfaces with San Diego TMC, Ramp Meters, Inductive Loops, CCTV, CMS, HAR. JTOC is the physical location for this center.

Existing


Element Name Stakeholder Name Element Description Status Caltrans District 12 Transportation Management Center

Caltrans, District 12 The District 12 Transportation Management Center (TMC) provides traffic management and incident management for District 12 freeway and highway systems. Real time information is gathered from many sources such as electronic sensors in the pavement, freeway call boxes, video cameras, 911 calls, officers on patrol, Caltrans highway crews, ramp meter sensors, earthquake monitors, motorist cellular calls, and commercial traffic reporters, which is sent to the TMC 24-hours a day, seven days a week.

Existing


Caltrans, District 2 The Caltrans District 2 TMC, called ARTIC (Advanced Rural Technology Integration Center) in the COATS architecture, coordinates transportation operations for north central California, serving Colusa, Glenn, Lassen, Modoc, Plumas, Shasta, Siskiyou, Tehama, It is a Tier 3 Satellite Operation Center which is connected to the Sacramento TMC.

Existing

Caltrans District 3 Regional Transportation Management Center

Caltrans, District 3 This system will monitor and control the area freeways, including the US Interstates 5 and 80, the US Federal Highway 50, and the California State Highway 99. Monitoring is accomplished by loop sensors and CCTV, and the use of ramp meters and DMS (CMS). Will archive data in the future. This Tier 1 TMC is tied to Tier 2 (Urban) TMCs in Stockton and Fresno and Tier 3 Satellite Operation Centers in Redding and Kingvale.

Existing


Caltrans, District 4 Real-time traffic management of Bay Area freeways and bridges. Monitors traffic flow (detectors and video), processes data for incident info, distributes information to motorists (signs and radio), and adjusts ramp meters to balance flow. This Tier 1 TMC is tied to Tier 3 Satellite Operation Centers in Eureka and San Luis Obispo.

Existing


Caltrans, District 5 Caltrans District 5 TMC provides traffic management for the district including managing of field devices and coordination of incident management with CHP and other agencies.

Planned


Caltrans, District 6 Provides traffic management, incident management, and information dissemination for state owned roads in District 6. Located in Fresno.

Existing


Caltrans, District 7 Caltrans District 7 TMC is responsible for monitoring and managing real-time traffic conditions for the Los Angeles and Ventura county freeways. Center is located in downtown Los Angeles.

Existing


Caltrans, District 8 Caltrans and CHP jointly operate a TMC located in San Bernardino. There are plans to build a new joint Caltrans/CHP facility in Fontana within the next three to five years, which will operate 24/7 and be designed to operate as an emergency operations center in times of emergency.

Existing


Element Name Stakeholder Name Element Description Status Caltrans District 9 Transportation Management Center

Caltrans, District 9 Provides traffic management and incident management for state highways in district 9.

Existing

Caltrans District Maintenance Dispatch

Caltrans Represents maintenance asset dispatch at the district level. Existing

Caltrans District Pavement Management Systems

Caltrans District based collection of Pavement status information. Existing

Caltrans District Web pages Caltrans Represents web pages of each of the Caltrans districts. Existing Caltrans Field Equipment Caltrans CCTV, sensors, RWIS, signal controllers, etc. Existing Caltrans HQ Construction Program

Caltrans HQ This program is responsible for implementing the state's highway construction program. It will provide information to local districts about future construction projects as they are introduced.

Existing

Caltrans HQ Traffic Operations Databases

Caltrans HQ Database systems that collect and analyze weight in motion data and other traffic operations data.

Existing

Caltrans Maintenance Administration

Caltrans Represents the headquarters administrative functions for maintenance operations. Existing

Caltrans Performance Monitoring System (PeMS)

UC Berkeley The Freeway Performance Monitoring System (PeMS) is an Internet-based tool that can be used to monitor conditions on urban freeways. PeMS will allow users to produce congestion monitoring reports using automatically collected data from sensors statewide.

Existing

Caltrans Satellite TMCs Caltrans Satellite TMCs that operate in remote or outlying portions of a Caltrans District. Existing Caltrans Security Monitoring Equipment

Caltrans Caltrans field equipment used for security monitoring of transportation infrastructure (e.g. CCTV used for security, not for assessment of traffic conditions).

Planned

Caltrans Single-Trip Application and Routing System (STARS)

Caltrans The purpose of this project is to automate the application process for obtaining OS/OW permits for all applicants. This project has been partly implemented under the name STARS for high-volume permit users. This project would extend the STARS capability to all OS/OW permit applicants. Coupled with an on-line routing system, this would be an effective streamlining of the current process.

Existing

Caltrans Statewide Pavement Management System

Caltrans Statewide Pavement Management System for Caltrans roadway – currently investigating possibility of an upgrade.

Existing


Element Name Stakeholder Name Element Description Status Caltrans Weigh-In-Motion Stations

Caltrans Caltrans has deployed automatic high-speed weigh-in-motion (WIM) stations on mainline highway lanes throughout California. These planning and data collection stations capture vehicle classification and vehicle weight data continuously. They are distinct and separate from facilities at which commercial vehicle enforcement is conducted. The vehicle classification/weigh data is stored in a roadside controller which is periodically (often daily) polled by the Data Center in Sacramento. The Data Center retrieves and analyzes the data for anomalies, which fall outside of expected value boundaries. Fourteen of these planning/data surveillance sites gather data for the Strategic Highway Research Program (SHRP). Each high speed WIM Data Collection Systems includes equipment for collecting, processing, storing and transmitting data to Caltrans, Headquarters, Division of Traffic Operations. The data collected provides info related to counting, classifying and speed monitoring of all vehicles and the weighing of trucks and buses. This system allows for single threshold weighing and operates over a speed range of 0 to 100 mph.

Planned

Central California 511 Systems

Caltrans, Regional, and Local Stakeholders

Phone based traveler information systems in California accessible through the 3-digit 5-1-1 telephone number assigned to the transportation community by the FCC. The system is being implemented at the regional level as the urban metropolitan areas in California convert their existing traveler information systems or establish enhanced 511 services. MTC is operating 511 in the Bay Area. Los Angeles and greater Southern California, San Diego, and Sacramento are each progressing towards regional implementation. For the rural areas, Caltrans is taking the lead for 511 planning and deployment. As it evolves, 511 in California will likely have both statewide and local public sector components, as well as alternative potential private sector providers and/or stakeholders.

Existing

Central California Transit System Stations and Transfer Points

Central California Transit Agencies

Transit stations and transfer points of central California transit systems. Existing

Central California Transit Systems


Represents the dispatch and administration functions for transit agencies in Central California.

Existing

Central California Transit Vehicles


Transit vehicles of central California transit agencies. Existing

CHP Commercial Vehicle Section


Section of CHP responsible for commercial vehicle inspection and enforcement. Existing

CHP Dispatch Centers California Highway Patrol (CHP)

Represents the 22 separate dispatch centers throughout the state that are dispatching CHP vehicles.

Existing

CHP Weigh-In-Motion/ California Highway Patrol Weigh-in-Motion stations that are a part of inspection stations. The WIM Bypass Planned


Element Name Stakeholder Name Element Description Status Inspection stations (CHP) System is a high speed weigh in motion technology used in the PrePass operation,

which enables registered heavy vehicles to legally bypass open weigh stations after electronic verification of their size, weight, registration, safety inspection and other credentials. These stations reduce delay in the weight enforcement process and increase ability to provide highway truck statistics data.

Commercial Drivers License Information System (CDLIS)

FMCSA The nationwide driver's license system that the Federal Highway Administration (FHWA) has developed and issued standards for testing and licensing CMV drivers.

Existing

Commercial Vehicle Fleet Management

Private Carriers Provide for real-time communication for vehicle locating, dispatching, and tracking to reduce delays from congestion and incidents. Technology type unspecified may include GPS Tracking, AVL, cellular communications, dispatching software. Stakeholders include individual carriers.

Planned

Commercial Vehicles Private Carriers Commercial Vehicles operated by private commercial vehicle fleets. Existing Correctional Facility Operations

Correctional Facilities Operations centers at Federal, state, or local correctional facilities. Existing

County and Local Emergency Operation Centers

Local Government Represents emergency operations centers at the county and municipal level. Existing

County Maintenance Dispatch

County Public Works This includes public works or transportation departments for each of the 60 counties in the state.

Existing

County Public Safety Dispatch Centers

County Public Safety Agencies

This includes public safety dispatch and communications centers (police, fire, EMS) that operate at the county level throughout the state.

Existing

Credentials One Stop Shopping


Supports a commercial vehicle company interface for credentials. Supports connection between CVIEW and databases including IRP, IFTA, etc. Carriers will be supported by a web-based interface.

Existing

Customs Electronic Clearance Systems for International Borders

US Customs Systems to provide electronic clearance of commercial vehicles at the border with Mexico.

Planned

CVO ATIS Truckstop Kiosks Caltrans This project is described under the Southern California ITS Priority Corridor Strategic Deployment Guide. The portion of the project discussed in this document is region specific. FM subcarrier will be used to disseminate real-time information to commercial vehicles from the District 8 TMC. Kiosks located at four truckstops in the region will provide route and real-time traffic information. Among other interested parties and stakeholders are the I-5 Consortium Cities Joint Powers Authority (Santa Fe Springs, La Mirada, Downey, Buena Park, Commerce, and Norwalk) and the Ports of Los Angeles and Long Beach.

Planned

CVO Automatic Safety California Highway Patrol Rapid inspection via handheld units to download information directly from the vehicle. Planned


Element Name Stakeholder Name Element Description Status Inspection Devices (CHP) Technology type unspecified, may include handheld computers, information

exchange software, CVISN database, and automated analysis tools. CVO OS/OW Permitting Processing System

Caltrans Reduce permitting application, processing, and issuance delays for commercial vehicle operators. Reduce data collection errors, staff resources required, and cost of permit processing. Project is also described as a Caltrans statewide project.

Planned

CVO Pre-Pass Sites California Highway Patrol (CHP)

PrePass is a nationwide AVI system that allows participating transponder equipped CVO to bypass designated weigh stations and port-of entry facilities. California has 35 sites in northern, central, and southern parts of the state. Sites are at Antelope (northeast of Sacramento, CA)- I-80, Blythe (near CA/ AZ border)I-10, Cache Creek (east of Bakersfield, CA) CA-58, Cajon (north of San Bernardino, CA) I-15, Carson (north of Long Beach, CA) I-405, Castaic (north of Santa Clarita, CA) I-5, Chowchilla River (south of Modesto, CA) CA-99, Conejo (west of Thousand Oaks, CA) US101, Cordelia (north of Oakland, CA)I-80, Cottonwood (south of Redding, CA) I-5, Desert Hills (west of Palm Springs, CA) I-10, Dunsmuir Grade (north of Redding, CA) I-5, Gilroy (south of San Jose, CA)I-101, Grapevine (south of Bakersfield, CA)I-5, Livermore (east of Oakland, Ca)I-580, Mission Grade (northeast of Oakland, CA) I-680, Nimitz (east of Oakland, Ca) I-880, Otay Mesa (near US/Mexico border) S-905, Peralta Hwy (east of Anaheim, CA) I-91, Rainbow (south of Temecula, CA) I-15, San Onofre (north of Oceanside, CA) I-5, Santa Nella (east of San Jose, CA) I-5, and Truckee (near CA/NV border) I-80.

Existing

Excise Summary Terminal Activity Reporting System (ExSTARS)

Caltrans A fuel tracking system developed with the cooperation of the IRS, DOT, States and Motor Fuel Industry which details the movement of any liquid product into or out of an IRS approval terminal.

Existing

Hazmat Freight Containers Private Carriers Represents Hazmat containers that are instrumented for providing a spill notification. Planned Hazmat Permitting System California Highway Patrol

(CHP) System that provides information on Hazmat permits issued. Existing

IFTA Clearinghouse IFTA, Inc. This is a national clearinghouse designed to allocate fuel taxes between multiple states for motor carrier activities across jurisdictional lines, in accordance with the International Fuel Tax Agreement.

Existing

In Vehicle Electronic Toll Tags

Travelers Represents electronic toll tags used by the general traveling public in their vehicles. Existing

In Vehicle Equipment Travelers Represents ITS equipment inside vehicles. Existing Intermodal Port Facility Systems

Port Facilities Represents intermodal port facilities and the systems they use to track cargo and manage operations.

Planned

IRP Clearinghouse IRP, Inc. This is a registration reciprocity agreement among jurisdictions in the United States Existing


Element Name Stakeholder Name Element Description Status and Canada which provides for payment of license fees on the basis of fleet miles operated in various jurisdictions.

LAMTA Transit Station Equipment

Los Angeles County Metropolitan Transportation Authority

Represents the equipment (e.g. electronic payment equipment) at LAMTA transit stations.

Existing

LAMTA Vehicles Los Angeles County Metropolitan Transportation Authority

This element represents the LAMTA transit vehicles. Existing

Los Angeles County Metro – Bus Operations


Responsible for radio communications (voice and data) and real-time fleet management for 2400 revenue buses and 75 non-revenue vehicles.

Existing

Los Angeles County Metro – Rail Dispatch Center


The dispatch center for the rail operations is located in the City of Compton. Center is manned 24/7 by personnel. Responsible for rail transportation for the county. Majority of trains have SCADA system that allows center to "track" the train.

Existing

MCMIS FMCSA MCMIS contains information on the safety fitness of commercial motor carriers and hazardous material shippers subject to the Federal Motor Carrier Safety Regulations and the Hazardous Materials Regulations. This information is available to the general public through the MCMIS Data Dissemination Program.

Existing

Metrolink Administration Metrolink Rail Agency The administration function, including electronic fare payment reconciliation for Metrolink.

Existing

Metrolink Operations Center Metrolink Rail Agency Metrolink Operations Center is located in Pomona. Area of responsibility includes Los Angeles to Lancaster/San Bernardino/Riverside/San Diego/Oxnard. Operational responsibilities are to coordinate train movements in a safe and efficient manner.

Existing

Multi-Agency CVO Web-site California CVO Council The primary purpose of this project is to develop a way to use the Internet to make useful, up-to-date state CVO documentation, information, and a calendar of events widely available to motor carriers. The project would result in a multi-agency CVO Web site. Project benefits include: Better informed industry capable of making business decisions and providing information back to state agencies based on accurate, up-to-date information regarding CVO in California.

Planned

Municipal Maintenance Dispatch

Local Government Represents the maintenance dispatch function at the municipal level. Existing

Municipal Public Safety Dispatch

Municipal Public Safety Agencies

This includes public safety dispatch functions (police, fire, EMS) provided at the municipal level throughout the state. Also includes Public Safety Answering Points (PSAPs) at the municipal level.

Existing


Element Name Stakeholder Name Element Description Status Municipal/County Traffic Operations

Local Government Represents municipal traffic operations centers and traffic signal systems throughout the state.

Existing

National Weather Service National Weather Service Represents the NWS weather information provided to transportation agencies in the state.

Existing

Nevada DOT TMCs Nevada DOT Traffic Management Centers in Nevada (including one in Reno). Planned Northern California 511 Systems


Represents 511 implementations in Northern California, not including TravInfo®, which is described by a separate element.

Planned

Northern California Electronic Toll Collection Plazas

Northern California Toll Agencies

This element represents the electronic toll collection systems that operate at the toll collection plazas.

Existing

Northern California Electronic Toll Systems

Northern California Toll Agencies

This element represents the back end, or administrative systems of northern California electronic toll systems.

Existing

Northern California Transit System Stations and Transfer Points

Northern California Transit Agencies

Transit stations and transfer points of northern California transit systems. Existing

Northern California Transit Systems


Represents the dispatch function for transit agencies in Northern California other than BART, Caltrain, and SF MUNI, which are called out separately.

Existing

Northern California Transit Vehicles


Transit vehicles of northern California transit systems. Existing

Northern California Traveler Information Systems

Regional Planning Agencies Traveler information systems (public or private) operating throughout regions of Northern California.

Existing

ODOT Medford TOC Oregon Department of Transportation

The ODOT Transportation Operations Center in Medford plays a central role in the COATS architecture. It connects to centers in Bend and Salem and Caltrans centers in Eureka and Redding.

Existing

Operation Respond Operation Respond Institute Electronic link with 911 and participating carriers, provides real-time access emergency response units to hazardous material information.

Existing

Other Caltrans District Maintenance

Caltrans This element is used to create an interface from one Caltrans District Maintenance to another District Maintenance.

Existing

Other Caltrans Field Equipment

Caltrans Represents DMS, CCTV, signal controllers, field masters, etc. This element used to show interface between field devices.

Existing

Other CHP Dispatch Centers California Highway Patrol (CHP)

This element is used to create an interface from one CHP dispatch center to another. Existing

Other County Emergency Operation Centers

Local Government This element is used to create an interface from one county EOC to another county EOC.

Existing


Element Name Stakeholder Name Element Description Status Other County Public Safety Dispatch Centers

County Public Safety Agencies

This element is used to create an interface between peer county safety dispatch organizations that cross regional boundaries. The element represents public safety dispatch and communications centers (police, fire, EMS) that operate at the county level throughout the state. In addition, this element includes Fire Districts and Coast Guard. This also includes California Fish and Game, National Park Service, U.S. Fish and Wildlife and U.S. Forest Service.

Existing

Other States Credentials Admin and Safety Systems

Other States DOTs Credentials and safety inspection systems in other states. Existing

Other States Maintenance Dispatch Centers

Other States DOTs Maintenance Dispatch Centers in Oregon, Nevada, or Arizona. Existing

PeMS Users Archive Data Users Users of PeMS system outputs. Existing Private Application Service Providers

Private ASPs This element represents those organizations that provide traveler information to end users including telematics service providers such as ATX, OnStar, AAA, and Cross Country, Microsoft (http://autos.msn.com), Tribune Interactive, Cox Interactive, Iteris.

Existing

Private ISPs Private ISPs This "Information Service Provider" element represents those organizations that collect, process, and supply traffic data and traveler information to Application Service Providers (ASPs) who in turn provide the information to end users. ISPs include Tele Atlas and Westwood One, TANN, and Iteris. As an example of the configuration of these systems, Tele Atlas/Westwood One California operations centers are located in San Francisco, San Jose, Sacramento, Fresno, Los Angeles and San Diego. Each operations center covers a very large region. For example, the Los Angeles and San Diego centers cover all of Southern California. The Sacramento center covers from the Bay Area to Lake Tahoe and as far south as Merced.

Existing

Rail Operations Centers Private Rail Operators Represents the rail operations centers of freight railroads that operate in the state. Existing Regional Integration of ITS (RIITS)

Southern California Association of Governments (SCAG)

Southern California system for information sharing between operators (transit agencies, etc.) and between transportation operators (e.g., transit agencies) and other organizations (e.g., Information Service Providers). Also includes arterial data, Caltrans data, and CHP data. Other data sources will be added as they become available.

Existing

Regional Transit Information System (RTIS)

Metropolitan Transportation Commission (MTC)

Northern California (Bay Area) system for information sharing and transit coordination between transit systems.

Existing

Regional Traveler Information Systems

Regional Planning Agencies Represents traveler information systems (public or private) that operate within a region.

Existing

Safestat Database FMCSA SafeStat (short for Motor Carrier Safety Status Measurement System) is an Existing


Element Name Stakeholder Name Element Description Status automated, data driven analysis system designed by the Federal Motor Carrier Safety Administration (FMCSA). SafeStat combines current and historical carrier-based safety performance information to measure the relative (peer-to-peer) safety fitness of interstate commercial motor carriers and intrastate commercial motor carriers that transport hazardous materials.

Safety and Fitness Electronic Report (SAFER)

FMCSA SAFER provides carrier, vehicle, and driver safety and credential information to fixed and mobile roadside inspection stations. This information will allow the roadside inspector to select vehicles and/or drivers for inspection based on the number of prior carrier inspections, as well as carrier, vehicle, and driver safety and credential historical information.

Existing

Safetynet 2000 FMCSA Distributing system for managing safety data on both interstate and intrastate motor carriers for federal and state offices to electronically exchange data on interstate carriers with MCMIS (Motor Carrier Management Information System).

Existing

San Francisco MUNI Operations

San Francisco MUNI Scheduling/Auto-Dispatch System (an integrated, client-server based scheduling and dispatch system with, among many other features, the ability to perform traffic/ride check data collection); NextBus and Coordinate with BART (Deploys automated arrival info of next train arrival); AVL-GPS; Digital Voice Annunciation System (Allows announcements to be made automatically, without driver intervention).

Planned

Single State Registration System (SSRS)

California DMV Commercial vehicle registration system. Existing

Southern California Electronic Toll Collection Plazas

Southern California Toll System Agencies

This element represents the electronic toll collection systems that operate at the toll collection plazas.

Existing

Southern California Electronic Toll Systems

Southern California Toll System Agencies

This element represents the back end, or administrative systems southern California electronic toll systems.

Existing

Southern California Fare Card

Southern California Transit Agencies

Future electronic fare card used by southern California transit systems. Planned

Southern California Transit System Station and Transfer Points


Transit stations and transfer points of southern California transit systems. Existing

Southern California Transit Systems


Represents the dispatch function for transit agencies in Southern California other than LAMTA and Metrolink, which are called out separately.

Existing

Southern California Transit Vehicles


Transit vehicles of southern California transit systems. Existing

Southern California Traveler Regional Planning Agencies Includes 511 systems and other traveler information systems in the Southern Existing


Element Name Stakeholder Name Element Description Status Information Systems California area.

Special Police Force Dispatch

Special Police Police forces other than state, county or municipal. This element includes Fire Districts and Coast Guard. This also includes public safety or enforcement aspects of California Fish and Game, National Park Service, U.S. Fish and Wildlife and U.S. Forest Service.

Existing

State Parks and Recreational Area Information

BLM, Fish and Game, Parks and Recreation

This represents visitor information for the state parks, state recreation areas, and other state level tourist activities. This would include sites managed by Bureau of Land Management, California Parks and Recreation, Department of Fish and Game, Harbor Recreation and Conservation and various State Parks.

Existing

Statewide Integrated Reporting System (SWITRS)


The Accident Reporting System consists of two components working in conjunction to record and manage accident/crash reporting data. The server component resides on a central database server, which hosts numerous other applications/databases. All accident/crash data will be transported and entered into this server component. The client component is central to entering and maintaining the accident/crash data. Most likely, the client component will be a web client that interconnects to the server component via XML and other Internet related protocols and standards. Pertinent data will be exported or queried by other systems such as xCVIEW.

Planned

Telematics Service Provider Telematics Service Providers

Service centers that provide Mayday and other special concierge services for their clients. These centers will typically not be associated with a single county or district, but will interact with local agencies when their client's have an emergency in the region. Current examples of this system include the service centers operated by OnStar, ATX Technologies, and AAA.

Existing

Toll Road Transportation Management Centers

Toll Road Operators The element represents the traffic operations centers of toll roads throughout the state.

Existing

Transit Data Users Archive Data Users Users (and their systems) of transit archive data. Planned Translink Smartcard Metropolitan Transportation

Commission (MTC) Contactless smartcard system being used in Bay Area. Existing

TravInfo® Metropolitan Transportation Commission (MTC)

TravInfo® is a comprehensive system to gather, organize and disseminate timely information on San Francisco Bay Area traffic and road conditions, public transit routes and schedules, carpooling, highway construction and road closures, van and taxi service.

Existing

US BCBP Customs Product Manifest System

BCBP Would provide load manifest pre-clearance information to Electronic Screening stations. Information would be requested as needed (real-time), and requests for vehicle, carrier, and driver histories.

Planned

US BCBP Electronic BCBP Systems to provide electronic clearance of commercial vehicles at the border with Planned


Element Name Stakeholder Name Element Description Status Clearance System for International Borders

Mexico.

User Personal Computing Devices

Travelers User Personal Computing Devices refers to equipment an individual owns and can personalize with their choices for information about transportation networks. An Internet-connected PC is an example.

Existing

091783000 California ITS Architecture and System Plan Appendix A3 - User Services.doc 1 Appendix A3: User Services

APPENDIX A3: NATIONAL ITS ARCHITECTURE USER SERVICES

User Service Bundle User Service Scope

1.1 Pre-Trip Travel Information I/S 1.2 En-Route Driver Information I/S 1.3 Route Guidance P 1.4 Ride Matching and Reservation L 1.5 Traveler Services Information P 1.6 Traffic Control I/S/L 1.7 Incident Management I/S/L 1.8 Travel Demand Management L 1.9 Emissions Testing and Mitigation L

Travel and Traffic Management

1.10 Highway-Rail Intersection L 2.1 Public Transportation Management I/S/L 2.2 En-Route Transit Information I/L 2.3 Personalized Public Transit L

Public Transportation Management

2.4 Public Travel Security L Electronic Payment 3.1 Electronic Payment Services I/S/L

4.1 Commercial Vehicle Electronic Clearance S 4.2 Automated Roadside Safety Inspection S/P 4.3 On-Board Safety and Security Monitoring S/P 4.4 Commercial Vehicle Administrative Processes S/P 4.5 Hazardous Material Security and Incident Response S/P

Commercial Vehicle Operations

4.6 Freight Mobility P 5.1 Emergency Notification and Personal Security I/S/L/P5.2 Emergency Vehicle Management I/S/L Emergency Management 5.3 Disaster Response and Evacuation I/S 6.1 Longitudinal Collision Avoidance P 6.2 Lateral Collision Avoidance P 6.3 Intersection Collision Avoidance L/P 6.4 Vision Enhancement for Crash Avoidance P 6.5 Safety Readiness P 6.6 Pre-Crash Restraint Deployment P

Advanced Vehicle Safety

6.7 Automated Vehicle Operation P

Information Management 7.1 Archived Data Function I/S

Maintenance and Construction Management 8.1 Maintenance and Construction Operations I/S/L

091783000 California ITS Architecture and System Plan Appendix A3 - User Services.doc 2 Appendix A3: User Services

Legend S - State-level - The service contains functions or interfaces that are statewide in nature. This service is covered by this project. I - Interregional - The service contains functions or interfaces that are Interregional in nature. This service is covered by this project. L - Local - The service contains functions or interfaces that are entirely local to a single region. This service is not covered by this project. P - Private - The service is made up of functions or interfaces between private entities. This project will not cover the service. S/L - Statewide Standardization - Where both S and L are identified for a service, that indicates that the services that are local in nature, but which have interfaces that are candidates for standardization on a statewide basis. By statewide standardization we mean statewide use of common data, message, and communications standards for transmitting information on an interface. These interfaces most commonly represent candidates for statewide standardization by Caltrans.

091783000 California ITS Architecture and System Plan Appendix A4 - Market Packages.doc 1 Appendix A4: Market Packages

APPENDIX A4: NATIONAL ITS ARCHITECTURE MARKET PACKAGES Market Package Bundle Market Package Scope

AD1 ITS Data Mart S AD2 ITS Data Warehouse S Archived Data AD3 ITS Virtual Data Warehouse S/I APTS1 Transit Vehicle Tracking L APTS2 Transit Fixed-Route Operations L APTS3 Demand Response Transit Operations L APTS4 Transit Passenger and Fare Management S/I APTS5 Transit Security L APTS6 Transit Maintenance L APTS7 Multi-Modal Coordination I

Public Transportation

APTS8 Transit Traveler Information I ATIS1 Broadcast Traveler Information S/I ATIS2 Interactive Traveler Information S/I ATIS3 Autonomous Route Guidance P ATIS4 Dynamic Route Guidance P ATIS5 ISP Based Route Guidance P ATIS6 Integrated Transportation Management/Route Guidance P ATIS7 Yellow Pages and Reservation P ATIS8 Dynamic Ridesharing L

Traveler Information

ATIS9 In Vehicle Signing L ATMS01 Network Surveillance S/L ATMS02 Probe Surveillance L ATMS03 Surface Street Control L ATMS04 Freeway Control S/L ATMS05 HOV Lane Management L ATMS06 Traffic Information Dissemination S/L/I ATMS07 Regional Traffic Control S/L/I ATMS08 Traffic Incident Management System S/L/I ATMS09 Traffic Forecast and Demand Management L ATMS10 Electronic Toll Collection S/L/I ATMS11 Emissions Monitoring and Management L ATMS12 Virtual TMC and Smart Probe Data L ATMS13 Standard Railroad Grade Crossing L ATMS14 Advanced Railroad Grade Crossing L ATMS15 Railroad Operations Coordination L ATMS16 Parking Facility Management L ATMS17 Regional Parking Management L ATMS18 Reversible Lane Management L ATMS19 Speed Monitoring L ATMS20 Drawbridge Management L

Traffic Management

ATMS21 Roadway Closure Management S/L


Market Package Bundle Market Package Scope AVSS01 Vehicle Safety Monitoring P AVSS02 Driver Safety Monitoring P AVSS03 Longitudinal Safety Warning P AVSS04 Lateral Safety Warning P AVSS05 Intersection Safety Warning P AVSS06 Pre-Crash Restraint Deployment P AVSS07 Driver Visibility Improvement P AVSS08 Advanced Vehicle Longitudinal Control P AVSS09 Advanced Vehicle Lateral Control P AVSS10 Intersection Collision Avoidance L/P

Vehicle Safety

AVSS11 Automated Highway System P MC01 Maintenance and Construction Vehicle and Equipment Tracking L MC02 Maintenance and Construction Vehicle Maintenance L MC03 Road Weather Data Collection S/L MC04 Weather Information Processing and Distribution L/I MC05 Roadway Automated Treatment L MC06 Winter Maintenance I MC07 Roadway Maintenance and Construction S/L MC08 Work Zone Management S/L/I MC09 Work Zone Safety Monitoring L

Maintenance and Construction

MC10 Maintenance and Construction Activity Coordination I CVO01 Fleet Administration P CVO02 Freight Administration P CVO03 Electronic Clearance S/P CVO04 CV Administrative Processes S/P CVO05 International Border Electronic Clearance S/P CVO06 Weigh-In-Motion S/P CVO07 Roadside CVO Safety S/P CVO8 On-board CVO and Freight Safety and Security S/P CVO9 CVO Fleet Maintenance P CVO10 HAZMAT Management S CVO11 Roadside HAZMAT Security Detection and Mitigation S CVO12 CV Driver Security Authentication P

Commercial Vehicle Operations

CVO13 Freight Assignment Tracking P EM01 Emergency Call-Taking and Dispatch S/L/I EM02 Emergency Routing S/L EM03 Mayday Support I/P EM04 Roadway Service Patrols L EM05 Transportation Infrastructure Protection S/L/I EM06 Wider-Area Alert S/I EM07 Early Warning System S/I EM08 Disaster Response and Recover S/I EM09 Evacuation and Reentry Management S/I

Emergency Management

EM10 Disaster Traveler Information S/I


Legend S - State-level - The service contains functions or interfaces that are statewide in nature. This service is covered by this project. I - Interregional - The service contains functions or interfaces that are Interregional in nature. This service is covered by this project. L - Local - The service contains functions or interfaces that are entirely local to a single region. This service is not covered by this project. P - Private - The service is made up of functions or interfaces between private entities. This project will not cover the service. S/L - Statewide Standardization - Where both S and L are identified for a service, that indicates that the services that are local in nature, but which have interfaces that are candidates for standardization on a statewide basis. By statewide standardization we mean statewide use of common data, message, and communications standards for transmitting information on an interface. These interfaces most commonly represent candidates for statewide standardization by Caltrans.

091783000 California ITS Architecture and System Plan Appendix A5 - AC Stakeholders.doc 1 Appendix A5: Advisory Committee Stakeholder Agencies

APPENDIX A5: ADVISORY COMMITTEE STAKEHOLDER AGENCIES

Alameda County Congestion Management Association

Alpine County Local Transportation Commission

Amador County Transportation Commission

Association of Monterey Bay Area Governments

Automobile Club of Southern California

Business, Transportation and Health Agency

Butte County Association of Governments

Calavaras Council of Governments

California Department of Finance

California Department of Transportation

California Highway Patrol

Center for Commercialization of Intelligent Transportation Systems Technologies

City/County Association of Governments of San Mateo County

Colusa County Transportation Commission

Contra Costa Transportation Authority

Council of Fresno County Governments

Council of San Benito County of Governments

Del Norte Local Transportation Commission

El Dorado County Transportation Commission

Federal Highway Administration

Glenn County Transportation Commission

Humboldt County Association of Governments

Imperial Valley Association of Governments

Inyo County Local Transportation Commission

Kern Council of Governments

Kings County Association of Governments

Lassen County Transportation Commission

League of California Cities (City of Stockton)

Legislative Analyst's Office

Los Angeles Metropolitan Transportation Authority

Marin Public Works/Congestion Management Agency

Mariposa County Transportation Commission

Mendocino Council of Governments

Metropolitan Transportation Authority

Merced County Association of Governments

Metropolitan Transportation Commission

Modoc County Local Transportation Commission

Mono County Local Transportation Commission

Napa County Transportation Planning Agency

Orange County Transportation Authority

Placer County Transportation Planning Agency

Plumas County Transportation Commission

Riverside County Transportation Commission

Rural Counties Task Force

Sacramento Area Council of Governments

San Bernardino Associated Governments

San Diego Association of Governments

San Francisco Transportation Authority

San Joaquin Council of Governments

San Luis Obispo Council of Governments

Santa Barbara County Association of Governments

Santa Clara Valley Transportation Authority

Shasta County Regional Transportation Planning Agency

Sierra Club

Sierra County Local Transportation Commission

Siskiyou County Transportation Commission

Solano County Transportation Authority

Sonoma County Transportation Authority

Southern California Association of Governments

Stanislaus Council of Governments

Tahoe Regional Planning Agency

Tehama County Transportation Commission

Transportation Agency for Monterey County

Trinity County Transportation Commission

Tulare County Association of Governments

Ventura County Transportation Commission

Westwood One

Yolo Transportation District

Yuma Metropolitan Planning Organization

091783000 California ITS Architecture and System Plan Appendix A6 - Operations Concept.doc 1 Appendix A6: Operational Concepts by Service Category

APPENDIX A6: OPERATIONAL CONCEPTS BY SERVICE CATEGORY

Traffic Management Traveler Information Goods Movement Electronic Payment Toll Collection Fare Payment Public Transportation State-Level Archived Data Maintenance and Construction Management Vehicle Safety and Control Emergency Management


Operational Concepts for Traffic Management

User Service Organization Roles and Responsibilities Traffic Control (I)

Caltrans Headquarters

(Current) Establish statewide policies for traffic management, including coordination with other agencies.

(Current) Fund traffic control programs (includes funds through State Highway Operation and Protection Program (SHOPP)).

(Current) Establish cooperative agreements for inter-regional traffic management.

(Current) Establish statewide criteria for communication, data collection, and data exchange among agencies for traffic management purposes.

(Current and Proposed) Ensure security around key transportation infrastructure throughout the state.

(Current) Facilitate sharing of real-time traffic information with local jurisdictions and other agencies.

Traffic Control (I) (continued)

Caltrans Districts (Current) Lead role in implementation, operation and maintenance of traffic control on state freeways and rural state highways.

(Current) Share real-time traffic information and traffic control actions with other agencies.

(Current) Provide real time traffic information on state freeways. Obtain cooperation from other parties, such as media, to expand the information sources on traffic conditions for use in traffic management.

(Current) Implement and operate HOV lanes on freeways, in partnership with regional agencies.

(Current) Implement and operate traffic control under adverse weather conditions, such as fog, snow.

(Current) Provide aid to CHP (such as incident information or traffic control).

(Current) Establish cooperative agreements for local and regional traffic management.

(Current) Implement and operate compatible data (includes video) exchange and communication with local agencies for regional traffic management.

(Current) Implement and operate surveillance equipment on state freeways, and share video images with other agencies, such as local counties and cities.

(Current) Implement and operate road closures under adverse weather conditions, such as fog or snow.

(Current) Develop and maintain regional database of road closures due to constructions or other events.


Operational Concepts for Traffic Management (continued)

User Service Organization Roles and Responsibilities CHP (Current) Direct traffic at incident scenes.

(Current) Enforce traffic violations on state freeways. (Current) Implement road closures under heavy traffic or

extreme adverse weather conditions, such as tulle fog, heavy snow.

(Current) Assist Caltrans with en-route driver information such as inclement weather closures.

(Current) Request lifting of lane closures or opening HOV lanes to single occupant vehicles to increase traffic flows during major incidents.

Regional agencies (Current) Implement traffic control for its regions. (Current) Reduce emissions within their regions through

reduced congestion. (Current) Implement and operate HOV lanes on freeways, in

partnership with Caltrans.

Traffic Control (I) (continued)

Local agencies (Current) Implement and operate traffic control on surface streets to reduce recurrent congestion on interregional arterials.

(Current and Proposed) Share real-time traffic information and traffic control actions with Caltrans and adjacent jurisdictions for traffic management purposes.

(Current and Proposed) Implement and operate traffic control and surveillance equipment on surface streets, and sharing of video images with Caltrans and other agencies.

Incident Management (I)


(Current) Establish statewide policies on incident management, including institutional relationships with other agencies.

(Current) Handle major incidents that affect inter-urban travel, such as disaster evacuation. Assume a lead role in developing evacuation plans for various regions in the state, with input and cooperation from the local districts, counties, cities, CHP and MPOs.

(Proposed) Establish cooperative agreements for inter-regional disaster evacuation. Caltrans currently leads or participates in several regional disaster response efforts.

(Proposed) Improve hazardous material movement information management in cooperation with the CHP.

(Current) Coordinate Statewide Hazardous Materials (HAZMAT) transportation routes and procedures, including:

– Load restrictions

– Load securement requirements

– Safety requirements


Operational Concepts for Traffic Management (continued)

User Service Organization Roles and Responsibilities Caltrans Districts (Current) Assume a lead role in traffic diversion and

implementation of traffic management schemes for incidents on state freeways.

(Current) Integrate various incident detection sources into regional incident databases for more timely accident and incident identification.

(Current) Implement and operate road closures on state freeways and state highways under adverse weather conditions, such as fog, snow. Provide weather conditions and forecasts to travelers.

(Current) Implement and operate planned road closures on freeways and state highways. Provide advanced information to travelers.

(Current) Establish or participate in cooperative agreements for local and regional incident management.

CHP (Current) Assume a lead role in handling and clearance of incidents on state freeways.

(Current) Assist Caltrans in integrating various incident detection sources into regional incident databases for dissemination to travelers.

(Proposed) Improve hazardous material movement information management in cooperation with Caltrans.

(Current) Provide real-time incident information to Caltrans relating to state freeways and rural state highways.

Local Police Depts. (Current) Assume a lead role in handling and clearance of incidents on interregional surface streets.

Regional agencies (Current) Implement incident management programs. Local agencies (Current) Assume lead roles in traffic management for

incidents on interregional surface streets.

Incident Management (I) (continued)

Service Authority for Freeway Emergencies (SAFE)

(Current) Implement call-box programs on freeways and highways (possibly including free cellular phone programs for motorists with mobility impairments). Implement service patrols.


Operational Concepts for Traveler Information

User Service Organization Roles and Responsibilities Caltrans Headquarters

(Current) Fund inter-regional and statewide traveler information programs.

(Current) Data fusion of regional and statewide traveler information on state freeways and rural state highways.

(Current) Develop and maintain statewide database of road closures due to constructions or other events.

(Current) Establish communications and data exchange criteria for statewide use.

(Proposed) Establish and implement statewide traveler information strategy for truckers and frequent inter-regional travelers.

Caltrans Districts (Current) Assume a lead role in implementation, operation and maintenance of pre-trip travel information relating to conditions of state freeways and rural state highways.

(Current) Obtain cooperation from other parties, such as media, to expand the information sources on traffic conditions for traveler information.

(Current) Implement and operate traffic advisories under adverse weather conditions, such as fog or snow.

(Current) Provide weather conditions and forecasts to travelers.

(Proposed) Inventory/disseminate data from additional sources (for example, using AVL data from buses),

Pre-trip travel information (IR)

Regional Agencies (Current and Proposed) Fund and implement traveler information for its regions.

(Current and Proposed) Monitor effectiveness of pre-trip traveler information as perceived by users and transportation agencies. Track usage statistics to assess market penetration of the traveler information system(s), and to direct marketing efforts. Survey users for suggestions and improvements.

Local/ regional agencies

(Current and Proposed) Implement and operate traveler information within its jurisdiction.

Pre-trip travel information (IR) (continued)

Media, ISP and other private sector partners

(Current) Independently implement and operate helicopter patrols and other means to obtain real-time traveler information.

(Current) Share traveler information with public agencies. (Current) Disseminate traveler information through various

means.


Operational Concepts for Traveler Information (continued)

User Service Organization Roles and Responsibilities En-route Driver Information (IR)


(Proposed) Fund inter-regional and statewide en-route driver information programs.

(Current) Facilitate sharing of real-time en-route driver information with private sector.

(Current and Proposed) Data fusion of regional and statewide traveler information on state freeways and rural state highways.

(Current) Establish communications and data exchange standards for statewide use for traveler information purposes.

(Proposed) Establish and implement statewide traveler information strategy for truckers and frequent inter-regional travelers.

Caltrans Districts (Current) Assume a lead role in implementation, operation and maintenance of en-route driver information relating to conditions of state freeways and rural state highways.

(Current) Obtain cooperation from other parties, such as media, to expand the information sources and dissemination means of en-route driver information.

(Current) Implement and operate en-route traffic advisories and/or road closures under adverse weather conditions, such as fog or snow.

(Proposed) Inventory/disseminate data from additional sources (for example, using AVL data from buses),

Regional Agencies (Current and Proposed) Fund and implement en-route driver information for its regions.

(Current and Proposed) Monitor effectiveness of en-route traveler information as perceived by users and transportation agencies. Track usage statistics to assess market penetration of the traveler information system(s), and to direct marketing efforts. Survey users for suggestions and improvements.

Local agencies (Current and Proposed) Implement and operate en-route driver information within its jurisdiction.

Provide real time traffic information on surface streets to public.

En-route Driver Information (IR) (continued)

Media, ISP and other private sector partners

(Current) Independently implement and operate en-route driver information systems.

(Current) Share en-route driver information with public agencies.


Operational Concepts for Goods Movement

User Service Organization Roles and Responsibilities Federal (Current) Establish commercial vehicle and carrier

regulations. National, interstate and intrastate regulations are adopted and enforced by California state regulatory agencies. (Many state regulatory agencies then develop, adopt and enforce additional regulations as described below).

(Current) Provide resources to state and local agencies in national and international goods movement tracking, regulations, and data sharing.

(Current) In cooperation with the International Registration Plan, Inc., (IRP) Clearinghouse, administer the electronic clearinghouse for jurisdictions in the US and Canada which provides for payment of license fees on the basis of fleet miles operated in various jurisdictions.

(Current) Administer the International Fuel Tax Agreement (IFTA) Clearinghouse, which is a national clearinghouse to allocate fuel taxes between multiple states for motor carrier activities across jurisdictional lines.

Commercial Vehicle Electronic Clearance (S)

California CVO Council (supported by the Inter-Agency Coordination Task Force)

(Current) Provide guidance for statewide CVO (commercial vehicle operation) activities. Coordination will be supported by the Inter-agency Coordination Task Force (ICTF), consisting of the following agencies:

– Caltrans

– Department of Motor Vehicles (DMV)

– California Highway Patrol (CHP)

– Board of Equalization (BOE)

Additional agencies on the council include:

– California Trucking Association

– National Private Truck Council

– United Highway Carriers Association


Operational Concepts for Goods Movement (continued)

User Service Organization Roles and Responsibilities Commercial Vehicle Electronic Clearance (S) (continued)

CHP (Current) Review and adopt interstate and intrastate federal regulations pertaining to loading, load securement, and size requirements, for materials other than household goods. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to loading, load securement and size.

(Proposed) Help lead efforts for statewide coordination of data and regulatory activities for goods movement.

(Current) Develop educational materials and deliver courses to inform shippers, drivers, and carriers about clearance requirements. For example, current educational programs include seminars on size and weight guidelines.

(Current) Issue oversize/overweight (OS/OW) permits. (Current) Operate statewide Commercial Vehicle

Enforcement Facilities (Weigh Stations or Truck Scales). (Current) Develop and implement operational improvements

to reduce clearance times at weigh stations, inspection stations, and borders.

(Current) Maintain a driver log containing profile data for enforcement purposes.

(Proposed) Provide one stop or no stop credential services to Commercial Vehicle carriers.

(Current) Facilitate electronic collection of inspection data and electronically forward to a CHP headquarters database and then to SAFETYNET, a federal commercial vehicle information system database.

(Proposed) Implement and operate Electronic Clearance Systems for International Borders, in cooperation with Customs Office of INS.

(Proposed) Test and expand use of the automated citation writing devices that use digitized driver’s license data at fixed and mobile commercial vehicle inspection facilities.




(Current) Establish statewide design standards for weigh stations, inspection stations, and borders.

(Proposed) Promote safety through statewide driver education.

(Proposed) Provide traveler information for drivers and carriers.


(Proposed) Coordinate with adjoining states to link regulatory, traveler information, and data exchange systems in line with federal and national initiatives and guidelines.

(Current) Maintain updated map and listing of statewide Commercial Vehicle Enforcement Facilities (Weigh Stations or Truck Scales) and Mainline Bypass Systems (PrePass™ locations).

(Current) Operate Weigh-in-Motion systems which collect real-time vehicle data such as axle and gross weight, axle spacing (for vehicle classification), and speeds, 24 hours a day. As of 2003 there are 85 Weigh-in-Motion locations across the state.

(Current) Operate PrePassTM, California’s automated preclearance system which uses transponder technology to verify weight, size and safety requirement adherence. As of 2003 there are 35 PrePassTM locations throughout the state.

(Current) Maintain and disseminate data regarding the state highway network and vehicle restrictions on various highways.

(Current) Conduct and support research on goods movement impacts and trends statewide. Facilitate inter-agency communications and agreements regarding action plans and alternatives.

(Proposed) Support an intermodal information system. Distribute or provide real-time information regarding the status of operations at the Mexican border, and at intermodal shipping ports.

Promote the ability to use a standard transponder technology for any activity that uses Automatic Vehicle Identification.

Commercial Vehicle Electronic Clearance (S) (continued)

Caltrans Districts (Current) Promote inter-agency communications for Commercial Vehicle electronic clearance on local level.

(Current ) Design and build infrastructure to improve clearance times at weigh stations, inspection stations, and borders.



User Service Organization Roles and Responsibilities DMV (Current) Review and adopt federal regulations pertaining to

registration, permits and licenses. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to registration, permits and licenses.


(Current) Issue photo identification licenses and maintain database of drivers.

(Current) Administer the Employee Pull Notice (EPN) Program, which maintains driver’s license records and continually checks for specified “action/’activity” violations such as accidents, convictions, or any other actions taken against the driving privilege. If any of these action/activities occur for that specified employer, a record is generated and mailed to that employer. The data is privacy protected; after the employer is notified under the EPN program, the data is destroyed. Furthermore, the data cannot be combined with any other information.

California Public Utilities Commission

(Current) Review and adopt any federal regulations pertaining to transport of household goods. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to transport of household goods.

(Current) Issue licenses for household goods carriers upon verification of adherence to financial and safety requirements.

Commercial Vehicle Electronic Clearance (S) (continued)

Local and regional public stakeholders (e.g., Ports)

(Proposed) Coordinate with other local, regional, and state-level agencies to link regulatory, traveler information, and data exchange systems.

Automated Roadside Safety Inspection (S)



– Caltrans







– United Highway Carriers Association



User Service Organization Roles and Responsibilities Commercial Vehicle Carriers and Fleet Managers

(Current) Partner with government agencies (including Caltrans) to develop and deploy advanced technology systems to create a cooperative operating and regulatory environment which improves the efficient and safe movement of commercial vehicles and the performance of highway systems.

CHP (Current) Review and adopt interstate and intrastate federal regulations pertaining to loading, load securement, size, safety and hazardous materials requirements, for materials other than household goods. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to loading, load securement, size, safety and hazardous materials.

(Current) Develop educational materials and deliver courses to inform shippers, drivers, and carriers about safety in goods transportation and at terminals. For example, current educational programs include vehicle and carrier inspection requirements, HAZMAT transportation requirements, rules of the road, and licensing requirements.

(Current) Lead roadside safety inspection operations. (Current) Operate weigh stations. (Current) Provide and automate carrier, vehicle, and driver

safety and credential information to fixed and mobile roadside inspection stations.

(Current) Promote inter-agency communications for Commercial Vehicle automated roadside safety inspection on statewide and local levels.

(Current) Provide current information to roadside enforcement officers.

(Current) Implement operational improvements to reduce clearance times at roadside safety inspection stations.

(Current) Establish connectivity with electronic screening system providers for the purpose of facilitating the efficient movement of commercial vehicles though inspection facilities.

(Proposed) Provide a means for linking carrier safety performance with the vehicle registration process, in cooperation with the DMV.

Automated Roadside Safety Inspection (S) (continued)


(Current) Establish statewide standards for infrastructure design of roadside safety inspection sites.

(Current) Promote inter-agency communications for Commercial Vehicle automated roadside safety inspection on statewide level.



User Service Organization Roles and Responsibilities Automated Roadside Safety Inspection (S) (continued)

Air Resources Board

(Current) Review and adopt federal regulations pertaining to exhaust emission requirements and motor vehicle emissions control devices. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to exhaust emission requirements and motor vehicle emissions control devices.



– Caltrans







– United Highway Carriers Association Caltrans Districts (Current) Lead the infrastructure design of roadside safety

inspection sites. (Current) Promote inter-agency communications for

Commercial Vehicle automated roadside safety inspection on a local level.

(Current) Design and build infrastructure to improve clearance times at roadside safety inspection stations.

(Current) Design and build weigh stations and weigh-in-motion stations.

CHP (Current) Lead on-board safety monitoring of Commercial Vehicles statewide.

(Current) Promote inter-agency communications for Commercial Vehicle on-board safety monitoring on statewide and local levels.

(Current) Implement and operate automatic safety inspection devices.

DMV (Current) Establish regulations to enhance on-board safety monitoring.

On-board Safety Monitoring (S)


(Proposed) Promote inter-agency communications for Commercial Vehicle on-board safety monitoring on statewide level.



User Service Organization Roles and Responsibilities Air Resources Board

(Current) Review and adopt federal regulations pertaining to exhaust emission requirements and motor vehicle emissions control devices. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to exhaust emission requirements and motor vehicle emissions control devices.

On-board Safety Monitoring (S) (continued)

Commercial Vehicle Carriers and Fleet Managers

(Current) Implement on-board monitoring systems that provide the sensory, processing, storage, and communications functions necessary to support safe and efficient commercial vehicle operations. Such systems will also provide two-way communications between the commercial vehicle drivers, their fleet managers, and roadside officials; and provide HAZMAT response teams with timely and accurate cargo contents information after a vehicle incident.



– Caltrans







– United Highway Carriers Association Caltrans Headquarters

(Current) Facilitate cooperative agreements for Commercial Vehicle administrative processes.

(Current) Promote inter-agency communications for Commercial Vehicle administrative processes on statewide level.

(Current) Streamline regulations for commercial vehicles. (Current) Establish statewide regulations and restrictions for

oversize and overweight vehicles. (Current) Obtain updated information related to counting,

classifying and speed monitoring of all vehicles and the weighing of trucks and buses at weigh-in-motion sites throughout the state.

Commercial Vehicle Administrative Processes (S)

Caltrans Districts (Current) Process oversize and overweight (OS/OW) vehicle permits.



User Service Organization Roles and Responsibilities CHP (Current) Facilitate cooperative agreements for Commercial

Vehicle administrative processes. (Current) Promote inter-agency communications for

Commercial Vehicle administrative processes on statewide level.

(Current) Review, adopt and enforce pertinent federal regulations pertaining to loading, load securement, size and safety requirements for materials other than household goods. Develop, adopt and enforce state-level regulations as needed. State-level regulations usually expand upon federal regulations in the above areas.

(Current) Issue Carrier Identification Numbers as part of the requirements for a Motor Carrier Permit (MCP), for carriers other than household goods carriers (household goods carriers are regulated by the California Public Utilities Commission). The MCP program is administered jointly by the DMV.

(Current) Enforce compliance with Motor Carrier Property Permit regulations.

(Current) Maintain a driver log containing profile data for enforcement purposes.

DMV (Current) Issue Motor Carrier Permits (MCPs) for carriers other than household goods carriers (household goods carriers are regulated by the California Public Utilities Commission). An MCP grants the carrier authority to commercially operate motor vehicles on California Highways. The MCP program is administered jointly with the CHP.

(Current) Administer applicable fees for truck weight requirements.

(Proposed) Develop a direct electronic interface with insurance companies for exchange of insurance and safety status.

California Board of Equalization

(Current) Administer fuel tax programs.

Commercial Vehicle Administrative Processes (S) (continued)

California Public Utilities Commission

(Current) Issue licenses for household goods carriers upon verification of adherence to financial and safety requirements.



User Service Organization Roles and Responsibilities California CVO Council (supported by the Inter-Agency Coordination Task Force)


– Caltrans







– United Highway Carriers Association Commercial Vehicle Carriers and Fleet Managers

(Current) Facilitate cooperative agreements for Commercial Vehicle administrative processes.

Federal (Current) Establish commercial vehicle regulations.

Hazardous Material Incident Response (S)

CHP (Current) Lead HAZMAT Incident response efforts by assuming the role of scene commander. Coordinate with Caltrans Maintenance personnel and Traffic personnel for cleanup and traveler information dissemination.

(Current) Review and adopt interstate and intrastate federal regulations pertaining to hazardous materials requirements. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to hazardous materials.

(Current) Develop educational materials and deliver courses to inform shippers, drivers, and carriers about safety and security of HAZMAT transport. For example, current educational programs recommend photo and electronic identification programs, security training for personnel, and the use of Global Positioning Systems (GPS) to track HAZMAT loads where possible.

(Current) Enforcement of HAZMAT routes. (Current) Obtain up-to-date information on the safety fitness

of commercial motor carriers and hazardous material shippers subject to the Federal Motor Carrier Safety Regulations and the Hazardous Materials Regulations.

(Current) Enforce HAZMAT regulations for commercial vehicles.

(Proposed) Coordinate and share HAZMAT information with adjoining states.




(Current) Develop statewide HAZMAT incident evacuation routes.

Caltrans Districts (Current) Implement HAZMAT diversion routes. (Current) Assist CHP to expedite HAZMAT incident

response. (Proposed) Provide information relating to HAZMAT

incidents on state freeways to public. Local and Regional Agencies

(Proposed) Provide information relating to HAZMAT incidents on arterials and surface streets to public.

DMV (Current) Establish HAZMAT regulations while meeting up-to-date Federal guidelines.

Hazardous Material Incident Response (S) (continued)

California Environmental Protection Agency, Division of Toxic Substances Control

(Current) Issue registrations for all HAZMAT carriers operating within California. HAZMAT carriers must comply with the CHP and Federal (US DOT) regulations.

(Current) Maintain searchable database of registered HAZMAT carriers.


Operational Concepts for Electronic Toll Collection

User Service Organization Roles and Responsibilities California State Legislature

(Current) Mandate toll agencies’ adherence to statewide standard for Electronic Toll Collection.

(Current) Mandate that toll agencies participate in a data registration process with the State. The “data” in data registration refers to record types which may be developed for future applications of the toll transponder technology. Unique data types would facilitate interregional interoperability of ETC equipment. Currently registered data types include codes for readers polling transponders, and codes for transponders sending data to readers. Future data types depend on desired applications of the transponder technology (for example, data pertaining to travel times or vehicle locations, or data pertaining to non-transportation applications such as retail transactions).

(Proposed) Mandate one non-proprietary standard for all forms of electronic payment (toll and transit, or at least one standard for tolls, and one standard for transit).

Electronic Payment Services (S)

Caltrans

(Current) Developed Title 21, the standard for two way communications for Automatic Vehicle Identification (AVI) equipment. Electronic Toll Collection is the first application for which the standard was developed.

(Current) Act as Title 21 Standard monitoring authority; maintain and update standard as necessary.

(Current) Administer data registration process for standard; authorize use of new data record types.

(Current) Identify and support innovative (transportation-related) applications of anonymous toll user data using the same or an interoperable technology. For example, the transponder reader technology is being tested in the Bay Area to provide motorist travel times from different origins and destinations.

(Proposed) Respond to inquiries from potential toll agencies and vendors regarding interoperability of equipment.

Electronic Payment Services (S) (continued)

Caltrans (continued)

(Proposed) As the Title 21 standard matures, ensure that new toll agencies and vendors are aware of the data registration process.

(Proposed) As technologies mature, if a new and separate standards setting organization is established, pass Caltrans’ role as standards monitoring authority to this new organization.

(Current) Facilitate inter-agency communication between toll operating agencies.

(Current) Monitor and publicize projects on which toll revenues are spent. Provide information on percentage of project financed with tolls, and time period over which financing occurs.


Operational Concepts for Electronic Toll Collection (continued)

User Service Organization Roles and Responsibilities Electronic Payment Services (S, I)

Local Toll Operating Agencies currently include: Caltrans, Orange County

Transportation Authority,

Transportation Corridor Agencies,

San Diego Association of Governments, and

Golden Gate Bridge, Highway and Transportation District

(Current) “Local” responsibilities will remain with these agencies. These roles and responsibilities are described by regional architectures and are not carried forward by the California Statewide ITS Architecture and System Plan project. “Local” roles and responsibilities include examples such as:

– Operate and maintain local toll collection on respective agency-owned facility/facilities.

– Define fare structures. – Select and implement technologies and policies

regarding toll evasion (for example, video capture of license plate information).

– Identify and process toll violations. – Provide anonymous toll usage data to support other

agency planning or operations (i.e., travel times). – Other local roles and responsibilities for operations and

implementation. Some or all of these responsibilities could be consolidated among the local agencies, in the form of consolidated service centers, consolidated transponder procurements, or a consolidated electronic clearinghouse provider.

(Current) Support standards allowing interoperability of FasTrakTM on facilities throughout the state.

(Current) Develop policies pertaining to transponder distribution, and user payment schemes (for interoperability of transponders among toll facilities).

Electronic Payment Services (S, I) (continued)

Local Toll Operating Agencies (continued)

(Proposed) Support continuing investigations and research into other payment applications using the same or an interoperable technology (for example, using transponders to pay for gas, or to pay for food purchases at drive-through restaurants).

(Current) Support continuing investigations and research into other (non-payment) applications using the same or an interoperable technology. For example, the transponder reader technology is being tested in the Bay Area to provide motorist travel times from different origins and destinations.


Operational Concepts for Electronic Fare Payment

User Service Organization Roles and Responsibilities Regional agencies (Current) Facilitate inter-agency partnerships. Provide a

possible forum in which to address any points of disagreement among the agencies or between the agencies and users or potential users.

(Current) Develop inter-agency participation agreements or Memoranda of Understanding (MOUs) pertaining to agency responsibilities and administrative duties.

(Current) Disseminate information to passengers regarding electronic payment structure and benefits. Provide details about coverage area. Publicize purchase locations and website.

Electronic Payment Services (I)

Local and Regional Transit Agencies

(Current) Ensure continued interoperability of equipment for multi-agency electronic fare payment (including vending machines and card readers).

(Current) Disseminate information to passengers regarding multi-agency electronic payment systems and benefits.

(Proposed) Maintain and provide anonymous ridership data for operational planning and analysis.

Private Industry (Current) Continue to research and develop integrated solutions for transit and other financial applications, adhering to statewide and national standards as they develop to ensure interoperability.

Electronic Payment Services (S,I)

Caltrans (Proposed) Mandate one non-proprietary standard for all forms of electronic payment (toll and transit, or at least one standard for tolls, and one standard for transit).


Operational Concepts for Public Transportation

User Service Organization Roles and Responsibilities Public Utilities Commission

(Current) Provide statewide safety design standards for light-rail/road and rail/road interface to reduce accidents, while utilizing ITS technologies.

(Current) Regulate Amtrak California, inter-regional rail travel provided by Amtrak.

State of California (Current) Provide funding for Amtrak California, inter-regional rail travel provided by Amtrak.

(Proposed) Develop statewide disaster evacuation plans utilizing public transit.

Local transit agencies

(Current and Proposed) Provide inter-modal interchanges for inter-regional travelers.

Public Transportation Management (L and I)

Inter-regional transit providers

(Current and Proposed) Promote reliability of inter-regional service

(Current and Proposed) Provide interface with regional transit services

(Current and Proposed) Promote travelers’ security State of California (Current and Proposed) Facilitate inter-modal transit

information sharing among regions to form a statewide database.

En-route Transit Information (L and I)

Local transit agencies

(Current and Proposed) Provide inter-modal transit information across different providers.


Operational Concepts for State-level Archived Data

User Service Organization Roles and Responsibilities Caltrans (Current role) Collect data from Caltrans roads (state

freeways and state highways statewide) [this is a transportation management role necessary to archive data].

Archive state data on a statewide basis. (Current role) Provide archived data to PeMS. Collect and archive data from additional sources such as

other archived data services, CHP, CVISN, PeMS, local and regional agencies (as desired by those agencies), and others.

Clearly define requirements for data for measurement standards, frequency of updates, data fusion and aggregation, presentation (graphical user interface), accessibility of data, and duration of storage for state level data.

Clearly define performance measurements for quality, quantity, and timeliness of data updates.

Provide access to archived data. Maintain operations of statewide archived data system. Publicize locations of information and instructions to access

the information. Document information use restrictions, policies, and

instructions for accessing and using data. Provide resource to regions by allowing them to partner in

the archived data service. CHP Provide data for archiving to the statewide service. Regional Agencies Collect, archive and provide access to archived local,

arterial-based data on a regional basis (this would remain a locally implemented, operated, and maintained service and as such should be defined at a regional level).

7.1 Archived Data Function (S)

UC Berkeley (Current role) “Operate” and maintain PeMS, which manages and calculates available data from Caltrans on a statewide basis.

(Current role) User of the archived data (used for monitoring Caltrans system performance).

(Current role) Provide access to aggregated, archived data to users via the PATH web site.


Operational Concepts for Maintenance and Construction Management

User Service Organization Roles and Responsibilities Caltrans HQ (Proposed) Develop and maintain statewide standards for

roadway pavement condition proactive maintenance on state highways.

(Proposed) Implement, operate, and maintain a database that includes data for pavement conditions and repair schedules statewide.

(Existing) Provide resources for districts to implement and operate fleet tracking and management systems as needed by districts.

Maintenance and Construction Operations (S)

Caltrans Districts (Proposed) Provide pavement condition and repair schedule data to statewide database.

(Existing and proposed) Implement, operate and maintain fleet tracking and management systems for maintenance vehicles as needed in each District.


Operational Concepts for Vehicle Safety and Control

User Services Organization Roles and Responsibilities

Private Sector (Current) Lead the research, development, implementation, operation and maintenance of in-vehicle systems.

(Current) Lead the research and development of roadside systems.

Intersection Collision Avoidance (P) Vision Enhancement for Crash Avoidance (P) Automated Vehicle Operation (P)

Federal (Current) Lead research and development of roadside systems on a national basis.

(Current) Provide a resource to states and regional/local agencies for implementation of roadside systems.

(Current) Provide a resource to states and regional/local agencies for guidance on liability risk assessment of roadside systems and vehicle-roadway interactions.

(Current) Coordination with private sector for vehicle-roadside interactions on a national basis.

Caltrans (Current) Lead research and development of roadside systems within the State of California.

(Current) Assess liability risk of roadside systems and vehicle-roadway interactions specific to the State of California.

(Potential) Provide a resource to regional/local agencies for guidance on liability risk assessment of roadside systems and vehicle-roadway interactions.

(Current) Coordination with private sector for vehicle-roadside interactions in California.

(Current) Fund research for in-vehicle technologies for specific application to maintenance vehicles and partner with other research partners in Advanced Highway Maintenance and Construction Technology Research Center.

Caltrans Districts (Potential) Implementation, operation and maintenance of roadside systems on state freeways and state highways for intersection collision avoidance.

(Potential) Implementation, operation and maintenance of roadside systems on state freeways and state highways for vision enhancement for crash avoidance.

Regional Agencies (Potential) Implementation, operation and maintenance of roadside systems as applicable to solve regional or local agency needs on local streets

Intersection Collision Avoidance (P) Vision Enhancement for Crash Avoidance (P) Automated Vehicle Operation (P) (continued)

Universities and other Research Partners

(Current) Lead research and development of roadside systems within the State of California.

(Current – UC Davis) Lead research for in-vehicle technologies for specific applications to maintenance vehicles and partner with other research partners in Advanced Highway Maintenance and Construction Technology Research Center.


Operational Concepts for Emergency Management


(Current) Establish statewide standards for emergency notification, call boxes, etc. in cooperation with the CHP, the DMV and regional agencies. Statewide legislation established the SAFE (Service Authority for Freeways and Expressways) program which is administered separately by the different regions in the state.

(Current) Establish and maintain statewide response procedures for emergencies in cooperation with other statewide agencies such as CHP, and local or regional police, fire and emergency services. Procedures include areas such as the following:

– traffic rerouting plans

– dissemination of information to the public

Emergency Notification and Personal Security (S)

Caltrans Districts (Current) Implement emergency notification and response as outlined in statewide plans and standards, and further outlined in local response plans.

CHP (Current) Establish statewide standards for emergency notification, call boxes, etc. in cooperation with Caltrans, the DMV and regional agencies.

(Current) Respond to emergencies through the different regional dispatch centers. Assume the role of scene commander.

(Current) Operate freeway service patrols. (Current) Establish statewide response procedures for

emergencies in cooperation with other statewide agencies such as Caltrans, and local or regional police, fire and emergency services.

Regional Agencies (Current) Implement travelers’ aid such as service patrols. SAFE (Current) Implement call boxes throughout freeways and

rural highways in the State. Different regions throughout the state operate their SAFE programs independently from each other, but in cooperation with Caltrans, the CHP and the DMV.

Emergency Notification and Personal Security (S) (continued)

DMV (Current) Bill and collect a fee on state motor vehicle registrations (fee is $1.00 as of 2003) to fund SAFE. Revenues are transferred to the appropriate regional entities who administer SAFE. Statewide legislation ensures that these fee revenues can only be used for implementation, maintenance and operation of travelers’ aid services, such as call boxes and roving tow truck patrols.


(Current and Proposed) Coordinate development of disaster response and evacuation plans for different regions, and establish inter-regional disaster response plans.

Disaster Response and Evacuation (S & IR) Caltrans Districts (Current) Develop disaster response and evacuation plans

for each region. (Current) Pre-plan emergency traffic diversion schemes.


Operational Concepts for Emergency Management (continued)

User Service Organization Roles and Responsibilities CHP (Current) Assist to develop, implement and maintain disaster

response plans. (Current) Lead HAZMAT Incident response efforts by

assuming the role of scene commander. Coordinate with Caltrans Maintenance personnel and Traffic personnel for cleanup and traveler information dissemination.

(Current) Review and adopt interstate and intrastate federal regulations pertaining to hazardous materials requirements. Further refine or develop additional regulations at the state level.

(Current) Enforce regulations adopted at the state level pertaining to hazardous materials.

(Current) Coordinate Statewide Hazardous Materials (HAZMAT) transportation routes and procedures, including:

– Load restrictions

– Load securement requirements

– Safety requirements (Current) Develop educational materials and deliver courses

to inform shippers, drivers and carriers about safety and security of HAZMAT transport. For example, current educational programs recommend photo and electronic identification programs, security training for personnel, and the use of Global Positioning Systems (GPS) to track HAZMAT loads where possible.

(Current) Enforce HAZMAT routes. (Current) Obtain up-to-date information on the safety fitness

of commercial motor carriers and hazardous material shippers subject to the Federal Motor Carrier Safety Regulations and the Hazardous Materials Regulations.

(Current) Enforce HAZMAT regulations for commercial vehicles.

(Proposed) Coordinate and share HAZMAT information with adjoining states.

Regional Agencies (MPOs and RTPAs)

(Current) Assist to develop disaster response plans for ITS Planning regions.

Disaster Response and Evacuation (S & IR) (continued)

Local counties and cities

(Current and Proposed) Assist to develop disaster response plans utilizing surface streets.

091783000 California ITS Architecture and System Plan Appendix A7 - Functional Requirements 1 Appendix A7: Functional Requirements Final- September 30, 2004

APPENDIX A7: FUNCTIONAL REQUIREMENTS

Entity Function (Equipment Package)

Functional Requirement Changed Added Inter-Regional

State-wide

State-level Standards

Archived Data Management Subsystem

Government Reporting Systems Support

The center shall provide data from an ITS archive to federal, state, or local government reporting systems.

X



The center shall provide the capability to select data from an ITS archive for use in government reports.

X



The center shall provide the capability to format data from an ITS archive suitable for input into government reports.

X



The center shall support requests for ITS archived data from Government Reporting Systems.

X



The center shall provide the applicable meta-data for any ITS archived data to satisfy government reporting system requests.

X X


ITS Data Repository The center shall collect data to be archived from one or more data sources.

X


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.

X


ITS Data Repository The center shall include capabilities for performing quality checks on the incoming archived data.

X


ITS Data Repository The center shall include capabilities for error notification on the incoming archived data.

X


ITS Data Repository The center shall include capabilities for archive to archive coordination.

X


ITS Data Repository The center shall support a broad range of archived data management implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.

X




State-wide



ITS Data Repository The center shall perform quality checks on received data.

X


ITS Data Repository The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.

X


ITS Data Repository The center shall respond to requests from the administrator interface function to maintain the archive data.

X


ITS Data Repository For archive data requiring financial payment, the center shall process the financial requests and manage an interface to a Financial Institution.

X


ITS Data Repository The center shall collect data catalogs (e.g., time range of entries, number of entries, or a sample of the data) from one or more data sources.

X X


ITS Data Repository The center shall generate the requested data product for the users systems when data or a catalog of data is received from the archive, .

X X


On-Line Analysis and Mining The center shall support the interface with Archive Data User Systems for requests for analysis of the archive data.

X


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.

X


On-Line Analysis and Mining The center shall respond to users systems requests for a catalog of the archived data analysis products available.

X


On-Line Analysis and Mining The center shall provide the capability to perform activities such as data mining, data fusion, summarizations, aggregations, and recreation from archive data.

X X


On-Line Analysis and Mining The center shall process the financial requests for archive analysis and data mining products requiring financial payment and manage an interface to a Financial Institution.

X X




State-wide



Traffic and Roadside Data Archival

The center shall manage the collection of archive data directly from collection equipment located at the roadside.

X



The center shall collect traffic sensor information from roadside devices.

X



The center shall collect environmental sensor information that from roadside devices.

X



The center shall respond to requests from theArchive Data Administer to input the parameters that control the collection process.

X



The center shall send the request for data and control parameters to the field equipment where the information is collected and returned.

X



The center shall record the status about the imported traffic and roadside data.

X



The center shall use the status information to adjust the collection of traffic and roadside data.

X


Virtual Data Warehouse Services

The center shall coordinate information exchange with a local data warehouse.

X X



The center shall provide the specialized publishing, directory services, and transaction management functions associated with coordinating remote archives.

X X



The center shall use data collected from different archives to build a set of global schema including the data archive definitions for the local archive plus any archives known to the local archive.

X X



The center shall provide capabilities to access "in-place" data from geographically dispersed archives.

X X



The center shall support the collection of archived data from other archives on an as-needed basis.

X X X



The center shall provide the local archived data schema to other archive systems.

X X X




State-wide


Commercial Vehicle Administration

Credentials and Taxes Administration

The center shall manage electronic credentials filing and processing for commercial vehicles.

X



The center shall manage the filing of appropriate taxes for the operation of commercial vehicles.

X



The center shall process requests for payments of electronic credentials and tax filing and maintain an interface to a Financial Institution.

X



The center shall exchange credentials and tax information with other commercial vehicle administration centers - either in other states or the federal government.

X



The center shall provide route restrictions information, including hazmat restrictions, to other centers and agencies for distribution to commercial vehicle operators. These centers and agencies may include commercial fleet and freight management operators, traveler information centers, digital map update providers, and other commercial vehicle adminstration centers.

X



The center shall use information on asset restrictions received from maintenance centers to develop the commercial vehicle route restrictions and process credentials applications.

X



The center shall provide an interface with commercial vehicle fleet and freight management centers to exchange audit and compliance review reports.

X



The center shall provide credentials information about commercial vehicle operators and carriers to authorized requestors such as insurance agencies.

X



The center shall receive and store information on commercial vehicle violations from enforcement agencies as part of the processing of credentials applications.

X




State-wide



CV Data Collection The center shall receive operational data from the roadside check systems as well as administration and credentials data.

X


CV Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of thecommercial vehicle operations data or for the data itself.

X


CV Data Collection The center shall be able to produce sample products of the data available.

X


CV Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X


CV Information Exchange The center shall exchange information with roadside check facitlities, including credentials and credentials status information, safety status information, daily site activity data, and citations.

X


CV Information Exchange The center shall exchange safety and credentials data among other commercial vehicle administration centers; includes border clearance status, credentials information, credentials status information, and safety status information.

X


CV Information Exchange The center shall package data concerning commercial vehicle safety and credentials into snapshots (top-level summary and critical status information).

X


CV Information Exchange The center shall package data concerning commercial vehicle safety and credentials into profiles (detailed and historical data).

X


CV Information Exchange The center shall provide commercial vehicle accident reports and citations to enforcement agencies.

X


CV Information Exchange The center shall provide commercial vehicle credentials and safety status information to authorized requestors such as insurance agencies.

X




State-wide



CV Information Exchange The center shall provide reports to the commercial vehicle fleet manager regarding fleet activity through roadside facilities including accident reports, citations, credentials status information, and safety status information.

X


CV Safety Administration The center shall provide commercial vehicle safety data to roadside check facilities.

X


CV Safety Administration The center shall collect and review safety inspection reports and violations from the roadside check facilities and pass on appropriate portions to other commercial vehicle administrative centers and commercial vehicle fleet operators.

X


CV Safety Administration The center shall notify enforcement agencies of commercial vehicle safety violations by individual commercial vehicles, drivers, or carriers.

X


International CV Administration The center shall receive domestic transportation and declaration information from Trade Regulatory Agencies such as U.S. Bureau of Immigration and Customs Enforcement(ICE), the U.S. Bureau of Customs and Border Protection (CBP), and their counterparts in Canada and Mexico.

X


International CV Administration The center shall provide an assessment regarding a commercial vehicle and driver at a border crossing. The assessment or clearance data will be forwarded on to the appropriate regulatory agencies and roadside check facilities operating at the border crossing.

X


International CV Administration The center shall provide border clearance status concerning commercial vehicles and their shipments to the roadside check facilities, the commercial vehicle fleet and freight management centers, intermodal freight shippers, other commercial vehicle administration centers, and the trade regulatory agencies.

X




State-wide



International CV Administration The center shall receive and store border clearance event data from the roadside check facilities that are located near border crossings.

X

Commercial Vehicle Check

Citation and Accident Electronic Recording

The roadside check facility equipment shall record the results of roadside inspections carried using an inspector's hand held terminal interface.

X



The roadside check facility equipment shall provide an interface for an inspector to add comments to the inspection results.

X



The roadside check facility equipment shall forward results of the roadside inspections to the commercial vehicle administration center either as needed or on a periodic (e.g. basis). These reports include accident reports, violation notifications, citations, and daily site activity logs.

X


International Border Crossing The roadside check facility equipment at a border crossing shall receive the border agency clearance results, transportation border clearance assessments, and trip declaration identifiers from the commercial vehicle administration center to be used to screen the incoming commercial vehicles.

X


International Border Crossing The roadside check facility equipment at a border crossing shall request and input the tag data from approaching commercial vehicles to determine the identity of the vehicle along with its carrier, driver, and a trip identity.

X


International Border Crossing The roadside check facility equipment at a border crossing shall request and input the border clearance data from approaching commercial vehicles to compare against the data received from the center concerning compliance with import/export and immigration regulations.

X


International Border Crossing The roadside check facility equipment at a border crossing shall request and input the electronic cargo lock data from approaching commercial vehicles to compare against the data received from the center.

X




State-wide



International Border Crossing The roadside check facility equipment at a border crossing shall send clearance event data regarding action taken at border to the commercial vehicle adminstration center and to the commercial vehicle. This may include a date/time stamped acceptance or override of system decisions whether to allow release of the vehicle and its cargo.

X


Roadside Electronic Screening The roadside check facility equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. Sensors can differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, and the identification of the vehicle and its cargo.

X


Roadside Electronic Screening The roadside check facility equipment shall receive the credential and credentials status information (e.g. snapshots) from the commercial vehicle administration center to maintain an up to date list of which vehicles have been cleared (enrolled) to potentially pass through without stopping.

X


Roadside Electronic Screening The roadside check facility equipment shall receive violation records from appropriate law enforcement agencies pertaining to commercal vehicles.

X


Roadside Electronic Screening The roadside check facility equipment shall provide an interface to inspectors in the field to allow them to monitor and if necessary override the pull-in decisions made by the system.

X


Roadside Electronic Screening The roadside check facility equipment shall request and input electronic screening data from the commercial vehicle's electronic tag data.

X




State-wide



Roadside Electronic Screening The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, enforcement agencies, and the inspector. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc.

X


Roadside Electronic Screening The roadside check facility equipment shall send a record of daily activities at the facility including summaries of screening events and inspections to the commercial vehicle administration center.

X


Roadside HAZMAT Detection The roadside check facility equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. Sensors can differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, presence of security sensitive hazardous materials, and the identification of the vehicle and its cargo.

X


Roadside HAZMAT Detection The roadside check facility equipment shall detect the presence of security sensitive substance, e.g. detection of radiation or ammonia compounds, carried on-boar commercial vehicles and freight equipment approaching a facility. This data is acquired by roadside sensors from the freight equipment electronically, optically, or manually.

X


Roadside HAZMAT Detection The roadside check facility equipment shall receive the credential information (e.g. snapshots) from the commercial vehicle administration center to maintain an up to date list of which vehicles with hazardous materials shipments have been cleared (enrolled).

X




State-wide



Roadside HAZMAT Detection The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the hazmat information received from the vehicle, the freight equipment, or the administration center. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc.

X


Roadside HAZMAT Detection The roadside check facility equipment shall raise and forward an alarm to the appropriate emergency management center if the hazmat-carrying commercial vehicle does not stop, or in the case of a positive identification of an unpermitted security sensitive hazmat cargo, to coordinate a traffic stop or some other action with respect to the offending commercial vehicle. The alarm will include information concerning the security sensitive hazmat detected at the roadside including the location, appropriate identifiers, route deviation, or assignment mismatches between the driver, commercial vehicle, or the freight equipment.

X


Roadside Safety and Security Inspection

The roadside check facility equipment shall receive information concerning commercial vehicles and freight equipment approaching a facility that are being pulled in for safety inspections.

X



The roadside check facility equipment shall receive the safety inspection and status information from the commercial vehicle administration center to include information such as safety ratings, inspection summaries, and violation summaries. Corresponds to the safety portion of CVISN "snapshots."

X




State-wide




The roadside check facility equipment shall provide an interface to inspectors in the field to allow them to safety inspection data including overrides to the pull-in decisions made by the system.

X



The roadside check facility equipment shall request and input electronic safety data from the commercial vehicle's electronic tag data. This includes driver logs, on-board safety data, safety inspection records, commercial vehicle breach information, as well as freight equipment information.

X



The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle, the administration center, and the inspector. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc.

X



The roadside check facility equipment shall receive information about a breach or tamper event on a commercial vehicle or its attached freight equipment which includes identity, type of breach, location, and time.

X



The roadside check facility equipment shall forward results of the roadside safety inspections to the commercial vehicle administration center.

X


Roadside WIM The roadside check facility equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. Sensors can differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, weight per axle, and the identification of the vehicle and its cargo.

X




State-wide



Roadside WIM The roadside check facility equipment shall request and input electronic screening data from the commercial vehicle's electronic tag data.

X


Roadside WIM The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle and the measurements taken. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc.

X

Commercial Vehicle Subsystem

On-board CV Electronic Data The commercial vehicle shall receive pass/pull-in messages from the roadside check facilities and present them to the driver in either audible or visual forms.

X


On-board CV Electronic Data The commercial vehicle shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo status, hazmat identifiers, out of service status, vehicle axle weight, vehicle weight, and time.

X


On-board CV Electronic Data The commercial vehicle shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, inlcuding border crossings.

X


On-board CV Electronic Data The commercial vehicle shall support an interface to a commercial vehicle driver that is also acting in the role of a commercial vehicle fleet manager to set up routes, pay necessary taxes, obtain proper credentials, and write the identifiers to the electronic tag for the driver, vehicle, and carrier.

X




State-wide



On-board CV Safety and Security

The commercial vehicle shall receive pass/pull-in messages from the roadside check facilities and present them to the driver in either audible or visual forms.

X



The commercial vehicle shall respond to requests to provide on-board safety inspection data to roadside check facilities including vehicle identification, driver logs, and characteristics data for initiating safety checking. Results of the inspection are read back into the on-board equipment.

X



The commercial vehicle shall monitor on-board systems pertaining to the safety and security of the vehice, its driver, and its cargo/freight equipment; and provide the information to the roadside check facilities.

X X



The commercial vehicle shall provide information concerning a breach or tamper event on a commercial vehicle or its attached freight equipment to roadside check facilities. The information shall include identity, type of breach, location, and time.

X X

Emergency Management Center Secure Area Sensor Management

The center shall exchange security sensor data with other emergency centers.

X


The center shall identify potential security threats based on collected security sensor data.

X


The center shall verify potential security threats by correlating security sensor data from multiple sources.

X


The center shall perform threat analysis based on correlations of security sensor and surveillance data.

X


The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing.

X


The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency

X




State-wide


management centers.


The center shall respond to control data from center personnel regarding security sensor data collection, processing, threat detection, and threat analysis.

X


The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).

X X

Emergency Management Center Secure Area Surveillance

The center shall exchange surveillance data with other emergency centers.

X


The center shall identify potential security threats based on collected security surveillance data.

X


The center shall verify potential security threats by correlating security surveillance data from multiple sources.

X


The center shall remotely control security surveillance devices in secure areas including facilities (e.g. maintenance yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).

X X


The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.

X


The center shall remotely monitor video images and audio surveillance data collected in traveler areas such as rest areas and other fixed sites along travel routes.

X X




State-wide



The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities (e.g. maintenance yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges)

X X

Emergency Management Emergency Call-Taking The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7-digit call routing) to receive emergency notification information and provide it to the emergency system operator.

X

Emergency Management Emergency Call-Taking The center shall receive emergency call information from 911 services and present the possible incident information to the emergency system operator.

X

Emergency Management Emergency Call-Taking The center shall receive emergency call information from motorist call-boxes and present the possible incident information to the emergency system operator.

X

Emergency Management Emergency Call-Taking The center shall receive emergency call information from mayday service providers and present the possible incident information to the emergency system operator.

X

Emergency Management Emergency Call-Taking The center shall receive emergency notification information from other public safety agencies and present the possible incident information to the emergency system operator.

X X

Emergency Management Emergency Call-Taking The center shall receive emergency notification information from public transit systems and present the possible incident information to the emergency system operator.

X

Emergency Management Emergency Call-Taking The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for incidents involving potential hazardous materials.

X X




State-wide


Emergency Management Emergency Call-Taking The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls and internal analysis of security sensor and surveillance data, and assign each a level of confidence.

X X

Emergency Management Emergency Call-Taking The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify the reported incident.

X

Emergency Management Emergency Call-Taking The center shall update the incident information log once the emergency system operator has verified the incident.

X X

Emergency Management Emergency Call-Taking The center shall provide the capability for digitized map data to act as the background to the emergency information presented to theemergency system operator.

X X

Emergency Management Emergency Call-Taking The center shall forward the verified emergency information to the responding agency based on the location and nature of the emergency.

X X

Emergency Management Emergency Call-Taking The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations, or commercial fleet operators and present the possible incident information to the emergency system operator.

X X X

Emergency Management Emergency Data Collection The center shall collect emergency service data, emergency vehicle management data, emergency vehicle data, sensor and surveillance data, threat data, and incident data.

X

Emergency Management Emergency Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emergency management data or for the data itself.

X

Emergency Management Emergency Data Collection The center shall be able to produce sample products of the data available.

X

Emergency Management Emergency Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X




State-wide


Emergency Management Emergency Dispatch The center shall dispatch emergency vehicles to respond to verified emergencies and provide suggested routing under center personnel control.

X

Emergency Management Emergency Dispatch The center shall store the current status of all emergency vehicles available for dispatch and those that have been dispatched.

X

Emergency Management Emergency Dispatch The center shall relay location and incident details to the responding vehicles.

X X

Emergency Management Emergency Dispatch The center shall provide the capability to request traffic control measures from traffic management centers such as signal preemption, traffic barriers and road closures.

X

Emergency Management Emergency Dispatch The center shall track the location and status of emergency vehicles responding to an emergency and update the incident status based on information from the emergency vehicle.

X X

Emergency Management Emergency Dispatch The center shall receive status information from care facilities to determine the appropriate facility and its location.

X

Emergency Management Emergency Dispatch The center shall store and maintain the emergency service responses in an action log.

X

Emergency Management Emergency Dispatch The center shall receive asset restriction information from maintenance centers to support the dispatching of appropriate emergency resources.

X

Emergency Management Emergency Dispatch The center shall receive traffic information, including closures, traffic conditions, etc. from traffic management centers.

X

Emergency Management Emergency Dispatch The center shall provide the capability for digitized map data to act as the background to the information presented to the emergency system operator.

X

Emergency Management Emergency Dispatch The center shall receive road network conditions and traffic images to support dispatch of emergency vehicles.

X




State-wide


Emergency Management Emergency Dispatch The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate resources are dispatched and utilized.

X

Emergency Management Emergency Early Warning System

The center shall provide the capability to correlate alerts and advisories, incident information, and security sensor and surveillance data.

X X


The center shall broadcast wide-area alerts and advisories to traffic management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X


The center shall broadcast wide-area alerts and advisories to transit management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X


The center shall broadcast wide-area alerts and advisories to toll administration centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X


The center shall broadcast wide-area alerts and advisories to traveler information service providers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X


The center shall broadcast wide-area alerts and advisories to maintenance centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X




State-wide



The center shall broadcast wide-area alerts and advisories to other emergency management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X X


The center shall process status information from each of the centers that have been sent the wide-area alert.

X X


The center shall coordinate the broadcast of wide-area alerts and advisories with other emergency management centers.

X X


The center shall receive incident information from other transportation management centers to support the early warning system.

X X


The center shall present the alert and advisory information and the status of the actions taken in response to the alert by the other centers to the emergency system operator as received from other system inputs.

X X


The center shall support the entry of alert and advisory information directly from the emergency system operator.

X X


The center shall monitor information (e.g. assessments, advisories or alerts) from Alerting and Advisory Systems such as the Information Sharing and Analysis Centers (ISACs), the National Infrastructure Protection Center (NIPC), and the Homeland Security Advisory System (HSAS).

X X X

Emergency Management Emergency Environmental Monitoring

The center shall collect current and forecast road and weather information from weather service providers (such as the National Weather Serviceand value-added sector specific meteorological services).

X


The center shall collect current road and weather information from roadway maintenance operations.

X




State-wide



The center shall assimilate current and forecast road conditions and surface weather information to support incident management.

X


The center shall present the current and forecast road and weather information to the emergency system operator.

X

Emergency Management Emergency Evacuation Support

The center shall manage inter-agency coordination of evacuation operations, from initial planning through the evacuation process and reentry.

X X


The center shall develop and exchange evacuation plans with allied agencies prior to the occurrence of a disaster.

X X


The center shall provide an interface to the emergency system operator to enter evacuation plans and procedures and present the operator with other agencies’ plans.

X X


The center shall coordinate evacuation destinations and shelter needs with shelter providers (e.g., the American Red Cross) in the region.

X X


The center shall provide evacuation information to traffic, transit, maintenance and construction, rail operations, and other emergency management centers as needed.

X X


The center shall request resources from transit agencies as needed to support the evacuation.

X X


The center shall request traffic management agencies to implement special traffic control strategies and to control evacuation traffic, including traffic on local streets and arterials as well as the major evacuation routes.

X X


The center shall provide traveler information systems with evacuation guidance including basic information to assist potential evacuees in determining whether evacuation is necessary and when it is safe to return.

X X




State-wide



The center shall monitor the progress or status of the evacuation once it begins and exchange tactical plans, prepared during the incident, with allied agencies.

X X


The center shall monitor the progress of the reentry process.

X X


The center shall submit evacuation information to toll administration centers along with requests for changes in the toll services or fee collection during an evacuation.

X X

Emergency Management Emergency Response Management

The center shall provide strategic emergency response capabilities such as that of an Emergency Operations Center for large-scale incidents and disasters.

X X


The center shall manage coordinated inter-agency responses to and recovery from large-scale emergencies. Such agencies include traffic management, transit, maintenance and construction management, rail operations, and other emergency management agencies.

X X


The center shall provide the capability to implement response plans and track progress through the incident by exchanging incident information and distributing response status to allied agencies.

X X


The center shall develop, coordinate with other agencies, and store emergency response plans.

X X


The center shall track the availability of resources (including vehicles, roadway cleanup?, etc.), request additional resources from traffic, maintenance, or other emergency centers if needed.

X X


The center shall allocate the appropriate emergency services, resources, and vehicle (s) to respond to incidents, and shall provide the capability to override the current allocation to suit the special needs of a current incident.

X X




State-wide



The center shall receive event scheduling information from Event Promoters.

X X


The center shall receive hazardous materials incident information from commercial fleet operators.

X X


The center shall provide the capability to request the safe disabling of a commercial vehicle during a hazardous materials incident.

X X


The center shall provide the capability to request transit resource availability from transit centers for use during disaster and evacuation operations.

X X


The center shall assimilate the status of the transit, traffic, rail, maintenance, and other emergency center services and systems to create an overall transportation system status, and disseminate to each of these centers and the traveling public via traveler information providers.

X X


The center shall provide information to the media concerning the status of an emergency response.

X X


The center shall provide the capability for digitized map data to act as the background to the information presented to the emergency system operator.

X X


The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters and evacuations.

X X

Emergency Management Incident Command The center shall provide tactical decision support, resource coordination, and communications integration for Incident Commands that are established by first responders to support local management of an incident.

X X

Emergency Management Incident Command The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.

X X




State-wide


Emergency Management Incident Command The center shall track and maintain resource information and action plans pertaining to the incident command.

X X

Emergency Management Incident Command The center shall share incident command information with other public safety agencies including resource deployment status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather conditions.

X X

Emergency Management Incident Command The center shall assess the status of responding emergency vehicles as part of an incident command.

X X

Emergency Management Mayday Support The center shall collect mayday messages from vehicles and drivers.

X X

Emergency Management Mayday Support The center shall collect mayday messages from travelers via personal handheld devices.

X X

Emergency Management Mayday Support The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by the vehicle's safety systems, or by a traveler via a personal handheld device.

X X

Emergency Management Mayday Support After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday message.

X X

Emergency Management Mayday Support The center shall determine whether the mayday message indicates an emergency that requires the attention of public safety agencies, and forward mayday emergency data to the appropriate agency as necessary.

X X

Emergency Management Mayday Support The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock doors.

X X

Emergency Management Mayday Support The center shall request additional emergency details from or issue commands to the vehicle's security systems or vehicle driver if needed.

X X

Emergency Management Mayday Support The center shall maintain a log of all mayday signals received from vehicles.

X X




State-wide


Emergency Management Mayday Support The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the portable handheld device as directed by the personnel.

X X

Emergency Vehicle Subsystem

On-board EV En Route Support

The emergency vehicle shall compute the location of the emergency vehicle based on inputs from a vehicle location determination function.

X X



The emergency vehicle shall send the vehicle's location and operational data to the center for emergency management and dispatch.

X X



The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene.

X



The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates.

X



The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.

X


On-board EV Incident Management Communication

The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the incident site such as the extent of injuries, identification of vehicles and people involved, hazardous material, etc.

X



The emergency vehicle shall provide an interface to the center for emergency personnel to transmit information about the current incident response status such as the identification of the resources on site, site management strategies in effect, and current clearance status.

X




State-wide




The emergency vehicle shall receive dispatch instructions sufficient to enable emergency personnel in the field to implement an effective incident response.

X X

Emissions Management Emissions Data Collection The center shall collect air quality and emissions management data from various sources, including emissions sensors distributed along the roadside and wide-area sensors detecting pollution over a larger geographical area.

X

Emissions Management Emissions Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the emissions management data or for the data itself.

X

Emissions Management Emissions Data Collection The center shall be able to produce sample products of the data available.

X

Emissions Management Emissions Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X

Fleet and Freight Management

Fleet Administration The center shall send data concerning enrollment of commercial vehicles for electronic clearance and tax filing to the appropriate commercial vehicle administration center. The data may include driver and vehicle identification, safety inspections/status, carrier credentials, related citations, and accident information.

X


Fleet Administration The center shall monitor the locations and progress of commercial vehicles against their planned routes and raise appropriate warnings based on route monitoring parameters.

X


Fleet Administration The center shall coordinate the response to security incidents and the sharing of security threat information involving commercial vehicles with other agencies including emergency management centers and alerting/advisory systems.

X




State-wide



Fleet Credentials and Taxes Management and Reporting

The center shall send data concerning enrollment and purchase of commercial vehicles credentials and tax filing to the appropriate commercial vehicle administration center.

X



The center shall receive compliance review reports from the appropriate commercial vehicle administration centers concerning the operations of the commercial vehicle fleet, including concomitant out-of-service notifications, and carrier warnings/notifications.

X



The center shall provide audit data to the appropriate commercial vehicle adminstration center to support tax audits.

X



The center shall support an interface with a commercial vehicle driver that is acting in the role of a commercial vehicle fleet manager for the purposes of obtaining credentials, filing taxes and audit data, and receiving compliance reports and status information.

X


Fleet HAZMAT Management The center shall track the routing and cargo information, including the manifest data plus the chemical characteristics of a hazardous materials (HAZMAT) load being carried by its fleet of commercial vehicles.

X


Fleet HAZMAT Management The center shall provide information concerning commercial vehicles carrying hazardous materials (HAZMAT) upon request from an emergency management center. The information includes the nature of the cargo being carried, identity of the vehicle and unloading instructions.

X




State-wide



Freight Administration and Management

The center shall collect data from the commercial vehicles carrying freight or from the freight equipment itself. Includes container, trailer, or chassis information regarding identity, type, location, brake wear data, mileage, seal number/type, door open/close status, chassis bare/covered status, tethered / untethered status, bill of lading, and sensor status.

X



The center shall provide the interface with intermodal freight shippers to setup transportation for freight equipment. Inputs to this include information about the shipper, consignee, commodities, pick-up and drop-off locations for freight equipment. Outputs include information about the driver and commercial vehicle that will be transporting the freight.

X



The center shall coordinate the shipment of cargo using freight equipment with intermodal freight depots. Information to be coordinated includes information regarding a freight transportation booking and the assigned driver and vehicle scheduled to transport the freight along with cargo movement logs, routing information, and cargo ID’s.

X



The center shall track the progress of freight equipment as it moves from source to destination based on inputs from the commercial vehicles, the freight equipment, intermodal freight depots, shippers, and commercial vehicle adminstration centers that provide border clearance status information.

X



The center shall collect diagnostic information fro freight equipment to schedule preventative and corrective maintenance.

X



The center shall notify other security functions within the center of deviations in the movement of freight equipment from its planned route.

X




State-wide


Information Service Provider

Basic Information Broadcast The center shall collect, process, store, and disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate transit routes and schedules, transittransfer options, transit fares, and real-time schedule adherence information to travelers.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate parking information to travelers, including location, availability, and fees.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate toll fee information to travelers.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate weather information to travelers.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate event information to travelers.

X X


Basic Information Broadcast The center shall collect, process, store, and disseminate air quality information to travelers.

X X


Basic Information Broadcast The center shall provide the capability to support requests from the media for traffic and incident data.

X X


Basic Information Broadcast The center shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information.

X X




State-wide



Interactive Infrastructure Information

The center shall collect, process, store, and disseminate customized traffic and highway condition information to travelers, including incident information, detours and road closures, recommended routes, and current speeds on specific routes upon request.

X X



The center shall collect, process, store, and disseminate customized maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities upon request.

X X



The center shall collect, process, store, and disseminate customized transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers upon request.

X X



The center shall collect, process, store, and disseminate customized parking information to travelers, including location, availability, and fees upon request.

X X



The center shall collect, process, store, and disseminate customized toll fee information to travelers upon request.

X X



The center shall collect, process, store, and disseminate customized weather information to travelers upon request.

X X



The center shall collect, process, store, and disseminate customized multimodal transportation service information (for example, from ferry and airline operators), including transfer points and other information, to travelers upon request.

X X



The center shall collect, process, store, and disseminate customized event information to travelers upon request.

X X



The center shall collect, process, store, and disseminate customized air quality information to travelers upon request.

X X




State-wide




The center shall provide all traveler information based on the traveler's current location or a specific location identified by the traveler, and filter or customize the provided information accordingly.

X X



The center shall accept traveler profiles for determining the type of personalized data to send to the traveler.

X X



The center shall manage payment for services, such as tolls, transit fares, parking lot charges, map updates, and advanced payment for tolls, and provide transaction success or failure details.

X X



The center shall support requests for traveler information and advanced payment for traveler services from commercial fleet operators.

X X



The center shall provide the capability to exchange information with another traveler information service provider current or predicted data for road links that are outside the area served by the local supplier.

X X



The center shall manage updates of digitized map data and provide updates to traveler interface systems upon request.

X X



The center shall provide the capability to support requests from the media for traffic and incident data.

X X



The center shall provide the capability for a system operator to control the type and update frequency of traveler information.

X X


ISP Data Collection The center shall collect traveler information data, such as parking lot data, rideshare data, road network use data, vehicle probe data, and other data from traveler information system operations.

X


ISP Data Collection The center shall collect traveler requests, confirmations, and payment transaction data for traveler services provided.

X




State-wide



ISP Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the traveler information data or for the data itself.

X


ISP Data Collection The center shall be able to produce sample products of the data available.

X


ISP Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X


ISP Emergency Traveler Information

The center shall collect and provide to the traveler interface systems emergency evacuation information, including evacuation zones, shelter information, available transportation modes, road closures and detours, changes to transit services, and traffic and road conditions at the origin, destination, and along the evacuation routes.

X X



The center shall provide evacuation information to shelter providers.

X X



The center shall collect and provide wide-area alert information to the traveler interface system with region-specific data, including major emergencies such as a natural or man-made disaster, civil emergency, child abductions, severe weather watches and warnings, military activities, and law enforcement warnings.

X X



The center shall provide the capability for a system operator to control the type and update frequency of emergency and wide-area alert information distributed to travelers.

X X


Traveler Telephone Information

The center shall provide the capability to process voice-formatted requests for traveler information from a traveler telephone information system, and return the information in the requested format.

X X



The center shall provide the capability to process dual-tone multifrequency (DTMF)-based requests (touch-tone) for traveler information from a traveler telephone information system.

X X




State-wide




The center shall provide the capability to process traveler information requests from a traveler telephone information system.

X X



The center shall collect and provide information on traffic conditions in the requested voice format and for the requested location.

X X



The center shall collect and provide work zone and roadway maintenance information in the requested voice format and for the requested location.

X X



The center shall collect and provide roadway environment conditions information in the requested voice format and for the requested location.

X X



The center shall collect and provide weather and event information in the requested voice format and for the requested location.

X X



The center shall collect and provide transit service information in the requested voice format and for the requested location.

X X



The center shall collect and provide yellow pages services information in the requested voice format and for the requested location.

X X



The center shall collect and provide current ferry and rail schedule and airport status information in the requested voice format and for the requested location.

X X



The center shall provide the capability to support both specific caller requests as well as bulk upload of regional traveler information.

X X




State-wide




The center shall receive and forward region-specific wide-area alert and advisory information to the traveler telephone information system, including major emergencies such as a natural or man-made disaster, civil emergency, child abductions, severe weather watches and warnings, military activities, and law enforcement warnings.

X X

Maintenance and Construction Management

MCM Data Collection The center shall collect maintenance and construction data (such as field equipment status, infrastructure status, maintenance and construction activity data) gathered from roadway, traffic, and other maintenance and construction sources.

X


MCM Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the maintenance and construction data or for the data itself.

X


MCM Data Collection The center shall be able to produce sample products of the data available.

X


MCM Data Collection The center shall provide data to Asset Management to be used in updating the status of assets in the inventory.

X


MCM Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X


MCM Environmental Information Collection

The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.

X



The center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.

X




State-wide




The center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from traffic, emergency, and transit management, traveler information providers, and environmental data collected from sensors deployed on and about the roadway as well as the fleet of maintenance and construction vehicles.

X



The center shall provide weather and road condition information to weather service providers and center personnel.

X



The center shall collect operational status for the roadside and vehicle-based environmental sensor equipment.

X



The center shall collect fault data for the roadside and vehicle-based environmental sensor equipment for repair.

X


MCM Environmental Information Processing

The center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services) and local environmental sensor data.

X



The center shall use the various data inputs of environmental sensors and road weather data to develop a view of current and predicted road weather and road conditions.

X




State-wide




The center shall disseminate current and forecasted road weather and road condition information to weather service providers (such as the National Weather Service and value-added sector specific meteorological services) as well as other agencies including traffic, emergency, and transit management, traveler information providers, rail operations centers, media, and other maintenance management centers.

X



The center shall provide value-added sector specific meteorological services with information on basic road facility and treatment information that supports forecasts for road conditions.

X


MCM Incident Management The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.

X X


MCM Incident Management The center shall exchange incident and threat information with emergency management centers as well as traffic management centers; including notification of existence of incident and expected severity, location, time and nature of incident.

X


MCM Incident Management The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.

X X


MCM Incident Management The center shall exchange road network status assessment information with emergency management and traffic management centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.

X X




State-wide



MCM Incident Management The center shall receive information indicating the damage sustained by transportation assets, derived from aerial surveillance, field reports, inspections, tests, and analyses to support incident management.

X X


MCM Incident Management The center shall exchange alert information and status, including disaster inforamtion, the nature of the emergency and the logistics of the emergency, with emergency management centers.

X X X


MCM Incident Management The center shall respond to requests from emergency management to provide maintenance and construction resources to implement response plans, assist in clean up, verify an incident, etc.

X X X


MCM Incident Management The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits.

X X X


MCM Maintenance Decision Support

The center shall provide the center personnel with tailored external information, including weather or road condition observations, forecasted weather information or road conditions, current usage of treatments and materials, available resources, equipment and vehicle availability, road network information, and source reliability information.

X


MCM Maintenance Decision Support

The center shall tailor the decision support information to include filtering (selection from a large amount of external information), errorreduction ('smoothing' the information), fusion (combination of disparate information to match the decision needs), and analysis (creating the decision).

X




State-wide



MCM Roadway Maintenance and Construction

The center shall maintain an interface with asset management systems to track the inventory, restrictions, repair needs and status updates of transportation assets (pavement, bridges, signs, etc.) including location, installation and materials information, vendor/contractor, current maintenance status, standard height, width, and weight restrictions.

X



The center shall collect the status and fault data from roadside equipment, such as traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.

X



The center shall collect the status and fault data from traffic management centers, including data for traffic, infrastructure, and environmental sensors, highway advisory radio and dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security sensors and surveillance equipment, etc., and provide a cohesive view of equipment repair needs.

X



The center shall remotely control and collect data from infrastructure monitoring sensors located along the roadway infrastructure or on maintenance and construction vehicles.

X



The center shall collect current and forecast traffic and weather information from traffic management centers and weather service providers (such as the National Weather Service and value-added sector specific meteorological services).

X




State-wide




The center shall exchange information with administrative systems to support the planning and scheduling of maintenance activities.

X X


MCM Vehicle Tracking The center shall monitor the locations of all maintenance and construction vehicles and other equipment under its jurisdiction.

X


MCM Vehicle Tracking The center shall present location data to center personnel for the fleet of maintenance and construction vehicles and other equipment.

X


MCM Winter Maintenance Management

The center shall respond to requests from emergency management and traffic management centers for hazard removal, field equipment repair, and other winter roadway maintenance.

X



The center shall exchange information with administrative systems to support the planning and scheduling of winter maintenance activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration.

X



The center shall provide status information about scheduled winter maintenance activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance centers, and the media.

X



The center shall collect current and forecast traffic and weather information from traffic management centers and weather service providers (such as the National Weather Service and value-added sector specific meteorological services).

X




State-wide




The center shall determine the need for roadway treatment based on current and forecasted weather information, current usage of treatments and materials, available resources, requests for action from other agencies, and recommendations from the Maintenance Decision Support system, specifically under winter conditions. This supports winter maintenance such as plowing, treating, anti-icing, etc.

X



The center shall assess the current status of all winter maintenance activities, including actual work activities performed, current locations and operational conditions of vehicles, materials and equipment inventories, field equipment status, environmental information, etc.

X


MCM Work Activity Coordination

The center shall provide work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.

X



The center shall provide status information about scheduled maintenance and construction activities including anticipated closures and impact to the roadway, alternate routes, anticipated delays, closure times, and durations. The information is provided to other management centers such as traffic, emergency, transit, traveler information providers, other maintenance centers, multimodal transportation providers, rail operations, and the media.

X




State-wide




The center shall collect and respond to feedback concerning scheduled maintenance and construction activities with other management centers such as traffic, emergency, transit, and rail operations.

X



The center shall collect and disseminate asset restriction information levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.

X



The center shall exchange information with administrative systems to support the planning and scheduling of maintenance and construction activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration.

X



The center shall exchange rail schedules and workplans with rail operations centers.

X


MCM Work Zone Management The center shall generate new work zone activity schedules for use by maintenance and construction vehicles, maintenance and construction operators, and for information coordination purposes.

X


MCM Work Zone Management The center shall control the collection of work zone status information including video images from cameras located in or near the work zone.

X


MCM Work Zone Management The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency management centers, other maintenance centers, traveler information providers, and the media.

X




State-wide



MCM Work Zone Management The center shall control traffic in work zones by providing remote control of dynamic message signs and highway advisory radio systems located in or near the work zone.

X


MCM Work Zone Management The center shall exchange information with administrative systems to support the planning and scheduling of work zone activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration.

X

Maintenance and Construction Vehicle

MCV Vehicle Location Tracking

The maintenance and construction vehicle shall compute the location of the vehicle based on inputs from a vehicle location determination function.

X

Maintenance and Construction Vehicle

MCV Vehicle Location Tracking

The maintenance and construction vehicle shall send the timestamped vehicle location to the controlling center.

X

Personal Information Access

Personal Mayday I/F The personal traveler interface shall provide the capability for a traveler to report an emergency and summon assistance.

X


Personal Mayday I/F The personal traveler interface shall provide the capability to accept input from a traveler via a panic button or some other functionally similar form of input device provided as part of the traveler's personal portable device.

X


Personal Mayday I/F When initiated by a traveler, the personal traveler interface shall forward a request for assistance to the center containing the traveler's current location and identity.

X


Personal Mayday I/F The personal traveler interface shall acknowledge the request for emergency assistance.

X

Remote Traveler Support Remote Transit Fare Management

The public interface for travelers shall support use of a common electronic payment instrument for payment of transit fares.

X X X




State-wide


Remote Traveler Support Remote Transit Fare Management

The public interface for travelers shall support the purchase of common electronic payment instrument for use on regional transit systems.

X X X

Roadway Subsystem Field Barrier System Control The field element shall return barrier system operational status to the controlling center.

X

Roadway Subsystem Field Barrier System Control The field element shall return barrier system fault data to the maintenance center for repair.

X

Roadway Subsystem Field Barrier System Control The field element shall activate barrier systems for transportation facilities and infrastructure under center control.

X X

Roadway Subsystem Field Safeguard System Control

The field element shall activate safeguard systems, equipment used to mitigate the impact of incidents on transportation infrastructure (e.g., blast shields, tunnel exhaust systems, etc.) under center control.

X


The field element shall return safeguard system operational status to the controlling center.

X


The field element shall return safeguard system fault data to the maintenance center for repair.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall collect, process, and send traffic images to the center for further analysis anddistribution.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall collect, digitize, and send pedestrian sensor data to the center for further analysis and storage.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall collect, process, and send pedestrian images to the center for further analysis and distribution.

X




State-wide


Roadway Subsystem Roadway Basic Surveillance The field element shall collect, digitize, and send multimodal crossing and high occupancy vehicle (HOV) lane sensor data to the center for further analysis and storage.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall return sensor and CCTV system operational status to the controlling center.

X

Roadway Subsystem Roadway Basic Surveillance The field element shall return sensor and CCTV system fault data to the controlling center for repair.

X

Roadway Subsystem Roadway Data Collection The field element shall collect traffic, road, and environmental conditions information.

X X

Roadway Subsystem Roadway Data Collection The field element shall include the sensors and supporting roadside devices that sense, collect, and send traffic, road, and environmental conditions information to a center for archival.

X X

Roadway Subsystem Roadway Data Collection The field element shall collect sensor status and sensor faults from roadside equipment and send it along with the recorded data to a center for archival.

X X

Roadway Subsystem Roadway Environmental Monitoring

The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.

X


The field element shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.

X


The field element's environmental sensors shall be remotely controlled by a maintenance center.

X


The field element's environmental sensors shall be remotely controlled by a traffic management center.

X


The field element's environmental sensors shall be remotely controlled by weather service providers such as the National Weather Service or value-added sector specific meteorological services.

X




State-wide



The field element shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle.

X X


The field element shall provide environmental sensor equipment fault indication to the controlling center or maintenance vehicle.

X X


The field element shall provide weather and road surface condition data to centers.

X X

Roadway Subsystem Roadway Equipment Coordination

The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic signals, work zone intrusion alert systems), without center control.

X


The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that receive control information from other field element devices, without center control.

X


The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems, barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent intersections), without center control.

X


The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems, barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive control information from other field element devices, without center control.

X




State-wide


Roadway Subsystem Roadway Freeway Control The field element shall include ramp metering controllers for use on freeways, under center control.

X

Roadway Subsystem Roadway Freeway Control The field element shall monitor operation of ramp meter indicators and report to the center any instances in which the indicator response does not match that expected from the indicator control information.

X

Roadway Subsystem Roadway Freeway Control The field element shall monitor operation of ramp meter indicators and report to the center any instances in which the indicator response does not match that expected from known indicator preemptions.

X

Roadway Subsystem Roadway Freeway Control The field element shall return ramp metering controller operational status to the controlling center.

X

Roadway Subsystem Roadway Freeway Control The field element shall return ramp metering controller fault data to the maintenance center for repair.

X

Roadway Subsystem Roadway Freeway Control The field element shall provide indications to the driver via dynamic message signs informing the driver that a freeway ramp is available for use, and possible lane usage data for the freeway they are entering.

X

Roadway Subsystem Roadway Incident Detection The field element shall collect, process, and send traffic images to the center for further analysis and distribution.

X

Roadway Subsystem Roadway Incident Detection The field element shall remotely process video data and provide an indication of potential incidents to the traffic management center.

X

Roadway Subsystem Roadway Incident Detection The field element's video devices shall be remotely controlled by a traffic management center.

X

Roadway Subsystem Roadway Incident Detection The field element shall provide operational status and fault data for the incident detection devices to the traffic management center.

X




State-wide


Roadway Subsystem Roadway Infrastructure Monitoring

The field element shall include infrastructure condition monitoring sensors that monitor the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., culverts), under maintenance center control.

X


The field element shall provide operational status for the infrastructure condition monitoring sensors to the maintenance center.

X


The field element shall provide fault data for the infrastructure condition monitoring sensors to the maintenance center for repair.

X

Roadway Subsystem Roadway Traffic Information Dissemination

The field element shall include driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers, under center control.

X


The field element shall include pedestrian information systems under center control (e.g. warning pedestrians of a potential hazard, or providing mandatory instructions as to the availability of pedestrian access).

X


The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.

X


The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for repair.

X


The field element shall include dynamic messages signs for dissemination of traffic and other information to drivers, under center control.

X X

Roadway Subsystem Roadway Work Zone Traffic Control

The field element shall collect, process, and send work zone images to the center for further analysis and distribution, under center control.

X




State-wide



Under traffic and maintenance center control, the field element shall include driver information systems (such as dynamic messages signs and highway advisory radios) that advise drivers of activity around the work zone through which they are currently passing.

X


The field element shall provide operational status for the surveillance (e.g. CCTV) and driver information systems in work zones to the maintenance center.

X


The field element shall provide fault data for the surveillance (e.g. CCTV) and driver information systems in work zones to the maintenance center for repair.

X

Security Monitoring Subsystem

Field Secure Area Sensor Monitoring

The field element shall include security sensors that monitor conditions of secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).

X



The field element shall be remotely controlled by a center.

X



The field element shall provide equipment status and fault indication of security sensor equipment to a center.

X



The field element shall include environmental threat sensors (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological).

X



The field element shall include infrastructure condition and integrity monitoring sensors.

X



The field element shall include motion and intrusion detection sensors.

X



The field element shall include object detection sensors (such as metal detectors).

X



The field element shall provide raw security sensor data.

X




State-wide




The field element shall remotely process security sensor data and provide an indication of potential incidents or threats to a center.

X


Field Secure Area Surveillance The field element shall include video and/or audio surveillance of secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).

X


Field Secure Area Surveillance The field element shall be remotely controlled by a center.

X


Field Secure Area Surveillance The field element shall provide equipment status and fault indication of surveillance equipment to a center.

X


Field Secure Area Surveillance The field element shall provide raw video or audio data.

X


Field Secure Area Surveillance The field element shall remotely process video and audio data and provide an indication of potential incidents or threats to a center.

X

Toll Administration Toll Administration The center shall exchange data with other toll agencies to coordinate toll transactions and pricing.

X

Toll Administration Toll Administration The center shall support wide-area alerts from emergency centers by passing on the information to its toll plazas and the Toll Administrator.

X

Toll Administration Toll Administration The center shall support toll transactions by commercial fleet operators.

X

Toll Administration Toll Administration The center shall process the financial information from toll plazas when electronic toll payments are made and manage an interface to a Financial Institution.

X X

Toll Administration Toll Data Collection The center shall collect toll operational data and pricing data.

X

Toll Administration Toll Data Collection The center shall receive and respond to requests from ITS Archives for either a catalog of the toll data or for the data itself.

X




State-wide


Toll Administration Toll Data Collection The center shall be able to produce sample products of the data available.

X

Toll Administration Toll Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X

Toll Administration Toll Operator Alert The center shall receive wide-area alerts and advisories from emergency management centers for emergency situations such as severe weather events, civil emergencies, child abduction (AMBER alert system), military activities, and other situations that pose a threat to life and property.

X

Toll Administration Toll Operator Alert The center shall return status back to the emergency management center that initiated the wide-area alert with information indicating the status of the alert from the toll operators including the information systems that are being used to provide the alert notification.

X

Toll Collection Toll Plaza Toll Collection The field element shall read data from vehicle toll tags to support toll payment transactions.

X X

Toll Collection Toll Plaza Toll Collection The field element shall update the toll tag value after debiting the toll amount and send a record of the transaction to a center.

X X

Toll Collection Toll Plaza Toll Collection The field element shall read the credit identity on the toll tag and send that identity and the amount to be debited to a center.

X X

Toll Collection Toll Plaza Toll Collection In the case of closed toll systems, the field element shall update the toll tag with the system entry point, and upon toll system exit, used in the calculation of the toll.

X X

Traffic Management Barrier System Management The center shall remotely control barrier systems for transportation facilities and infrastructure. Barrier systems include automated or remotely controlled gates, barriers and other systems that manage entry to roadways.

X

Traffic Management Barrier System Management The center shall collect barrier system operational status.

X




State-wide


Traffic Management Collect Traffic Surveillance The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.

X

Traffic Management Collect Traffic Surveillance The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.

X

Traffic Management Collect Traffic Surveillance The center shall monitor, analyze, and store pedestrian sensor data collected from field elements under remote control of the center.

X

Traffic Management Collect Traffic Surveillance The center shall monitor, analyze, and distribute pedestrian images from CCTV systems under remote control of the center.

X

Traffic Management Collect Traffic Surveillance The center shall monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data under remote control of the center.

X

Traffic Management Collect Traffic Surveillance The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic data.

X

Traffic Management Collect Traffic Surveillance The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.

X

Traffic Management Collect Traffic Surveillance The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.

X

Traffic Management Collect Traffic Surveillance The center shall maintain a database of surveillance and sensors for freeways, surface street and rural roadways.

X X

Traffic Management Safeguard System Management

The center shall remotely control safeguard systems, equipment used to mitigate the impact of incidents on transportation infrastructure (e.g., blast shields, tunnel exhaust systems, etc.)

X




State-wide



The center shall collect safeguard system operational status.

X


The center shall collect safeguard system fault data and send to the maintenance center for repair.

X

Traffic Management TMC Environmental Monitoring The center shall remotely control environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.

X

Traffic Management TMC Environmental Monitoring The center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.

X

Traffic Management TMC Environmental Monitoring The center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway.

X

Traffic Management TMC Environmental Monitoring The center shall provide weather and road condition information to weather service providers and center personnel.

X

Traffic Management TMC Environmental Monitoring The center shall respond to control data from center personnel regarding environmental sensor control and weather data collection and processing.

X

Traffic Management TMC Evacuation Support The center shall coordinate planning for evacuation with emergency management centers - including pre-planning activities such as establishing routes, areas to be evacuated, timing, etc.

X

Traffic Management TMC Evacuation Support The center shall support requests from emergency management centers to preempt the current traffic control strategy, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems to support evacuation traffic control plans.

X




State-wide


Traffic Management TMC Evacuation Support The center shall coordinate information and controls with other traffic management centers.

X

Traffic Management TMC Evacuation Support The center shall coordinate execution of evacuation strategies with emergency management centers - including activities such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.

X

Traffic Management TMC Freeway Management The center shall remotely control systems to manage use of the freeways, including ramp meters, mainline metering/lane controls.

X

Traffic Management TMC Freeway Management The center shall collect operational status from ramp meters, mainline metering/lane controls and compare against the control information sent by the center.

X

Traffic Management TMC Freeway Management The center shall collect fault data from ramp meters, mainline metering/lane controls.

X

Traffic Management TMC Freeway Management The center shall implement control strategies, under control of center personnel, on some or all of the freeway network devices (e.g. ramp meters, mainline metering/lane controls), based on data from sensors monitoring traffic conditions upstream, downstream, and queue data on the ramps themselves.

X

Traffic Management TMC Incident Detection The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.

X

Traffic Management TMC Incident Detection The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, and intermodal freight depots.

X

Traffic Management TMC Incident Detection The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.

X




State-wide


Traffic Management TMC Incident Detection The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field.

X

Traffic Management TMC Incident Detection The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.

X

Traffic Management TMC Incident Detection The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.

X

Traffic Management TMC Incident Dispatch Coordination/Communication

The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.

X


The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.

X


The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.

X


The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, and rail operations centers.

X


The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.

X




State-wide



The center shall exchange road network status assessment information with emergency management and maintance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.

X


The center shall coordinate information and controls with other traffic management centers.

X


The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.

X


The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic incident management.

X


The center shall exchange alert information and status information (including disaster information, child abduction information, the nature of the emergency, public responder instructions and information not available to the general public) with emergency

X X


The center shall respond to requests from emergency management to provide traffic management resources to implement special traffic control measures, assist in clean up, ord verify an incident (which may involve coordination with maintenance centers).

X X

Traffic Management TMC Regional Traffic Control The center shall exchange traffic information with other traffic management centers, includes incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.

X




State-wide


Traffic Management TMC Regional Traffic Control The center shall exchange traffic control information with other traffic management centers, includes remote monitoring and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).

X

Traffic Management TMC Signal Control The center shall remotely control traffic signal controllers.

X

Traffic Management TMC Signal Control The center shall accept notifications of right-of-way requests from pedestrians.

X

Traffic Management TMC Signal Control The center shall collect traffic signal controller operational status and compare against the control information sent by the center.

X

Traffic Management TMC Signal Control The center shall collect traffic signal controller fault data from the field.

X

Traffic Management TMC Signal Control The center shall implement control plans to coordinate signalized intersections, under control of center personnel, based on data from sensors and surveillance monitoring traffic conditions, incidents, emergency vehicle preemptions, the passage of commercial vehicles with unusual loads, equipment faults, pedestrian crossings, etc.

X

Traffic Management TMC Traffic Information Dissemination

The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.

X


The center shall remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.

X


The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).

X


The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.

X




State-wide



The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), etc.

X


The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, and traveler information providers.

X


The center shall provide the capability for center personnel to control the nature of the data that is available to non-traffic operations centers and the media.

X

Traffic Management TMC Work Zone Traffic Management

The center shall receive work zone images from a maintenance center.

X


The center shall analyze work zone images for indications of a possible incident.

X


The center shall remotely control driver information systems (such as dynamic messages signs, highway advisory radios) to advise drivers of activity around a work zone.

X


The center shall collect operational status for the driver information systems equipment in work zones.

X


The center shall collect fault data for the driver information systems equipment in work zones for repair.

X

Traffic Management Traffic Data Collection The center shall collect traffic management data such as operational data, event logs, etc.

X

Traffic Management 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 itself.

X

Traffic Management Traffic Data Collection The center shall be able to produce sample products of the data available.

X




State-wide


Traffic Management Traffic Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X

Traffic Management Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.

X

Traffic Management Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.

X

Traffic Management Traffic Maintenance The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance center for repair.

X

Traffic Management Traffic Maintenance The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.

X

Traffic Management Traffic Maintenance The center shall collect environmental sensor operational status.

X

Traffic Management Traffic Maintenance The center shall collect environmental sensor equipment fault data and send to the maintenance center for repair.

X

Traffic Management Traffic Maintenance The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic maintenance data.

X

Traffic Management Traffic Maintenance The center shall exchange data with maintenance centers concerning the reporting of faulty equipment and the schedule/status of their repair.

X X

Transit Management Transit Center Fare and Load Management

The center shall process the financial requests from the transit vehicles or roadside and manage an interface to a Financial Institution.

X


The center shall support the payment of transit fare transactions using data provided by the traveler cards / payment instruments.

X X




State-wide



The center shall exchange fare and load information with other transit management centers, including potential Centralized Payments facilities.

X


The center shall provide transit fare information to other centers, including traveler information providers upon request.

X


The element shall support fare reconciliation with other agencies using a common fare media.

X X

Transit Management Transit Center Information Services

The center shall exchange transit schedules, real-time arrival information, fare schedules, and general transit service information with other transit organizations to support transit traveler information systems.

X


The center shall provide transit service information to traveler information service providers including routes, schedules, schedule adherence, and fare information as well as transit service information during evacuation.

X


The center shall broadcast transit advisory data, including alerts and advisories pertaining to major emergencies, or man made disasters.

X X

Transit Management Transit Center Multi-Modal Coordination

The center shall coordinate schedules and services between transit agencies, traffic management, maintenance and construction operations, parking management, and other surface or air transportation modes.

X


The center shall share transfer cluster and transfer point information with multimodal transportation service providers, other transit agencies, and traveler information service providers. A transfer cluster is a collection of stops, stations, or terminals where transfers can be made conveniently.

X


The element shall coordinate with transit agencies within its service region to provide connection protection for travelers.

X X




State-wide



The element shall receive static or real-time service information from transit agencies throughout the service area of the element.

X X


The element shall send static or real-time service information to transit agencies throughout the service area of the element.

X X

Transit Management Transit Center Security The center shall exchange transit incident information along with other service data with other transit agencies.

X

Transit Management Transit Center Security The center shall receive information pertaining to a wide-area alert such as weather alerts, disaster situations, or child abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.

X

Transit Management Transit Center Security The center shall receive threat information and status on the integrity of the transit infrastructure.

X

Transit Management Transit Center Security The center shall receive information pertaining to a wide-area alert such as weather alerts, disaster situations, or child abductions.

X X

Transit Management Transit Data Collection The center shall collect transit management data such as transit fares and passenger use, transit services, paratransit operations, transit vehicle maintenance data, etc.

X

Transit Management 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 itself.

X

Transit Management Transit Data Collection The center shall be able to produce sample products of the data available.

X

Transit Management Transit Data Collection The center shall assign quality control metrics and meta-data to be stored along with the data.

X X

Transit Management Transit Evacuation Support The center shall manage the use of transit resources to support evacuation and subsequent reentry of a population in the vicinity of a disaster or other emergency.

X




State-wide


Transit Management Transit Evacuation Support The center shall coordinate regional evacuation plans with Emergency Management - identifying the transit role in an evacuation and the transit resources that would be used.

X

Transit Management Transit Evacuation Support The center shall coordinate the use of transit and school bus fleets during an evacuation, supporting evacuation of those with special needs and the general population.

X

Transit Management Transit Evacuation Support The center shall adjust and update transit service and fare schedules and provide that information to other agencies as they coordinate evacuations.

X

Transit Vehicle Subsystem On-board Transit Fare and Load Management

The transit vehicle shall support the support the payments of transit fares via a common electronic payment instrument.

X X X

Vehicle Vehicle Toll/Parking Interface The vehicle shall respond to requests from toll collection equipment for tag information including credit identity, stored value card cash, etc.

X X

Vehicle Vehicle Toll/Parking Interface The vehicle shall provide an interface with the traveler card / payment instrument carried on-board the vehicle (tag) - to exchange identity information and payment transactions.

X X

091783000 California ITS Architecture and System Plan Appendix A8 - Elements and Interfaces.doc 1 Appendix A8: Elements and Interfaces Final- September 30, 2004

APPENDIX A8: ELEMENTS AND INTERFACES (PRINTABLE DOCUMENT)

The California Statewide ITS Architecture focuses on state-level and interregional services in California that will supplement the regional ITS Architectures and deployment plans to ensure that statewide and interregional services are deployed in an integrated and cost-effective manner. The Interfaces web page provides a set of hyperlinks to the complete statewide ITS architecture information, spanning all Caltrans districts and planning regions in the state. Information for a particular district or region can be accessed by returning to the “Project Reports” page and selecting “Regional”. The web page also provides access to the following existing and planned information: § Stakeholders; § ITS Elements (organized by stakeholder and by National ITS Architecture entity); § Market Packages; § Interfaces and Information Flows; and § Functional Requirements. This information has been generated from a Turbo Architecture database which defines the entire Statewide ITS Architecture. The source database in Microsoft Access format is also available for downloading. A primary purpose of the architecture is to identify the interregional and statewide connectivity between California transportation systems. The following table identifies every interface defined for the statewide architecture. Each entry in the “Interfacing Element” column is a link to more detailed information about the particular interface. The individual element interfaces can be accessed on the California Statewide ITS Architecture and System Plan web site, located at http://www.kimley-horn.com/caarchitecture/task9/intro.htm, by clicking on the “Interfaces” button.

Element Interfacing Element Amtrak Schedule Operations Metrolink Operations Center

California HPMS Archive Data User Systems

Caltrans District Pavement Management Systems Caltrans District 11 Transportation Management Center Arizona DOT TMCs



Commercial Vehicles Safety and Fitness Electronic Report (SAFER)

ASPEN


Baja Transportation Management Center Caltrans District 11 Transportation Management Center

California Office of Emergency Services Operations Centers CHP Dispatch Centers



Central California Transit Systems Bay Area Transit Administration



Element Interfacing Element Bay Area Transit Administration (continued) Northern California Transit Systems

Bay Area Transit Stations and Stops Translink Smartcard Bay Area Transit Vehicles Translink Smartcard

CHP Dispatch Centers BCBP Offices


California Highway Information Network(CHIN) California Highway Information Web Page

Caltrans District Web pages

Broadcast and Print Media

CHP Dispatch Centers

CHP Commercial Vehicle Section CHP Weigh-In-Motion/ Inspection stations


CVO Pre-Pass Sites

IFTA Clearinghouse IRP Clearinghouse


Safestat Database


CA CVIEW

Single State Registration System (SSRS)

Caltrans Weigh-In-Motion Stations CA DMV Enforcement Vehicles

CHP Weigh-In-Motion/ Inspection stations

CHP Commercial Vehicle Section Commercial Vehicles




Broadcast and Print Media Caltrans District Maintenance Dispatch

Central California Transit Systems CHP Dispatch Centers County Public Safety Dispatch Centers CVO ATIS Truckstop Kiosks Municipal Public Safety Dispatch Northern California Transit Systems Regional Integration of ITS (RIITS) Regional Transit Information System (RTIS) Southern California Transit Systems Special Police Force Dispatch


User Personal Computing Devices Broadcast and Print Media


CVO ATIS Truckstop Kiosks




Element Interfacing Element Archive Data User Systems

Caltrans District 1 Transportation Management Center Caltrans District 10 Transportation Management Center



Caltrans District 2 Transportation Management Center Caltrans District 3 Regional Transportation Management Center






Caltrans Satellite TMCs

California HPMS

Regional Transportation Management Information System (RTMIS) Central California 511 Systems California National Parks and National Forests

Northern California 511 Systems


Caltrain Operations Center Caltrans District 1 Transportation Management Center









Caltrans District 9 Transportation Management Center Caltrans District Maintenance Dispatch



CHP Dispatch Centers County and Local Emergency Operation Centers


Los Angeles County Metro - Bus Operations

Los Angeles County Metro - Rail Dispatch Center


Metrolink Operations Center


Element Interfacing Element Municipal Publc Safety Dispatch

Municipal/County Traffic Operations Northern California 511 Systems


Northern California Traveler Information Systems

San Francisco MUNI Operations Southern California Transit Systems

Southern California Traveler Information Systems

California Office of Emergency Services Operations Centers (continued)

TravInfo

Central California Transit Systems Northern California Transit Systems

Regional Integration of ITS (RIITS)




Transit Data Users



Caltrain Operations Center

County and Local Emergency Operation Centers California HPMS



Caltrans District 3 Regional Transportation Management Center Caltrans District 4 Transportation Management Center



Caltrans Field Equipment Caltrans Performance Monitoring System (PeMS)



County Public Safety Dispatch Centers Intermodal Port Facility Systems

Municipal Publc Safety Dispatch

National Weather Service

Northern California 511 Systems ODOT Medford TOC

Private ISPs

Rail Operations Centers

Regional Traveler Information Systems Traffic Accident and Surveillance Analysis System(TASAS)


TravInfo


Element Interfacing Element California HPMS







Caltrans Field Equipment

Caltrans Performance Monitoring System (PeMS) Central California 511 Systems



County Public Safety Dispatch Centers Municipal Publc Safety Dispatch

Municipal/County Traffic Operations


Nevada DOT TMCs Private ISPs




Traffic Accident and Surveillance Analysis System(TASAS)

Arizona DOT TMCs Baja Transportation Management Center California HPMS






Caltrans Performance Monitoring System (PeMS) CHP Dispatch Centers



Intermodal Port Facility Systems Municipal Publc Safety Dispatch



Private ISPs


Element Interfacing Element Rail Operations Centers

Regional Traveler Information Systems Southern California Traveler Information Systems

Caltrans District 11 Intermodal Transportation Management Center (continued)


California HPMS

California Office of Emergency Services Operations Centers Caltrans District 11 Intermodal Transportation Management Center



Caltrans District Maintenance Dispatch Caltrans District Web pages





Intermodal Port Facility Systems

Municipal Publc Safety Dispatch National Weather Service

Private ISPs


Regional Traveler Information Systems Southern California Traveler Information Systems




California HPMS California Office of Emergency Services Operations Centers










Nevada DOT TMCs




Element Interfacing Element ODOT Medford TOC

Private ISPs Rail Operations Centers



Caltrans District 2 Transportation Management Center (continued)

TravInfo California HPMS






Caltrans District Web pages Caltrans Field Equipment



County and Local Emergency Operation Centers County Public Safety Dispatch Centers



Nevada DOT TMCs Northern California 511 Systems

Private ISPs


Regional Traveler Information Systems Traffic Accident and Surveillance Analysis System(TASAS)


TravInfo

California HPMS

California Office of Emergency Services Operations Centers Caltrans District 1 Transportation Management Center







Caltrans Security Monitoring Equipment




Element Interfacing Element County and Local Emergency Operation Centers

County Public Safety Dispatch Centers Intermodal Port Facility Systems







TravInfo California HPMS












National Weather Service Private ISPs





TravInfo

California HPMS










Element Interfacing Element Caltrans Performance Monitoring System (PeMS)

Central California 511 Systems CHP Dispatch Centers




Private ISPs





California HPMS





Caltrans District Maintenance Dispatch Caltrans District Web pages



Caltrans Security Monitoring Equipment CHP Dispatch Centers



Intermodal Port Facility Systems Municipal Publc Safety Dispatch


Private ISPs

Rail Operations Centers Regional Traveler Information Systems




California HPMS California Office of Emergency Services Operations Centers








Element Interfacing Element Caltrans District Web pages




County Public Safety Dispatch Centers Municipal Publc Safety Dispatch


Nevada DOT TMCs







California HPMS











National Weather Service Nevada DOT TMCs

Private ISPs












Element Interfacing Element Caltrans District 12 Transportation Management Center







Caltrans District Pavement Management Systems Caltrans District Web ages


Caltrans HQ Construction Program

Caltrans Maintenance Administration Caltrans Maintenance Vehicles



Central California 511 Systems CHP Dispatch Centers


County Maintenance Dispatch

Municipal Maintenance Dispatch National Weather Service


Other Caltrans District Maintenance

Other States Maintenance Dispatch Centers Private ISPs




Caltrans District Maintenance Dispatch (continued)

TravInfo

Caltrans District Maintenance Dispatch Caltrans District Pavement Management Systems


Broadcast and Print Media Caltrans District 1 Transportation Management Center












Caltrans District Maintenance Dispatch CHP Dispatch Centers

County Public Safety Dispatch Centers CVO ATIS Truckstop Kiosks Municipal Public Safety Dispatch Northern California Transit Systems Regional Integration of ITS (RIITS) Regional Transit Information System (RTIS) Southern California Transit Systems

Caltrans District Web pages (continued)

User Personal Computing Devices Caltrans District 1 Transportation Management Center

Caltrans District 10 Transportation Management Center Caltrans District 11 Intermodal Transportation Management Center











Other Caltrans Field Equipment

Caltrans HQ Construction Program Caltrans District Maintenance Dispatch

Caltrans HQ Traffic Operations Databases Caltrans Weigh-In-Motion Stations

Caltrans Maintenance Administration Caltrans District Maintenance Dispatch Caltrans Maintenance Vehicles Caltrans District Maintenance Dispatch



Caltrans District 11 Intermodal Transportation Management Center Caltrans District 12 Transportation Management Center











Caltrans Performance Monitoring System (PeMS) (continued)

PeMS Users California HPMS







Rail Operations Centers Caltrans District 4 Transportation Management Center Caltrans Security Monitoring Equipment


Archive Data User Systems



Caltrans District Pavement Management Systems

CA DMV Enforcement Vehicles

Caltrans HQ Traffic Operations Databases

Caltrans Weigh-In-Motion Stations

Commercial Vehicles California National Parks and National Forests






Central California Transit Systems CHP Dispatch Centers

In Vehicle Equipment

Private ISPs





Translink Smartcard







Element Interfacing Element Central California 511 Systems

CHP Dispatch Centers Metrolink Operations Center



Private ISPs Regional Integration of ITS (RIITS)


Central California Transit Systems (continued)


Central California Transit Vehicles Translink Smartcard ASPEN

CA CVIEW


CHP Weigh-In-Motion/ Inspection stations CVO Automatic Safety Inspection Devices

CVO OS/OW Permitting Processing System

CVO Pre-Pass Sites


Safety and Fitness Electronic Report (SAFER) BART Fleet Management System

BCBP Offices

Broadcast and Print Media California Highway Information Network(CHIN)


Caltrain Operations Center











Caltrans District Web pages Caltrans Satellite TMCs





Element Interfacing Element CHP Weigh-In-Motion/ Inspection stations

Commercial Vehicle Fleet Management Commercial Vehicles

Correctional Facility Operations


County Public Safety Dispatch Centers CVO Pre-Pass Sites

Hazmat Freight Containers

Hazmat Permitting System

Intermodal Port Facility Systems Los Angeles County Metro - Bus Operations



Municipal Publc Safety Dispatch Municipal/County Traffic Operations



Northern California Electronic Toll Systems Northern California Transit Systems

Operation Respond

Other CHP Dispatch Centers

San Francisco MUNI Operations Southern California Electronic Toll Systems



Special Police Force Dispatch Statewide Integrated Reporting System (SWITRS)

Telematics Service Provider

CHP Dispatch Centers (continued)

TravInfo

CA CVIEW CA DMV Enforcement Vehicles



Commercial Vehicles

CHP Weigh-In-Motion/Inspection stations


CVO Pre-Pass Sites Commercial Drivers License Information System (CDLIS) US BCBP Customs Product Manifest System

CHP Dispatch Centers Commercial Vehicles





Element Interfacing Element CVO OS/OW Permitting Processing System

Intermodal Port Facility Systems Multi-Agency CVO Web-site


Commercial Vehicle Fleet Management (Continued)


ASPEN California Commercial Vehicle Inspection System (CCVIS)

Caltrans Weigh-In-Motion Stations


CHP Weigh-In-Motion/ Inspection stations Commercial Vehicle Fleet Management


CVO Automatic Safety Inspection Devices

CVO Pre-Pass Sites Municipal Publc Safety Dispatch

Commercial Vehicles

US BCBP Electronic Clearance System for International Borders





BART Fleet Management System Bay Area Transit Administration California Office of Emergency Services Operations Centers Caltrain Operations Center Caltrans District 1 Transportation Management Center Caltrans District 10 Transportation Management Center









Caltrans District Maintenance Dispatch Central California Transit Systems CHP Dispatch Centers Commercial Vehicle Fleet Management Commercial Vehicles Correctional Facility Operations




Element Interfacing Element Hazmat Freight Containers Hazmat Permitting System Los Angeles County Metro - Bus Operations Los Angeles County Metro - Rail Dispatch Center Metrolink Operations Center Municipal Public Safety Dispatch Northern California Transit Systems Operation Respond Other County Emergency Operation Centers San Francisco MUNI Operations Southern California Transit Systems

County and Local Emergency Operation Centers (continued)

Special Police Force Dispatch County Maintenance Dispatch Caltrans District Maintenance Dispatch

BCBP Offices California Highway Information Network(CHIN)












Caltrans Satellite TMCs CHP Dispatch Centers



Intermodal Port Facility Systems Other County Public Safety Dispatch Centers




Telematics Service Provider CA CVIEW


Excise Summary Terminal Activity Reporting System (ExSTARS)


IFTA Clearinghouse


Element Interfacing Element IRP Clearinghouse Credentials One Stop Shopping (continued)


California Highway Information Network(CHIN) California Highway Information Web Page Caltrans District Web pages


Multi-Agency CVO Web-site CHP Commercial Vehicle Section

Commercial Vehicles Safety and Fitness Electronic Report (SAFER)

CVO Automatic Safety Inspection Devices

Statewide Integrated Reporting System (SWITRS) CA CVIEW CHP Commercial Vehicle Section Commercial Vehicle Fleet Management

CVO OS/OW Permitting Processing System

CVO Pre-Pass Sites CA CVIEW



Commercial Drivers License Information System (CDLIS) Commercial Vehicles

CVO Pre-Pass Sites

CVO OS/OW Permitting Processing System Credentials One Stop Shopping Excise Summary Terminal Activity Reporting

System (ExSTARS) US BCBP Customs Product Manifest System CHP Dispatch Centers







CA CVIEW IFTA Clearinghouse

Credentials One Stop Shopping Northern California Electronic Toll Collection Plazas In Vehicle Electronic Toll Tags



Northern California 511 Systems Private Application Service Providers




TravInfo Caltrans District 1 Transportation Management Center



Intermodal Port Facility Systems




CHP Dispatch Centers Commercial Vehicle Fleet Management


Intermodal Port Facility Systems (continued)


CA CVIEW IRP Clearinghouse Credentials One Stop Shopping

LAMTA Transit Station Equipment Southern California Fare Card

LAMTA Vehicles Southern California Fare Card

California Office of Emergency Services Operations Centers CHP Dispatch Centers

Los Angeles County Metro - Bus Operations






Metrolink Administration Los Angeles County MTA Administration


Safety and Fitness Electronic Report (SAFER) MCMIS Safetynet 2000

Los Angeles County MTA Administration Metrolink Administration


Amtrak Schedule Operations California Office of Emergency Services Operations Centers



County and Local Emergency Operation Centers Regional Integration of ITS (RIITS)





Multi-Agency CVO Web-site


Municipal Maintenance Dispatch Caltrans District Maintenance Dispatch














Caltrans District Web pages Caltrans Satellite TMCs



Commercial Vehicles County and Local Emergency Operation Centers



Intermodal Port Facility Systems Operation Respond


Municipal Publc Safety Dispatch (continued)


California Office of Emergency Services Operations Centers Municipal/County Traffic Operations CHP Dispatch Centers Caltrans District 1 Transportation Management Center










Central California Transit Systems CHP Dispatch Centers







Nevada DOT TMCs



Element Interfacing Element California National Parks and National Forests







Private ISPs Regional Transit Information System (RTIS)




Northern California Electronic Toll Collection Plazas


CHP Dispatch Centers Northern California Electronic Toll Systems Southern California Electronic Toll Systems


Translink Smartcard



California Office of Emergency Services Operations Centers California Transit Data Archive



County and Local Emergency Operation Centers National Weather Service


Private ISPs



TravInfo

Northern California Transit Vehicles Translink Smartcard

California Office of Emergency Services Operations Centers Northern California Traveler Information Systems

User Personal Computing Devices Caltrans District 1 Transportation Management Center ODOT Medford TOC




Operation Respond


Other Caltrans District Maintenance Caltrans District Maintenance Dispatch

Other Caltrans Field Equipment Caltrans Field Equipment

Other CHP Dispatch Centers CHP Dispatch Centers


Element Interfacing Element Other County Emergency Operation Centers County and Local Emergency Operation Centers

Other County Public Safety Dispatch Centers County Public Safety Dispatch Centers CA CVIEW Other States Credentials Admin and Safety

Systems Credentials One Stop Shopping

Other States Maintenance Dispatch Centers Caltrans District Maintenance Dispatch

PeMS Users Caltrans Performance Monitoring System (PeMS) In Vehicle Equipment

Private ISPs

Private Application Service Providers











Caltrans District Maintenance Dispatch Central California 511 Systems



Northern California Transit Systems Private Application Service Providers



Southern California Transit Systems Southern California Traveler Information Systems

Private ISPs

TravInfo













Rail Operations Centers (continued)


California Highway Information Network(CHIN) California Transit Data Archive Caltrans District Web pages Central California Transit Systems

Metrolink Operations Center Private ISPs




California Highway Information Network(CHIN) California Transit Data Archive Caltrans District Web pages Central California Transit Systems

Northern California 511 Systems Northern California Transit Systems

Private ISPs



TravInfo Regional Transportation Management Information System (RTMIS)

California HPMS













Safestat Database CA CVIEW

ASPEN

CA CVIEW California Commercial Vehicle Inspection System (CCVIS)




Element Interfacing Element CHP Weigh-In-Motion/ Inspection stations

CVO Automatic Safety Inspection Devices MCMIS

Safety and Fitness Electronic Report (SAFER) (continued)

Safetynet 2000

MCMIS Safetynet 2000

Safety and Fitness Electronic Report (SAFER) California Office of Emergency Services Operations Centers


San Francisco MUNI Operations

County and Local Emergency Operation Centers Single State Registration System (SSRS) CA CVIEW



CHP Dispatch Centers Southern California Electronic Toll Systems

Northern California Electronic Toll Systems LAMTA Transit Station Equipment

LAMTA Vehicles

Southern California Transit System Station and Transfer Points


Southern California Transit Vehicles Southern California Transit System Station and Transfer Points


California Highway Information Network(CHIN) California Office of Emergency Services Operations Centers California Transit Data Archive Caltrans District Web pages Central California Transit Systems CHP Dispatch Centers County and Local Emergency Operation Centers Los Angeles County MTA Administration Metrolink Administration






Southern California Transit Vehicles Southern California Fare Card


Caltrans District 11 Intermodal Transportation Management Center Caltrans District 12 Transportation Management Center







Element Interfacing Element Private ISPs

Regional Integration of ITS (RIITS) Southern California Transit Systems


Southern California Traveler Information Systems (continued)


California Highway Information Network(CHIN) Caltrans District Maintenance Dispatch




County Public Safety Dispatch Centers Central California 511 Systems




ASPEN California Commercial Vehicle Inspection System (CCVIS)



CVO Automatic Safety Inspection Devices Municipal Publc Safety Dispatch




County Public Safety Dispatch Centers In Vehicle Equipment



Caltrans District 12 Transportation Management Center Toll Road Transportation Management Centers


Caltrans District 1 Transportation Management Center Caltrans District 10 Transportation Management Center Caltrans District 11 Intermodal Transportation Management Center Caltrans District 12 Transportation Management Center Caltrans District 2 Transportation Management Center Caltrans District 3 Regional Transportation Management Center Caltrans District 4 Transportation Management Center Caltrans District 5 Transportation Management Center Caltrans District 6 Transportation Management Center Caltrans District 7 Transportation Management Center Caltrans District 8 Transportation Management Center Caltrans District 9 Transportation Management Center


Statewide Integrated Reporting System (SWITRS) Bay Area Transit Stations and Stops Bay Area Transit Vehicles

Translink Smartcard



Element Interfacing Element Central California Transit Vehicles


Translink Smartcard (continued)

Northern California Transit Vehicles









Private ISPs Regional Transit Information System (RTIS)

TravInfo


Commercial Drivers License Information System (CDLIS) Commercial Vehicle Fleet Management Excise Summary Terminal Activity Reporting System (ExSTARS)


US BCBP Electronic Clearance System for International Borders Commercial Vehicles US BCBP Electronic Clearance System for

International Borders US BCBP Customs Product Manifest System

California Highway Information Network(CHIN) California Highway Information Web Page Caltrans District Web pages Central California 511 Systems Multi-Agency CVO Web-site Northern California 511 Systems Northern California Traveler Information Systems Private Application Service Providers Southern California Traveler Information Systems


TravInfo

CCaalliiffoorrnniiaa IITTSS AArrcchhiitteeccttuurree aanndd SSyysstteemm PPllaann

Final Appendix A9 - Maintaining the Architecture (Maintenance Plan) Prepared by:

For:

September 30, 2004 091783000 Copyright © 2004, Kimley-Horn and Associates, Inc and Consensus Systems Technologies Corp.

TABLE OF CONTENTS MAINTAINING THE ARCHITECTURE

091783000 California ITS Architecture and System Plan Appendix A9 - Maintenance Plan.doc i Maintaining the Architecture Final – September 30, 2004

1. INTRODUCTION .................................................................................................................................. 1 1.1 Project Overview ....................................................................................................................... 1 1.2 Maintenance Plan Overview..................................................................................................... 1 1.3 Intended Audience ..................................................................................................................... 2 1.4 Plan Organization...................................................................................................................... 3

2. ROLES AND RESPONSIBILITIES FOR MAINTENANCE....................................................................... 4 2.1 Stakeholders ............................................................................................................................... 4 2.2 Responsible Agency ................................................................................................................... 6 2.3 Maintenance Working Group .................................................................................................. 6 2.4 Policy Committee ....................................................................................................................... 8 2.4 Maintenance Manager............................................................................................................... 8

3. TIMETABLE FOR MAINTENANCE .................................................................................................... 10 3.1 Introduction ............................................................................................................................. 10 3.2 What changes will impact the architecture? ......................................................................... 10 3.3 Timetable for Changes ............................................................................................................ 11

4. ARCHITECTURE BASELINE.............................................................................................................. 13 4.1 Introduction ............................................................................................................................. 13 4.2 Baseline Documents and Outputs........................................................................................... 13 4.3 Version Control........................................................................................................................ 14

4.3.1 Version Control Guidelines ............................................................................................. 15 4.3.2 Revision History............................................................................................................... 15 4.3.3 Baseline Availability ........................................................................................................ 16

5. CHANGE MANAGEMENT PROCESS ................................................................................................. 17 5.1 Introduction................................................................................................................................. 17 5.2 Identifying Changes................................................................................................................. 19

5.2.1 Who can Request a Change? ........................................................................................... 19 5.2.2 Defining the Change ........................................................................................................ 19

5.3 Evaluating Changes................................................................................................................. 21 5.4 Approving Changes ................................................................................................................. 21 5.5 Updating Architecture Baseline ............................................................................................. 22 5.6 Notifying Stakeholders ............................................................................................................ 23

APPENDIX A – GLOSSARY....................................................................................................................... 24

APPENDIX B – CHANGE REQUEST FORM .............................................................................................. 25

TABLE OF CONTENTS MAINTAINING THE ARCHITECTURE

091783000 California ITS Architecture and System Plan Appendix A9 - Maintenance Plan.doc ii Maintaining the Architecture Final – September 30, 2004

LIST OF FIGURES Figure 1 – Maintenance Organization Chart .............................................................................................. 4 Figure 2 – Change Management Process ................................................................................................. 18 LIST OF TABLES Table 1 – Architecture Baseline ............................................................................................................... 13 Table 2 – Project Outputs not includedArchitecture Baseline ................................................................. 14

091783000 California ITS Architecture and System Plan Appendix A9 - Maintenance Plan.doc iii Maintaining the Architecture Final – September 30, 2004

REVISION HISTORY

Filename Version Date Author Comment CalifMaintPlan-2-6-04.doc 0.00.01 02/06/04 B Eisenhart First draft

CalifMaintPlan 030904.doc 0.00.02 03/09/04 B. Eisenhart Revision of First Draft

Appendix A9 – Maintenance Plan.doc 1.00 9/30/04 B. Eisenhart Initial Baseline Release of Document

091783000 California ITS Architecture and System Plan Appendix A9 - Maintenance Plan.doc 1 Maintaining the Architecture Final – September 30, 2004

1. INTRODUCTION

1.1 Project Overview

New federal regulations require ITS projects funded with highway trust funds to conform to the National ITS Architecture and standards; be guided by a regional architecture of geographic boundaries defined by stakeholder needs; and use a system engineering analysis that considers the total project life cycle. These requirements are referred to as the Final Rule. The California ITS Architecture and System Plan will accomplish two goals in this context:

Compile an ITS architecture focusing on state-level and interregional services in California that will supplement the regional ITS Architectures and deployment plans to ensure that statewide and interregional services are deployed in an integrated and cost-effective manner, thereby adhering to the “regional architecture” requirement described in the above summary of the Final Rule for those projects developed at this level.

Develop a 10-year System Plan that describes the blueprint for deployment of specific projects that fall within this category of statewide or interregional services. Based on the Final Rule summarized above, each of these projects will require that a systems engineering approach be taken when it is developed and throughout the project life cycle.

The development process for the California ITS Architecture and System Plan considers ITS plans and architectures including regional ITS architectures and strategic deployment plans, the statewide Initiatives project, and the Caltrans draft Transportation Management Systems Master Plan and is developing a new Architecture and System Plan that focuses on the state-level and interregional systems in the state.

The general approach proposed for this project is one of public participation and a coalition building process that is fully integrated into the ITS Architecture and System Plan development. The approach is built around extensive interaction with and input by regional ITS stakeholders throughout the process and the end result will be an Architecture and System Plan that reflects the needs and goals of the transportation network from a state-level and interregional standpoint.

1.2 Maintenance Plan Overview

The California Statewide ITS Architecture and System Plan is a dynamic set of outputs. Following the completion of the first version of the architecture and system plan, it will need to be updated or maintained on a periodic basis in order to keep the contents up-to-date with the current and planned ITS activities throughout the State. This document describes the Maintenance Plan for keeping the California Statewide ITS Architecture and System Plan up-to-date and includes discussion of the major components of the Plan and how recommendations were developed (e.g., how often the document should be updated).

Other terms used for maintenance are configuration management or change management. Configuration management (or change management) is defined as: “A management process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design and operational information throughout its life” 1 and can

1 ANSI/EIA 649-1998, National Consensus Standard for Configuration Management


be applied to the development of any system. In the context of the California Statewide ITS Architecture and System Plan it is a process for establishing and maintaining consistency of the architecture’s information content throughout its life. In general, configuration management consists of five major activities:

Configuration management planning – making decisions about what needs to be controlled within a product configuration, when you establish a controlled configuration, how you change a controlled configuration, and what amount of effort you’re going to expend in managing configurations, with the decisions formalized in a configuration management plan. In the context of maintaining the California Statewide ITS Architecture and System Plan this corresponds to this Architecture Maintenance Plan (described in this report).

Configuration identification – identifying the configuration items and the unique identifiers that you use to keep track of all items that need to be independently identified, stored, tested, reviewed, used, changed, delivered and/or maintained. In the context of maintaining the California Statewide ITS Architecture and System Plan this corresponds to the architecture baseline (described in Section 4 below).

Configuration control – the control of which changes are made to the architecture baseline and when and how they are made.

Configuration status accounting – keeping track of the state of all configuration items, all pending proposed changes, and all approved changes to configuration items.

Configuration audits – verifying consistency of configuration documentation against the product. In the context of the California Statewide ITS Architecture and System Plan this includes verifying that different representations of the architecture (e.g., reports and database files) match.

This maintenance plan addresses the following four key areas:

Who will maintain the architecture? When will the maintenance happen? What will be maintained? How it will be maintained (i.e., what configuration control process will be used)?

1.3 Intended Audience

This Maintenance Plan document is intended primarily for stakeholders and stakeholder representatives directly involved with the maintenance of the California ITS Architecture. The majority of the persons participating with the architecture will not be directly involved with the actual initiation of the change management policies and procedures contained in this Maintenance Plan. However, all stakeholders, including planners, managers, and implementers, should be familiar with the highlights of the maintenance plan. These highlights include the purpose of the maintenance plan, what constitutes a change, the components of the architecture that are subject to the maintenance process, and how to initiate a change to the architecture.


1.4 Plan Organization

This Maintenance Plan is organized in five chapters to facilitate the different parts of a maintenance plan:

Chapter 1: Introduction – Provides introductory and background information about the project and this document.

Chapter 2: Roles and Responsibilities for Maintenance – This section defines the roles and responsibilities of each stakeholder in the maintenance of the California Statewide ITS Architecture and System Plan.

Chapter 3: Timetable for Maintenance – This section describes when changes to the architecture might occur.

Chapter 4: Baseline – This section describes what documents and other outputs are to be maintained by the process and procedures documented in this Maintenance Plan.

Chapter 5: Change Management Process – This section defines the process and the procedures to be used for initiating, accepting, and updating any changes to the architecture.


2. ROLES AND RESPONSIBILITIES FOR MAINTENANCE This section defines the stakeholders and their roles and responsibilities for the maintenance of the California ITS Architecture and System Plan. Each subsection provides an introduction describing the particular set of stakeholders considered followed by a description of their roles and responsibilities for the maintenance of the California ITS Architecture and System Plan.

The following stakeholder groups will have a role in the maintenance of the architecture:

Stakeholders – Any government agency or private organization that has a role in providing transportation services in the region.

Maintenance Working Group – The group of persons responsible for reviewing proposed changes to the California ITS Architecture and System Plan and for forwarding the proposed changes to the Policy Committee.

Policy Committee – The group of persons responsible for approving the proposed changes recommended by the Maintenance Working Group. They are also responsible for any policy or institutional decision-making.

Responsible Agency – The stakeholder agency responsible for supporting the maintenance of the architecture.

Maintenance Manager – The person(s) assigned by the Responsible Agency to lead the maintenance effort.

Figure 1 provides an organizational chart that depicts the relationships for each of these groups that will

be covered in more detail below.

Figure 1 – Maintenance Organization Chart

2.1 Stakeholders

Introduction

Stakeholders•Submit architecture changes•Participate in Maintenance Working Group

Stakeholders•Submit architecture changes•Participate in Maintenance Working Group

Maintenance Working Group

•Submit, review, and disposition changes to the architecture

Maintenance Working Group

•Submit, review, and disposition changes to the architecture

Policy Committee•Oversee maintenance effort and resolve policy or institutional issues

Policy Committee•Oversee maintenance effort and resolve policy or institutional issues

Responsible Agency•Agency responsible for architecture maintenance effort

Responsible Agency•Agency responsible for architecture maintenance effort

Maintenance Manager•Person(s) assigned by responsible agency to lead maintenance effort


Stakeholders are any government agency or private organization that is involved with or has an interest in providing transportation services in the state. Each stakeholder owns, operates, and/or maintains one or more ITS elements in the architecture. In some cases the elements of the architecture are owned by a single stakeholder (e.g., the Metrolink Rail Agency operates the Metrolink Operations Center in Southern California). In some cases the “stakeholder” represents a variety of individual agencies (e.g., the element Central California Transit Systems has as its stakeholder “Central California Transit Agencies”, which represent a variety of transit operators in the central part of the state).

Stakeholders are important to the change management process described in this Maintenance Plan because changes to the architecture start from changes in the scope, definition, and interconnection of the stakeholder elements.

Each stakeholder who has one or more elements in the California ITS Architecture should assign one or more authorized representatives who can submit or approve changes to their elements. The architecture created is a consensus architecture and changes to it should only be made with the concurrence of affected stakeholders. The stakeholder may also assign a point-of-contact for the agency to assist with day-to-day communications. The point-of-contact will receive updates regarding the status of the California ITS Architecture and System Plan and will be responsible for distributing these updates to the appropriate persons within their agency. The point-of-contact for the agency may be the same person as the Authorized Representative, or they may be different people.

Each stakeholder will be assigned to one or more ITS Planning Regions based upon their elements. ITS Planning Regions is a term used in this project to refer to informal alliances formed to address ITS planning under the combined jurisdiction of member agencies, MPO’s, RTPA’s, the State of California, cities, counties or some mix thereof. The following ITS Planning Regions are defined for the purposes of this effort. Key stakeholders from these ITS Planning Regions will form the basis for the makeup of the Maintenance Working Group and Policy Committee (described below).

The ITS Planning Regions are defined as:

Bay Area; North Central; Statewide (representing state-level

stakeholders such as Caltrans Headquarters);

Central Coast; National Parks; Northern California (representing the

California portion of COATS);

Sacramento Area; San Diego Area; San Joaquin Valley; Southern California; Sierra Nevada; Tahoe Basin; and Tahoe Gateway.

The assignment of stakeholders to ITS Planning Regions will serve as the path for introducing changes into the California ITS Architecture and System Plan relative to elements belonging to the stakeholder. Each stakeholder should assign someone to periodically gather information from within their agency on the status of their agency’s ITS systems. This person should collect the information and submit Change Requests to the member(s) of the Maintenance Working Group from their planning region.


Roles and Responsibilities

For the maintenance of the California ITS Architecture and System Plan, each Stakeholder has the following responsibilities:

Appoint one or more Authorized Representatives to submit changes and make decisions for the Stakeholder relative to maintenance of the California ITS Architecture and System Plan;

May appoint a point-of-contact for day-to-day communications regarding updates and status of the California ITS Architecture and System Plan;

Provide the Maintenance Manager or Responsible Agency with current contact list of all Authorized Representative(s) and point-of-contact(s);

Submit changes in the architecture relevant to their elements to the Planning Region representatives to the Maintenance Working Group;

Provide stakeholder staff to support evaluation of any change request impacting the stakeholder’s aspects of the architecture; and

Concur on changes in the architecture submitted through other sources that affect their elements. This concurrence would be provided to the appropriate Planning Region representatives to the Maintenance Working Group.

If stakeholders desire more involvement, they can get involved through voluntary representation on the Maintenance Working Group.

2.2 Responsible Agency

Introduction

The Responsible Agency is the government agency that will formally maintain the California ITS Architecture and System Plan. The Responsible Agency will assign resources for making the physical changes to the architecture baseline and for coordinating the maintenance of the architecture. A Maintenance Manager may be assigned by the responsible agency as being the individual responsible for the activities required by that agency to maintain the architecture.

For the maintenance of the California ITS Architecture, the Responsible Agency will be Caltrans Headquarters.


For the maintenance of the California ITS Architecture and System Plan, the Responsible Agency has the following responsibilities:

Identifies resources for maintaining the architecture baseline; and Assign a person (or persons) to be the Maintenance Manager for the architecture.

2.3 Maintenance Working Group

Introduction

The ITS Architecture Maintenance Working Group, or the Maintenance Working Group, consists of representatives from each ITS Planning Region (described above) responsible for reviewing submitted Change Requests. The Maintenance Working Group evaluates all proposed changes to


the California ITS Architecture and System Plan, reaches a consensus on the proposed change, and makes a recommendation to the Policy Committee on the disposition of the Change Request.

Any agency identified as a Stakeholder in the California ITS Architecture and System Plan may assign representative(s) to the Maintenance Working Group to participate in discussions about proposed changes to the architecture.

The Maintenance Working Group members, particularly the ITS Planning Region representatives, will need to commit some time and effort to the change management process. The level of effort required will be a function of how many changes are brought forward, which cannot be known at this stage in the development of the plan. Funding considerations do need to be addressed in order to have adequate participation in the change management process.

The Maintenance Working Group should consist of the following members:

One voting member from each ITS Planning Region. The voting member represents the ITS Planning Region;

A designated alternate voting member from each ITS Planning Region (who can act for the voting member in their absence); and

Voluntary representatives of stakeholders or agencies that are part of the ITS Planning Region.

Note: it is the responsibility of each ITS Planning Region to select a voting member and alternate voting member.

Any agency identified as a Stakeholder in the California ITS Statewide Architecture (See Section 2.1, Stakeholders) may participate in the Maintenance Working Group. Other agencies or organizations that wish to participate in the Maintenance Working Group must be identified as a “guest” of a current Stakeholder. FHWA and FTA representatives, and any consultant hired on behalf of stakeholders to assist with the maintenance of the California ITS Architecture and System Plan, may also participate in the Maintenance Working Group. The Maintenance Manager shall maintain the list of stakeholders along with their association with ITS Planning Regions.

Chairperson

The Maintenance Working Group shall elect a Chairperson to conduct the meetings. The Chairperson shall be responsible for calling meetings, leading the meetings, and reporting to the Policy Committee.

A Chairperson shall be elected for a two-year term by a majority vote of the voting members present. If the Chairperson is unable to attend a meeting, the Maintenance Manager shall act as the Chairperson, or the Chairperson may appoint another representative to act in his/her place.

Election of the Chairperson will be the first action of the first Maintenance Working Group meeting.


The primary responsibilities of the Maintenance Working Group are:


Collecting and compiling proposed major and minor changes to the architecture from stakeholders within the ITS Planning Regions. (Major and minor changes are discussed in more detail below in Section 5.1);

Review submitted Change Request forms from a technical standpoint and consider the effects of the proposed changes to the California ITS Architecture and System Plan;

Reaching a consensus on the proposed changes, and dispositioning the changes (i.e. deciding to approve, reject, or defer the change.) One additional possible output of this dispositioning is to refer the change to the Policy Committee for review and resolution; and

Reporting to the Policy Committee on a periodic basis about the maintenance activities of the Maintenance Working Group and requesting guidance on issues or problems that may arise.

2.4 Policy Committee

Introduction

The California ITS Architecture Policy Committee, or the Policy Committee, is a group of policy level agency representatives who shall oversee the activities of the Maintenance Working Group and decide upon any policy or institutional issues facing the maintenance effort.

The Policy Committee shall consist of one representative from each ITS Planning Region. Each ITS Planning Region may designate alternates to the representative. The Responsible Agency (described above) would be a permanent member of this committee and would be the lead (chairperson would be a designated representative of the Responsible Agency).

A Chairperson shall be designated by the Responsible Agency (Caltrans Headquarters) to conduct the meetings. The Chairperson shall be responsible for calling meetings and leading the meetings.


The primary responsibilities of the Policy Committee are:

Reviewing the status and decisions of the Maintenance Working Group; and Making any institutional or policy related decisions that arise in the maintenance of the

architecture.

2.4 Maintenance Manager

Introduction

The Responsible Agency shall appoint a person to the role of Maintenance Manager to coordinate the maintenance activities of the California ITS Architecture and System Plan. The Maintenance Manager will be the coordinator and main point of contact for all maintenance activities, including receiving Change Requests forms, tracking Change Requests, “framing the issues” of each Change Request and submitting the Change Request to the Maintenance Working Group, distributing documentation, maintaining lists, and sending annual reminders to update the ITS Architecture.


For the maintenance of the ITS Architecture, the Maintenance Manager has the following responsibilities:


Updates the “official” records of the ITS Architecture, including the baseline documents, meeting minutes, the Change Request Database, the list of the Authorized Representatives for each Stakeholder, and the list of members of the Maintenance Working Group;

Receives Change Request forms and updates the Change Request Database; “Frames” the issues of each Change Request and submits it to the Maintenance Working

Group for its consideration; Distributes updates and documentation to Stakeholders; and Sends annual reminders to the Stakeholders to update the ITS Architecture.

Some of the Maintenance Manager’s responsibilities may be delegated to staff or consultants, although the Maintenance Manager is ultimately responsible for the performance of these tasks.


3. TIMETABLE FOR MAINTENANCE

3.1 Introduction

This section addresses how often the California Statewide ITS Architecture and System Plan will be modified or updated and what events or timetables will be used for making modifications or updates. The timetable will depend on the basic approach chosen for maintaining the architecture. Several options were considered:

Periodic Maintenance. This approach ties the maintenance of the architecture to one of the recurring activities of the transportation planning process. For example, it’s natural that the ITS architecture would be updated at the same frequency as the statewide transportation plan is updated (approximately every five years) or the Statewide Transportation Improvement Program is updated (every two years). The update of the architecture should occur several months prior to the update of the California Transportation Plan (the most recent update was the California Transportation Plan 2025, published in 2003), so that the revised architecture could serve as an input to the planning update. Publication and versioning costs are minimized for the periodic maintenance approach since there is a new version only once in the maintenance cycle.

Exception Maintenance. This approach considers and makes changes to the architecture in a process that is initiated as needed. Publication and versioning costs are dependent on the frequency of changes made to the regional ITS architecture.

Combination. An approach may be considered that is a combination of these timetables, based on the types of changes. For example, minor changes may not warrant exception maintenance, but rather would be collected to be incorporated into the next regularly scheduled periodic update. A major change, however, may warrant exception maintenance to occur.

3.2 What changes will impact the architecture?

The California ITS Architecture and System Plan is dynamic. It must change as plans change, ITS projects are implemented, and the ITS needs and services evolve throughout the State. The architecture must be maintained so that it continues to reflect the current and planned ITS systems, interconnections, and other aspects of architecture. There are many actions that may cause a need to update the architecture. These actions include:

Changes in Needs. ITS architectures are created to support transportation planning in addressing local, regional, and statewide needs. Over time these needs can change and the corresponding aspects of the ITS architecture that address these needs may need to be updated. These changes in needs should be expressed in updates to planning documents such as Regional Transportation Plans.

New stakeholders. New stakeholders become active in ITS and the ITS architecture should be updated to reflect their place in the regional view of ITS elements, interfaces, and information flows. Why might new stakeholders emerge? The stakeholders might represent new organizations that were not in place during the original development of the regional ITS architecture. Or maybe additional transportation modes or transportation services are being considered that affect the systems of additional stakeholders.

Changes in stakeholder or element names. An agency’s name or the name used to describe their element(s) undergoes change. Transportation agencies occasionally merge, split, or


rename themselves. In addition element names may evolve as projects are defined. The California ITS Architecture and System Plan should be updated to use current names for stakeholders and elements.

Changes in other architectures. The California ITS Architecture and System Plan covers not only elements and interfaces that provide statewide services, but also elements and interfaces that provide interregional services. Many of these elements will be described in various regional ITS architectures in California and adjoining states. Changes in these regional ITS architectures may necessitate changes in the California ITS Architecture and System Plan in order to maintain consistency between the architectures.

There are several changes relating to projects that will cause the need for updates to the California ITS Architecture and System Plan.

Changes to Project Definitions. As funding for projects is identified, and as projects are implemented, the projects may add, subtract or modify elements, interfaces, or information flows based on available funding or changes in requirements. Because the architecture is meant to describe not only ITS planned for the State, but also the current ITS implementations, it should be updated to correctly reflect changes in the scope of projects.

Changes for Project Addition/Deletion. Occasionally a project will be added, deleted, or modified during the planning process. When this occurs, the aspects of the architecture associated with the project should be added, deleted, or modified.

Changes in Project Status. As projects are deployed, the status of the architecture elements, services and flows that are part of the project should be updated from planned to existing. Elements, services, and flows are considered existing when they are substantially complete and tested.

Changes in Project Priority. Due to funding constraints, technological changes or other considerations, a project planned for the region may be delayed or accelerated. Such changes should be reflected in the architecture.

The development of an architecture maintenance plan and the implementation of a program to maintain the architecture is also a requirement of the ITS Architecture and Standards Final Rule/ Final Policy, which says: “The agencies and other stakeholders participating in the development of the regional ITS architecture shall develop and implement procedures and responsibilities for maintaining it, as needs evolve within the region.”

3.3 Timetable for Changes

A comprehensive architecture update should occur every three years, concurrent with the formal update of the Statewide Transportation Plan. This is a natural result of the California ITS Architecture and System Plan being a component of the statewide transportation planning process. The update is necessary to ensure that the architecture continues to accurately represent the statewide view of ITS Systems. The comprehensive update, which would be considered a “major update” (note: for a definition of types of updates see Section 5.1), may include adding new stakeholders, reviewing transportation needs and services covered by the architecture, updating the status of projects, and reflecting new goals and strategies, as appropriate. Operational concepts, system functional requirements, project sequencing, ITS standards, and list of agency agreements should also be updated at this time.


Between major updates of the architecture, the following interim update actions should be performed:

Accept comments as they come in. The Maintenance Working Group should review the changes every six months and decide if updates are needed, or can wait until the yearly update discussed next.

Actively solicit changes on an annual basis from each ITS Planning Region to provide a set of needed updates on an annual basis. The Maintenance Working Group should review all changes requested, evaluate and approve the changes as appropriate, and decide if the architecture should be updated. Minor updates (see section 5.1 for a description of types of updates) should be implemented at this yearly update. Major updates may be addressed at this time or deferred for the comprehensive architecture update mentioned previously. The Maintenance Working Group will decide on the appropriate timing for the updates.

The Maintenance Plan should also be reviewed at the previously discussed times for required changes. Use of the California ITS Architecture and System Plan and modifications to it may differ from what was anticipated during the initial development of this Maintenance Plan. Revising the Maintenance Plan will ensure that the change management process defined is effective.


4. ARCHITECTURE BASELINE

4.1 Introduction

Establishing an architecture baseline requires clear identification of the architecture products that will be maintained, including specific format and version information. This Section defines what documents, databases, etc. will be included in the Architecture Baseline and hence will be subject to the change management process described in this Maintenance Plan. The section also establishes the specific formats and version information for the initial maintenance activities.

4.2 Baseline Documents and Outputs

The set of documents and outputs that comprise the California ITS Architecture and System Plan Architecture Baseline are listed in Table 1. The set of outputs of the California ITS Architecture and System Plan Project that were produced on the project but that will not be included in the Architecture Baseline are shown in Table 2.

Table 1 – Architecture Baseline

Output Type of Output Comments Project Task

User Needs Database Access Database 3

User Needs Website Hyperlinked files Provides information from the User Needs Database in a hyperlinked format.

3

User Service and Market Package Database

Access Database 5

User Service and Market Package Website

Hyperlinked files Provides information from the User Service and Market Package Database in a hyperlinked format.

5

Operational Concepts Document 6

Functional Reqmts Database

Access Database 7

Functional Reqmts Website

Hyperlinked files Provides information from the Functional Requirements Database in a hyperlinked format.

7

Turbo Architecture Database (Interconnects and Information Flows)

Access Database 8 and 9

Set of Interconnect diagrams

EMF files 8

Sausage Diagram PDF File 8

Customized Market Packages

EMF files 9

Elements (final inventory) and Information Flows Website

Hyperlinked files Contains diagrams and info from turbo database.

9



Project Sequencing- Project List

Access Database Part of Federal Rule Reqmts for Arch 12

Project Sequencing- Dependencies and actual sequence

Document Part of Federal Rule Reqmts for Arch 12

List of Agency Agreements

Document Part of Federal Rule Reqmts for Arch 13

Standards mapping details (part of Turbo Database)

Access Database Baselined as part of baselining Turbo Database 14

Maintenance Plan Document The process used to maintain the architecture- this document.

15

Final Architecture and System Plan Document

Document Compilation of documentation from previous tasks, will contain some of the outputs described above and will be baselined.

16

Table 2 – Project Outputs not includedArchitecture Baseline


Interim Inventory Database

Access Database This was an interim output- the final arch inventory (in the Turbo Arch database) is what needs to be baselined.

2

Interim Inventory Website

Hyperlinked files This is an interim output- the final arch inventory (in the Turbo Arch database) is what needs to be baselined.

2

Comment Database Access Database The comments received are part of the initial development process and don’t need to be maintained.

all

Vision Report Document An interim document developed primarily to assist the stakeholders in assessing gaps and interregional services to pursue. Not a part of the Federal Rule Reqts for Arch.

4 and 11

Project Sequencing- Sys Eng Analysis

Document Each project will do its own system engineering analysis. This is a starting set of outputs from this contract.

12

Project Sequencing- project evaluations

Document Each project will do its own system engineering analysis. This is a starting set of outputs from this contract.

12

4.3 Version Control

Over time, the components and documents that are part of the architecture baseline will change. Documents may be deleted or added to the list and changes will be made to the various outputs. To manage the changes to the components and documents, version numbers should be assigned to each revision approved by the Policy Committee or the Maintenance Working Group. This section provides guidelines on assign version numbers when revisions are approved.

All baseline documents subject to the change management process outlined in this Maintenance Plan shall have a version number and a revision date clearly identified.


Each update of a document or other output (e.g., databases) shall be designated with a new version number. The version number shall be assigned by the Maintenance Manager in accordance with the version control guidelines. The revision date shall be the date the document was created.

4.3.1 Version Control Guidelines

The following version control guidelines for documents that are a part of the architecture baseline:

Each baseline document shall have a version number consisting of at least 3 digits, in the format p.ss, where p is the major version number, and ss is the secondary version number.

The version number and the revision date shall be approved (or assigned) by the Maintenance Manager.

Minor revisions approved by the Maintenance Working Group shall be incremented in the second order, that is, p.ss, such that the first minor revision will be p.01. Minor revisions may include grammatical or spelling corrections, or modifications to a limited number of information flows, elements, or stakeholders. These changes may include changes in project status (e.g., from future to existing).

The first released version of a baseline document is Version 1.00. Approved significant changes to the architecture or to a document are considered to be

a major revision. Major changes involve multiple and significant modifications to the architecture or to baseline documents. These changes may be a result of a new Transportation Plan, Transportation Improvement Plan, or other significant changes. When a major revision is approved by the Policy Committee, the version number shall be incremented in the first order. Thus, the first approved major revision will be Version 2.00.

4.3.2 Revision History

Each baseline document shall include at least one page with a Revision History, indicating the history of the document since the last approved major version. The Revision History shall include the following columns:

Version Number – Version number of the document as approved or assigned by the Maintenance Manager.

Revision Date – Date the document was revised. Filename – File name of the document. To aid the California ITS Architecture in

architecture version document control, the filename of the database should contain the last revision date.

Author – Principal author of the revisions. This should be the name of the person who compiled and made the approved changes to the document.

Comments – Comments should consist of a short description of the modifications made since the last major or minor revision.

The revision history shall have an entry for each major revision since and including the original baseline (Version 1.00); and an entry for each minor revision since the last major revision.


A database or list shall be maintained by the Maintenance Manager containing the entire revision history of each baseline document, including all major and minor revisions. This list shall be made available to all Policy Committee members, Maintenance Working Group members, or the authorized representative from each stakeholder who requests it. Distribution may be hardcopy and/or electronic means.

A list or database shall also be kept by the Maintenance Manager on all changes made to any of the baselined documents. Where the software allows, the Tracking feature shall be used to reflect the changes since the last revision.

4.3.3 Baseline Availability

The most current version of each baseline document or other baseline outputs shall be available to all Maintenance Working Group members, Policy Committee members, and stakeholders. It is the responsibility of the Maintenance Manager to have access to the versions of the baseline documents and make it available for distribution. All baseline documents shall be available by hardcopy and/or electronic means, as appropriate.


5. CHANGE MANAGEMENT PROCESS

5.1 Introduction

Once a baseline is defined, the process for making changes to this baseline must be established. The purpose of this Section is to define the procedures to initiate, approve, and document proposed changes to the California ITS Architecture and System Plan architecture baseline

These procedures will apply to all changes to any of the documents or outputs identified in the architecture baseline. This Maintenance Plan is part of the architecture baseline, and is also subject to the change management process. As the California ITS Architecture and System Plan is used, implemented and maintained, new change management processes may be added or existing procedures may be modified as required.

The change management process outlined in this Maintenance Plan is based on the philosophy that the California ITS Architecture and System Plan is a consensus plan and changes to it will be made based on the approval of the Stakeholders directly affected by the proposed changes. It is expected that in most cases the affected stakeholders will reach consensus on changes and they will be simply incorporated into the baseline. The inclusion of the Policy Committee in the plan is to handle those cases where consensus is not reached, or where questions of the scope of the architecture require resolution. The change management process was structured to:

Formalize the procedures so proposed and approved changes can be carefully tracked for future reference; and

Second, to provide the opportunity for other Stakeholders to review and comment on the proposed changes.

The change management process for the California ITS Architecture and System Plan is depicted in Figure 2.


Figure 2 – Change Management Process


5.2 Identifying Changes

The primary aspects of identifying changes are:

Who can request a change? How is the change request documented?

5.2.1 Who can Request a Change?

For a “region” with as many stakeholders as the State of California, the question of who can make change requests is an important one. If literally anyone can input requests the region runs the risk of being overrun by requests that will tax scarce resources to review and decide upon. On the other end of the spectrum, if too much formality or paperwork is added to the process then many valid or needed changes may go unexpressed.

All requests for change to the Architecture Baseline shall be made through Authorized Representatives of stakeholders who are included in the architecture. The stakeholder authorized representative submits the change request to the Maintenance Manager and provides a copy to the ITS Planning Region representative on the Maintenance Working Group.

A stakeholder, for the purposes of the Maintenance Plan, is any agency or private organization identified as a participant in the architecture. This effectively indicates that all changes have the approval of an existing, defined stakeholder in the architecture. The requirement that only current stakeholders may request changes has the added benefit of spreading the resources needed to generate or evaluate changes among the Maintenance Working Group.

If the Change Request is to add a new Stakeholder and that Stakeholder’s ITS Elements and Interfaces, the approval of one of the ITS Planning Region representatives (to the Maintenance Working Group) or an existing Stakeholder impacted by the change is sufficient.

5.2.2 Defining the Change

How will changes to the Architecture Baseline be defined and made? Is it possible to have a “self-service” model for changes where any stakeholder with elements in the architecture can access directly the baseline and input changes? Because the Architecture Baseline is under configuration management, this level of self-service is not really practical. The Architecture Baseline is made up of databases, documents, and other outputs. Any change that is requested must be put into all of the outputs in the same manner. The requested change needs to first be documented on some change request form. This form can be provided on-line so that stakeholders can create change requests with a minimum of effort.

Stakeholders shall propose changes in writing through their Authorized Representatives to the Maintenance Manager. A copy of the change request shall be forwarded to their ITS Planning Region representative on the Maintenance Working Group.


The change request form to be used in proposing changes is shown Appendix B. The form contains the following information, which should be completed by the requesting stakeholder:

Agency(ies) requesting the change; Date of the request; Description of the proposed change; Nature of change (Major or minor- see description below); The architecture aspects to be added, deleted or revised; Rationale for change; Contact information for the person proposing the change if questions arise; Originator name or agency; Signature of authorized representative(s) of the originating stakeholder; and Signature of the ITS Planning Region representative (only required when change is

generated by a new stakeholder).

To support the understanding of the proposed changes, copies of the sections or diagrams marked with the proposed changes should be included with the change requests.

Other information on the change request form, to be completed by the Maintenance Manager include:

Change request number to be assigned by the Maintenance Manager; Date the change request was evaluated for recommendation; Disposition Date; Change disposition (approved, rejected, deferred [need more information]); and Disposition Comment.

Two general types of change are addressed via the change request:

Minor update are these changes have small impacts on a single stakeholder’s element status, description, or other attributes of the elements. Also attributes of interfaces and information flows (e.g. changing the status of an information flow from planned to existing due to the implementation of a project). Also considered minor are changes to interfaces or information flows that impact interfaces elements of one or two stakeholders only.

Major update are those changes that have a wider impact on the architecture baseline, such as inclusion of a new service or deletion of an existing service. Also considered a major update are those changes affecting an array of stakeholders. The definitions of minor vs. major are purposely somewhat vague, as it is hard to envision all the possible changes that might arise. It is up to the Maintenance Working Group to decide whether a change should be considered major or minor.

There is a third type of change not covered directly by the Change Request and that is the comprehensive update, which is the every 3 year review of the architecture as a whole and updating of the baseline to reconcile the architecture with the current status and plans for ITS in the state. This type of change could be handled by a single Change Request that summarizes what was changed in the update.


A database shall be maintained by the Maintenance Manager to track change requests. The database shall include all the information entered on the change request form.

5.3 Evaluating Changes

Upon receiving a change proposal, an initial assessment of the change proposal is to be made for the impact to the overall architecture or the affected document. There are several options as to who performs the initial assessment, including:

The Maintenance Manager; Maintenance Working Group; and The person proposing the change.

Each of the above options has advantages and challenges, but regardless of the selection the evaluator must have working knowledge of the architecture to evaluate the proposed changes.

The initial assessment shall include an analysis of what impact the proposed change has on the architecture. The evaluator shall then provide a written recommendation to the Maintenance Working Group on the impact of the proposed change, whether or not to approve the change, if the change(s) requires a major or minor revision, and if the change requires immediate action.

If the proposal for architecture modification has an impact on other stakeholders, the evaluator(s) shall contact the stakeholders to confirm their agreement with the modification. All stakeholders directly involved with the change request must approve and sign-off the change request proposal before the Maintenance Working Group considers the change proposal.

5.4 Approving Changes

The approval process for changes will depend upon whether the change is minor or major.

Minor changes shall require approval from the affected stakeholders and the appropriate ITS Planning Region representative. They do not need approval from other members of the Maintenance Working Group, nor do they need to be brought before the full Maintenance Working Group. The minor changes can be handled via email and do not require face-to-face meetings.

For major changes, upon completing the initial assessment, the Maintenance Manager will distribute the assessment to members of the Maintenance Working Group for discussion at the next Maintenance Working Group meeting. The Maintenance Manager is responsible for assembling an agenda for the Maintenance Working Group meeting, and the agenda should include, at a minimum, what change proposals are to be discussed during the meeting.

It is at the discretion of the Maintenance Manager when to distribute the change proposals and assessments to the Maintenance Working Group. If the change proposals are minor in nature, the Maintenance Manager may choose to wait until other change proposals are received and distribute all the change proposals and assessments simultaneously. However, the requests and recommendations shall be distributed to the members within three months of the Maintenance Manager receiving the proposed change.

Either once every six months, or when sufficient change requests warrant it, the Maintenance Working Group shall meet and discuss the change proposals and assessments. The Maintenance Manager shall distribute change proposals to the Maintenance Working Group members. The


Maintenance Working Group shall have sufficient time to review the change proposals and assessments before the meeting. The meeting may be in person or by teleconference.

During the meeting, the Maintenance Working Group will review the change proposals (primarily for major updates, but also for any minor updates that have some issue to discuss), reach consensus and disposition each change proposal. All stakeholders may have an opportunity to comment on each change request. Recommendations shall be “approve”, “reject” or “request more information”. The intent is to achieve unanimous consent of the affected stakeholders on change proposals (major or minor). For major change proposals (where a wide array of stakeholders are affected) the approval may be by ITS Planning Regions, rather than by individual stakeholder. If consensus cannot be reached then attempts should be made to amend the change so that consensus is developed, or the change can be forwarded to the Policy Committee for review and action. If more information is requested, the Maintenance Manager will send the request to the stakeholder that submitted the change proposal.

The Chairperson of the Maintenance Working Group or the Maintenance Manager shall present to the Policy Committee any change proposals requiring action on their part. They shall also present any other issues requiring the Policy Committee input (e.g. issues relating to the scope of the architecture). In addition, the status of maintenance actions should be presented (effectively the results of the Maintenance Working Group activities) along with plans for updating the baseline.

The Policy Committee shall meet at least once a year, or more often if recommendations of the Maintenance Working Group need to be reviewed. Their recommendations will be given to the Maintenance Manager who will distribute them to affected stakeholders.

The Maintenance Manager shall be responsible for seeing that minutes are taken at both Maintenance Working Group and Policy Committee meetings. Minutes are to be distributed to the attendees and to the identified representatives of each stakeholder no less that five working days after the meeting. Comments are due within 10 working days to the Maintenance Manager.

Minutes shall include, at a minimum, an attendance list, comments made on each change proposal, and the consensus recommendation (approve/reject/request more information) of the Maintenance Working Group. Approved minutes will be distributed to all stakeholders and posted on the website. The minutes provide a recording process for the change management process and provide traceability.

5.5 Updating Architecture Baseline

Once a set of changes are approved, the Architecture Baseline must be updated. In addition to updating the baseline documents, databases, or other outputs, the configuration status should be updated. In the discipline of Configuration Management this is known as Configuration Status Accounting. This accounting is performed by having a document that defines the following information for each separate output of the architecture baseline:

Output name; Output revision number; Date of latest revision; File Name; and Location/Point of Contact.


Periodically, the information in the various outputs of the architecture baseline should be audited to assure that the different representations of the architecture information (e.g. the database and document) are in sync. This configuration auditing should be performed by someone independent of the staff or resources used to actually enter the changes.

Once the change proposal is dispositioned, the Maintenance Manager shall implement the decision agreed upon. The change proposal form is updated with the disposition information, and the same information is updated in the change proposal database by the Maintenance Manager. The Maintenance Manager shall also notify the originator of the change proposal of the results of the vote.

If the decision is to accept the change, then the appropriate portions of the architecture baseline are updated by the Maintenance Manager (or whomever they assign to perform the updates) and an updated architecture baseline is defined.

The configuration status document shall be updated to identify the current versions of the Architecture Baseline. On a biannual basis the information in the various outputs of the architecture baseline should be audited to assure that the different representations of the architecture information (e.g. the database and document) are in sync. The Maintenance Manager shall assign resources to perform this audit.

5.6 Notifying Stakeholders

Authorized representatives for each stakeholder shall be notified by e-mail from the Maintenance Manager when baseline documents have been updated. All baseline documents shall also be available to stakeholders from a website or other electronic location, such as an ftp site. It is the responsibility of the Maintenance Manager to ensure the most recent document is available from the website.

Request for copies or access to the baseline documents shall be made to the Maintenance Manager. Only Policy Committee members, Maintenance Working Group members or the authorized representatives from each stakeholder may request the baseline documents. It is the responsibility of that stakeholder authorized representative to distribute the revised documents to all other members from his/her agency who requests a copy.

After major revisions to the architecture or the baseline documents, the Policy Committee may elect to also provide all baseline documents to members on CD-ROMs.


APPENDIX A – GLOSSARY

Architecture Baseline: Documents and other outputs that define the California ITS Architecture and System Plan

Element: The name of an ITS system (or portion of an ITS system) operated by one of the stakeholders.

Maintenance Working Group: The group of persons responsible for reviewing and dispositioning proposed changes to the California ITS Architecture and System Plan.

Policy Committee: The group of persons responsible for resolving issues that arise from the activities of the Maintenance Working Group. They are also responsible for any policy or institutional decision-making.

Stakeholder: Any agency or private organization identified as a participant in the architecture


APPENDIX B – CHANGE REQUEST FORM


California ITS Architecture and System Plan

Change Request (CR) FormOriginator Name: Date Submitted Originator Telephone: Originator Fax: Originator E - Mail: Originator Agency: Revision Type:

______Major ______Minor

Agency Authorized Signature: Signature Date:

Planning Region Representative (if applicable):

Planning Region Representative Signature: Signature Date:

Description of Proposed Change: Rationale for Proposed Change: Affected Agency: Authorized Signature: Signature Date: Affected Agency: Authorized Signature: Signature Date: List Attachments: Baseline Documents Affected: _____ Website ______Turbo Architecture ______Customized MPs ______Document ______Other (describe)

To Be Completed By Maintenance Manager

Change Request Number: Date CR Received: Date CR Logged: Date Initially Discussed: Disposition:

Accepted Rejected More Info

Disposition Comments

Date Discussed: Disposition:


Disposition Comm ents

Date Discussed: Disposition:


Disposition Comments

Date Approved by Policy Committee:

Baseline Documents Affected/Version implemented

Turbo Architecture Date: _______ Version: _______ Website Date: _______ Version: _______

Customized MPs Date: _______ Version: _______ ____________ Date: _______ Version: ______

091783000 California ITS Architecture and System Plan Appendix A10 - Agency Agreements.doc 1 Appendix A10: Agency Agreements

APPENDIX A10: AGENCY AGREEMENTS

Reason for Agreement Stakeholder A Stakeholder B Collecting Performance Monitoring Systems (PeMS) data for archiving (existing)

UC Berkeley Caltrans

Coordinating work plans Caltrans Private Rail Operators Bay Area Transit Agencies Central California Transit Agencies Coordination between electronic fare

payment systems Northern California Transit Agencies Bay Area Transit Agencies

Local Government California Highway Patrol (CHP) Local Government County Public Safety Agencies Local Government Municipal Public Safety Agencies State Office of Emergency Services Caltrans California Highway Patrol (CHP) State Office of Emergency Services County Public Safety Agencies State Office of Emergency Services Local Government State Office of Emergency Services

Coordination of emergency plans and resources. Sharing incident reports or incident response information.

Municipal Public Safety Agencies State Office of Emergency Services Caltrans Arizona DOT Caltrans Mexican Transportation Agency Caltrans Toll Road Operators Caltrans Oregon Department of Transportation

Coordination of traffic information

Caltrans Nevada DOT Metrolink Rail Agency Central California Transit Agencies Coordination of transit service

information Metrolink Rail Agency Southern California Transit Agencies Coordination of transit services Central California Transit Agencies Metrolink Rail Agency

Central California Transit Agencies Northern California Transit Agencies

Northern California Transit Agencies Metropolitan Transportation Commission (MTC)

Coordination of transit services and transit fares

Southern California Transit Agencies Metrolink Rail Agency

Central California Transit Agencies Metropolitan Transportation Commission (MTC)

Central California Transit Agencies Southern California Transit Agencies Metropolitan Transportation Commission (MTC) Northern California Transit Agencies

Southern California Association of Governments (SCAG) Central California Transit Agencies

Coordination of transit services and transit traveler information

Southern California Transit Agencies Southern California Association of Governments (SCAG)


Reason for Agreement Stakeholder A Stakeholder B

Bay Area Rapid Transit (BART) State Office of Emergency Services Caltrain State Office of Emergency Services Central California Transit Agencies State Office of Emergency Services Los Angeles County Metropolitan Transportation Authority State Office of Emergency Services

Metrolink Rail Agency State Office of Emergency Services Northern California Transit Agencies State Office of Emergency Services San Francisco MUNI State Office of Emergency Services

Coordination of transit services before or during an evacuation

Southern California Transit Agencies State Office of Emergency Services Fee reconciliation between toll systems (existing)

Northern California Toll Agencies Southern California Toll System Agencies

Providing CVO credentials information California Department of Motor Vehicles (DMV) California Highway Patrol (CHP)

State Office of Emergency Services Caltrans, Regional, and Local Stakeholders

State Office of Emergency Services Metropolitan Transportation Commission (MTC)

Providing evacuation information and transportation system status for traveler information systems

State Office of Emergency Services Regional Planning Agencies Port Facilities California Highway Patrol (CHP) Port Facilities County Public Safety Agencies

Providing information on incidents at intermodal facilities Port Facilities Municipal Public Safety Agencies Providing information on incidents or traffic related events at intermodal facilities

Port Facilities Caltrans

Providing road network conditions, traffic images, and incident information Caltrans County Public Safety Agencies

Providing road network status during evacuations. Coordination of emergency plans.

Caltrans State Office of Emergency Services

Providing road weather information Caltrans Metropolitan Transportation Commission (MTC)

Caltrans County Public Works Caltrans Local Government Caltrans Municipal Public Safety Agencies

Providing roadway maintenance status and work zone information. Coordinating work plans.

Caltrans Other States DOTs


Reason for Agreement Stakeholder A Stakeholder B

Central California Transit Agencies Caltrans, Regional, and Local Stakeholders

Northern California Transit Agencies Private ISPs

Northern California Transit Agencies Caltrans, Regional, and Local Stakeholders

Northern California Transit Agencies Private ISPs Southern California Association of Governments (SCAG) Private ISPs

Southern California Association of Governments (SCAG) Regional Planning Agencies

Providing transit information for traveler information systems

Southern California Transit Agencies Regional Planning Agencies Bureau of Land Management (BLM), Fish and Game, Parks and Recreation


Bureau of Land Management (BLM), Fish and Game, Parks and Recreation Regional Planning Agencies Providing travel service information

National Park Service/U.S. Forest Service


California Highway Patrol (CHP) Bay Area Rapid Transit (BART) California Highway Patrol (CHP) Caltrain California Highway Patrol (CHP) Central California Transit Agencies

California Highway Patrol (CHP) Los Angeles County Metropolitan Transportation Authority

California Highway Patrol (CHP) Metrolink Rail Agency

California Highway Patrol (CHP) Metropolitan Transportation Commission (MTC)

California Highway Patrol (CHP) Northern California Transit Agencies California Highway Patrol (CHP) Regional Planning Agencies California Highway Patrol (CHP) San Francisco MUNI

Providing wide area alerts

California Highway Patrol (CHP) Southern California Transit Agencies Providing wide area alerts and incident response status. Sharing incident information. Providing commercial vehicle credentials information. Making resource requests.

California Highway Patrol (CHP) Caltrans

Providing work zone information. Coordinating work plans. Providing evacuation information and coordination of emergency plans.

Local Government Caltrans

California Highway Patrol (CHP) Operation Respond Institute Local Government Operation Respond Institute Requesting hazmat information

Municipal Public Safety Agencies Operation Respond Institute

California Highway Patrol (CHP) International Fuel Tax Agreement (IFTA), Inc.

Sharing credentials information California Highway Patrol (CHP) International Registration Plan (IRP),

Inc.


Reason for Agreement Stakeholder A Stakeholder B Sharing incident information Special Police Caltrans

County Public Safety Agencies Caltrans Local Government Special Police Municipal Public Safety Agencies California Highway Patrol (CHP)

Sharing incident information and incident response status

Municipal Public Safety Agencies Caltrans Sharing incident information and incident response status. Emergency plan and resource coordination.

Municipal Public Safety Agencies Local Government

Sharing incident information. Providing road network condition, traffic images, road weather information and commercial vehicle credentials information.

Caltrans California Highway Patrol (CHP)

Bureau of Customs and Border Protection (BCBP) California Highway Patrol (CHP)

Bureau of Customs and Border Protection (BCBP) County Public Safety Agencies

California Highway Patrol (CHP) County Public Safety Agencies California Highway Patrol (CHP) Local Government California Highway Patrol (CHP) Municipal Public Safety Agencies California Highway Patrol (CHP) Special Police Special Police County Public Safety Agencies

Sharing incident reports or incident response coordination

Special Police Local Government Sharing of traffic information Toll Road Operators Caltrans Sharing safety inspection information and credentials information California Highway Patrol (CHP) Federal Motor Carrier Safety

Administration (FMCSA)

091783000 California ITS Architecture and System Plan Appendix A11 - California Standards.doc 1 Appendix A11: California Standards

APPENDIX A11: CALIFORNIA STANDARDS

Lead SDO Standard Name Document IDVersion

Footnotes: Advanced Traveler Information Systems (ATIS) Bandwidth Limited Standards Group

Document IDStandard NameSDO SAE Location Referencing Message Specification

(LRMS) SAE J2266

SAE Message Set for Advanced Traveler Information System (ATIS)

SAE J2354

SAE Standard for ATIS Message Sets Delivered Over Bandwidth Restricted Media

SAE J2369

SAE Rules for Standardizing Street Names and Route IDs SAE J2529SAE Messages for Handling Strings and Look-Up Tables

in ATIS Standards SAE J2540

SAE RDS (Radio Data System) Phrase List SAE J2540-1SAE ITIS (International Traveler Information Systems)

Phrase Lists SAE J2540-2

SAE National Names Phrase List SAE J2540-3SAE Converting ATIS Message Standards from ASN.1 to

XML SAE J2630

Advanced Traveler Information Systems (ATIS) General Use Standards GroupDocument IDStandard NameSDO

SAE Location Referencing Message Specification (LRMS)

SAE J2266

SAE Message Set for Advanced Traveler Information System (ATIS)

SAE J2354






XML SAE J2630

Dedicated Short Range Communication at 5.9 GHz Standards GroupDocument IDStandard NameSDO

IEEE Resource Manager for DSRC 5.9 GHz IEEE 1609.1IEEE Application Services (Layers 6,7) for DSRC 5.9

GHz IEEE 1609.2

IEEE Communications Services (Layers 4,5) for DSRC 5.9

IEEE 1609.3

IEEE Medium Access Control (MAC) Extension & the MAC Extension Management Entity for DSRC 5.9 GHz

IEEE 1609.4

IEEE Standard Specification for Telecommunications and Information Exchange Between Roadside and Vehicle Systems - 5 GHz Band Dedicated Short Range Communications (DSRC) Medium Access Control (MAC) and Physical Layer (PHY) Specifications

IEEE 802.11

IEEE Logical Link (Layer 2) for DSRC 5.9 GHz IEEE 802.2ISO Networking Services (Layer 3) for DSRC 5.9 GHz ISO 21210



Dedicated Short Range Communication at 915 MHz Standards GroupDocument IDStandard NameSDO

ASTM Standard Specification for Dedicated Short Range Communication (DSRC) Physical Layer using Microwave in the 902-928 MHz Band

ASTM E2158-01

ASTM Standard Provisional Specification for Dedicated Short Range Communication (DSRC) Data Link Layer

ASTM PS 105-99

Incident Management Standards Group Document IDStandard NameSDO

IEEE Standard for Traffic Incident Management Message Sets for Use by EMCs

IEEE 1512.1-2003

IEEE Standard for Hazardous Material IMMS for use by EMCs

IEEE 1512.3-2002

IEEE Standard for Common Incident Management Message Sets (IMMS) for use by EMCs

IEEE 1512-2000

IEEE Standard for Public Safety IMMS for use by EMCs IEEE P1512.2NTCIP Center-to-Center Standards Group

Document IDStandard NameSDO AASHTO/ITE/NEMA Base Standard: Octet Encoding Rules (OER) NTCIP 1102AASHTO/ITE/NEMA CORBA Naming Convention NTCIP 1104AASHTO/ITE/NEMA CORBA Security Service NTCIP 1105AASHTO/ITE/NEMA CORBA Near-Real Time Data Service NTCIP 1106AASHTO/ITE/NEMA Subnet Profile for Ethernet NTCIP 2104AASHTO/ITE/NEMA Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202AASHTO/ITE/NEMA Application Profile for File Transfer Protocol (FTP) NTCIP 2303AASHTO/ITE/NEMA Application Profile for Data Exchange ASN.1

(DATEX) NTCIP 2304

AASHTO/ITE/NEMA Application Profile for Common Object Request Broker Architecture (CORBA)

NTCIP 2305

AASHTO/ITE/NEMA Information Profile for DATEX NTCIP 2501AASHTO/ITE/NEMA Information Profile for CORBA NTCIP 2502

NTCIP Center-to-Field Standards Group Document IDStandard NameSDO

AASHTO/ITE/NEMA Simple Transportation Management Framework (STMF)

NTCIP 1101

AASHTO/ITE/NEMA Base Standard: Octet Encoding Rules (OER) NTCIP 1102AASHTO/ITE/NEMA Simple Transportation Management Protocol

(STMP) NTCIP 1103

AASHTO/ITE/NEMA Point to Multi-Point Protocol Using RS-232 Subnetwork Profile

NTCIP 2101

AASHTO/ITE/NEMA Subnet Profile for PMPP Over FSK modems NTCIP 2102AASHTO/ITE/NEMA Subnet Profile for Point-to-Point Protocol using RS

232 NTCIP 2103

AASHTO/ITE/NEMA Subnet Profile for Ethernet NTCIP 2104AASHTO/ITE/NEMA Transportation Transport Profile NTCIP 2201AASHTO/ITE/NEMA Internet (TCP/IP and UDP/IP) Transport Profile NTCIP 2202AASHTO/ITE/NEMA Application Profile for Simple Transportation

Management Framework (STMF) NTCIP 2301

AASHTO/ITE/NEMA Application Profile for Trivial File Transfer Protocol NTCIP 2302AASHTO/ITE/NEMA Application Profile for File Transfer Protocol (FTP) NTCIP 2303

On-board Vehicle Mayday Standards Group Document IDStandard NameSDO



On-board Vehicle Mayday Standards Group Document IDStandard NameSDO

SAE Location Referencing Message Specification (LRMS)

SAE J2266

SAE On-Board Land Vehicle Mayday Reporting Interface SAE J2313SAE Message Set for Advanced Traveler Information

System (ATIS) SAE J2354






XML SAE J2630