Intelligent Transportation Systems (ITS) Systems Engineering (SE) Process

Engineering process | Planning | Intelligent Transportation Systems

Introduction

Intelligent Transportation Systems (ITS) consists of electronics, communications, or information processing used to improve the efficiency of the transportation system singly or in combination.

The purpose of this guidance is to ensure that project managers and other practitioners implement 23 CFR §940 (Rule 940) on applicable trunk highway projects. The Federal Highway Administration (FHWA) established Rule 940 based on Federal Transit Administration (FTA) policy, the intent of which is to foster the integration of regional ITS systems, including regional ITS integration and deployment.

Rule 940 requires states to use a Systems Engineering (SE) process to develop all ITS systems and components. SE is an interdisciplinary approach that enables the realization of successful systems. The scale of the SE process must be on a scale commensurate with the project.

Resources

The following guidance documents are available for project managers:

Classes of ITS projects

Minnesota has five classes of ITS projects:

Class A-1: Programmatic ITS applications for standard traffic signals, road weather information systems (RWIS), weigh-in-motion (WIM) systems, and railroad-highway grade crossings
Class A-2: Programmatic ITS applications for dynamic message signs, traffic detection, video, ramp metering, communications, and flood warning systems
Class B-1: Freeway traffic management
Class B-2: Arterial traffic management
Class C: Large scale/complex ITS projects

Tools and resources to assist you with the identification of project classes and SE requirements are available on the MnDOT ITS Systems Engineering Website.

Class A-1 programmatic ITS applications

Class A-1 projects include:

Traffic signals, including:

Basic traffic signals
Flashing yellow arrows
Advanced warning flashers
Railroad preemption
Emergency vehicle preemption (localized without control center oversight)
Transit signal priority (localized without control center oversight)
Enforcement lights (e.g. blue lights)
Vehicle presence detection
Traffic signal interconnects (closed loop systems)

RWIS, including:

Environmental sensor stations
Communication systems for data transfer
Central hardware and software to collect and disseminate field data
Pan-tilt-zoom cameras

Railroad-Highway Grade Crossings, including:

Flashing light signals
Standard crossing gates
Four quadrant gates
Traffic signal preemption

WIM systems for commercial vehicle operations (CVO) weight enforcement and inspection

You can access MnDOT SE documentation for Class A-1 programmatic ITS applications on the MnDOT ITS Implementation for Connected and Automated Vehicles (CAV) Readiness Project Website.

Class A-2 programmatic ITS applications

Class A-2 projects include:

Dynamic message signs
Traffic detection
Ramp meters
Video
Video switches
Flood warning systems

You can access MnDOT SE documentation for Class A-2 programmatic ITS applications on the MnDOT SE for ITS Readiness Project Website.

Class B-1 Freeway management applications

Class B-1 projects include:

Traffic observation and detection, including:

Video (e.g. cameras)*
Traffic detection*
Condition reporting systems
Weather sensors and provisions of current and forecast weather conditions
Automatic vehicle location (AVL) for Freeway Incident Response Team (FIRST), maintenance, and State Patrol vehicles

Traffic Control Systems, including:

Lane control signs
Ramp meters*
Electronic toll collection*
Automated gate closure systems

Data processing and response formulation (manual and automated), including Traffic Management Center (TMC) software and data extract tools
Infrastructure support tools, including:

Landline communication (fiber, copper, telephone lines, digital subscriber lines (DSL))*
Wireless communication (point-to-point and cellular)*
Power

Information sharing, including

Dynamic message signs (DMS)*
Radio broadcasts
Web pages for construction and traveler information
511 phone
Computer Aided Dispatch (CAD) for FIRST, maintenance, and State Patrol vehicles

You can access MnDOT SE documentation for Class B-1 freeway management applications at MnDOT ITS Concept of Operations for Freeway Traffic Management. There is SE analysis available for programmatic ITS applications specific to MnDOT implementation. They include an * in the list above. Other agencies can use these SE documents as references for performing SE analysis for their deployments. Contact the MnDOT contact for more information.

Class B-2 Arterial traffic management applications

Class B-2 projects include:

Central traffic signal control systems
Adaptive signal control system and automated traffic signal performance measures (ATSPM)
Traffic observation and detection, including;

Video (e.g. cameras)*
Traffic detection*
Condition reporting systems

