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.

103   Summary of Impacts is section addresses the impacts to the rural agency’s daily operations and management; internal and external organization interactions; and temporary impacts during development of the connected vehicle capabilities and integration of connected vehicles with the existing systems. S E C T I O N 7 Note to reader: The impacts listed are based on stakeholder feedback and project team experience with connected vehicle deployments. These impacts provide the reader with a starting point. The list of impacts should be tailored for each unique implementation using specific information as applicable. 7.1 Operational Impacts ere are expected to be operational impacts on the user, development, and support or maintenance agency or agencies during operation of the proposed system. e degree of impact connected vehicles will have on a rural agency’s operations will vary from agency to agency. Capability of rural agencies varies immensely, with some being very advanced and others operating with basic ITS, old equipment, and even without a TMC. Changes expected from the integration of connected vehicles into the agency Backoce to support rural operations may include the following: • Changes to the management of new data—increased volume, sensitivity and need for protec- tion, and new data management strategies. • Updates to operator procedures to reect new connected vehicle capabilities and data sources. Assess if new procedures should be added. • Updates to any procedures/processes with others within the TMC, other agency groups, other jurisdictions, or partners, such as event promoters, eet, and freight. Connected vehicle deployment will require more proactivity among agencies and their systems as it relates to incident response times, work zone management, road weather, improving mobility issues, and so forth. • Additional new equipment, such as connected vehicle and ITS, requiring installation, opera- tion, and maintenance. • Requirements for additional services and soware.

104 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 7.2 Organizational Impacts e impact on the rural agency’s organizational structure will be specic and unique to that agency. A smaller-scale deployment is likely to have a lesser impact on the organization; however, with a larger scale deployment, there could be economies of scale particularly if an agency has implemented connected vehicles in other areas (e.g., urban, regional) of the state. Note that an agency opting for a large-scale rural deployment may have already implemented connected vehicles. Organizational impacts may include the following: • Responsibility structure is likely to change or shi. e change may manifest as sta taking on new roles and responsibilities if funding is limited for new deployments. Agencies should consider that integrating connected vehicles could automate processes that are currently performed manually. • Data management practices will be updated based on connected vehicle data created. • e workforce will likely need some transformation. Rural corridors are oen supported by a few sta (e.g., in operations as well as in maintenance) who have limited ITS and connected vehicle expertise in rural agencies and who wear multiple hats. Existing practices will evolve as a result of connected vehicles. As such, there could be a need for management and train- ing given the new data. A phased approach may be the most viable option, with the agency prioritizing where ability or capability is needed most. • Training on connected vehicle systems, including managing big data, cybersecurity, DSRC (or other wireless communication), deployment, roles, and responsibilities, may be added to existing sta (e.g., new capabilities/functions), and changes may be needed to manage- ment and maintenance practices (e.g., asset management). Consideration should be given to whether new sta will be required or whether the shiing of duties of existing sta is sucient to maintain normal operations. Sta training or retraining may be needed for operators and agency eet drivers. • Determine how SaaS and IT as a service will change and how contracts and procurement will change. Determine how support to develop/provide APIs will change. • Understand the new connected vehicle technology (e.g., DSRC, C-V2X), applicable standards, and connected vehicle equipment (e.g., OBUs, RSUs). New equipment (Backoce and eld) installation, monitoring, management, and maintenance need to be considered. • Coordinate the new capabilities/features and roles within the agency (e.g., telecommunications group, eld maintenance, road weather practices, trac management) and external organi- zations (e.g., state police, re, and emergency management) and across states. 7.3 Impacts During Development e impacts during development of the proposed system will be temporary; however, they will span soware development, integration of new functionality with existing systems, and verication/testing. ese impacts may include the following: • Involvement in studies, meetings, and discussions before awarding the contract. It is important to maintain stakeholder engagement to ensure new capabilities match their needs. • User and support involvement in reviews and demonstrations, evaluation of initial operating capabilities and evolving versions of the system, development or modication of databases, and required training. • Follow new, stable connected vehicle and other relevant standards to ensure interoperability. Maintain awareness of existing standards, development organizations, and eorts. It is important to have a connected vehicle data dictionary to communicate and exchange infor- mation. For example, the Work Zone Data Dictionary, while this is not generating connected vehicle data, it enables the consumption of such data.

Summary of Impacts 105   • Interoperability of new equipment and system integration is critical. Monitor equipment obsolescence and advancements in technology. Need an API to enable exchange of data. Consider consumers of the data. Be mindful of the difficulty to integrate information from equipment that has been processed and filtered. • Understand what SCMS capability will be used and the required software and hardware. • Parallel operation of the new and existing systems. • Operational impacts during system testing of the proposed system. • Required training.