Connected Vehicle Reference Implementation Architecture (CVRIA) David Binkley, Iteris

Topics recent activities regarding the development and uses of the Connected Vehicle Reference Implementation Architecture (CVRIA) user tools based on CVRIA that are being developed to support Connected Vehicle project planning and development

Program Background Project Goals and Approach Recent Activities CVRIA Overview Program Background Project Goals and Approach Recent Activities

CVRIA Landscape Looking ahead Applications Safety Crash-imminent V2V V2V V2I Mobility Data Capture & Management Dynamic Mobility Applications Environment AERIS Road Weather Applications Looking ahead 10-20 years from now when 80% of vehicles are equipped in some way – maintaining a robust CV environment Shorter term – supporting the researchers and early deployers Collecting and aggregating connected vehicle needs Developing a multi-faceted architecture Identifying and prioritizing candidate interfaces for standardization Supporting policy analysis

Architecture & Standardization Plan The CVRIA provides a reference for applications and systems as well as identifying candidate interfaces within the architecture. But… how do we implement those interfaces? Standardization is a critical component of implementation. The standardization plan will provide a strategy for ensuring that there are sufficient standards to support implementation and ensure interoperability. Candidate Interfaces Adopt Adapt or Create

CVRIA Viewpoints CVRIA uses multiple viewpoints to capture stakeholders’ concerns Enterprises to carry out applications Functions to satisfy requirements Physical objects to implement that functionality Communications protocols necessary ~100 connected vehicle applications included

CVRIA Website: www.iteris.com/cvria

CVRIA Website – Reduced Speed Zone Warning (RSZW) The diagrams help visualize the physical view of any given cv application – note the high level physical objects and information flows (interfaces). On the website each of these is hyperlinked to the definitions and other resources. In addition to the physical view for each application there are other tabs for enterprise, functional, and the list of requirements. The idea is that these help stakeholders and reviewers of the architecture “see” what all is included – did their research get included and if so, is it captured adequately. Remember it is these lines that are then becoming the inputs into the standardization planning process. There is another use for these applications and that is to use these diagrams as a starting point for new projects, ideas.

CVRIA Status CVRIA v1 complete in January 2013: http://www.iteris.com/cvria/index.htm Public Workshops San Jose, CA – April 30 2013 Focused on draft architecture views San Francisco – February 2014 Focused on inputs to standardization plan Webinar Series – fall 2013 T3 Archive: http://www.pcb.its.dot.gov/t3_archives.aspx 7 webinars, each provided general overview and then drilled into specifics of 2 or 3 CV applications Contact Us page or “Comment on Page” links to ask questions or provide comments to the team Use the website to Reviewing the architecture viewpoints Reviewing the standards development plan Providing inputs for policy development and review policy options Come to the WS where

What’s Next CVRIA is providing the input into the standardization process Architecture definitions, applications helping stakeholders verify that framework adequately captures the connected vehicle activities Beyond that, it is becoming a resource in the near-term for project implementers – research, test bed projects “Mini-Tool” developed to help define project architecture Using CVRIA applications drawings as a starting point Application of CVRIA to guide project development and application implementation

Tools for Applying CVRIA System Architectures are meant to be used To understand new concepts, scope/define projects, present alternatives, capture interfaces and functions Aka – supporting a systems engineering approach New software tool available June 2014 Systems Engineering Tool for Intelligent Transportation (SET-IT) Takes all the content in CVRIA and makes it available for projects to start with a common base and customize/build upon it June release includes basic physical view capabilities Includes ability to select CVRIA applications and customize them for a local project Supports systems engineering process activities with direct process outputs Based on Visio and Access

SET-IT

SET-IT Using CVRIA drawing stencil – allowing for easy comparisons, reuse across projects Support customization for local variations

Notional SET-IT Based on Visio drawing tools Quickly import CVRIA drawings CVRIA physical view includes more detail than current ITS drawings (security and other flow characteristics) Add local customizations Connections to database definitions Notional

Software Toolset will be evolving SET-IT initial release via CVRIA website June 2014 Subsequent releases will build upon the physical drawings; look for: Formal physical diagram hierarchy Stakeholder tracking and Basic Enterprise drawings Communications dialogs CVRIA Enterprise imports Communications State transitions Message definitions Enterprise correspondence rules – relationships between views Web page generation Formal document template outputs (ConOps, ICDs) SET-IT – not an architecture tool but a tool for connected vehicle systems engineering

Where is CVRIA Going Long-term: CVRIA and National ITS Architecture will be integrated in approximately 2 years Will include updated tools that will include support for regional ITS architecture Look to websites to download tools and provide feedback: www.standards.its.dot.gov/cvria.asp www.iteris.com/cvria Integrating CVRIA and the National ITS Architecture provides 1 architecture to guide planning and project development for all stakeholders