Local area arterial traffic control and traveler alerts, including:

Dynamic speed display signs
Emergency vehicle preemption (with or without control center oversight)
Red light running systems
Transit signal priority (with or without control center oversight)

Data processing and response formulation (manual and automated), including TMC software (e.g. central traffic signal control software*) and data extract tools
Infrastructure support tools, including:

Landline communication (fiber, copper, telephone lines, DSL lines)*
Wireless communication (point-to-point and cellular)*
Power

Information sharing (travelers, media, and other agencies), including:

Dynamic message signs (DMS)*
Web pages for construction and traveler information
511 phones

You can access MnDOT SE documentation for B-2 arterial management applications at MnDOT ITS Concept of Operations for Arterial Traffic Management. There is SE analysis available for programmatic ITS applications specific to MnDOT implementation. They include an * in the list above. Other agencies can use these SE documents as references for performing SE analysis for their deployments. Contact the MnDOT contact for more information.

Class C projects

The following list contains all of the class C applications:

Integrated corridor management (ICM)
Bus rapid transit (BRT)
Communications (e.g. fiber network)*
TMC
Incident management systems
Intersection conflict warning systems
Infrastructure-based safety systems
Truck priority
Smart work zones
Other complex applications that are not included in class B-1 or B-2

There is SE analysis available for programmatic ITS applications specific to MnDOT implementation. They include an * in the list above. Other agencies can use these SE documents as references for performing SE analysis for their deployments. Contact the MnDOT contact for more information.

ITS SE Rule 940 compliance

Application

Implementing the ITS SE process allows projects to move forward while taking proper consideration of interoperability and future expansion needs to enable full integration of ITS.

Implementing the ITS SE process for Rule 940 compliance is required for all ITS projects funded (in whole or in part) with the highway trust fund (Includes National Highway System (NHS) and non-NHS facilities).
MnDOT also requires that we the ITS SE process for Rule 940 compliance on all state-funded ITS projects in which there will be ITS component(s) connected/integrated to another ITS component, project, or system.

The ITS SE process applies to all ITS Class A-1, A-2, B-1, B-2, and C projects.

Implementation

When you are implementing the ITS SE process on your projects, you will have to:

Coordinate with the District Traffic Engineer or District State Aid Engineer to determine if the project is an ITS project and/or a project with an ITS component(s)
Receive the completed SE checklist from the Traffic Project Engineer
Submit the SE checklist to MnDOT’s Pre-Letting Engineer or the District State Aid Engineer (for federal authorization) with the Project Submittal

Statewide Regional ITS Architecture

The Minnesota Statewide Regional ITS Architecture is a shared vision of how multiple agencies’ systems work together with the systems of other agencies by sharing information and resources to enhance transportation safety, efficiency, capacity, mobility, and security. The information exchange among the many transportation stakeholders helps illustrate various integration options, gain consensus on cost-effective ITS technologies, and systems worth considering prior to the investigation of design, development, and deployment of ITS.

The latest architecture version includes a detailed operational concept for each service and identified need, providing more information on how to use a system and what stakeholder will use it.

The Minnesota Statewide Regional ITS Architecture Version 2018, Implementation Volume provides a full list of near-term and future ITS projects that the state and local transportation agencies defined in 2018. The Implementation Volume provides all necessary information and references for developing ITS projects while complying with 23 CFR §940.

The SE process

SE process steps

Use the SE process to develop, design, and implement the ITS project or projects with and ITS component. The SE analysis should be on a scale commensurate with the project scope.
Perform the minimum steps as follows:

Coordinate with regional ITS architecture:

Identify the portions of the regional ITS architecture being implemented from the Minnesota Statewide Regional ITS Architecture in order to

Ensure that the final design accommodates the interface requirements and information exchanges specified in the regional ITS architecture
Update the regional ITS architecture so that it accommodates the interface requirements and information exchanges of the project

If the Minnesota Statewide Regional ITS Architecture does not contain the ITS project:

Create a project-level architecture that coordinates with the development of the regional ITS architecture. Refer to CAV-X for guidance
Coordinate the project-level ITS architecture with the development of the regional ITS architecture to make sure the project accommodates the regional ITS architecture

