Driving Towards Deployment: Lessons Learned from the Design/Build/Test Phase

The Connected Vehicle Pilot Deployment (CV Pilots) Program seeks to spur innovation among early adopters of connected vehicle application concepts. Pilot deployment awards were given to three sites, New York City, Wyoming, and Tampa, FL. The CV pilot sites are expected to integrate connected vehicle research concepts into practical and effective elements, enhancing current operational capabilities. Each pilot deployment site is being developed in three distinct phases: Phase 1: Concept Development, Phase 2: Design/Build/Test, and Phase 3: Operate and Maintain.

At the time of writing (Fall 2018), the CV Pilot sites are wrapping up Phase 2 (Design/Build/Test) of the Connected Vehicle Pilot Deployment Program – though not without having experienced significant technical and non-technical challenges along the way. Phase 2 required substantial CV engineering and development, resulting from the still maturing state of key applications, a dynamic security credential management environment and challenges in radio-frequency interference.

One should keep in mind that the CV Pilot sites are “piloting” this technology – and are doing so on a scale covering all elements of the surface transportation system and involving numerous stakeholder partnerships and data captured from multiple sources. As a result, some of the challenges documented in this paper were simply the result of the low technological maturity of the systems being deployed and are expected to be mitigated in the future as connected vehicle and supporting technologies mature.

Each CV Pilot, while unique regarding size, features, and functionality to be deployed, is a prime example of a large “system of systems” entailing complex design, procurement, specification, build, integration, and testing principles. It is imperative that agencies considering CV deployment have a deep knowledge and understanding of systems engineering concepts prior to designing and building such systems. Further, data management procedures for the collection, processing and storage of data should be scalable and sustainable while still providing value during system operation. Deployers are also encouraged to compose requirements specifications for the software, firmware and hardware that will be procured outside the development team to prevent additional cost and schedule risks. Though there are many challenges associated with integrating and testing large disparate systems, addressing these needs early in the project lifecycle is guaranteed to reap significant project resource savings over the life of the system.

In the next phase of the Connected Vehicle Pilot Deployment Program, the tested connected vehicle systems will be operated and maintained for a minimum 18-month period. During this phase, the Pilot sites will measure the impacts of their deployments – including improved safety, improved personal mobility, enhanced economic productivity, reduced environmental impacts and transformations to public agencies’ operations.

Please visit the full version of this document for more detailed information at: https://rosap.ntl.bts.gov/view/dot/37681