U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000


Skip to content U.S. Department of Transportation/Federal Highway AdministrationU.S. Department of Transportation/Federal Highway Administration

California Division

Home / About / Field Offices / California Division / Systems Engineering Guidebook for ITS

Home What's New Systems Engineering Guidebook Views Search Glossary Resources Feedback Site Map
Process View

Examples by Project

Sort by Deliverable Hide All

I-15 Reversible Lanes Control System

  • Description: The I-15 Reversible Lanes project is a modernization of the existing control system for the I-15 HOV and HOT lanes between Ted Williams and state route 163. The existing system has been in operation since 1988.
    Location: San Diego, CA
    Partners: Caltrans and the San Diego Association of Governments (SANDAG)
  • I-15 Concept of Operations and User Requirements

    • Name: I-15 Concept of Operations and User Requirements
      Description: This document articulates the User Requirements for the I-15 Reversible Lane Control Systems Upgrade and Modernization. It is a free form non-structured narrative that reflects the needs, expectations, and desires of the Stakeholders involved in the System. The User Requirements is a synthesis of several interviews and workshops that were held with the Stakeholders and with the consultant for Caltrans District 11.
      Type: Concepts of Operations
      Access: HTML MS Word

    I-15 Graphical User Interface Requirements

    • Name: I-15 Graphical User Interface Requirements
      Description: This document extracts the requirements for the Graphical User Interface (GUI) from the I-15 HOV Reversible Lane Control System Project, System Requirements Document, and organizes them into a top-level design for the user interface. It identifies the user type requirements, user security requirements, and all required user tasks, by user type and user security level.
      Type: Requirements
      Access: HTML MS Word

    I-15 High Level Design

    • Name: I-15 High Level Design
      Description: This document provides a description of the selected system architecture and high level design for the I-15 Reversible Lane Control System. The architecture/design incorporates those elements of the existing system that should be retained and provides a platform for the new system functionality.
      Type: Design Specifications
      Access: HTML MS Word

I-680 Smart Carpool Lane Electronic Toll System

  • Description: This project will implement a Smart Carpool Lane or High Occupancy Toll (HOT) Lane on a 14 mile segment of an existing HOV lane on I-680. Carpools would continue to use the lane for free while solo drivers could use the lane for a fee that would vary depending on the level of congestion in the Smart Lane.
    Location: Alameda and Santa Clara Counties, CA
    Partners: The Sunol Smart Carpool Lane Joint Powers Agency is authorized by State legislation to design, implement and operate the project. The Sunol Smart Carpool Lane Joint Powers Authority, has members from Santa Clara County's Valley Transportation Authority, the Alameda County Congestion Management Agency, and the Alameda County Transportation Improvement. The Alameda County Congestion Management Agency serves as administrator of the project.
  • I-680 Configuration Management Plan Guidelines

    • Name: I-680 Configuration Management Plan Guidelines
      Description: This document provides various guidelines pertaining to the ETS configuration and how the Integrator should develop, maintain and adhere to internal configuration management procedures and processes. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Configuration Management Plans
      Access: HTML MS Word

    I-680 Deployment Plan Guidelines

    • Name: I-680 Deployment Plan Guidelines
      Description: This document provides all of the details pertaining to how the Smart Lane system will be prepared for installation, installed, tested and opened to traffic. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Deployment Plans
      Access: HTML MS Word

    I-680 Electronic Toll System Requirements

    • Name: I-680 Electronic Toll System Requirements
      Description: The purpose of this document is to describe the functional I-680 Southbound Smart Lane (Smart Lane) electronic toll system (ETS) requirements, various operating business rules, and interfaces to other external systems. This document will be reviewed and approved by Alameda County Congestion Management Agency (ACCMA) staff on behalf of the Sunol Smart Carpool Lane Joint Powers Authority (JPA) and will be used as the basis for developing the ETS Request for Proposals (RFP) document to procure the ETS for the Smart Lane facility. In addition, the requirements presented herein will be used as the basis for the validation of the designed, developed and delivered ETS
      Type: Requirements
      Access: HTML MS Word

    I-680 Integration Plan Guidelines

    • Name: I-680 Integration Plan Guidelines
      Description: This document provides the required details regarding how the various equipment, subsystems and overall system will be fully integrated and tested by the Integrator to ensure that a fully integrated and operating system is deployed that meets all of the functional requirements that are presented in the RFP and the other contract documents. This pertains to the hardware and software components of the Smart Lane system. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Integration Plans
      Access: HTML MS Word

    I-680 Quality Management Plan Guidelines

    • Name: I-680 Quality Management Plan Guidelines
      Description: This document provides various guidelines that need to be implemented by the Integrator to ensure that all necessary quality assurance (QA) and quality control (QC) processes are identified, maintained and adhered to by the Integrator. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Other Technical Planning Documents
      Access: HTML MS Word

    I-680 Smart Lane Data Security and Safety Plan Guidelines

    • Name: I-680 Smart Lane Data Security and Safety Plan Guidelines
      Description: This document includes various built-in data security measures that need to be incorporated into the ETS. This Plan will also identify the ways in which the system design, development and deployment will be performed to ensure that the work is conducted in a safe manner. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Other Technical Planning Documents
      Access: HTML MS Word

    I-680 System Development Plan Guidelines

    • Name: I-680 System Development Plan Guidelines
      Description: This document provides details regarding how the Integrator will conduct the actual hardware and software design, system development, shop testing, integration and factory testing of the ETS. This Technical Plan is a requirement of the I-680 Systems Engineering Management Plan.
      Type: Other Technical Planning Documents
      Access: HTML MS Word

    I-680 System Verification Plan Guidelines

    • Name: I-680 System Verification Plan Guidelines
      Description: This document presents the I-680 Smart Lane electronic toll system (ETS) equipment and system verification testing process. It will outline the different types of tests that shall be conducted and identify the roles and responsibilities of each group that will be working on this project.
      Type: Verification Documents
      Access: HTML MS Word

    I-680 Systems Engineering Management Plan

    • Name: I-680 Systems Engineering Management Plan
      Description: This is a Final SEMP, completed by the SE at end of System High-Level Design. Several of the Technical Plan Guidelines associated with the SEMP are also available on this website. This will guide the engineering effort of the Integrator.
      Type: Systems Engineering Management Plans (Base Documents)
      Access: HTML MS Word

