Home » Example View » Examples

Requests for Proposal

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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML PDF

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”.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML PDF

Project Plans

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.
  Project:	VTA Dynamic Passenger Information
  Access:	HTML MS Word

Systems Engineering Management Plans (Base Documents)

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML MS Word

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.
  Project:	San Mateo County Smart Corridors Program
  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.
  Project:	San Francisco Parking Management Program (SFpark)
  Access:	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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Configuration Management Plans

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML MS Word

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.
  Project:	San Francisco Bay Area Interim C2C System
  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.
  Project:	San Francisco Parking Management Program (SFpark)
  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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Other Technical Planning Documents

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML 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.
  Project:	San Francisco Parking Management Program (SFpark)
  Access:	HTML MS Word

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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Concepts of Operations

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.
  Project:	Minneapolis TMC Upgrade
  Access:	HTML PDF

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.
  Project:	I-15 Reversible Lanes Control System
  Access:	HTML MS Word

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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Requirements

CHART II System Requirements

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

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.
  Project:	I-15 Reversible Lanes Control System
  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.
  Project:	I-15 Reversible Lanes Control System
  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
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML MS Word

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
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Design Specifications

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.
  Project:	I-15 Reversible Lanes Control System
  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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Integration Plans

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML MS Word

Verification Documents

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word

Deployment Plans

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.
  Project:	I-680 Smart Carpool Lane Electronic Toll System
  Access:	HTML MS Word

FHWA Rule/FTA Policy Compliance Documents

California SERF – Electronic Toll Collection and Violation Enforcement

• Name:	California SERF – Electronic Toll Collection and Violation Enforcement
  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.
  Project:	Other
  Access:	HTML MS Word

California SERF - New Traffic Signal with Interconnect

• Name:	California SERF - New Traffic Signal with Interconnect
  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. The response is complete for this low-risk (“Minor”) ITS projects that does not require rigorous use of the systems engineering Vee life-cycle model.
  Project:	Other
  Access:	HTML MS Word

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.
  Project:	San Francisco Parking Management Program (SFpark)
  Access:	HTML MS Word

California SERF – Traffic Signal Coordination

• Name:	California SERF – Traffic Signal Coordination
  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. The response is complete for this low-risk (“Minor”) ITS projects that does not require rigorous use of the systems engineering Vee life-cycle model.
  Project:	Other
  Access:	HTML MS Word

California SERF – Transit Vehicle Signal Priority

• Name:	California SERF – Transit Vehicle Signal Priority
  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.
  Project:	Other
  Access:	HTML MS Word

California SERF – Transportation Management System

• Name:	California SERF – Transportation Management System
  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.
  Project:	Other
  Access:	HTML MS Word

New Jersey SERF- Programmatic ITS

• Name:	New Jersey SERF- Programmatic ITS
  Description:	This document is a Systems Engineering Review Form (SERF), and associated instructions, that provides responses to the federal regulatory requirements in 23 CFR 940 part 11. The Programmatic ITS definition applies to standard ITS systems, e.g., CCTV, DMS,HAR, WIM, RWIS, controlled traffic signals, and roadway detectorization.
  Project:	Other
  Access:	HTML MS Word

New Mexico DOT ITS Project Checklist

• Name:	New Mexico DOT ITS Project Checklist
  Description:	This checklist is submitted to the FHWA New Mexico Division Office for all NMDOT projects to demonstrate compliance with Rule 940. The checklist is also used to determine whether a project is minor (completing the checklist is sufficient) or major (a systems engineering management plan must also be submitted for approval).
  Project:	Other
  Access:	HTML MS Word

Tennessee Procedures for Implementing ITS Regulation 23CFR940

• Name:	Tennessee Procedures for Implementing ITS Regulation 23CFR940
  Description:	This document provides step by step procedures and guidelines for meeting Rule 940 for ITS projects in Tennessee. It includes guidance for different types of ITS projects and includes a Systems Engineering Analysis form that is completed that is sufficient for basic ITS projects.
  Project:	Other
  Access:	HTML MS Word

Miscellaneous

Caltrans Systems Engineering Evaluation for ITS Executive Summary

• Name:	Caltrans Systems Engineering Evaluation for ITS Executive Summary
  Description:	This executive summary is based on the “Final Report: Systems Engineering Evaluation  for ITS,” 2006 (Final Report). The primary objective of the study was to document and implement best practices in systems engineering for ITS projects and at a minimum  meet the 23 CFR 940 part 11 of the FHWA Final Rule on the application of the Systems  Engineering Analysis (SEA) for ITS projects.
  Project:	Other
  Access:	HTML PDF

Caltrans Systems Engineering Evaluation for ITS Final Report

• Name:	Caltrans Systems Engineering Evaluation for ITS Final Report
  Description:	The purpose of this systems engineering evaluation was to Capture best practices, evaluate the existing practices , develop a tailored project development model, and develop a Roadmap and Action Plan to successful implementation of SE best practices. A detailed CMMI appraisal was performed to support this evaluation.
  Project:	Other
  Access:	HTML PDF

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.
  Project:	Sacramento Transportation Area-wide Network (STARNET)
  Access:	HTML MS Word