The National Academies Press

Currently Skimming:

Pages 22-31

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 22... ... 22 Chapter 4 builds on the ndings from the literature review and stakeholder engagement to conceptualize the connected vehicle environment, develop user needs, identify relevant applications of connected vehicle technologies, and describe use cases for these applications. e information described serves as the foundation for the model ConOps and SyRS documents presented in Chapter 5. Read the entire page →
From page 23... ... Rural Connected Vehicle Needs, Systems, and Applications Findings 23 4.2 User Needs Dra high-level needs or need statements that capture the desired capability (i.e., not fully developed, well-written needs) for the actors were developed to document specic user needs that were further dened and developed in the model ConOps. Read the entire page →
From page 24... ... 24 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors – Fleet and Freight Management System – Event Promoters – ird-Party Providers • Field-Specic User Needs – ITS Roadway Equipment • Agency-Personnel-Specic User Needs – Rural Agency Personnel (Note: some of the Rural Agency Personnel needs are embedded in the Center needs.) • Support Environment-Specic User Needs – Security Needs – Positioning and Timing System • Vehicle-Specic Needs – Basic Vehicle – Commercial Vehicle – Public Safety Vehicle – Maintenance and Construction Vehicle – Vulnerable Road User • System-Level Needs e user needs developed here are compliant with systems engineering criteria for a wellwritten need, which are dened as follows: • Uniquely Identiable: Each need must be uniquely identied (i.e., each need shall be assigned a unique number and title) Read the entire page →
From page 25... ... Rural Connected Vehicle Needs, Systems, and Applications Findings 25 • Additional information about trac management applications can be found on the Connected Vehicle Pilots website: https://www.its.dot.gov/pilots/pilots_mobility.htm. • For additional information about implementation of work zone applications and U.S. Read the entire page →
From page 26... ... Table 6. Example connected vehicle applications by topic area. Read the entire page →
From page 27... ... Rural Connected Vehicle Needs, Systems, and Applications Findings 27 Use cases (also referred to as operational scenarios) are used in ConOps documents to provide a step-by-step description of how the proposed system should operate and interact with its users or actors. Read the entire page →
From page 28... ... 28 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 4. Freight-Specific Situational Awareness. Read the entire page →
From page 29... ... Rural Connected Vehicle Needs, Systems, and Applications Findings 29 protection for nonmotorized users. They integrate traffic, pedestrian, and cyclist information from roadside or intersection detectors, and new forms of data from wirelessly connected nonmotorized traveler-carried mobile devices, to assist nonmotorized travelers on when to cross and how to remain aligned with the crosswalk or pathway based on real-time Signal Phase and Timing (SPaT) Read the entire page →
From page 30... ... 30 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 2. The Connected Vehicle Roadside Equipment receives the DN message from the OBUequipped vehicle. Read the entire page →
From page 31... ... Rural Connected Vehicle Needs, Systems, and Applications Findings 31 R elated U ser N eeds C0 1, C0 3, C0 6 , C0 8 , C14, C18 , C19 , C20 , C21, C25, C26 F0 1, F0 2 AP0 1, AP0 2 SE0 1, SE0 2, SE0 3, SE0 4, SE0 5, SE0 6 V0 1, V0 2, V0 4 Note: User Need Identifiers (e.g., C0 1, AP0 1) relating to the use case are listed in the model ConOps, Section 4.2. Read the entire page →

From page 22...

... 22 Chapter 4 builds on the ndings from the literature review and stakeholder engagement to conceptualize the connected vehicle environment, develop user needs, identify relevant applications of connected vehicle technologies, and describe use cases for these applications. e information described serves as the foundation for the model ConOps and SyRS documents presented in Chapter 5.

Read the entire page →

From page 23...

... Rural Connected Vehicle Needs, Systems, and Applications Findings 23 4.2 User Needs Dra high-level needs or need statements that capture the desired capability (i.e., not fully developed, well-written needs) for the actors were developed to document specic user needs that were further dened and developed in the model ConOps.

Read the entire page →

From page 24...

... 24 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors – Fleet and Freight Management System – Event Promoters – ird-Party Providers • Field-Specic User Needs – ITS Roadway Equipment • Agency-Personnel-Specic User Needs – Rural Agency Personnel (Note: some of the Rural Agency Personnel needs are embedded in the Center needs.) • Support Environment-Specic User Needs – Security Needs – Positioning and Timing System • Vehicle-Specic Needs – Basic Vehicle – Commercial Vehicle – Public Safety Vehicle – Maintenance and Construction Vehicle – Vulnerable Road User • System-Level Needs e user needs developed here are compliant with systems engineering criteria for a wellwritten need, which are dened as follows: • Uniquely Identiable: Each need must be uniquely identied (i.e., each need shall be assigned a unique number and title)

Read the entire page →

From page 25...

... Rural Connected Vehicle Needs, Systems, and Applications Findings 25 • Additional information about trac management applications can be found on the Connected Vehicle Pilots website: https://www.its.dot.gov/pilots/pilots_mobility.htm. • For additional information about implementation of work zone applications and U.S.

Read the entire page →

From page 26...

... Table 6. Example connected vehicle applications by topic area.

Read the entire page →

From page 27...

... Rural Connected Vehicle Needs, Systems, and Applications Findings 27 Use cases (also referred to as operational scenarios) are used in ConOps documents to provide a step-by-step description of how the proposed system should operate and interact with its users or actors.

Read the entire page →

From page 28...

... 28 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 4. Freight-Specific Situational Awareness.

Read the entire page →

From page 29...

... Rural Connected Vehicle Needs, Systems, and Applications Findings 29 protection for nonmotorized users. They integrate traffic, pedestrian, and cyclist information from roadside or intersection detectors, and new forms of data from wirelessly connected nonmotorized traveler-carried mobile devices, to assist nonmotorized travelers on when to cross and how to remain aligned with the crosswalk or pathway based on real-time Signal Phase and Timing (SPaT)

Read the entire page →

From page 30...

... 30 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 2. The Connected Vehicle Roadside Equipment receives the DN message from the OBUequipped vehicle.

Read the entire page →

From page 31...

... Rural Connected Vehicle Needs, Systems, and Applications Findings 31 R elated U ser N eeds C0 1, C0 3, C0 6 , C0 8 , C14, C18 , C19 , C20 , C21, C25, C26 F0 1, F0 2 AP0 1, AP0 2 SE0 1, SE0 2, SE0 3, SE0 4, SE0 5, SE0 6 V0 1, V0 2, V0 4 Note: User Need Identifiers (e.g., C0 1, AP0 1) relating to the use case are listed in the model ConOps, Section 4.2.

Read the entire page →

Key Terms

← Previous Chapter Skim

Next Chapter Skim →

This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.