Maryland CHART

  • Description: The Coordinated Highways Advanced Response Team (CHART) system is a comprehensive, advanced traffic management system that includes a newly constructed state-of-the-art command and control center called the Statewide Operations Center (SOC). The SOC is the "hub" of the CHART system, functioning 24 hours-a-day, seven days a week with satellite Traffic Operations Centers (TOCs) spread across the state to handle peak-period traffic.
    Location: Maryland
    Partners: The CHART program is directed by the CHART Board, consisting of senior technical and operational personnel from The Maryland State Highway Administration, Maryland Transportation Authority, Maryland State Police, Federal Highway Administration, University of Maryland Center For Advanced Transportation Technology and various local governments
  • CHART II System Requirements

    • Name: CHART II System Requirements
      Description: This is one of many systems engineering documents that were produced for Maryland CHART.
      Type: Requirements
      Access: HTML MS Word

Minneapolis TMC Upgrade

  • Description: The Minneapolis Traffic Management Center (TMC), which is operated, managed and maintained by the City of Minneapolis Traffic and Parking Services Division, provides traffic signal control, traffic and incident management, and traffic operation coordination in downtown Minneapolis and surrounding areas within Minneapolis City limits.In order to meet the future needs, the City of Minneapolis will increase its TMC operational ability with several system upgrades to be accomplished in three separate phases: (1) upgrading TMC computer system and communication facilities, (2) replacing the City’s old electromechanical traffic signal controllers, and (3) enhancing ITS capabilities.
    Location: Minneapolis, Minnesota
    Partners: City of Minneapolis, Mn/DOT, City of St. Paul, Hennepin County, FHWA
  • City of Minneapolis TMC Upgrade Concept of Operations

    • Name: City of Minneapolis TMC Upgrade Concept of Operations
      Description: This Concept of Operations is a necessary step in the systems engineering process and a key component leading to the development of system requirements and design in the next phase. This document provides a high-level description of what the upgraded TMC’s major capabilities will be, how the future system will be operated, the roles and responsibilities for designated stakeholders, and typical operational scenarios.
      Type: Concepts of Operations
      Access: HTML PDF

