Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors, Volume 2: Model Concept of Operations (2021)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

1   is preface, normally not included in a Concept of Operations (ConOps), is added to introduce background topics that set the tone for this model ConOps. • Project Background: NCHRP Project 08-120, “Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors” State and local transportation agencies are preparing their infrastructure for the inte- gration of connected vehicles. To date, most connected vehicle research has focused on applications in urban areas, but agencies also need long-term planning to assess resource needs required for deploying, operating, and maintaining connected vehicle infrastructure on rural corridors. Rural corridors oen include (1) long stretches of highway with limited power, communications, and intelligent transportation systems (ITS) infrastructure; (2) long distances between cities or services for travelers; (3) dierent trac and roadway charac- teristics (e.g., higher posted speed limits, higher percentage of truck volume, and roadway geometry); and (4) signicant incident-related rerouting distances. Connected vehicle deployments in rural areas present opportunities for potential improvements in safety, mobility, and eciency. erefore, it is important for the agencies that operate and maintain rural corridors have a vision for connected vehicle deployment. e objectives of this research are to identify (1) connected vehicle applications that will be most relevant on rural corridors; (2) scalable ways connected vehicles may be integrated into transportation agencies’ trac operations and management plans; (3) the requirements of connected vehicles and cyber-physical infrastructure within rural cor- ridors; (4) the anticipated roles and responsibilities of agencies in authorizing, deploy- ing, operating, and maintaining ITS and other transportation systems management and operations (TSMO) technologies within rural corridors; and (5) the related stang and resource needs. is research project uses a systems engineering approach to develop this model ConOps (NCHRP Research Report 978: Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors, Volume 2: Model Concept of Operations) and the System Requirements Specication (SyRS) (NCHRP Research Report 978: Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors, Volume 3: Model System Requirements Specication) to guide agencies responsible for rural corridors as they begin to assess their needs, operational concepts, scenarios, and requirements for connected vehicle deployment. P R E F A C E Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors, Volume 2: Model Concept of Operations

2 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors • How to Use This Model ConOps 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. To assist the reader in tailoring this model ConOps, the project team is using callout boxes labeled “Note to reader” (see the following example) to differentiate between “model ConOps text” and “how to adapt the text.” Note to reader: The deficiencies or limitations of the current ITS and processes presented in this section are based on feedback from project stakeholders interviewed during the development of this document. These problems or challenges within the current environment are representative of many rural settings but do not represent a comprehensive list of all issues agencies experience in rural corridors. The reader is encouraged to use this information as a starting point then tailor/add/delete information presented in this section based on the specific agency situation. Key sections of this model ConOps that readers may focus on in more detail and refer- ence more than others are Section 3.2, Description of the Current System or Situation; Section 4.2, Description of Desired Changes; Section, 5.2 Description of the Proposed System; and Section 6, Operational Scenarios. This is not to suggest that the other sections be ignored. • High-Level Overview of the Systems Engineering Process and the Role of the ConOps in the Systems Engineering Lifecycle Process Systems engineering is an interdisciplinary approach and means to enable the realization of a successful system that focuses on the entire system lifecycle as represented by FHWA’s Systems Engineering Vee diagram (see Figure 1). Customer needs and required functionality are defined early in the development stage. Requirements are documented followed by design synthesis and system validation while considering the complete problem: operations, cost and schedule, performance, training and support, test, manufacturing, and disposal. The ConOps is a foundation document that directs the technical course for the project. It is used to convey a high-level view of the system that each stakeholder can understand for the development of the system and how the system will be operated and maintained. The ConOps aims to identify high-level user needs and system capabilities that will later be used to develop the requirements of the proposed system (see NCHRP Research Report 978, Volume 3). The ConOps document serves as the bridge between the early project moti- vations and the technical requirements. It is technology-independent and focuses on the functionality of the proposed system. The ConOps document serves two additional purposes. The first is to communicate the user’s needs for, and expectations of, the proposed system. These needs provide a descrip- tion of the way stakeholders desire to conduct business on a day-to-day basis. The second

