1
2	Agenda Introductions & Logistics IntelliDrive System Engineering System Engineering Vehicle Infrastructure Integration (VII) IntelliDrive Program User Needs Overview / Examples User Needs Break-Out #1 / Discussion User Needs Break-Out #2 / Discussion Wrap Up
3	Introductions IntelliDrive SE Team Participating Organizations: State/Local Transportation Agency Public Safety/ Emergency Services Automotive/Vehicle equipment developer Traveler Information Service Provider Academic / Research organization Networking / Telecommunications Provider Transportation Device Manufacturer System Integrators Transit communities Rail communities
4	Logistics Main Room Breakout Rooms Restrooms Safety Issues
5	INTELLIDRIVE SYSTEM ENGINEERING (SE)
6	IntelliDrive SE Program Revisit and update the IntelliDrive concept of operations, requirements, and architecture Existing documentation and lessons learned will be used as a resource Focus on the Core, Enabling System necessary to form the basis for the safety, mobility, environmental applications The first step in this process is to elicit User Needs from you.
7	IntelliDrive SE Program (cont.) Provide the technical foundation for future activities next generation of field tests initial and ongoing deployments continued research as the core technologies and program evolve
8	IntelliDrive SE Process
9	SYSTEMS ENGINEERING
10	What is a System?
11	What is Systems Engineering? An inter-disciplinary approach and means to enable the realization of successful systems.¹
12	Systems Engineering (cont.) Focuses on: Defining customer needs and required functionality early in the development cycle Documenting requirements Then proceeding with design, implementation, and system validation while considering the complete problem
13	Systems Engineering Principles Start with Your Eye on the Finish Line Stakeholder Involvement is Key Define the Problem before Implementing the Solution Delay Technology Choices
14	Benefits of Using SE Reduced risk of schedule and cost overruns Increased likelihood that implementation will meet users’ needs Improved stakeholder participation Verified functionality and fewer defects Better documentation More adaptable and resilient systems Extensibility, scalability, robustness
15	IntelliDrive System Engineering
16	VEHICLE INFRASTRUCTURE INTEGRATION (VII)
17	VII Key Constraints Communications – air gap bridged by 5.9 GHz DSRC and only 5.9 GHz DSRC Vehicles equipped as new production only VII Network not to be used to replace existing infrastructure (e.g. to provide communications between centers and signal controllers) Probe data required Privacy principles
18	VII-era Context
19	VII-era Resulting Architecture
20	INTELLIDRIVE^SMPROGRAM
21	What is IntelliDrive? Suite of technologies and applications that use wireless communications to provide connectivity: Between vehicles (of all types) Between vehicles and roadway infrastructure Between vehicles and wireless communication devices Between wireless communication devices and roadway infrastructure
22	The Problem!!!
23	Program Evolution
24	When is IntelliDrive Taking Place
25	It’s All About Connectivity
26	ITS JPO IntelliDrive Program Structure
27	USDOT Activities Broad program of research to address all aspects of IntelliDrive Safety – V2V, V2I Mobility – Data Capture Management, Dynamic Mobility Applications Environment – AERIS along with road weather management (Clarus) As well as looking at higher level issues Regulatory needs Policy framework Standards evolution
28	Scope of IntelliDrive IntelliDrive is composed of 3 layers: (1) Users, Mobile, Non-Mobile, Public and Private (2) Applications, which bring about safer, smarter, and greener transportation, and (3) a Core System, which enables applications by providing cooperative data exchange capabilities. Our Focus today is on the Core System
29	Potential IntelliDrive Users
30	Safety & Mobility & Environment Safety and mobility capabilities, while a continual focus of the program over the last several years, are not intended to be its limit. Capabilities that provide environmental benefit are a new focus for IntelliDrive support. While strictly commercial capabilities are no longer a point of focus for the IntelliDrive program, commercial capabilities that enhance safety, provide mobility and/or are environmentally-focused may also be supported.
31	Potential Capabilities of IntelliDrive Vehicle to Vehicle (from the basics to more advanced capabilities) Location/speed: “Here-I-Am” Emergency electronic brake lights: “Look out, I’m braking” Accident notification: “I just had an accident” Cooperative platooning
32	Potential Capabilities of IntelliDrive Vehicle to Infrastructure (covers safety and mobility) Intersection based collision avoidance Signal optimization, prioritization, pre-emption Curve speed/rollover warning Credentialing Payment
33	Potential Capabilities of IntelliDrive Vehicles, Infrastructure and Wireless Devices (mobile to fixed – either broadcast or transaction specific communications) Where is my car? Pedestrian alert to vehicle eCommerce
34	How does DSRC fit in? Dedicated Short Range Communications (DSRC) Remains one of the important technologies used within the IntelliDrive System 75MHz of spectrum in 5.9 GHz range allocated by FCC to: “[provide] vehicle-to-vehicle and vehicle-to-infrastructure communications, helping to protect the safety of the traveling public. It can save lives by warning drivers of an impending dangerous condition or event in time to take corrective or evasive actions.” “The band is also eligible for use by non-public safety entities for commercial or private DSRC operations.”
35	Changing Assumptions & Constraints Wireless Technologies such as Wi-Fi and Cellular may supplement DSRC at 5.9 GHz Aftermarket, Retrofit, Carry-In Devices considered Deployments could be more organic Various Vehicle Types will be supported Alternative Approaches to Privacy and Anonymity may be considered Different Services may be provided
36	VII vs. IntelliDrive
37	IntelliDrive Context
38	IntelliDrive SE Process: Gather User Needs Workshops Conducted Vancouver, BC – August 10/11 Detroit, MI – August 25/26 San Jose, CA – Sep 1/2 Washington, DC - Today
39	Gathering User Needs: What have we heard so far? Give me the data – current traffic, all roads, all the time Standardized Support multiple modes – include Cyclists, Pedestrians, other vulnerable users Set driver’s expectations: inform them when IntelliDrive/safety services are available Support targeted broadcasts to sets of vehicles – by location, type, individual Support back-office brokering of data sets via standardized interfaces, services Support roaming for users devices Provide authentication, ensuring users that messages are from legitimate sources
40	Gathering User Needs: So What’s New? Sample Need: Need location of pedestrians Traffic Management Center, for signal operations Transit Management Center, for rider demand Transit Vehicles, for rider demand Roadside, for signal operations and safety Vehicles, for safety Sample Constraints: All interfaces should be defined as open standards IntelliDrive deployments should be maintainable by existing ITS maintenance organizations
41	Gathering User Needs: Perspectives Well represented in previous workshops: Vehicle device makers Traffic management and operations Traveler Information Service Providers Perspectives we hope to gain this week: Public safety, emergency management Planning Fleet operations – public, private Insurance Rail Carry in devices
42	INTELLIDRIVE USER NEEDS OVERVIEW/EXAMPLES
43	What is a User Need? A “User Need” is defined as a capability that is identified to accomplish a specific goal or solve a problem that is to be supported by the IntelliDrive System. “A user requirement for a system that a user believes would solve a problem experienced by the user.” IEEE Std 1362-1998, Section 3.26 - User Need Describes “what” is needed and not “how” it is to be implemented
44	Characteristics of User Needs Scoped to the appropriate level Too general -- needs to be further defined Too specific -- may imply design Not Application specific May include notional latency, security, size or bandwidth (if applicable) needs Not the solution of any specific interface or protocol
45	Vending Machine Example
46	Vending Machine User Need 1 Who: Thurston What: I need the soda pop vending machine to provide a way to quench my thirst. Why: To increase my chance of survival.
47	Vending Machine User Need 2 Who: Allen Wright What: I need the soda pop vending machine to accept some means of payment for the product. Why: To finance more product, my salary, and the gas for my delivery truck.
48	Vending Machine User Need 3 Who: Tony What: I need for the soda pop vending machine to increase the amount of customers to my gas station convenience mart. Why: So that I can sell more snacks and other high margin items in my convenience mart.
49	User Needs – The User’s Role Identify User Needs (capabilities, problems to be solved, processes to be improved) Attribute each need to an individual/group/organization What is your Rationale? Tell us your perspective
50	A User Need Example Who? Traffic Manager What is the problem? I don’t have a complete picture of traffic conditions on my roadway network. Why is this a problem? I need to manage the roadways to reduce congestion while improving safety and mobility. What do you need to solve this problem? I need current and historical information that describes traffic conditions on the entire scope of the roadways I manage. Why should IntelliDrive solve this problem? If I could get vehicle locations with IntelliDrive I could perform better adaptive signal control. Getting this information with fixed sensors is cost prohibitive.
51	Another User Need Example Who? Emergency Operations Center Manager What is the problem? I currently only broadcast advisory information. I want to selectively send advisory information to travelers in specific geographical areas. Why is this a problem? The advisories can be received by travelers not impacted by the advisory. What do you need to solve the problem? I want to increase the relevancy of the advisory information to the travelers for more effective communication. Why should IntelliDrive solve this problem? I want IntelliDrive to provide me a means to communicate emergency advisory information directly to travelers in certain geographic areas. Providing this capability with existing dissemination methods is cost prohibitive.
52	Another User Need Example Who? Vehicle OEM What is the problem? I would like to provide a way of notifying the vehicle’s systems of upcoming bad road weather conditions. Why is this a problem? Road weather surface conditions can change rapidly and pose a safety risk to vehicles. What do you need to solve the problem? I need better road surface condition data. Why should IntelliDrive solve this problem? IntelliDrive can provide actual vehicle’s reactions to weather conditions (ABS, traction control etc.) that I cannot get another way. IntelliDrive can also provide information for areas where I cannot install fixed sensors.
53	Another User Need Example Who? Transit Manager What is the problem? I can’t ensure that my transit vehicles stay on schedule. Why is this a problem? Late transit vehicles has resulted in a drop in ridership. What do you need to solve the problem? I have a need for the signals to be modified in order to accommodate a bus that is behind schedule. Why should IntelliDrive solve this problem? IntelliDrive could provide a way for my transit fleet to communicate with the signals and reduce my reliance on proprietary signal priority equipment.
54	Next Steps Who are you? What is the problem? Why is this a problem? What do you need to solve the problem? Why should IntelliDrive solve this problem?
55	For More Information…
56	INTELLIDRIVE USER NEEDS BREAKOUT #1 / DISCUSSION
57	Break-Out Groups Identify Breakout Session You are encouraged to attend that topic that you are familiar with and that you are interested in Once you get there start by introducing yourselves – who you are and what your background with IntelliDrive is. Each group will discuss topics particular to that domain along with general findings across all domains
58	Break-Out Group Room Assignments – 12:30pm
59	Breakout Group Introduction Introduce ourselves Name Company/Agency/ Organization Involvement, Background with IntelliDrive (and its predecessors) Expectations Objectives Capture User Needs– problems/solutions/rationale
60	Breakout Group – Key Questions Who are you? What is the problem? Why is this a problem? What do you need to solve the problem? Why should IntelliDrive solve this problem?
61	Day 2 Agenda 9:00 – 9:05 Welcome Back 9:05 – 9:45 Breakout #1 Reports 9:45 – 10:00 Intro of Breakout #2 Topics 10:00 – 10:30 Breakout Sessions #2 10:30 – 10:45 Break 10:45 – 12:00 Breakout Sessions (cont’d) 12:00 – 1:15 Lunch 1:15 – 2:45 Breakout Sessions (cont’d) 2:45 – 3:00 Break 3:00 – 4:00 Breakout #2 Discussion, Wrap-Up
62	Breakout #1 – Reports What did we learn? Someone from each group summarize key points Problems Needs Rationale
63	INTELLIDRIVE USER NEEDS INTRO OF BREAKOUT #2 TOPICS
64	Information Exchanges
65	“What If” … Scenarios selected from yesterday’s input for discussion today Characterize the information exchanges necessary to solve these problems Think of today, and think of the future……evolutionary and revolutionary
66	Scenario Examination Identify the entities (Center, Roadside, Traveler, Vehicle) Consider the following questions from the perspective of each entity: What data or information is necessary to solve this problem? What other data from outside of the Core System would be helpful? Does the Core System need to ensure a high probability of information delivery? Does Core System need to support the delivery of large data sets? Does Core System need to store data or information? Does Core System need to provide any processing capability?
67	INTELLIDRIVE USER NEEDS BREAKOUT #2 / DISCUSSION
68	Breakout #2: Summarize What We Heard Possibilities Additional Needs Considerations moving forward
69	WRAP UP
70	Next Steps The inputs from this workshop will be collected and organized Findings Report provided to USDOT DOT will disseminate to the participants Next step for the program will be to update the IntelliDrive System Concept of Operations Stay tuned!
71	PLEASE FILL OUT YOUR EVALUATION FORM
72	Thank you for your participation!