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 deliverable. 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.
| 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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/systems-engineering-analysis-sea(Opens in a new window) |
| 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. |
| Project: | FDOT Systems Engineering 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. |
| Project: | FDOT Systems Engineering Guidance |
| Access: | https://www.fdot.gov/traffic/ITS/Projects-Deploy/SEMP.shtm(Opens in a new window) |
| 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. |
| Project: | Minnesota DOT Systems Engineering Guidance |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/pennascse.pdf(Opens in a new window) |
| 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: | https://www.arc-it.net/seforits/files/other/sampserfld.pdf(Opens in a new window) |
| 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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(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. |
| Project: | FDOT Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/fdot/w75004006_v001.pdf(Opens in a new window) |
| 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. |
| Project: | Minnesota DOT Systems Engineering Guidance |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(Opens in a new window) |
| 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. |
| Project: | New York City Transit Signal Priority |
| Access: | https://www.arc-it.net/seforits/files/nyctsp/TspPsear2019UpdateFinalv5.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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/pennascse.pdf(Opens in a new window) |
| 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: | https://www.arc-it.net/seforits/files/other/tnitsproc.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. |
| Project: | FDOT District 2 - Florida Regional Advanced Mobility Elements (D2 FRAME) |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameCVAlternativeAnalysis.pdf(Opens in a new window) |
| 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. |
| Project: | Utah DOT Central Traffic Signal Control System |
| Access: | https://www.arc-it.net/seforits/files/utahctscs/utahctscsrfp.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. |
| Project: | ADOT Loop 101 Mobility Project |
| 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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101pmpNov2020excerptriskid.pdf(Opens in a new window) |
| 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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101pmpNov2020.pdf(Opens in a new window) |
| 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: | https://www.arc-it.net/seforits/files/vtadpi/vtadpipmp.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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020excerptseprocess.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. |
| Project: | FDOT District 2 - Florida Regional Advanced Mobility Elements (D2 FRAME) |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2framePSEMP-v2excerptseprocess.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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020.pdf(Opens in a new window) |
| 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. |
| Project: | San Mateo County Smart Corridors Program |
| Access: | https://www.arc-it.net/seforits/files/sanmatsmart/sanmatsemp.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. |
| Project: | FDOT District 2 - Florida Regional Advanced Mobility Elements (D2 FRAME) |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2framePSEMP-v2.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. |
| Project: | San Francisco Parking Management Program (SFpark) |
| Access: | https://www.arc-it.net/seforits/files/sfpark/sfparksemp.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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020excerptcm.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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020.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. |
| Project: | ADOT Loop 101 Mobility Project |
| Access: | https://www.arc-it.net/seforits/files/loop101/loop101sempNov2020.pdf(Opens in a new window) |
| 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: | https://www.arc-it.net/seforits/files/sfpark/sfparkcm.pdf(Opens in a new window) |
| 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. |
| Project: | San Diego Next Operating System (OS) |
| Access: | https://www.arc-it.net/seforits/files/sandagnos/sandag2021raupdate.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. |
| Project: | San Francisco Parking Management Program (SFpark) |
| Access: | https://www.arc-it.net/seforits/files/sfpark/sfparktrain.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. |
| Project: | Drive Ohio |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioconopsexcerptscope.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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamseexcerptuoopdescr.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. |
| Project: | Oregon Statewide Variable Speed System |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotvssconopsexcerptuoopdesc.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 |
| Project: | New York Metro I-495 Integrated Corridor Management (ICM) |
| Access: | https://www.arc-it.net/seforits/files/nycicm/ICM-495conopsfinal-userneeds.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. |
| Project: | FDOT District 2 - Florida Regional Advanced Mobility Elements (D2 FRAME) |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameConOps-v1excerptsysoverview.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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelinesexcerptOpsSupportEnv.pdf(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. |
| Project: | Drive Ohio |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioconopsexcerptopscenarios.pdf(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. |
| Project: | Rural Connected Vehicle Corridors Systems Engineering Model Documents |
| Access: | https://www.arc-it.net/seforits/files/rcvc/26388excerptopscen.pdf(Opens in a new window) |
| 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. |
| Project: | Buffalo NY ITS4US Deployment Project |
| Access: | https://rosap.ntl.bts.gov/view/dot/57571(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| 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. |
| Project: | FDOT District 2 - Florida Regional Advanced Mobility Elements (D2 FRAME) |
| Access: | https://www.arc-it.net/seforits/files/fdotd2frame/fdotd2frameConOps-v1.pdf(Opens in a new window) |
| 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop19019/index.htm(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. |
| Project: | FHWA Model Systems Engineering 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18080/index.htm(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | (Coming Soon) |
| 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. |
| Project: | Minneapolis TMC Upgrade |
| Access: | https://www.arc-it.net/seforits/files/minntmc/minntmcconops.pdf(Opens in a new window) |
| 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. |
| Project: | Minnesota DOT Systems Engineering Guidance |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(Opens in a new window) |
| 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. |
| Project: | New York Metro I-495 Integrated Corridor Management (ICM) |
| Access: | https://www.arc-it.net/seforits/files/nycicm/ICM-495ConOpsFINAL.pdf(Opens in a new window) |
| 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. |
| Project: | Oregon Statewide Variable Speed System |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotatmsconops.pdf(Opens in a new window) |
| 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. |
| Project: | Drive Ohio |
| Access: | https://drive.ohio.gov/programs/av-cv/cv-av-systems/tools/03-conops(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. |
| Project: | Oregon Statewide Variable Speed System |
| Access: | https://www.arc-it.net/seforits/files/odotvss/odotvssconops.pdf(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.pdf(Opens in a new window) |
| 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. |
| Project: | Rural Connected Vehicle Corridors Systems Engineering Model Documents |
| 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: | 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. |
| Project: | San Diego Next Operating System (OS) |
| 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. |
| Project: | San Diego Next Operating System (OS) |
| Access: | https://www.arc-it.net/seforits/files/sandagnos/sandagsisconops.pdf(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerptreq.pdf(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. |
| Project: | Drive Ohio |
| Access: | https://www.arc-it.net/seforits/files/driveohio/driveohioreqexcerptrws.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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerpttrace.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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsedmsexcerptvermeth.pdf(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. |
| Project: | Buffalo NY ITS4US Deployment Project |
| Access: | https://rosap.ntl.bts.gov/view/dot/61725(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| Name: | CHART II System Requirements |
|---|---|
| Description: | This is one of many systems engineering documents that were produced for Maryland CHART. |
| Project: | Maryland CHART |
| Access: | https://www.arc-it.net/seforits/files/chart/chartsysreq.pdf(Opens in a new window) |
| 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop19019/index.htm(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. |
| Project: | FHWA Model Systems Engineering 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18080/index.htm(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | (Coming Soon) |
| 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. |
| Project: | Minnesota DOT Systems Engineering Guidance |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(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. |
| Project: | Drive Ohio |
| Access: | https://drive.ohio.gov/programs/av-cv/cv-av-systems/requirements/02-system-workbook(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.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. |
| Project: | Rural Connected Vehicle Corridors Systems Engineering Model Documents |
| 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: | 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. |
| Project: | Utah DOT Central Traffic Signal Control System |
| Access: | https://www.arc-it.net/seforits/files/utahctscs/utahctscsrfp.pdf(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. |
| Project: | NYC Connected Vehicle Pilot Deployment Program |
| Access: | https://www.arc-it.net/seforits/files/cvpilotnyc/dot_61189_ds1nyccvpilottracematrix.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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplatehldexcerpthld.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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplateddexcerptdd.pdf(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| 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). |
| Project: | NYC Connected Vehicle Pilot Deployment Program |
| Access: | https://rosap.ntl.bts.gov/view/dot/61189(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.pdf(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.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. |
| Project: | Sacramento Transportation Area-wide Network (STARNET) |
| Access: | https://www.arc-it.net/seforits/files/starnet/starnetvpexcerptconducting.pdf(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsedmsexcerptvercaseid.pdf(Opens in a new window) |
| 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop19019/index.htm(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. |
| Project: | FHWA Model Systems Engineering 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18080/index.htm(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | (Coming Soon) |
| 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. |
| Project: | Minnesota DOT Systems Engineering Guidance |
| Access: | https://www.dot.state.mn.us/its/systemsengineering.html(Opens in a new window) |
| 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. |
| Project: | Sacramento Transportation Area-wide Network (STARNET) |
| Access: | https://www.arc-it.net/seforits/files/starnet/starnetvp.pdf(Opens in a new window) |
| 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. |
| Project: | Pennsylvania Systems Engineering Guidance |
| Access: | https://www.arc-it.net/seforits/files/penndot/tsmodesignintegrguidelines.pdf(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| 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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.arc-it.net/seforits/files/cdotseag/cdottemplateconopsexcerptvalidation.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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://www.arc-it.net/seforits/files/fhwamse/fhwamsetssexcerptvalidation.pdf(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. |
| Project: | CDOT Systems Engineering Analysis Guidance |
| Access: | https://www.codot.gov/programs/intelligent-transportation-systems/systems-engineering-analysis-sea/sea-documents(Opens in a new window) |
| 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop19019/index.htm(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. |
| Project: | FHWA Model Systems Engineering 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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | https://ops.fhwa.dot.gov/publications/fhwahop18080/index.htm(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. |
| Project: | FHWA Model Systems Engineering Documents |
| Access: | (Coming Soon) |
| 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: | https://www.arc-it.net/seforits/files/other/caltransevalsumm.pdf(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. |
| Project: | Rural Connected Vehicle Corridors Systems Engineering Model Documents |
| 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) |