Preface 3   is to identify high-level user needs and system capabilities to develop the requirements of the proposed system. e ConOps document derives from extensive interviews with the stakeholders. e ConOps document development gives stakeholders the opportunity to provide their input on what they want the proposed system to do. It is the users’ document and should reect all their needs accurately. It is important to note that the ConOps does not specify “how” but rather “what” should be achieved, with a focus on the user needs, the enhancements to current practice enabled by the connected vehicles, the functionality desired to meet the user needs, and impacts during the development phase. Rural transportation agencies seeking to deploy connected vehicle solutions for their rural corridors are the primary intended audience of this ConOps document. e project team solicited input from a subset of rural stakeholders across the country to develop the model ConOps. While an ideal situation would have been regular communica- tion with stakeholders during the development of the ConOps and SyRS, due to resource constraints, the team instead hosted a webinar with project stakeholders aer the devel- opment of the dra model ConOps and SyRS to review and nalize the documents. e webinar was an opportunity to conrm that the nal products addressed the project stake- holders’ feedback. • Precursor Work at Agencies Need to Do Before Developing a ConOps ITS/connected vehicle projects are typically identied based on a need to overcome a problem(s) or a challenge(s) the transportation agency is facing. Oen a new system (or additional capability integrated into an existing system) is required to address the chal- lenges. ese projects are identied and funded through the transportation planning and budgeting process at the state DOT agency or regional planning organization. Once a project need has received support, the systems engineering and Vee process begin.1 Development (Source: FHWA Systems Engineering for Intelligent Transportation Systems, January 2007.) Figure 1. Systems engineering “Vee” diagram. 1 Systems Engineering for Intelligent Transportation Systems: An Introduction for Transportation Professionals.

4 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors of the ConOps is not the rst step in commencing an ITS/connected vehicle project. Initial steps of a project are on the le side of the Vee diagram—or “the le wing” of the Vee (see Figure 2). A typical rst step is identifying what portion of the regional architecture relates to your project. Asking and understanding where the project falls within the over- all regional architecture vision is an important consideration for the project team. e gap between the Regional Architecture(s) and Feasibility Study/Conceptual Exploration indicates that the regional architecture applies to the broader transportation planning process for all other ITS projects, and the step to the right directly aer the gap pertains to the specic ITS/connected vehicle project under discussion. For that reason, this section focuses on the Feasibility Study/Concept Exploration step. e initial steps entail scoping the project, identifying high-level risks, determining benets versus costs, conducting a feasibility analysis, and evaluating possible alternatives—all to ensure the project addresses the stated needs/issues and challenges and is the correct investment for the agency at the time. FHWA Oce of Operations developed the Systems Engineering for Intelligent Trans- portation Systems: An Introduction for Transportation Professionals2 as a handbook to introduce transportation professionals to systems engineering and describe how to apply systems engineering principles to the plan, design, and implementation of ITS projects. e principles in the handbook apply to connected vehicle projects as well. In addition to the systems engineering handbook, the FHWA Oce of Operations developed several other applicable resources to assist transportation professionals plan and implement TSMO strategies. One key document is the Regional Concept for Transporta- tion Operations: e Blueprint for Action—A Primer.3 is document puts the regional TSMO strategies in context for transportation planning, the regional ITS architecture, and how it relates to the ConOps. A study of four metropolitan areas that applied the Regional Concept for Transportation Operations (RCTO) primer was conducted with the successes and lessons learned documented in a practitioner guide.4 Each of the four demonstration sites applied the RCTO primer to their specic situation and tailored the principles to meet the regional needs. Both primer and practitioner’s guide stress the importance of inter- agency relationships and working collaboratively. A third (and more current) resource is a primer on using scenario planning to advance TSMO strategies.5 Scenario planning (Source: FHWA Systems Engineering for Intelligent Transportation Systems, January 2007.) Figure 2. Feasibility study/concept exploration. 2 https://ops.wa.dot.gov/publications/seitsguide/index.htm. 3 https://ops.wa.dot.gov/plan4ops/focus_areas/trans_ops.htm. 4 https://ops.wa.dot.gov/publications/wahop11032/wahop11032.pdf. 5 https://ops.wa.dot.gov/publications/wahop16016/index.htm.

Preface 5   “is an approach to strategic planning that uses alternate narratives of plausible futures (or future states) to play out decisions in an effort to make more informed choices and create plans for the future.”6 The report, Advancing Transportation Systems Management and Operations Through Scenario Planning, explains when and how to use scenario planning. It applies to statewide, urban, rural, corridor, and local levels. Readers of this model ConOps are encouraged to review these materials and to work with the regional TSMO planners and ITS/connected vehicle engineers to advance their projects. 6 Ibid.