Sacramento Transportation Area-wide Network (STARNET)

  • Description: The Sacramento Transportation Area-wide Network (STARNET) is the communications backbone for regional ITS integration in the Sacramento region. A Systems Engineering Technical Assistant established a management plan, concept of operations, and systems and subsystems requirements for STARNET. The consultant will oversee the design and deployment of the hardware and software for STARNET, and conduct verification testing to ensure the system satisfies stakeholders' requirements. The consultant will also develop a plan for the first phase of 511 traveler information system implementation.
    Location: Sacramento, CA
    Partners: FHWA, Caltrans, Sacramento Area Council of Governments (SACOG), and the Sacramento Region ITS Partnership, made up of regional public agency stakeholders
  • STARNET Concept of Operations

    • Name: STARNET Concept of Operations
      Description: This document identifies the concept of operations which represents the STARNET stakeholders' envisioned day-to-day conditions and activities (operation) during the on-going use of STARNET.
      Type: Concepts of Operations
      Access: HTML MS Word

    STARNET Configuration Management Plan

    • Name: STARNET Configuration Management Plan
      Description: This document identifies the procedures to be used for managing changes to STARNET and for keeping accurate and up-to-date records of its current configuration. This Technical Plan is a requirement of the STARNET Systems Engineering Management Plan.
      Type: Configuration Management Plans
      Access: HTML MS Word

    STARNET High Level Design

    • Name: STARNET High Level Design
      Description: This High Level Design document presents one possible approach for implementing STARNET. It is consistent with the STARNET system requirements that will be used in procuring system integration services for the initial STARNET deployment. The goals of the High Level Design Document are: 1) To provide a basis for refining the estimated cost of STARNET deployment and to facilitate obtaining funding, 2) To delve deeper into the system requirements, to verify that the requirements as written can be implemented, to identify clarifications that may be needed in the wording of requirements, and to identify modifications to requirements that may simplify the design and reduce implementation costs while still addressing user needs, and 3) Provide the System Integrator additional information to assist in clarifying the requirements and objectives of STARNET.
      Type: Design Specifications
      Access: HTML MS Word

    STARNET ITS Systems Engineering RFP

    • Name: STARNET ITS Systems Engineering RFP
      Description: This RFP was used to hire the SE for the STARNET project. This RFP has a strong tie to the Systems Engineering Guidebook for ITS.
      Type: Requests for Proposal
      Access: HTML PDF

    STARNET Stakeholders Cooperation Plan

    • Name: STARNET Stakeholders Cooperation Plan
      Description: The Stakeholders Cooperation Plan was developed to address the challenge of so many agencies coming together. It will identify the procedures and documents that will be used to coordinate the activities of stakeholders in the implementation, operation, and maintenance of STARNET. This Technical Plan is a requirement of the STARNET Systems Engineering Management Plan.
      Type: Other Technical Planning Documents
      Access: HTML MS Word

    STARNET System Integrator Evaluation Interview Questions

    • Name: STARNET System Integrator Evaluation Interview Questions
      Description: This is a selection of questions that were asked during the interviews with candidate firms for the STARNET System Integrator selection process.
      Type: Miscellaneous
      Access: HTML MS Word

    STARNET System Integrator RFP

    • Name: STARNET System Integrator RFP
      Description: This request for proposals (RFP) is the first step in a process to procure the services of a systems integrator to implement STARNET in accordance with the STARNET System Requirements document. After proposals are received and evaluated, selected responders may be invited to an oral interview and a final short list may be invited to submit a “best and final offer”.
      Type: Requests for Proposal
      Access: HTML PDF

    STARNET System Requirements

    • Name: STARNET System Requirements
      Description: This System Requirements document presents high-level requirements to be used in procuring system integration services for the initial STARNET deployment. System requirements were derived from User Needs described in the document titled STARNET Concept of Operations. Initially, the system requirements provide guidance to firms responding to the Request for Proposals for integration services for the initial STARNET deployment. During negotiations with the selected firm, it is expected that requirements will change some what to reflect the specifics of the chosen solution. The modified system requirements document will form part of the initial system integration contract agreement
      Type: Requirements
      Access: HTML MS Word

    STARNET Systems Engineering Management Plan

    • Name: STARNET Systems Engineering Management Plan
      Description: This is a SEMP Framework, which is the early contract deliverable that defines the technical approach and technical plans to be developed. Approval of this document by the project sponsor and SE team is a control gate requirement before work progresses on the project.
      Type: Systems Engineering Management Plans (Base Documents)
      Access: HTML MS Word

    STARNET Verification Plan

    • Name: STARNET Verification Plan
      Description: A verification plan is a document that describes the objectives, scope, approach, and focus of a system’s acceptance testing effort. The verification plan describes the efforts needed to determine the acceptability of the developed system. It states what the items to be tested are, how the item will be tested, and describes the test environment. The objective of this verification plan is to provide a plan to verify the system produced meets each requirement as listed in the System Requirements Table.
      Type: Verification Documents
      Access: HTML MS Word

