Skip to main content

Currently Skimming:


Pages 15-36

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 15...
... 15   S E C T I O N 3 At the highest level, system requirements must dene all the functions that the system must perform at a technical level. For ITS and connected vehicle systems, this usually includes collecting data, analyzing data, securing data and devices, sending information to other entities or system elements, and commanding/controlling devices within the system.
From page 16...
... 16 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors Note to reader: Many of the requirements in this section are taken in part or whole from the New York City (NYC) , Tampa Hillsborough Expressway Authority (THEA)
From page 17...
... System Requirements 17   T raffic C o nd itio ns Vehicle Speed ( mph/ kph) , Vehicle Acceleration, Brake Status Basic Safety Message ( BSM)
From page 18...
... 18 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors F unctio nal Requirements F R-01 The following system requirements define the functions of the traffic management applications.
From page 19...
... System Requirements 19   F R-02. 09 The Decision Support subsystem shall retrieve stored fused work zo ne data for dissemination.
From page 20...
... 20 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors F R-03. 16 The Data Dissemination subsystem shall send road weather event information to ITS Roadway Equipment.
From page 21...
... System Requirements 21   F R-04. 15 The Data Dissemination subsystem shall provide incident information to Emergency Management/ Public Safety System.
From page 22...
... 22 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 3.2 Physical Requirements is section describes the requirements for the physical aspects of rural connected vehicle deployment. Physical requirements refer to the hardware aspects of the devices or elements of the system.
From page 23...
... System Requirements 23   P h y sical Requirements P RC -19 The OBU interface to the CAN bus, J- bus, or OBD- II shall not interfere with the vehicle' s passenger safety systems ( e.g., restraints and ex trication)
From page 24...
... 24 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 3.2.3 Adaptability e connected vehicle devices will meet all the indicated adaptability requirements listed within this section (see Table 8)
From page 25...
... System Requirements 25   S y stem P erfo rmance Requirements S P R-01 All OBUs shall use the same G PS time source and common accuracy configuration as the DOT infrastructure used for the Backoffice and RSUs. S P R-02 The OBUs shall provide the alerts to the driver within 250 milliseconds of being triggered by the application.
From page 26...
... 26 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 3.4 System Security System security is of the utmost importance from both a personally identiable information (PII) perspective as well as a system intrusion (hacking)
From page 27...
... System Requirements 27   (continued on next page) S y stem S ecurity Requirements S S R-15 If the host processor fails the integrity checks, it shall not allow any privileged application to operate.
From page 28...
... 28 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors S y stem S ecurity Requirements S S R-38 A Message Authentication Code shall not be used to protect the software unless the Message Authentication Code key is unique to the H SM. S S R-39 Cryptographic information shall be managed based on F IPS 140- 2.
From page 29...
... System Requirements 29   (continued on next page) S y stem S ecurity Requirements S S R-56 OBU devices shall support the ability to reset default usernames and passwords by users with Administrative functions ( ENG , MRG , and Admin)
From page 30...
... 30 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors S y stem S ecurity Requirements S S R-8 3. 02 The RSU W SA for certificate download shall advertise a channel other than 178 or 172 if DSRC is being used.
From page 31...
... System Requirements 31   Information Management Requirements IMR-01 The system shall protect participan ' personal information including name, address, vehicle make/model, driver' license number at a minimum. IMR-02 Personal information collected when registering participants shall be electronically stored separately from connected vehicle data (i.e., BSMs, alerts)
From page 32...
... 32 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors warnings from devices they are presented with. However, participants may act because of the alert they received (e.g., applying the brake, turning around)
From page 33...
... System Requirements 33   System Maintainability Requirements SMR-01 The Backoffice staff shall be able to monitor systemwide malfunctions. SMR-01.1 The Backoffice shall monitor the system for availability of ping services running.
From page 34...
... 34 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors S y stem M aintainab ility Requirements S M R-22 The OBU shall record the last SPaT message it hears from each RSU along with the contents of its own location at the time and the RF level. S M R-23 The OBU shall record the last TIM message it hears from each RSU along with the contents of its own location at the time and the RF level.
From page 35...
... System Requirements 35   S y stem Reliab ility Requirements S p ecific D ev ice/ S y stem/ S ub sy stem S RR-01 The OBU shall revert to a failsafe mode when unable to perform its normal operations. S RR-02 Connected Vehicle Roadside Equipment shall revert to a failsafe mode when unable to perform its normal operations.
From page 36...
... 36 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors 3.8 System Lifecycle Sustainment System lifecycle sustainment describes the quality activities, such as review, measurement collection, and analysis, to realize a quality system. During the initial stages of the systems engineering process, the produced documents, such as ConOps, SyRS, Safety Management Plan, Security Management Operating Concept, and Performance Measurement Management Plan, to name a few, are reviewed by stakeholders, partners, and other interested parties.

Key Terms



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.