Identify the roles and responsibilities of all participating agencies
Define requirements
Analyze alternative system configurations and technology options and determine what best meets requirements
Identify procurement options
Identify applicable ITS standards and testing procedures
Identify the procedures and resources necessary to operate and manage the system

SE process resources

See the following resources for more information about the SE process:

23 CFR §940.11
FHWA SE for ITS
SE Guidebook for ITS
Model Systems Engineering Documents for Adaptive Signal Control Technology (ASCT Systems)

Agencies involved

FHWA regulates FHWA-funded ITS projects and provides full oversight of ITS projects.

The MnDOT Office of CAV-X provides guidance and technical assistance for all ITS projects and projects with any ITS components, including guidance on the SE process.

Metropolitan Council and greater Minnesota metropolitan planning organizations (MPOs) manage the planning for ITS projects according to the MnDOT family of plans, including the Minnesota Statewide Regional ITS Architecture and Adoption of Minnesota Statewide Regional ITS Architecture.

Approvals

The following list explains who must approve certain types of projects:

Local projects: MnDOT State Aid for Local Transportation (SALT)
MnDOT trunk highway projects: Central Office Traffic, District Traffic, or Regional TMC (RTMC)
Transit projects: MnDOT Office of Transit
Railroad projects: MnDOT Office of Freight and Commercial Vehicle Operations (OFCVO)
WIM: MnDOT Transportation System Management, Traffic Forecasting and Analysis and/or District Traffic Office
RWIS: MnDOT Central Office Maintenance

General guidelines and regulations

Federal Register 23 CFR §§655 and 940

US DOT RITA/ITS Joint Program Office
FHWA ITS Architecture Implementation Program

SE and highway project development process Comparison

For ITS projects, the SE procedures complements the traditional DOT planning, pre-design, final design, and construction quality analysis/quality control (QA/QC) with a series of activities that are more appropriate for technology projects.

For ITS, the SE process begins with the development and implementation of an ITS architecture. It continues by outlining the steps and level of detail of each phase of project deployment from high-level tasks such as establishing a concept of operations to very detailed component design, installation, and testing. The purpose of the SE process is to ensure that a well-planned foundation is in place and then to affirm the requirements of an ITS system.

SE reduces risk and errors in developing complex projects. It is a cyclical process of planning, designing, implementing, testing, operating, and maintaining a system or project throughout its useful life.

Glossary

Concept of Operations (Con Ops): A narrative description of how a system should work

ITS Architecture: Both the logical architecture and physical architecture (infrastructure) designed to satisfy a defined set of user services. The logical architecture provides a common framework for ITS interoperability. ITS Architecture includes the functions and activities of ITS and provides a framework for planning, defining, and integrating these systems.

National ITS Architecture (also "Architecture Reference for Cooperative and Intelligent Transportation" or “ARC-IT”): Architecture maintained by the US DOT and available at https://local.iteris.com/arc-it/
Regional ITS Architecture: A regional framework for ensuring institutional agreement and technical integration for the implementation of ITS projects or groups of projects. Regional ITS architectures help guide the integration of ITS components. During development of a regional ITS architecture, agencies that own and operate transportation systems must consider current and future needs together to ensure that today's processes and projects are compatible with future deployments of ITS projects/systems.
Project-Level ITS Architecture: A framework that identifies the institutional agreement and technical integration necessary to interface a major ITS project with other ITS projects and systems

ITS Project: Any project that in whole or in part funds the acquisition of technologies or systems of technologies that provide or significantly contribute to the provision of one or more ITS user services as defined in the National ITS Architecture

Major ITS Project: Any ITS project that implements part of a regional ITS initiative that is multi-jurisdictional, multi-modal, or otherwise affects the regional integration of ITS systems

National ITS Architecture (also "national architecture"): See ITS Architecture

Project level ITS Architecture: See ITS Architecture

Region: The geographical area that identifies the boundaries of the regional ITS architecture and is defined by and based on the needs of the participating agencies and other stakeholders. In metropolitan areas, a region should be no less than the boundaries of the metropolitan planning area.

Regional ITS Architecture: See ITS Architecture

Systems Engineering (SE): An interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle (i.e. Concept of Operations), documenting requirements (i.e. Functional or System Requirements), then proceeding with design synthesis and system validation while considering the complete problem. Systems engineering integrates all disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. It also considers both the business and technical needs of all customers with the goal of providing a quality product that meets the user needs.