San Francisco Bay Area Interim C2C System

  • Description: The San Francisco Bay Area’s Interim C2C System project will implement a system that enables the real-time exchange of data and video between the Smart Corridors and the Regional Transportation Management Center (TMC), which includes Caltrans TMC and TravInfo®. The Interim C2C System is expected to be a short-term solution to the Bay Area’s existing need for real-time exchange of data and video, and will be upgraded or replaced as Caltrans develops statewide TMC software.
    Location: San Francisco Bay Area, CA
    Partners: Metropolitan Transportation Commission and participating centers: Silicon Valley-ITS, Sfgo, Caltrans, I-580 Smart Corridor, TravInfo.
  • Interim Bay Area Center to Center Configuration Management Plan

    • Name: Interim Bay Area Center to Center Configuration Management Plan
      Description: The purpose of this document is to identify and describe the overall policies and methods for the Configuration Management (CM) activities to be used during the system life cycle of the Interim C2C system, including SWCIs comprising data interfaces, and will be updated progressively as the work proceeds and the necessity arises. The primary intention of this CMP is to provide overall information on the Configuration Management policy and methods to be adopted and implemented for the Interim C2C project including: submitting, planning, approving, and implementing changes to participating Centers’ C2C software, ICD, DDI, message sets, and communications system.
      Type: Configuration Management Plans
      Access: HTML MS Word

San Francisco Parking Management Program (SFpark)

  • Description: To help San Francisco address issues related to parking and congestion, the San Francisco Municipal Transportation Agency (SFMTA) initiated Sfpark. Sfpark will use new parking management approaches and technology to manage San Francisco’s parking demand. SFMTA will use three primary strategies to achieve its goals for Sfpark: better parking management, parking information, and enforcement. Parking management – To better manage demand for on- and off-street parking, Sfpark will use demand-responsive pricing of parking, that will adjust prices periodically and gradually to help meet availability targets. Parking information – To help drivers make more informed travel decisions, Sfpark will provide real-time information about parking location, availability, and price in a variety of ways, including variable message signs, static way-finding signs, web-based maps, PDA / Smart Phone accessible maps, and text message. Enforcement – For on-street parking, good policies will be followed up with a consistent level of enforcement of those policies to help maximize their effectiveness.
    Location: San Francisco, CA
    Partners: San Francisco Municipal Transportation Agency (SFMTA), the San Francisco County Transportation Authority (SFCTA), and the Metropolitan Transportation Commission (MTC).
  • California SERF – Parking Management Program

    • Name: California SERF – Parking Management Program
      Description: This document is an example of a Systems Engineering Review Form (SERF) that provides responses to the federal regulatory requirements in 23 CFR 940 part 11. For this high-risk (“Major”) ITS projects, completion of responses will occur during the system definition phase of the systems engineering process.
      Type: FHWA Rule/FTA Policy Compliance Documents
      Access: HTML MS Word

    SFpark Configuration Management Plan

    • Name: SFpark Configuration Management Plan
      Description: The configuration management plan provides the specifications and processes for recording, and managing changes to, the configuration of hardware, Commercial-off- the- Shelf (COTS) software, and communications facilities that compose the parking management system (PMS). Among other things, it is intended to prevent a situation where one vendor or person may unilaterally make a change that has negative consequences for data collection or system maintenance. It is also intended to prevent situations where a repair or change is needed for the benefit of all, but is made very difficult by inadequate documentation of the current and/or proposed configuration.
      Type: Configuration Management Plans
      Access: HTML MS Word

    SFpark Systems Engineering Management Plan Base Document

    • Name: SFpark Systems Engineering Management Plan Base Document
      Description: This is the base document of the Systems Engineering Management Plan (SEMP) for the San Francisco Municipal Transportation Agency’s (SFMTA) Urban Partnership Program-funded SFpark pilot projects. This base document has basic information about the pilot projects as a foundation for the documents that form the SEMP. The SEMP is intended to serve as a guidebook for the SFMTA project team and its vendors throughout the course of the project that follows the systems engineering approach to project completion. The SEMP will identify tasks to be completed, and summarize the project schedule, tasks, responsibilities, and how the final products will be integrated, installed, verified, and maintained. The SEMP will enable the project team to manage the project using systems engineering principles and methods to maximize the quality of the system being implemented while minimizing the budget and schedule. The SEMP documents are living documents, so as information is gathered through the life of the project, some plans may be updated to reflect the most current data.
      Type: Systems Engineering Management Plans (Base Documents)
      Access: MS Word

    SFpark Training Plan

    • Name: SFpark Training Plan
      Description: This Training Plan documents the required training and guidelines for SFpark pilot projects. It identifies the roles and responsibilities of the project members to ensure SFMTA implements SFpark smoothly.
      Type: Other Technical Planning Documents
      Access: HTML MS Word

