Connected Vehicle Reference Implementation Architecture Update - - PowerPoint PPT Presentation
Intelligent Transportation Systems (ITS) Joint Program Office (JPO) Connected Vehicle Reference Implementation Architecture Update Stakeholders Webinar November & December 2013 1 Response, Emergency Staging and Communications, Uniform
1
2
2
3
4
□ Develop and test prototypes for INC-ZONE and RESP-STG □ Define an architecture for EVAC and identify institutional issues □ Awarded to Battelle/UMD-CATT team; kickoff 8/28/2013
□ Estimate impacts of integrated multi-application deployments using
□ Awarded to Booz Allen; kickoff in mid-September
5
□ Completed
□ Under development now; final by January 2014 □ Your input today on the Phase I System Architecture will be welcome and
□ Final due in January 2014
□ Final due in February 2014 □ Testing and results due in March 2014
□ Go/No-Go decision based on test results. □ If approved, expect demos in late FY14 / early FY15
6
7
8
Attended one of the previous webinars Visited the CVRIA website This is my first experience
9
□ Familiarize attendees with the Connected Vehicle Reference
□ Provide an update on the development of the CVRIA □ Review portions of the CVRIA Website □ Discuss standardization planning and policy analysis
□ Linda Dodge □ David Binkley, Ron Ice, Tom Lusco □ Chris Karaffa, Jim Marousek □ Dawn LaFrance-Linden, Scott Smith
10
(All Times Eastern)
11
12
13
Landscape: Safety, Mobility, Environmental Applications with common supporting infrastructure
□ Collecting and aggregating connected vehicle needs/requirements □ Developing a multi-faceted system architecture □ Identifying and prioritizing candidate interfaces for standardization □ Conducting policy analysis around the architecture
□ regional ITS architectures/plans □ future transportation projects
□ Are we capturing the connected vehicle applications adequately? □ Are we including all of the necessary interfaces? □ We’ll show you how to provide feedback via the website?
14
15
□ Different web browsers support SVGs in different ways (some not at all).
□ As an alternative to SVGs all graphics are also available Portable Network
16
Applications Tab Architecture Viewpoints Tab
Physical Tab (objects, flows, comm) Standards Tab
Comment on Page Enterprise Tab (4 phases)
JPO / Stds / Activities / CVRIA Start / Home www.iteris.com/c vria/ Functional & Requirements Tabs Resources / Glossary
17
At conclusion of webtour Skip to Use of CVRIA Slides
18
19 19
SE Michigan 2014 Future Connected Vehicle Projects
use the CVRIA Visio Drawings
describe future projects using same ‘language’ and format
□ Layer 0 – high-level objects and
interconnections
□ Layer 1 – project specific physical,
application objects
□ Layer 2 – application level (just like the
application drawings on CVRIA website) Connected Vehicle projects can be defined as collections of applications from CVRIA and use the same ‘language’, interfaces, standards Now that you’ve completed the ‘tour’ of the website, let’s talk about some ways that CVRIA can be used...
between vendors, operators and solution providers by developing V2I data exchanges
□ Field and Back-Office functions
CVRIA:
□ Physical (What)
▪ Multi-layer diagrams
□ Enterprise (Who) □ Communications
20
□ Gathering feedback from webinars and website □ Incorporate inputs □ Update tools
□ Maintain CVRIA
□ Monitor usage in Test Beds, Demos, Early Deployments
□ Merge / Incorporate CVRIA into Nat’l ITS Arch
21
22
23
Standards Plan The standards prioritization will be applied to those gaps to develop the standards plan. The CVRIA will identify and define interfaces within the connected vehicle environment (CVE).
24
Prioritization Criteria USDOT Policy Leadership Direction
25
□ The CVRIA viewpoints/database are being analyzed now to identify and
□ Feedback on applications or other aspects of the architecture will help us
□ Presentation of findings and results of interface and standards prioritization □ First opportunity to share results of the interface and standards analyses □ Tentatively planned for the San Francisco Bay Area, February 19-20, 2014
26
27
28
□
□
□
□
□
□
□
29
□
□
□
□
□
□
30
31
□ Primarily from physical
□ Some enterprise
32
issue
apply to multiple applications
33 33
Application Specific Issues
□ Interoperability with institutions (e.g., hospitals)
whose primary mission is not transportation
□ Are some of the data items (medical records,
care facility status) available?
□ Who designs and tests the routing and staging
algorithms?
□ Handling of medical records □ Carriers may consider their vehicle cargoes to
be proprietary
□ Ensuring that smaller service providers (e.g., a
volunteer fire department or private ambulance) has access to the benefits Most Relevant Universal Issues
□ When is DSRC really needed? □ Speed and reliability of safety-critical
communications
□ Enforcement □ Liability
□ Avoid driver distraction
□ Failure to follow advice from the system □ System gives bad advice
equipment (RSE) and onboard equipment (OBE)
sources (Maps and RSE) and vehicle OBE; security of links to RSE
34
35 35
Application Specific Issues
□ What requirements apply to personal information
devices (PIDs)
□ Size, weight and power constraints on PIDs □ Speed and reliability of safety-critical
communications
□ Vehicle movement data from this application could
conceivably be used to improve future response to incidents, in terms of traffic management. What are the rules for using the data?
□ Education on worker’s use of these systems and
their limitations
□ Ensuring that smaller service providers (e.g., a
volunteer fire department or private ambulance) has access to the benefits Most Relevant Universal Issues
□ When is DSRC really needed?
□ Enforcement □ Liability
□ Avoid driver and worker distraction
□ Failure to follow advice from the
system
□ System gives bad advice
information devices (PID) roadside equipment (RSE) and onboard equipment (OBE)
sources (Maps and RSE) and vehicle OBE; security of links to RSE
36
37
38
□ CVRIAcomments@iteris.com
□ Steve.Sill@dot.gov – 202-366-1603 □ Walt.Fehr@dot.gov – 202-366-0278