Example systems engineering documents were collected from many different ITS projects to support development of this website. This view provides access to the collected examples, organized by project. Note that these real world examples are not perfect, but you still may find them helpful. We are always looking for good examples, so please Contact Us if you or your agency may have additional examples to share.
| Description: | This project, part of the Advanced Transportation Congestion Management and Technology Demonstration (ATCMTD) program, implemented Integrated Corridor Management (ICM) systems on the Loop 101 corridor in the Phoenix metropolitan area. This Loop 101 Mobility Project leverages significant investments over the years by ADOT, MCDOT, Valley Metro, the Maricopa Association of Governments (MAG) and local agencies in freeway, arterial, and transit operations and management strategies. Building on the successful ADOT Freeway Management System (FMS) and several regional/local agencies traffic operations and management systems, ICM will facilitate improved real-time freeway-arterial coordination when incidents impact Loop 101 and divert traffic onto local streets. The ICM program will increase agency awareness of incidents, develop enhanced Decision-Support System (DSS) capabilities for advanced Transportation System Management and Operations (TSMO) strategy implementation, promote cross-agency information sharing, and provide advanced warning and alerts to travelers on the corridor to promote trip decision-making. The ATCMTD application also will pilot connected vehicle applications to support incident management and transit operations for ICM. The Loop 101 Mobility Project consists of multiple projects that will be planned, designed and implemented across multiple phases over the course of four years. |
|---|---|
| Location: | Phoenix, AZ |
| Partners: | Arizona DOT, Maricopa County DOT, Valley Metro, Maricopa Association of Governments, and local agenices. |
| Name: | ADOT Loop 101 Project Management Plan |
|---|---|
| Description: | The Loop 101 Mobility Project consists of multiple projects that will be planned, designed and implemented across multiple phases. This Project Management Plan (PMP) outlines the processes for managing and administering the project, including scope management, a quality control and quality management plan, a risk management strategy, schedule management and change management plans. It also includes a communications strategy for how communications will be facilitated among the multi-agency partnership as well as between PMTs and internal consultant teams. |
| Type(s): | Project Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101pmpNov2020.pdf(Opens in a new window) |
| Name: | ADOT Loop 101 Project Management Plan - Project Scope Excerpt |
|---|---|
| Description: | This excerpt of the ADOT Loop 101 Mobility Project Management Plan defines each of the project development processes in terms of the Vee model and provides an overview of each task with identification of responsible parties and a general discussion of the work involved. |
| Type(s): | Project Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101pmpNov2020excerptscope.pdf(Opens in a new window) |
| Name: | ADOT Loop 101 Project Management Plan - Risk Identification Excerpt |
|---|---|
| Description: | This excerpt of the ADOT Loop 101 Mobility Project Management Plan covers risk identification and mitigation for the project. It includes a table that identifies key risks with several mitigation strategies for each risk. |
| Type(s): | Project Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101pmpNov2020excerptriskid.pdf(Opens in a new window) |
| Name: | ADOT Loop 101 Systems Engineering Management Plan |
|---|---|
| Description: | The Loop 101 Mobility Project consists of multiple projects that will be planned, designed and implemented across multiple phases. The project will be complex, incorporating software acquisition and development, hardware acquisition, field device firmware and the integration of these into a system that supports both short-term and long-term decision-making. This Systems Engineering Management Plan (SEMP) will serve as a guiding document for how the systems engineering tasks and processes will be planned and implemented. |
| Type(s): | Systems Engineering Management Plans, Configuration Management Plans, Configuration Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020.pdf(Opens in a new window) |
| Name: | ADOT Loop 101 Systems Engineering Management Plan - CM Plan Excerpt |
|---|---|
| Description: | This excerpt of the ADOT Loop 101 Mobility Project SEMP describes the configuration management process for the project. It covers formation of a Change Management Board, Configuration Identification, Change Control, and Status Reporting. |
| Type(s): | Configuration Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020excerptcm.pdf(Opens in a new window) |
| Name: | ADOT Loop 101 Systems Engineering Management Plan - SE Process Excerpt |
|---|---|
| Description: | This excerpt of the ADOT Loop 101 Mobility Project SEMP describes the systems engineering process for the project. It describes in some detail how each of the systems engineering process steps will be performed. |
| Type(s): | Systems Engineering Management Plans |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020excerptseprocess.pdf(Opens in a new window) |
| Description: | The Buffalo NY ITS4US Deployment Project seeks to improve mobility to, from and within the Buffalo Niagara Medical Campus by deploying new and advanced technologies with a focus on addressing existing mobility and accessibility challenges. Examples of the technologies to be deployed are electric and self-driving shuttles, a trip planning app that is customized for accessible travel, intersections that use tactile and mobile technologies to enable travelers with disabilities navigate intersections, and Smart Infrastructure to support outdoor and indoor wayfinding. The deployment geography includes the 120-acre Medical Campus and surrounding neighborhoods with a focus on nearby neighborhoods with underserved populations. |
|---|---|
| Location: | Buffalo, NY |
| Partners: | ICF International, University at Buffalo, Open Doors Organization, RSG, ETCH, BNMC, NYSDOT, City of Buffalo, NFTA, NITTEC, GBNBRTC, USDOT |
| Name: | Buffalo NY ITS4US Phase 1 Concept of Operations |
|---|---|
| Description: | This document describes the Concept of Operations (ConOps) for Phase 1 of the Complete Trip Deployment in Buffalo, NY. This ConOps lists the high-priority user needs, describes the current environment that the system will be developed in, details the high-level functionality and capabilities to be deployed, and defines high-level outcomes and improvements expected from the deployment. |
| Type(s): | Concepts of Operations |
| Access: | https://rosap.ntl.bts.gov/view/dot/57571(Opens in a new window) |
| Name: | Buffalo NY ITS4US Phase 1 System Requirements Specification |
|---|---|
| Description: | This document is the System Requirements Specification, which identifies the requirements for the system's components to be developed or procured through this pilot. |
| Type(s): | Requirements |
| Access: | https://rosap.ntl.bts.gov/view/dot/61725(Opens in a new window) |
| Description: | CDOT developed extensive systems engineering analysis guidance in 2020-2021 that includes a process overview, a SEA assessment checklist, and templates for all of the key systems engineering documents. Consult their website for more information. |
|---|---|
| Location: | Colorado |
| Partners: | CDOT-Wide team including representation from HQ and all five regions. |
| Name: | CDOT SEA Assessment Checklist |
|---|---|
| Description: | The CDOT systems engineering analysis process includes a series of Word templates for the key SEA documents. The first template is the Technology/SEA Assessment Checklist that project managers use to determine the scope of the SEA for their particular project. |
| Type(s): | Process Checklists |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| Name: | CDOT Systems Engineering Analysis Document Templates |
|---|---|
| Description: | The CDOT systems engineering analysis process includes a series of Word templates for the key SEA documents. All templates are currently available on this webpage. |
| Type(s): | Concepts of Operations, Requirements, Design Specifications, Integration Plans, Operation and Maintenance Plans, Validation Documents |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| Name: | CDOT Systems Engineering Analysis Document Templates - ConOps and Validation Plan Excerpt |
|---|---|
| Description: | This template includes an abbreviated ConOps template that includes User Needs and a Validation Plan template. |
| Type(s): | Validation Documents |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplateconopsexcerptvalidation.pdf(Opens in a new window) |
| Name: | CDOT Systems Engineering Analysis Document Templates - Detailed Design Excerpt |
|---|---|
| Description: | This detailed design template covers detailed design information for hardware development, software development, and communications networks. It provides a series of sections that support early coordination and collaboration between ITS project managers and networking and ITS divisions that provide services to these projects. |
| Type(s): | Design Specifications |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplateddexcerptdd.pdf(Opens in a new window) |
| Name: | CDOT Systems Engineering Analysis Document Templates - High-Level Design Excerpt |
|---|---|
| Description: | This high-level design template provides some front matter and a content description for the initial document section. |
| Type(s): | Design Specifications |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplatehldexcerpthld.pdf(Opens in a new window) |
| Name: | CDOT Systems Engineering Analysis Process Overview |
|---|---|
| Description: | CDOT has a well documented systems engineering analysis process. This webpage provides an overview of the process for CDOT project managers. |
| Type(s): | Process Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/systems-engineering-analysis-sea(Opens in a new window) |
| Description: | Ohio is home to dozens of public and private entities all involved in the design, development, testing, use, and regulation of automated, connected, electric, and advanced air mobility technologies. DriveOhio, the state's center for smart mobility, connects all of these organizations to advance this technology across the state. An integral part of the Ohio Department of Transportation, DriveOhio fosters cooperation and collaboration, offers faster access to resources, and improves efficiency for people and organizations that are looking to be a part of this industry. |
|---|---|
| Location: | Ohio |
| Partners: | Ohio Department of Transportation and Public and Private Partners |
| Name: | Ohio Statewide CV/AV Concept of Operations |
|---|---|
| Description: | The Ohio CV/AV Concept of Operations (ConOps) describes, at a high-level, how CV/AV applications can be implemented and coordinated to address transportation needs. This includes identifying stakeholder roles and responsibilities for CV/AV applications, and the data they share to meet those needs. Building on the Ohio Statewide CV/AV Architecture, the ConOps describes the state of existing transportation systems in Ohio; presents the justi?cation for changing those systems to support CV/AV; outlines a proposed system concept for identi?ed CV/AV functions, including an ODOT Event Streaming Platform that will enable this functionality; identifies operational scenarios to demonstrate the in?uence of CV/AV in the delivery of transportation services; and describes anticipated impacts and performance measures for the proposed system concept. |
| Type(s): | Concepts of Operations |
| Access: | https://drive.ohio.gov/programs/av-cv/cv-av-systems/tools/03-conops(Opens in a new window) |
| Name: | Ohio Statewide CV/AV Concept of Operations - Operational Scenarios Excerpt |
|---|---|
| Description: | This excerpt from the Ohio Statewide CV/AV Concept of Operations includes the Operational Scenarios chapter. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioconopsexcerptopscenarios.pdf(Opens in a new window) |
| Name: | Ohio Statewide CV/AV Concept of Operations - Scope Excerpt |
|---|---|
| Description: | This excerpt from the Ohio Statewide CV/AV Concept of Operations includes the Scope chapter. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioconopsexcerptscope.pdf(Opens in a new window) |
| Name: | Ohio System Requirements Workbook |
|---|---|
| Description: | The Ohio CV/AV System Requirements Workbook outlines functional requirements for all CV/AV deployments in Ohio. Ohio project owners should follow these as a baseline to meet project-specific requirements and procurement documentation, which support overall function of any CV application and set the stage for interoperability among various deployments. The provided link includes a number of requirements document downloads organized by application and focus area. I link to guidance on how to use the Workbook is also available. |
| Type(s): | Requirements |
| Access: | https://drive.ohio.gov/programs/av-cv/cv-av-systems/requirements/02-system-workbook(Opens in a new window) |
| Name: | Ohio System Requirements Workbook - Road Weather Requirements Excerpt |
|---|---|
| Description: | This excerpt from the Ohio CV/AV System Requirements Workbook includes the Road Weather Application Requirements. |
| Type(s): | Requirements |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioreqexcerptrws.pdf(Opens in a new window) |
| Description: | The primary objectives of the D2 FRAME project were to identify, select, and deploy connected vehicle (CV) equipment that can support emerging safety and mobility applications throughout the Gainesville region. Specifically, D2 FRAME deployed CV equipment on the Interstate 75 (I-75) corridor as well as various arterial roads within Alachua County and the City of Gainesville. There were no roadside CV technologies or systems currently deployed within Alachua County, the City of Gainesville, or within the limited-access right-of-way of I-75. Enhancing existing traffic control systems with CV equipment will provide a platform able to support state-of-the-art safety and mobility applications, enhance the City's ability to efficiently operate arterial corridors, and provide a regional research and development environment for future CV-related initiatives and operations. The addition of CV equipment will further enhance both the City's and FDOT's ability to cooperatively operate arterial and limited-access corridors and expand their existing capabilities. D2 FRAME is a component of a larger project encompassing deployments along the I-75 corridor through both the Gainesville area in Alachua County (District 2) and the Ocala area in Marion County (District 5). |
|---|---|
| Location: | Gainesville, FL |
| Partners: | FDOT, FDOT District 2, City of Gainesville |
| Name: | FDOT D2 FRAME Concept of Operations |
|---|---|
| Description: | This ConOps was developed for the D2 FRAME CV Infrastructure deployment project. The purpose of this document was to identify and outline the Concept of Operations (ConOps) for the Florida Department of Transportation (FDOT) District 2 (D2) Florida's Regional Advanced Mobility Elements (FRAME) project. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameConOps-v1.pdf(Opens in a new window) |
| Name: | FDOT D2 FRAME Concept of Operations - System Overview Excerpt |
|---|---|
| Description: | This excerpt includes the System Overview from the FDOT D2 FRAME Concept of Operations. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameConOps-v1excerptsysoverview.pdf(Opens in a new window) |
| Name: | FDOT D2 FRAME CV Alternatives Analysis |
|---|---|
| Description: | This alternatives analysis was developed for the D2 FRAME CV Infrastructure deployment project. The purpose of this document was to summarize the evaluation and testing strategy used to evaluate multiple alternative systems and findings to date, including methods used for CV system evaluation and product selection. |
| Type(s): | Alternatives Analysis/Trade Study |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameCVAlternativeAnalysis.pdf(Opens in a new window) |
| Name: | FDOT D2 FRAME CV Infrastructure Deployment PSEMP |
|---|---|
| Description: | This project systems engineering management plan was developed for the D2 FRAME CV Infrastructure deployment project. It used FDOT's Statewide Systems Engineering Management Plan as a reference guide. |
| Type(s): | Systems Engineering Management Plans |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2framePSEMP-v2.pdf(Opens in a new window) |
| Name: | FDOT D2 FRAME CV Infrastructure Deployment PSEMP - SE Process Excerpt |
|---|---|
| Description: | This excerpt of the FDOT D2 FRAME CV Infrastructure Deployment PSEMP provides a brief overview of the SE process steps as tailored for this project. |
| Type(s): | Systems Engineering Management Plans |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2framePSEMP-v2excerptseprocess.pdf(Opens in a new window) |
| Description: | Florida Department of Transportation conducted a series of process workshops, performed a appraisal of their Systems Engineering capabilities, and established a procedure for FDOT and other agencies in the state to follow. The process is supported by a series of templates for systems engineering documentation. |
|---|---|
| Location: | Florida |
| Partners: | FDOT |
| Name: | FDOT Systems Engineering and Intelligent Transportation Systems (ITS) Procedure |
|---|---|
| Description: | The Florida Department of Transportation Systems Engineering and Intelligent Transportation Systems (ITS) Procedure #750-040-003 provides FDOT, other state agency, and local agency information on carrying out the systems engineering process for the delivery of ITS projects, including the use of the Systems Engineering templates as applicable. |
| Type(s): | Process Guidance |
| Access: | https://www.arc-it.net/seforits/files/fdot/750-040-003.pdf(Opens in a new window) |
| Name: | FDOT Systems Engineering Overview |
|---|---|
| Description: | FDOT has a well documented systems engineering process. This webpage provides background on systems engineering efforts at FDOT and links to the key procedure (750-040-003), a statewide Systems Engineering Management Plan (SEMP), and templates for all systems engineering documents. |
| Type(s): | Process Guidance |
| Access: | https://www.fdot.gov/traffic/ITS/Projects-Deploy/SEMP.shtm(Opens in a new window) |
| Name: | FDOT Systems Engineering Project Checklist |
|---|---|
| Description: | This checklist (FDOT Form #750-040-06) is used to show an ITS Project is compliant with 23 CFR 940 and an FDOT procedure (#750-040-003) for system engineering. This is version 1 of the checklist, dated 10/10/2017. Visit the FDOT website if you need the latest version. |
| Type(s): | Process Checklists |
| Access: | https://www.arc-it.net/seforits/files/fdot/w75004006_v001.pdf(Opens in a new window) |
| Description: | FHWA has published a series of Systems Engineering (SE) Model Documents that can be used to guide the deployment of common ITS projects. They guide the user through the process of developing systems engineering documents for definition and procurement of frequently deployed projects that include traffic signals, dynamic message signs, CCTV systems, and sensor and detection systems. The model documents are intended for projects that are relatively small and use existing products to support well-established ITS applications. Agencies building large projects with custom software development or innovative applications will need to perform more detailed custom systems engineering, though these documents may provide an effective and time-saving starting point for that effort |
|---|---|
| Location: | US-National |
| Partners: | Federal Highway Administration |
| Name: | FHWA Model Systems Engineering Documents for Central Traffic Signal Systems |
|---|---|
| Description: | This document is intended to provide guidance for professionals involved in developing systems engineering documents covering the evaluation, selection and implementation of Central Traffic Signal Systems. (CTSS). It includes initial user needs, system requirements, and template statements that can support efficient development of a Concept of Operations, a Requirements Document, a Verification Plan, and a Validation Plan. The CCTS may be a brand new deployment or an expansion of an existing system. The Model Systems Engineering Documents for CTSS are intended for projects with the following characteristics: * Relatively small, such that the project budget cannot be reasonably expected to fund systems engineering document development from scratch. * Constrained to existing products in the market. The model documents are not intended to provide the detail necessary to support new significant software development. * Applications of CTSS already well-defined in the transportation industry. Agencies building large projects with custom software development or innovative applications will need to perform more detailed custom systems engineering, though these documents may provide an effective and time-saving starting point for that effort. |
| Type(s): | Concepts of Operations, Requirements, Verification Documents, Validation Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop19019/index.htm(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Central Traffic Signal Systems - Requirements Excerpt |
|---|---|
| Description: | This excerpt includes system requirements statements from the FHWA Model SE Documents for Central Traffic Signal Systems. |
| Type(s): | Requirements |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerptreq.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Central Traffic Signal Systems - Traceability Matrix Excerpt |
|---|---|
| Description: | This excerpt includes the needs to requirements traceability matrix from the FHWA Model SE Documents for Central Traffic Signal Systems. |
| Type(s): | Requirements |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerpttrace.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Central Traffic Signal Systems - User Oriented Operational Description Excerpt |
|---|---|
| Description: | This excerpt includes guidance for the User Oriented Operational Description from the FHWA Model SE Documents for Central Traffic Signal Systems. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamseexcerptuoopdescr.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Central Traffic Signal Systems (CTSS) - Conducting Validation |
|---|---|
| Description: | This excerpt from the FHWA Model SE Documents for CTSS provides chapter-by-chapter guidance for Validation Plans. |
| Type(s): | Validation Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerptvalidation.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Closed Circuit Television (CCTV) Systems |
|---|---|
| Description: | This document is intended to provide guidance for professionals involved in developing systems engineering documents covering the evaluation, selection and implementation of CCTV systems. It includes initial user needs, system requirements, and template statements that can support efficient development of a Concept of Operations, a Requirements Document, a Verification Plan, and a Validation Plan. The CCTV system may be a brand new deployment or an expansion of an existing system. The Model Systems Engineering Documents for CCTV Systems are intended for projects with the following characteristics: * Relatively small, such that the project budget cannot be reasonably expected to fund systems engineering document development from scratch. * Constrained to existing products in the market. The model documents are not intended to provide the detail necessary to support new significant software development. * Applications of CCTV are already well-defined in the transportation industry. Agencies building large projects with custom software development or innovative applications will need to perform more detailed custom systems engineering, though these documents may provide an effective and time-saving starting point for that effort. |
| Type(s): | Concepts of Operations, Requirements, Verification Documents, Validation Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18060/index.htm(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Dynamic Message Sign (DMS) Systems |
|---|---|
| Description: | This document is intended to provide guidance for professionals involved in developing systems engineering documents covering the evaluation, selection and implementation of Dynamic Message Sign (DMS) systems. It includes initial user needs, system requirements, and template statements that can support efficient development of a Concept of Operations, a Requirements Document, a Verification Plan, and a Validation Plan. The DMS system may be a brand new deployment or an expansion of an existing system. The Model Systems Engineering Documents for DMS Systems are intended for projects with the following characteristics: * Relatively small, such that the project budget cannot be reasonably expected to fund systems engineering document development from scratch. * Constrained to existing products in the market. The model documents are not intended to provide the detail necessary to support new significant software development. * Applications of DMS systems already well-defined in the transportation industry. Agencies building large projects with custom software development or innovative applications will need to perform more detailed custom systems engineering, though these documents may provide an effective and time-saving starting point for that effort. |
| Type(s): | Concepts of Operations, Requirements, Verification Documents, Validation Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18080/index.htm(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Dynamic Message Sign (DMS) Systems - Verification ID Excerpt |
|---|---|
| Description: | This excerpt from the FHWA Model SE Documents for DMS identifies high-level verification test cases for each major requirements category. |
| Type(s): | Verification Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsedmsexcerptvercaseid.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Dynamic Message Sign (DMS) Systems - Verification Methods Excerpt |
|---|---|
| Description: | This excerpt includes verification methods from the FHWA Model SE Documents for Dynamic Message Signs. |
| Type(s): | Requirements |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsedmsexcerptvermeth.pdf(Opens in a new window) |
| Name: | FHWA Model Systems Engineering Documents for Transportation Sensor and Detection Systems (TSDS) |
|---|---|
| Description: | This document is intended to provide guidance for professionals involved in developing systems engineering documents covering the evaluation, selection and implementation of Transportation Sensor and Detection Systems (TSDS). It includes initial user needs, system requirements, and template statements that can support efficient development of a Concept of Operations, a Requirements Document, a Verification Plan, and a Validation Plan. The TSDS may be a brand new deployment or an expansion of an existing system. The Model Systems Engineering Documents for TSDS are intended for projects with the following characteristics: * Relatively small, such that the project budget cannot be reasonably expected to fund systems engineering document development from scratch. * Constrained to existing products in the market. The model documents are not intended to provide the detail necessary to support new significant software development. * Applications of TSDS already well-defined in the transportation industry. Agencies building large projects with custom software development or innovative applications will need to perform more detailed custom systems engineering, though these documents may provide an effective and time-saving starting point for that effort. |
| Type(s): | Concepts of Operations, Requirements, Verification Documents, Validation Documents |
| Access: | (Coming Soon) |
| 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 |
| Name: | CHART II System Requirements |
|---|---|
| Description: | This is one of many systems engineering documents that were produced for Maryland CHART. |
| Type(s): | Requirements |
| Access: | https://www.arc-it.net/seforits/files/chart/chartsysreq.pdf(Opens in a new window) |
| 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 |
| Name: | 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(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/minntmc/minntmcconops.pdf(Opens in a new window) |
| Description: | MnDOT has developed a process, along with guidance, tools and useful resources, to implement systems engineering and ensure compliance with their Highway Project Development Process (HPDP) for all projects containing ITS. |
|---|---|
| Location: | Minnesota |
| Partners: | MnDOT and Local Agencies |
| Name: | MnDOT Systems Engineering Overview |
|---|---|
| Description: | This is the primary entry point that provides links to the Highway Project Development Process, a decision tree tool, a quick reference with step-by-step instructions, and a detailed set of checklists for most common ITS projects. The example content includes Concepts of Operation, Requirements, and Test Plans for many types of projects that are grouped by class. If you are looking for systems engineering information for most types of typical ITS projects, you are likely to find it in this broad collection of ITS technical resources. |
| Type(s): | Process Guidance, Process Checklists, Concepts of Operations, Requirements, Verification Documents |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(Opens in a new window) |
| Description: | The NYC central TSP project is intended to increase the on-time schedule performance of the Metropolitan Transportation Authority's (MTA) 5800+ buses over their 2,952 miles of service routes in all five boroughs and improve the overall intersection traffic operation (delays, speed, air quality, etc.) specifically during the peak commute hours. |
|---|---|
| Location: | New York City |
| Partners: | NYC MTA and DOT |
| Name: | NYC Transit Signal Priority SEA Final Report |
|---|---|
| Description: | This document is an update to the "Transit Signal Priority Project Systems Engineering Analysis Report (TSP PSEAR)" dated January 2015. This update includes NYC central Traffic Signal Priority (TSP) developments since January 2015, including alignment with the 2018 update of the NYC Sub-regional Intelligent Transportation System (ITS) Architecture (NYCSRA). The NYCSRA 2018 update, in turn, incorporates dataflows recommended in the 2015 TSP PSEAR relevant service packages. This report is written for systems engineering staff responsible for overseeing ITS programs. It includes information for constructing and deploying the system which provides the foundation for system operation and future configuration management. |
| Type(s): | Process Checklists |
| Access: | https://www.arc-it.net/seforits/files/nyctsp/TspPsear2019UpdateFinalv5.pdf(Opens in a new window) |
| Description: | The Interstate 495 (I-495) Corridor, centrally located in the New York/New Jersey metropolitan area with a population of 19.8 million people, is the most densely populated area in the United States. In response to the need to enhance mobility, safety and travel reliability across the region, partnering agencies and authorities, led by the New York City Department of Transportation (NYC DOT) and New York State Department of Transportation (NYSDOT) submitted and received a United States Department of Transportation (USDOT) grant to support the development of a Concept of Operations (ConOps) for Integrated Corridor Management (ICM) on the I-495 corridor. The purpose of the ICM initiative in this corridor (henceforth referred to as the ICM-495 corridor) is to align relevant congestion management processes across the metropolitan region in order to build integrated, balanced and responsive transportation programs and systems throughout the corridor. |
|---|---|
| Location: | New York/New Jersey Metro Area |
| Partners: | Includes New York and New Jersey state transportation agencies (NYSDOT and NJDOT), New York City’s transportation agency (NYC DOT), and New York and New Jersey MPOs (NYMTC and NJTPA) and other public and private entities responsible for operations in the region |
| Name: | NYM Integrated Corridor Management ConOps for the I-495 Corridor in the NY Metro Region |
|---|---|
| Description: | This document presents the ConOps for the ICM-495 Corridor and is developed based on input from regional operations, maintenance, and systems management stakeholders. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/nycicm/ICM-495ConOpsFINAL.pdf(Opens in a new window) |
| Name: | NYM Integrated Corridor Management ConOps for the I-495 Corridor in the NY Metro Region - User Needs Excerpt |
|---|---|
| Description: | This is an excerpt from the NYM Integrated Corridor Management ConOps that includes the User Needs |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/nycicm/ICM-495conopsfinal-userneeds.pdf(Opens in a new window) |
| Description: | The NYC CVPD project is one of three initial CV deployment projects that establish a base for growing a nation-wide connected vehicle system. As such, its focus is on utilizing standards to build basic infrastructure in a manner that provides a foundation for future deployments of connected vehicle technology. The NYC CVPD project provides a real demonstration and evaluation of the benefits of the CV technology in a dense urban environment. NYC has deployed a robust infrastructure with advanced traffic controllers (ATC), an advanced adaptive traffic signal control system which currently uses travel times as part of its operational algorithms, an aggressive maintenance program, and a ubiquitous high speed wireless network (NYCWiN). By deploying Aftermarket Safety Devices (ASD) and Roadside Units (RSU), our team can bring the benefits of the CV paradigm to NYC's Vision Zero initiative and provide the opportunity to evaluate the benefits with a significant number of vehicles that are regularly driving in the area. This project will also provide the Federal Highway Administration (FHWA) the opportunity to showcase the benefits of CV technology without replacing the vehicle fleet – which is likely to be the situation for many years to come. At the same time, the NYC CVPD will be used to demonstrate the benefits to vulnerable road users who suffer the most from roadway fatalities in NYC. |
|---|---|
| Location: | New York City |
| Partners: | NYCDOT, NYC DCAS, MTA/NYCT, PASS, USDOT |
| Name: | NYC CV Pilot Deployment System Design |
|---|---|
| Description: | This System Design Document (SDD) describes the scope of the proposed New York City (NYC) Connected Vehicle Pilot Deployment (CVPD) system. It is a continuation of the systems engineering work based on the system architecture identified in the System Architecture Document (SAD). Its objective is to identify the subsystems and decompose them further into components. This document defines the system components and their interfaces and traces the requirements to them. Specific details on the individual system interfaces and their ITS standards are listed in the Interface Control Document (ICD). |
| Type(s): | Design Specifications |
| Access: | https://rosap.ntl.bts.gov/view/dot/61189(Opens in a new window) |
| Name: | NYC CV Pilot Deployment System Design – Traceability Matrix Excerpt |
|---|---|
| Description: | This is an excerpt from the NYC Connected Vehicle Pilot System Design document. This traceability matrix connects system requirements with system design elements. |
| Type(s): | Design Specifications |
| Access: | https://www.arc-it.net/seforits/files/cvpilotnyc/dot_61189_ds1nyccvpilottracematrix.pdf(Opens in a new window) |
| Description: | The purpose of this project was to develop a concept of operations for a statewide variable speed system. The primary stakeholder, the Oregon Department of Transportation, wishes to create a statewide variable speed system that is flexible enough to cater to all highways throughout the state, whether urban or rural, highway or interstate. The goal of this project is to ensure that future variable speed systems operate under the same guidelines so that consistency can be achieved between systems. |
|---|---|
| Location: | Oregon |
| Partners: | ODOT HQ and all ODOT regions |
| Name: | ODOT Active Traffic Management Suite and Travel Time Concept of Operations |
|---|---|
| Description: | The purpose of this document is to describe the operation of the Oregon statewide Active Traffic Management (ATM) Suite application that automates messages to variable message signs for congestion warning, weather warning, and variable speed limits. This document was prepared in accordance with the Oregon Statewide Variable Speed System Concept of Operations and provides substantially more detail than would be provided in a typical Concept of Operations. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotatmsconops.pdf(Opens in a new window) |
| Name: | Oregon Variable Speed System Concept of Operations |
|---|---|
| Description: | Many independent variable speed systems are currently or will soon be in operation throughout Oregon. As more projects are being planned, ODOT wishes to create one system that can process real-time data and provide an automated response appropriate for the measured condition, independent of location. This ConOps defines this statewide variable speed system. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotvssconops.pdf(Opens in a new window) |
| Name: | Oregon Variable Speed System Concept of Operations - User Oriented Operational Description Excerpt |
|---|---|
| Description: | This excerpt of the Oregon Variable Speed System Concept of Operations includes the User Oriented Operational Description. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotvssconopsexcerptuoopdesc.pdf(Opens in a new window) |
| Description: | Pennsylvania DOT shared systems engineering guidance for adaptive signal control systems and integration of ITS devices into PennDOTs Advanced Traffic Management System (ATMS) and Video Management System (VMS) |
|---|---|
| Location: | Pennsylvania |
| Partners: | PennDOT |
| Name: | PennDOT TSMO Design and Integration Guidelines |
|---|---|
| Description: | The intent of this guide is to serve as a reference to design consultants, contractors, and network integrators on key items that should be considered during the various phases of a PennDOT Intelligent Transportation Systems (ITS) design project for successful integration of ITS devices into PennDOT's Advanced Traffic Management System (ATMS) software platform and/or PennDOT's Video Management System (VMS). The main body of the document provides the design guidance. Two appendices provide sample systems engineering documentation for a typical simple project that adds a few devices and a complex project that implements new variable speed limit and queue warning capabilities to a corridor. Each appendix includes a sample ConOps, System Requirements, a system design with specified device locations, a communications plan that includes an integration plan, maintenance and operations overview, a cost assessment, and a procurement strategy. |
| Type(s): | Process Guidance, Concepts of Operations, Requirements, Design Specifications, Integration Plans, Deployment Plans |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.pdf(Opens in a new window) |
| Name: | PennDOT TSMO Design and Integration Guidelines - Operational and Support Environment Excerpt |
|---|---|
| Description: | This excerpt includes chapters covering the Operational Environment and the Support Environment from the PennDOT TSMO Design and Integration Guidelines. |
| Type(s): | Concepts of Operations, Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelinesexcerptOpsSupportEnv.pdf(Opens in a new window) |
| Name: | PennDOT TSMO Design and Integration Guidelines - Operational and Support Environment Excerpt |
|---|---|
| Description: | This excerpt includes chapters covering the Operational Environment and the Support Environment from the PennDOT TSMO Design and Integration Guidelines. |
| Type(s): | Concepts of Operations, Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelinesexcerptOpsSupportEnv.pdf(Opens in a new window) |
| Name: | Pennsylvania Adaptive Signal Control System Evaluation |
|---|---|
| Description: | This document is used to properly evaluate and streamline the Systems Engineering Process for Adaptive Signal Control Systems. This document follows guidance provided by the Federal Highway Administration's (FHWA) Model Systems Engineering Documents for Adaptive Signal Control Technology (ASCT) Systems (FHWA-HOP-11-027) and PennDOT's direction for adaptive signal systems in Publication 46. Upon completing this document, the appropriate needs, requirements, and evaluation of acceptable vendor products, a recommendation will be made based on the information and technology available when this evaluation was completed. |
| Type(s): | Process Guidance, Process Checklists |
| Access: | https://www.arc-it.net/seforits/files/penndot/pennascse.pdf(Opens in a new window) |
| Description: | NCHRP Research Report 978: Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors provides state and local transportation agencies with a systems engineering approach for planning the integration of connected vehicle technologies along roadways in rural corridors This research project followed a systems engineering process to develop a model concept of operations (ConOps) and a model system requirements specifacation (SyRS) for connected vehicle applications most relevant to rural corridors. Both documents are resources for state and local practitioners, agencies, and their contractor/consultant as they begin to deploy connected vehicle technologies. Whether or not an agency is using highway trust funds for the rural connected vehicle deployment, these products will support connected vehicle deployments that ensure local needs and challenges are addressed, measurable goals and objectives are set, and appropriate connected vehicle applications and solutions are identi ed. |
|---|---|
| Location: | US-National |
| Partners: | National Cooperative Highway Research Program |
| Name: | Rural Connected Vehicle Corridors - Model Concept of Operations |
|---|---|
| Description: | NCHRP Research Report 978 provides state and local transportation agencies with a systems engineering approach for planning the integration of connected vehicle technologies along roadways in rural corridors This model ConOps contains information that will apply in general to most current and proposed rural systems and is intended to be a starting point for readers. It addresses core, common priorities and provides a base document that deploying agencies can customize to fit their specific project and situation. It is not written for a specific implementation and does not address a transportation agency's unique operations and system management. |
| Type(s): | Concepts of Operations |
| Access: | https://nap.nationalacademies.org/catalog/26388/initiating-the-systems-engineering-process-for-rural-connected-vehicle-corridors-volume-2-model-concept-of-operations(Opens in a new window) |
| Name: | Rural Connected Vehicle Corridors - Model Concept of Operations - Operational Scenarios Excerpt |
|---|---|
| Description: | This excerpt includes the Operational Scenarios chapter from the Rural Connected Vehicle Corridors Model ConOps, NHCRP Research Report 978. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/rcvc/26388excerptopscen.pdf(Opens in a new window) |
| Name: | Rural Connected Vehicle Corridors - Model System Requirements Specification |
|---|---|
| Description: | NCHRP Research Report 978 provides state and local transportation agencies with a systems engineering approach for planning the integration of connected vehicle technologies along roadways in rural corridors. This document is a model System Requirements Specification (SyRS), meaning it contains information that will apply in general to most current and proposed systems, and it is intended to be a starting point for deployers. It addresses the core, common priorities and provides a base document that a deploying agency can customize to their project and situation. It is not written for a specifi c implementation and does not address a transportation agency's unique operation and system management. |
| Type(s): | Requirements |
| Access: | https://nap.nationalacademies.org/catalog/26387/initiating-the-systems-engineering-process-for-rural-connected-vehicle-corridors-volume-3-model-system-requirements-specification(Opens in a new window) |
| Name: | Rural Connected Vehicle Corridors - Research Overview |
|---|---|
| Description: | NCHRP Research Report 978: Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors provides state and local transportation agencies with a systems engineering approach for planning the integration of connected vehicle technologies along roadways in rural corridors This report provides an overview of the research project and provides key context for the model Concept of Operations and System Requirements Specification that were developed. |
| Type(s): | Miscellaneous |
| Access: | https://nap.nationalacademies.org/catalog/26389/initiating-the-systems-engineering-process-for-rural-connected-vehicle-corridors-volume-1-research-overview(Opens in a new window) |
| 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 |
| Name: | Sacramento 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(s): | Verification Documents |
| Access: | https://www.arc-it.net/seforits/files/starnet/starnetvp.pdf(Opens in a new window) |
| Name: | Sacramento STARNET Verification Plan - Conducting Verification Excerpt |
|---|---|
| Description: | This excerpt from the STARNET Verification Plan describes the process to be used for conducting system verification. |
| Type(s): | Verification Documents |
| Access: | https://www.arc-it.net/seforits/files/starnet/starnetvpexcerptconducting.pdf(Opens in a new window) |
| Description: | The Next Operating System (OS) is one of 5 Big Moves introduced in the SANDAG 2021 Regional Transportation Plan for the San Diego region. The Next OS is envisioned to be a next generation system that will connect all devices, vehicles, and travel options through a proactively managed approach that includes integrated trip planning, payment, and reservation choices. This broad vision will ultimately be implemented by multiple projects spanning multiple modes. To further define the Next OS concept, SANDAG developed several high-level Concepts of Operation for Next OS use cases in parallel with the 2021 Regional Plan update. |
|---|---|
| Location: | San Diego, CA |
| Partners: | SANDAG, Caltrans, Local Agencies |
| Name: | SANDAG 2021 Regional ITS Architecture Update |
|---|---|
| Description: | In parallel with the 2021 regional plan, the San Diego Regional ITS Architecture was updated to support the 5 Big Moves envisioned in the regional plan, including the Next OS. This document provides an overview of the updates that put the Next OS into the regional ITS architecture context, with links to the online regional ITS architecture for San Diego. |
| Type(s): | Other Technical Planning Documents |
| Access: | https://www.arc-it.net/seforits/files/sandagnos/sandag2021raupdate.pdf(Opens in a new window) |
| Name: | SANDAG Curb Access Management Concept of Operations |
|---|---|
| Description: | The purpose of this document is to provide a Concept of Operations (ConOps) for curbside management implementation in the San Diego region. The ConOps provides a non-technical description of the curbside management system from the point of view of the stakeholders, giving each stakeholder a conceptual look at how the system will function and their roles and responsibilities in operating and maintaining the system. The ConOps provides a high-level description of the system, how it will operate, who will operate what, and describes the anticipated scenarios under which the system will be operating. This document allows stakeholders to provide input on the high-level concept of the system and ultimately agree to the system to be designed. Stakeholders can use this document as a framework for further development of projects, policies, and projects that reflect the goals, objectives, and needs presented here. While the ConOps provides a regional vision for deployments that are consistent with the San Diego Forward: 2021 Regional Plan, implementation will be performed by local stakeholder groups. The existing capabilities of each agency and each corridor vary significantly across the region, and the operational scenarios presented in this document have been chosen to represent a cross-section of possibilities for the diverse user groups across the region. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/sandagnos/sandagcamconops.pdf(Opens in a new window) |
| Name: | SANDAG Smart Intersection Systems Concept of Operations |
|---|---|
| Description: | The purpose of this document is to provide a Concept of Operations (ConOps) for Smart Intersection Systems (SIS) implementation in the San Diego region. The ConOps provides a non-technical description of the SIS from the point of view of the stakeholders, giving each stakeholder a conceptual look at how the system will function and their roles and responsibilities in operating and maintaining the system. This ConOps provides stakeholders the opportunity to provide input on the high-level system concept and provides a description of how the system will operate, who will operate what, and a description of three operational scenarios. Stakeholders can use this document as a framework for further development of projects, policies, and projects that reflect the goals, objectives, and needs presented here. While the ConOps provides a regional vision for deployments that are consistent with the San Diego Forward: 2021 Regional Plan, implementation will be performed by local stakeholder groups. The existing capabilities of each agency and each corridor vary significantly across the region, and the operational scenarios presented in this document have been chosen to represent a cross-section of possibilities for the diverse user groups across the region. Stakeholders should conduct a capability maturity assessment to determine strategies that will enable them to benefit from the full range of functionalities. |
| Type(s): | Concepts of Operations |
| Access: | https://www.arc-it.net/seforits/files/sandagnos/sandagsisconops.pdf(Opens in a new window) |
| 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). |
| 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(s): | Configuration Management Plans |
| Access: | https://www.arc-it.net/seforits/files/sfpark/sfparkcm.pdf(Opens in a new window) |
| 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(s): | Systems Engineering Management Plans |
| Access: | https://www.arc-it.net/seforits/files/sfpark/sfparksemp.pdf(Opens in a new window) |
| 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(s): | Other Technical Planning Documents |
| Access: | https://www.arc-it.net/seforits/files/sfpark/sfparktrain.pdf(Opens in a new window) |
| 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 |
| Name: | CA 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(s): | Systems Engineering Management Plans |
| Access: | https://www.arc-it.net/seforits/files/sanmatsmart/sanmatsemp.pdf(Opens in a new window) |
| Description: | The Traffic Management Division (TMD) of the Utah Department of Transportation, in partnership with many cities, counties and other agencies throughout Utah, is responsible for the operation of a central traffic signal control system. The Signal Partners include 55 agencies that are responsible for signalized intersections within Utah. Combined, the Signal Partners operate over 1,500 signalized intersections in such jurisdictions as: Bountiful, Layton, Lehi, Logan, Ogden, Orem, Pleasant Grove, Provo, Salt Lake City, Salt Lake County, St. George, and UDOT controlled arterials. This project replaces the existing central traffic signal system ("i2", developed by Siemens) with a new central traffic signal system that will expand and enhance the Signal Partners capabilities to maximize the efficiency of traffic flow. |
|---|---|
| Location: | Utah |
| Partners: | UDOT, Cities, Counties, Other Local Agencies throughout Utah |
| Name: | UDOT Central Traffic Signal Control System RFP |
|---|---|
| Description: | The purpose of this request for proposal is for the State of Utah to enter into a contract with a qualified firm for the Supply and Implementation of a new central traffic signal control system (CTSCS). It is anticipated that this RFP may result in a contract award to a single contractor. The RFP includes a detailed scope of work for the CTSCS including an overview of current system capabilities and a set of system functional requirements, implementation requirements that cover testing, including system acceptance testing, warranty, and training. |
| Type(s): | Requests for Proposal, Requirements |
| Access: | https://www.arc-it.net/seforits/files/utahctscs/utahctscsrfp.pdf(Opens in a new window) |
| 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) |
| 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(s): | Project Management Plans |
| Access: | https://www.arc-it.net/seforits/files/vtadpi/vtadpipmp.pdf(Opens in a new window) |