San Mateo County Smart Corridors Program

  • Description: The San Mateo County Smart Corridors Program focuses on a portion of the US 101 and SR 82 (El Camino Real) Corridors including major local streets identified as alternate routes. The Smart Corridors Program will enable stakeholders to implement traffic management strategies through the deployment of Intelligent Transportation System (ITS) elements along state routes and major local streets. These designated routes will have the tools to manage non-recurring traffic congestion and improve mobility during major freeway incidents. The development and successful implementation of this project will serve as a roadmap for the long-term direction of ITS deployment in the region.
    Location: San Mateo County, CA
    Partners: C/CAG, Caltrnas, SMCTA, CHP, MTC, San Mateo County, San Mateo County Transit, Caltrain, BART, Dumbarton Express, Local Emergency Response and Public Safety Agencies
  • San Mateo County Smart Corridors Systems Engineering Management Plan

    • Name: San Mateo County Smart Corridors Systems Engineering Management Plan
      Description: The purpose of this document is to: 1) Identify the stakeholders and their roles/responsibilities, 2) Document the process to be followed in developing, installing, operating and maintaining the system, 3) Specify the documentation requirements for the system, and 4) Document the management controls that will be used to manage the project.
      Type: Systems Engineering Management Plans (Base Documents)
      Access: HTML MS Word

VTA Dynamic Passenger Information

  • Description: The primary objective of the DPI System is to provide VTA’s customers with accurate and reliable real-time transit information. This information includes the real-time location of transit vehicles and the estimated next vehicle arrival and departure times for all transit routes. It is envisioned that this information would be accessible by way of the Internet and telephone, as well as electronic information display boards at key transit stops within Santa Clara County. These locations include major bus stops, Bus Rapid Transit (BRT)/Rapid Bus stops, Light Rail Transit (LRT) stations, transit centers, and joint transit stops (e.g. those shared with other transit service providers). This real-time information would also be disseminated through MTC’s 511 Systems and VTA’s customer service center.
    Location: Santa Clara County, CA
    Partners: Santa Clara Valley Transportation Authority (VTA)
  • VTA Dynamic Passenger Information Project Management Plan

    • Name: VTA Dynamic Passenger Information Project Management Plan
      Description: This plan documents and defines the objectives of the project, the approach to be taken, and the commitment being assumed. This document contains the details required to successfully execute the project. Once project execution begins, this plan will be reviewed, baselined, and updated on a regular basis.
      Type: Project Plans
      Access: HTML MS Word
Federal Highway Administration | 1200 New Jersey Avenue, SE | Washington, DC 20590 | 202-366-4000