About the Connected Vehicle Core System Project:
The Connected Vehicle Core System will support applications for – safety, mobility, and sustainability – and all of the modes – passenger vehicle, transit, and heavy truck. This work is the successor to work originally performed under the Vehicle Infrastructure Integration Proof of Concept (VII POC). The Core System supports a distributed, diverse set of applications. These applications use both wireless and wire line communications to provide:
- Wireless communications with and between mobile elements including vehicles (of all types), pedestrians, cyclists, and other transportation users
- Wireless communications between mobile elements and field infrastructure
- Wireless and wire line communications between mobile elements, field infrastructure, and back office/center
The Connected Vehicle Core Systems Engineering project provided updated baseline documents describing the technology platform for connected vehicles. The Connected Vehicle Core Systems Engineering Team worked closely with interested stakeholders across the Country to identify and defined updated baseline documents for concept of operations, architecture, requirements, standards interfaces, and critical deployment risks. These documents are provided below for those interested in deploying their own Connected Vehicle Core Systems.
- To describe and define the elements of the Connected Vehicle Core System
- To capture and reflect needs of stakeholder groups across the Country
- To update and refine existing documentation from the VII POC
The Connected Vehicle Core Systems Engineering Team reviewed systems engineering documentation (ConOps, architecture, and requirements) developed during the VII POC and lessons learned from the VII POC to begin the Connected Vehicle Core System work. The Team then conducted stakeholder meetings and technical walkthroughs across the Country to capture input from connected vehicle stakeholders. The Team then developed updated baseline documents for the Core System ConOps, architecture, requirements, and critical deployment risks. The architecture and requirements documents will be used as the basis for detailed designs. Additionally, the team identified interfaces that may require new and/or updated standards.
There are five tracks within the Core Systems Engineering Program:
Track 1- Overall Project Management
The objective of this track was to organize all efforts and coordination of the work performed, team structure, roles and responsibilities, and reporting relationships. This included development of the Project Management Plan, Systems Engineering Management Plan and detailed project schedule.
Track 2 –Development of Refinements and Revisions to the Core System Concept
This track produced a refined, revised Core System Concept of Operations document, one that follows the guidance in IEEE Std. 1362 and that reflects:
- Changes in assumptions and constraints identified by the U.S. DOT and other key stakeholders
- Effective and inclusive involvement of representatives of connected vehicles users and operators
- Clearly articulated and well-written customer (user) needs from which sound Core System requirements can be developed
- Concepts and ideas imported from European and Asian projects, where the ideas reflect improvements over the previous U.S. approach to connected vehicles
Track 3 –Analysis and Development of Revised, Refined Requirements for the Core System
This track produced a revised, refined Core System Requirements Specification (SyRS), replacing the current National System Requirements document. The new SyRS follows IEEE Std. 1233 – and includes a Needs to Requirements matrix, tracing requirements back to needs defined in the Concept of Operations.
Track 4 –Development of a Revised, Refined Set of Architectures for the Core System
This track produced a revised Core System Architecture document, one that follows the guidance in IEEE Std. 1471-2000 (or ISO/IEC 42010, which incorporates the IEEE standard as an international standard), and includes architecture considerations from various viewpoints including:
- An enterprise viewpoint describing relationships between organizations
- A communications viewpoint showing communication interfaces
- A connectivity viewpoint that identifies system components
- A functional viewpoint that identifies major subsystems
- An information viewpoint describing data relationships
Additionally, this track produced a standards recommendations report based on the interfaces identified during viewpoint development.
Track 5 –Assessment of Critical Risks to Core System Deployment
This track documented identified risks, their potential impact on deployment, and the recommended mitigation measures for those risks having the most significant impacts in a Risk Assessment Report.
The research resulted in a set of critical products that define the Core System as a comprehensive and interoperable system:
- A revised Concept of Operations for connected vehicles
- An updated Architecture showing all components and interfaces, and identifying how security processes will ensure the integrity of the system and protect the privacy of its users
- A refined System Requirements Specification (SyRS) that will result in inputs to standards updates
- A report identifying critical risks to Core System deployment
- A standards report that identifies Core System interfaces that may require new and/or updated standards
- Core System Concept of Operations (ConOps) [PDF 2.43MB]
- Core System Architecture Document (SAD) [PDF 3.34MB]
- Core System Requirements Specification (SyRS) [PDF 1.68MB]
- Core System Deployment Critical Risk Assessment Report [PDF 432KB]
- Core System Standards Recommendations [PDF 475KB]
- Applying Systems Engineering Principles to the Development of Transportation Communication Standards
- Systems Engineering Research Program
To learn more about this research, contact:
Program Manager, Systems Engineering
Research and Innovative Technology Administration
ITS Joint Program Office