Concept Development and Needs Identification for Intelligent Network Flow Optimization (INFLO)

hesitantdoubtfulAI and Robotics

Oct 29, 2013 (3 years and 7 months ago)

118 views

1

Concept Development and Needs
Identification for Intelligent
Network Flow Optimization (INFLO)

Functional and Performance Requirements
and Communication and Data Needs

Stakeholder Walkthrough Webinar

August 9, 2012

Agenda

1:00


1:10 PM

1. Welcome and Introductions, 2. Background and Walkthrough Objectives

1:10


1:15
P
M

3. High
-
Level Discussion of INFLO Systems and Subsystems

1:15


1:45 PM

4. SPD
-
HARM Functional and Performance Requirements

1:45


2:15 PM

5. Q
-
WARN Functional
and Performance Requirements

2:15


2:45 PM

6. CACC Functional
and Performance
Requirements

2:45


3:00 PM

BREAK

3:00


3:20 PM

7. SPD
-
HARM Data and Communication Needs

3:20


3:40 PM

8
.
Q
-
WARN Data and Communication
Needs

3:40


4:00
PM

9. CACC Data
and Communication
Needs

4:00 PM


10. Wrap
-
up and Next Steps

2

2. INFLO Background and
Walkthrough Objectives

3

The INFLO Bundle

Intelligent
Network Flow Optimization (INFLO
)
bundle of applications:


Dynamic Speed Harmonization (SPD
-
HARM)


Queue Warning (Q
-
WARN)


Cooperative Adaptive Cruise Control (CACC)

4

Goals of INFLO

Utilize frequently collected and rapidly
disseminated multi
-
source data drawn from
connected travelers, vehicles, and
infrastructure
to:


Improve
roadway throughput


Reduce delay


Improve safety


Reduce emissions and fuel consumption

5

INFLO Deployment Vision

6

Walkthrough Objectives


Ensure accuracy and completeness of INFLO
requirements
and
data and
communication
needs


Provide functional, technical, management,
and implementation comments as
necessary

7

3
. INFLO Systems
and Subsystems


8

Key INFLO Systems

9


Connected
Vehicle
-
based
INFLO Application


the core in
-
vehicle application that processes real
-
time data
and makes speed
harmonization/queue warning/gap and speed recommendations for
the
individual vehicle


Connected
Vehicle Driver Interface System


in
-
vehicle
system that displays
output
and receives user input


Connected
Vehicle Communication System


the in
-
vehicle system that communicates wirelessly with
infrastructure and other Connected Vehicles
(
may
utilize DSRC
, cellular communication, or
WiFi
)


On
-
board
Diagnostic (OBD) reader/Vehicle Bus System


the in
-
vehicle systems that read real
-
time vehicle
data (speed, heading, temperature, etc.) to make available to the
INFLO Application


Traffic Management Entity
(TME)


the generalized system (which could refer to a TMC)
responsible
for
making segment
-
specific and network
-
wide target speed
recommendations, queue warning determinations
and predictions, and gap policies
for
enabled Connected
Vehicles and communicating these
recommendations via I2V communications


TME
-
based INFLO Application


the core infrastructure
-
based application that processes real
-
time and
historical transportation network data to determine
the abovementioned recommendations


V2I/I2V
Roadside Equipment


the infrastructure
-
based communication systems that receive and send
information between
INFLO
-
enabled
Connected Vehicles and the
TME


TME
Performance Monitoring Subsystem


the subsystem of the TME
-
based
INFLO
Application that monitors
the effectiveness of
INFLO recommendations
and policies on the transportation network using safety and
mobility measures


Data
Environments


the systems that receive, store, and summarize real
-
time data gathered from Connected
Vehicles and Infrastructure to be made available to various Dynamic Mobility Applications



Generic SPD
-
HARM Systems Information
Flow Diagram

10

Traffic Mgmt. Entity

Performance
Meas.

V2I

Roadway

V2X Comm.

Traffic
Detection

Weather
Sensors

SPD
-
HARM
App

Connected Vehicle

OBD Reader/
Vehicle Bus

Driver
Interface

Onboard SPD
-
HARM App

Data
Communication

DMS

Data Environment

External Data
Sources

(Weather, EMS,
etc.)

Remote Connected
Vehicle

V2V

4. SPD
-
HARM Requirements

11

Structure of the INFLO Requirements

12


INFLO
requirements are organized by
user need addressed
, as identified in
the INFLO
ConOps


The near
-
, mid
-
, and long
-
term achievability of each requirement is
indicated in the
Application Evolution State

columns


Near
-
term: 1
-
10
year
horizon


Mid
-
term: 10
-
20
year
horizon


Long
-
term: 20
+ year
horizon


Key
systems and subsystems
involved in the given requirement are
indicated in the next
column


Requirement type
indicated
in the last
column (Functional, Performance,
System
-
to
-
system interface, Human
-
machine interface, Security, Privacy)

SPD
-
HARM User
Need 1 & 8: Know the
recommended speed to travel & Communicate
relevant information to vehicle operator

13

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
1.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM appl ication, Connected
Vehi cl e dri ver interface system

The Connected Vehi cl e
-
based SPD
-
HARM application shall
pass target speed recommendations to the dri ver i nterface
system.

System
-
to
-
system
Interface

RS
-
1.2

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall
communi cate i ndividualized target speed recommendations
to the dri ver.

Functi onal

RS
-
1.2.1

x

x

x

Connected Vehicle driver interface
system

The Connected Vehicle driver interface system shall
communicate individualized target speed recommendations
to the driver utilizing auditory, visual, or haptic alerts and on
-
screen messages.

Human
-
Machine
Interface

SPD
-
HARM
User Need 2 & 8: Know which lane
to be in & Communicate relevant information
to vehicle operator

14

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
2.1

x

x

x

Connected Vehi cl e

The Connected Vehi cl e shall have the ability to detect the l ane
i n whi ch it i s traveling.

Functi onal

RS
-
2.2

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM appl ication, Connected
Vehi cl e dri ver interface system

The Connected Vehi cl e
-
based SPD
-
HARM application shall
pass target l ane recommendations to the dri ver interface
system.

System
-
to
-
system
Interface

RS
-
2.3

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall
communi cate target l ane recommendations to the dri ver.

Functi onal

RS
-
2.3.1

x

x

x

Connected Vehicle driver interface
system

The Connected Vehicle driver interface system shall
communicate individualized target lane recommendations to
the driver utilizing auditory, visual, or haptic alerts and on
-
screen messages.

Human
-
Machine
Interface

SPD
-
HARM User Need 3 & 8: Know why
given
speed is being recommended & Communicate
relevant information to vehicle operator

15

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
3.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM appl ication, Connected
Vehi cl e dri ver interface system

The Connected Vehi cl e
-
based SPD
-
HARM application shall
pass speed change justification information to the dri ver
i nterface system.

System
-
to
-
system
Interface

RS
-
3.2

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall
communi cate speed change justification information to the
dri ver.

Functi onal

RS
-
3.2.1

x

x

x

Connected Vehicle driver interface
system

The Connected Vehicle driver interface system shall
communicate individualized speed change justification
information to the driver utilizing auditory or visual (on
-
screen) messages.

Human
-
Machine
Interface

SPD
-
HARM User Need 4:

Personal
data to remain private and secure

16

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
4.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM appl ication

The Connected Vehi cl e
-
based SPD
-
HARM application shall
uti l ize secure data transmission methods when di ssemi nating
any personally identifiable i nformation.

Securi ty

RS
-
4.2

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall
anonymize

all personally
i denti fiable i nformation obtained from Connected Vehi cles.

Pri vacy

RS
-
4.3

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall use secure transmission
methods for di ssemi nating target speed and l ane
recommendati ons and justification for speed changes

Securi ty

RS
-
4.4

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall protect systems and data
(i ncluding PII) from unauthorized access.

Securi ty

SPD
-
HARM User Need 5:

Collect
relevant vehicle data

17

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
5.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, On
-
board Diagnostic (OBD)
reader, Vehi cle Bus System

The Connected Vehi cl e
-
based SPD
-
HARM application shall
communi cate wi th the vehi cle bus system to gather real
-
time vehi cle
-
col lected data from the vehi cle network.

Functi onal

RS
-
5.1.1

x

x

x

Connected Vehicle
-
based SPD
-
HARM
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based SPD
-
HARM application shall
communicate with the vehicle bus system to gather vehicle
movement data (time, location, velocity, heading, lateral and
longitudinal acceleration, yaw rate, rate of change of steering wheel,
brake status, brake boost status, impact sensor status, anti
-
lock
braking status) from the vehicle network.

Functional

RS
-
5.1.2

x

x

x

Connected Vehicle
-
based SPD
-
HARM
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based SPD
-
HARM application shall
communicate with the vehicle bus system to gather weather data
(time, location, external air temperature, barometric pressure, wiper
status, headlight status) from the vehicle network.

Functional

RS
-
5.1.3

x

x

x

Connected Vehicle
-
based SPD
-
HARM
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based SPD
-
HARM application shall
communicate with the vehicle bus system to gather road surface data
(time, location, traction control status, stability control status,
differential wheel speed) from the vehicle network.

Functional

RS
-
5.2

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, OBD reader, Vehi cle Bus
System

Communi cations between the Connected Vehi cl e
-
based SPD
-
HARM
appl ication and the vehi cle bus system shall uti lize standardized data
sets and communications protocols.

Functi onal

SPD
-
HARM User Need
6: Disseminate
relevant
vehicle data to other vehicles or systems

18

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
6.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, Target Connected Vehi cle
communi cation system

The Connected Vehi cl e
-
based SPD
-
HARM application shall
di ssemi nate vehi cle
-
collected data (current lane, current speed,
current l ocation, current acceleration/deceleration, actions
[accel eration, deceleration, compliance wi th target speed], road
condi tion, and weather information) to other connected vehicles
uti l izing V2V communication.

System
-
to
-
system
Interface

RS
-
6.2

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, RSE, Transportation Mgmt
Enti ty

The Connected Vehi cl e
-
based SPD
-
HARM application shall
di ssemi nate vehi cle
-
collected data (current lane, current speed,
current l ocation, current acceleration/deceleration, actions
[accel eration, deceleration, compliance wi th target speed], road
condi tion, and weather information) to i nfrastructure systems
uti l izing V2I communication.

System
-
to
-
system
Interface

SPD
-
HARM User Need 7:
Receive
relevant
information from other vehicles or systems

19

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
7.1

x

x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, Target Connected Vehi cle
communi cation system

The Connected Vehi cl e
-
based SPD
-
HARM application shall have the
abi lity to receive target vehi cle
-
collected data (current lane,
current speed, current l ocation, current acceleration/decel eration,
acti ons [acceleration, decel eration, compliance wi th target speed],
road condition, and weather i nformation) from other connected
vehi cl es utilizing V2V communi cation.

System
-
to
-
system
Interface

RS
-
7.2



x

x

Connected Vehi cl e
-
based SPD
-
HARM
appl ication, RSE, Transportation Mgmt
Enti ty

The Connected Vehi cl e
-
based SPD
-
HARM application shall have the
abi lity to receive target speed recommendations, target l ane
recommendati ons and justification for speed changes from
i nfrastructure
-
based systems utilizing I2V communication.

System
-
to
-
system
Interface

SPD
-
HARM User Need
9:

Receive
multi
-
source data

20

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
9.1



x

x

Traffi c Management Enti ty
(TME)
-
based
SPD
-
HARM appl ication, Weather Data
Envi ronment, RSE, Connected Vehi cles

The
Traffi c Management Enti ty
(TME)
-
based SPD
-
HARM
appl ication shall have a data collection capability for receiving real
-
ti me data from mul ti ple sources.

Functi onal

RS
-
9.1.1



x

x

Traffi c Management Enti ty
(TME)
-
based
SPD
-
HARM appl ication, Weather Data
Envi ronment, Roadside Equipment
(RSE), Connected Vehi cl es

The TME
-
based SPD
-
HARM application shall have a data collection
capability for receiving real
-
time traffic, road conditions, and
weather data from i nfrastructure
-
based systems.

Functi onal

RS
-
9.1.2



x

x

TME
-
based SPD
-
HARM application,
Connected Vehi cl es

The TME
-
based SPD
-
HARM application shall have the capability to
recei ve real
-
time traffic (i ncluding speed, fl ow and density), road
condi tions (e.g. i ce, wet, etc.), and weather data (clear, rainy and
snowy) from connected vehicles.

Functi onal

RS
-
9.2



x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have the capability to
access a data envi ronment that i ncludes historical traffic data
(i ncluding speed, flow and density), road conditions data (e.g. i ce,
wet, etc.), and weather data (clear, rainy and snowy).

Functi onal

SPD
-
HARM User Need
10:

Process multi
-
source data

21

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
10.1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall be capable of fusing
and processing data from various sources to make target speed
recommendati ons.

Functi onal

RS
-
10.1.1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize real
-
time,
hi storical, and predicted traffic data when calculating the
recommended target speed.

Functi onal

RS
-
10.1.2

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize real
-
time and
predi cted weather data when calculating the recommended target
speed.

Functi onal

RS
-
10.1.3

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize real
-
time and
predi cted road surface data when calculating the recommended
target speed.

Functi onal

RS
-
10.2

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a shockwave
detecti on capability for known fi xed bottleneck locations.

Functi onal

RS
-
10.2.1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a shockwave
detecti on capability that i dentifies at least 95% of all shockwave
occurrences for known fixed bottl eneck l ocations.

Performance

RS
-
10.2.2

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a false positive
i denti fication rate of no more than 5% of al l shockwave events at
known fi xed bottl eneck locations.

Performance

RS
-
10.2.3

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall detect formed
shockwaves wi thin 5 seconds of formation at known fixed
bottl eneck l ocations.

Performance

RS
-
10.2.4

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the l ane(s)
i mpacted by the formed shockwave.

Functi onal

RS
-
10.2.4.
1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the l ane(s)
i mpacted by the formed shockwave wi thin 5 seconds of shockwave
detecti on.

Performance

SPD
-
HARM User Need
10:

Process multi
-
source
data (continued)

22

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
10.2.5

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the l ength
of the formed shockwave.

Functi onal

RS
-
10.2.5.1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the l ength
of the formed shockwave to wi thi n 10 ft.

Performance

RS
-
10.2.5.2

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the l ength
of the formed shockwave wi thin 5 seconds of shockwave
detecti on.

Performance

RS
-
10.2.5.3

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall update the current
shockwave l ength estimation once per second.

Performance

RS
-
10.2.6

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize real
-
time traffic,
road condition, and weather data in shockwave detecti on
al gorithms.

Functi onal

RS
-
10.3





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a
shockwave/breakdown prediction capability for known fixed
bottl eneck poi nts.

Functi onal

RS
-
10.3.1





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a false positive
predi ction rate of no more than 5% of al l shockwave/breakdown
predi ctions at known fi xed bottleneck locations.

Performance

RS
-
10.3.2





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a mi ssed
predi ction rate of no more than 5% of al l formed
shockwaves/breakdowns at known fixed bottl eneck l ocations.

Performance

RS
-
10.3.3





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall predict impending
shockwaves/breakdowns wi thin 5 seconds of availability of relevant
real
-
time data at known fixed bottleneck locations.

Performance

RS
-
10.3.4





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the
expected ti me of formati on of the predi cted
shockwaves/breakdowns.

Functi onal

SPD
-
HARM User Need
10:

Process multi
-
source
data (continued)

23

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
10.3.4.1





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the ti me of
formati on of the predi cted shockwave/breakdown to wi thin 5 seconds
of actual shockwave/breakdown formation.

Performance

RS
-
10.3.4.2





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall update the
shockwave/breakdown time of formation prediction once per second.

Performance

RS
-
10.3.5





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
l ane(s) i mpacted by the predi cted shockwave/breakdown.

Functi onal

RS
-
10.3.5.1





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
l ane(s) i mpacted by the predi cted shockwave/breakdown wi thin 5
seconds of shockwave/breakdown determi nation.

Performance

RS
-
10.3.5.2





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall update the
shockwave/breakdown impacted lane(s) prediction once per second.

Performance

RS
-
10.3.6





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
l ength of the predi cted shockwave/breakdown.

Functi onal

RS
-
10.3.6.1





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
l ength of the predi cted shockwave/breakdown accurate to wi thin 20 ft
of actual formed shockwave l ength.

Performance

RS
-
10.3.6.2





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
l ength of the formed shockwave/breakdown wi thin 5 seconds of
shockwave/breakdown determination.

Performance

RS
-
10.3.6.3





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall update the
shockwave/breakdown length prediction once per second.

Performance

RS
-
10.3.7





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall determi ne the expected
duration of the predi cted shockwave/breakdown.

Functi onal

RS
-
10.3.8





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize real
-
time and
hi storical data in shockwave/breakdown prediction algorithms.

Functi onal

RS
-
10.3.9





x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize online and offline
model i ng for shockwave/breakdown prediction.

Functi onal

SPD
-
HARM User Need
11:

Generate speed harmonization
strategies

24

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
11.1



x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a target speed
generati on capability.

Functi onal

RS
-
11.1.1



x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall generate target speed
strategies for different segments of the roadway.

Functi onal

RS
-
11.1.2



x

x

TME
-
based SPD
-
HARM application,
Weather Data Environment, RSE,
Connected Vehi cl es

The TME
-
based SPD
-
HARM application shall generate target speed
strategies that consider downstream traffic conditions, predicted
future traffic conditions, weather, and l ocal roadway surface
condi tions.

Functi onal

RS
-
11.1.3



x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall utilize online and
offl i ne model ing to generate target speed strategies.

Functi onal

RS
-
11.1.4

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall take i nto account
anti cipated l evels of driver compliance when generating specific
target speed strategies.

Functi onal

RS
-
11.2

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall provide user education on the
need to compl y wi th recommended speed targets.

Pol icy

SPD
-
HARM User Need
12: Disseminate
speed
harmonization recommendations and
information to connected vehicles/devices

25

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mid

Long

RS
-
12.1

x

x

x

TME
-
based SPD
-
HARM application

The TME
-
based SPD
-
HARM application shall have a target speed
recommendati on dissemination capability.

Functi onal

RS
-
12.1.1

x

x

x

TME
-
based SPD
-
HARM application,
Connected Vehi cl es

The TME
-
based SPD
-
HARM application shall disseminate target
speed recommendati ons to SPD
-
HARM enabl ed connected
vehi cl es on the facility via I2V communications.

Functi onal

RS
-
12.1.2

x

x

x

TME
-
based SPD
-
HARM application, RSE

The TME
-
based SPD
-
HARM application shall disseminate target
speed recommendati ons to DMS l ocations.

Functi onal

SPD
-
HARM User Need 13: Analyze
performance of SPD
-
HARM system

26

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
13.1

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall have the
capability to conduct segment
-
specific and network
-
wide
operati onal performance analysis.

Functi onal

RS
-
13.1.1

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based SPD
-
HARM application shall conduct operational
performance analysis in terms of travel ti me rel iability, travel del ay,
and capacity drop.

Functi onal
/
Performance

RS
-
13.1.2

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall conduct
operati onal performance analysis uti lizing macro
-
, meso
-
, and
mi cro
-
simulation.

Functi onal
/
Performance

RS
-
13.2

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall generate
trends and historical performance reports.

Functi onal
/
Performance

RS
-
13.3

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall have the
capability to assess the rel iability of data.

Functi onal

RS
-
13.4

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based SPD
-
HARM application shall be modi fiable such
that al gorithms and software performance can be i mproved.

Desi gn

RS
-
13.5

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall
conti nuously compare the actual performance of the system wi th
the performance determi ned by the SPD
-
HARM application to
determi ne recommended cal ibrations to the application.

Functi onal
/
Performance

RS
-
13.6

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall provide a
means to i denti fy, track, and analyze uni dentified or mi s
-
identified
shockwave/breakdown formation events.

Functi onal
/
Performance

RS
-
13.7





x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall provide a
means to compare predicted versus actual shockwave/breakdown
occurrences and characteristics.

Functi onal
/
Performance

SPD
-
HARM User Need 14: Collect SPD
-
HARM
data and disseminate relevant information to
other dynamic mobility applications

27

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RS
-
14.1

x

x

x

SPD
-
HARM appl ication, Q
-
WARN
appl ication, CACC application, Dynamic
Mobi l ity Applications (DMAs), Data
Envi ronment

The SPD
-
HARM appl ication shall make SPD
-
HARM
-
derived target
speed i nformation (impacted road segments, target speeds
recommended, user messages provided) available to other dynamic
mobi l ity applications vi a the Data Environment.

System
-
to
-
system
Interface

RS
-
14.2

x

x

x

SPD
-
HARM appl ication, Q
-
WARN
appl ication, CACC application, DMAs,
Data Envi ronment

The SPD
-
HARM appl ication shall make SPD
-
HARM
-
derived
shockwave/breakdown formation information ([predicted] time of
formati on, l ength, duration, lanes i mpacted, user messages
provi ded) available to other dynamic mobility applications via the
Data Envi ronment.

System
-
to
-
system
Interface

5. Q
-
WARN Requirements

28

Q
-
WARN
User Need 1 & 8: Know of a downstream
traffic queue in sufficient time to react safely &
Communicate queue warning to vehicle operator

29

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
1.1

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, Connected Vehi cle driver
i nterface system

The Connected Vehi cl e
-
based SPD
-
HARM application shall pass
i ndi vidualized queue warnings and queue characteristic information
(di stance to end of queue, l ength of queue, l ane(s) i mpacted, other
descri ptions of the queue condi tion) to the dri ver i nterface system.

System
-
to
-
system
Interface

RQ
-
1.2

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall communicate
i ndi vidualized queue warnings and queue characteristic information
(di stance to end of queue, l ength of queue, l ane(s) i mpacted, other
descri ptions of the queue condi tion) to the dri ver.

Functi onal

RQ
-
1.2.1

x

x

x

Connected Vehicle driver interface
system

The Connected Vehicle driver interface system shall communicate
individualized queue warnings and queue information to the driver
utilizing auditory, visual, or haptic alerts and auditory or visual (on
-
screen) messages.

Human
-
Machine
Interface

Q
-
WARN
User Need 2 & 8: Know what actions to
take to respond to an impending queue &
Communicate queue warning to vehicle operator

30

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
2.1

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, Connected Vehi cle driver
i nterface system

The Connected Vehi cl e
-
based Q
-
WARN application shall pass
i ndi vidualized queue response strategies (speed reduction, l ane
change, di version recommendations) to the dri ver interface system.

System
-
to
-
system
Interface

RQ
-
2.2

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall communicate
i ndi vidualized queue response strategies (speed reduction, l ane
change, di version recommendations) to the dri ver.

Functi onal

RQ
-
2.2.1

x

x

x

Connected Vehicle driver interface
system

The Connected Vehicle driver interface system shall communicate
individualized queue response strategies to the driver utilizing
auditory or visual (on
-
screen) messages.

Human
-
Machine
Interface

Q
-
WARN
User Need
3
:

Personal
data to remain private and secure

31

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
3.1

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall utilize
secure data transmission methods when di ssemi nating any
personally identifiable i nformation.

Securi ty

RQ
-
3.2

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall
anonymize

all personally
i denti fiable i nformation obtained from Connected Vehi cles.

Pri vacy

RQ
-
3.3

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall use secure transmission
methods for di ssemi nating queue warnings, queue characteristic
i nformation, and response strategies.

Securi ty

RQ
-
3.4

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall protect systems and data
(i ncluding PII) from unauthorized access.

Securi ty

Q
-
WARN
User Need 4
:

Detect a queued state

32

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
4.1

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall have the
abi lity to detect when the vehi cl e is i n a queued state.

Functi onal

RQ
-
4.2

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, On
-
board Diagnostic (OBD)
reader, Vehi cle Bus System

The Connected Vehi cl e
-
based Q
-
WARN application shall
communi cate wi th the vehi cle bus system to gather real
-
time
vehi cl e
-
collected data from the vehi cle network.

Functi onal

RQ
-
4.2.1

x

x

x

Connected Vehicle
-
based Q
-
WARN
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based Q
-
WARN application shall
communicate with the vehicle bus system to gather vehicle
movement data (time, location, velocity, heading, lateral and
longitudinal acceleration, yaw rate, rate of change of steering wheel,
brake status, brake boost status, impact sensor status, anti
-
lock
braking status) from the vehicle network.

Functional

RQ
-
4.2.2

x

x

x

Connected Vehicle
-
based Q
-
WARN
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based Q
-
WARN application shall
communicate with the vehicle bus system to gather weather data
(time, location, external air temperature, barometric pressure,
wiper status, headlight status) from the vehicle network.

Functional

RQ
-
4.2.3

x

x

x

Connected Vehicle
-
based Q
-
WARN
application, On
-
board Diagnostic (OBD)
reader, Vehicle Bus System

The Connected Vehicle
-
based Q
-
WARN application shall
communicate with the vehicle bus system to gather road surface
data (time, location, traction control status, stability control status,
differential wheel speed) from the vehicle network.

Functional

RQ
-
4.3

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, OBD reader, Vehi cle Bus
System

Communi cations between the Connected Vehi cl e
-
based Q
-
WARN
appl ication and the vehi cle bus system shall uti lize standardized data
sets and communications protocols.

Functi onal

Q
-
WARN
User Need
5
: Disseminate queued status
alert to upstream vehicles and other systems

33

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
5.1

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, Target Connected Vehi cle
communi cation system

The Connected Vehi cl e
-
based Q
-
WARN application shall disseminate
a queued status alert to other connected vehi cles via V2V
communi cation.

Functi onal

RQ
-
5.2

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, RSE

The Connected Vehi cl e
-
based Q
-
WARN application shall disseminate
a queued status alert to i nfrastructure systems via V2I
communi cation.

Functi onal

Q
-
WARN
User Need 6: Receive relevant queue
information from other vehicles or systems

34

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
6.1



x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall have the
abi lity to receive queue warning messages vi a I2V communication
channel s.

Functi onal

RQ
-
6.2

x

x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, Target Connected Vehi cle
communi cation system

The Connected Vehi cl e
-
based Q
-
WARN application shall have the
abi lity to receive queue warning messages vi a V2V communication
channel s.

Functi onal

Q
-
WARN
User Need
7:

Generate
queue response strategies

35

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
7.1



x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall
i ndi vidualize generi c queue warning message based on vehicle's
posi tion and distance to the end of the queue.

Functi onal

RQ
-
7.2



x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall generate
appropriate queue response strategies based on l ocal traffic,
weather, and roadway conditions and distance to end of queue.

Functi onal

RQ
-
7.3



x

x

Connected Vehi cl e
-
based Q
-
WARN
appl ication, SPD
-
HARM application,
Enabl eATIS application, FRATIS
appl ication

The Connected Vehi cl e
-
based Q
-
WARN application shall generate
appropriate queue response strategies that i nclude speed
reducti on, lane change, or di version recommendations.

Functi onal

RQ
-
7.3.1



x

x

Connected Vehicle
-
based Q
-
WARN
application, SPD
-
HARM application

The Connected Vehicle
-
based Q
-
WARN application shall interface
with the Connected Vehicle
-
based SPD
-
HARM application to
generate appropriate speed reduction targets.

System
-
to
-
system
Interface

RQ
-
7.3.2



x

x

Connected Vehicle
-
based Q
-
WARN
application, SPD
-
HARM application

The Connected Vehicle
-
based Q
-
WARN application shall interface
with the Connected Vehicle
-
based SPD
-
HARM application to
generate appropriate lane change recommendations.

System
-
to
-
system
Interface

RQ
-
7.3.3



x

x

Connected Vehicle
-
based Q
-
WARN
application, EnableATIS application,
FRATIS application

The Connected Vehicle
-
based Q
-
WARN application shall interface
with the Connected Vehicle
-
based EnableATIS and/or FRATIS
applications to generate appropriate route diversion
recommendations.

System
-
to
-
system
Interface

Q
-
WARN
User Need 9: Collect relevant
traffic, road conditions, and weather data

36

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
9.1



x

x

Traffi c Management Enti ty
(TME)
-
based
Q
-
WARN appl ication, Weather Data
Envi ronment, RSE, Connected Vehi cles

The
Traffi c Management Enti ty
(TME)
-
based Q
-
WARN application
shall have a data collection capability for receiving real
-
time traffic,
road conditions, and weather data from mul tiple sources.

Functi onal

RQ
-
9.1.1



x

x

Traffic Management Entity
(TME)
-
based
Q
-
WARN application, Weather Data
Environment, RSE, Connected Vehicles

The
Traffic Management Entity
(TME)
-
based Q
-
WARN application
shall have a data collection capability for receiving real
-
time traffic,
road conditions, and weather data from infrastructure
-
based
systems.

Functional

RQ
-
9.1.2



x

x

TME
-
based Q
-
WARN application,
Connected Vehicles

The TME
-
based Q
-
WARN application shall have the capability to
receive real
-
time traffic (including speed, flow and density), road
conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and
snowy) from connected vehicles.

Functional

RQ
-
9.2



x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall have the capability to
access a data envi ronment that i ncludes historical traffic data
(i ncluding speed, flow and density), road conditions data (e.g. i ce,
wet, etc.), and weather data (clear, rainy and snowy).

Functi onal

Q
-
WARN
User Need 10: Disseminate relevant
traffic, road condition, and weather data to
vehicles

37

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
10.1

x

x

x

Traffic Management Entity,
Connected
Vehicles

The
Traffic Management Entity
shall communicate traffic, road
condition, and weather data to connected vehicles/devices via I2V
communications systems.

Functional

Q
-
WARN
User Need
11:

Detect
a formed queue

38

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
11.1

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall be capable of fusing and
processing data from various sources to perform queue detecti on.

Functi onal

RQ
-
11.1.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time, predicted,
and historical traffic data in queue detection algorithms.

Functional

RQ
-
11.1.2

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time and
predicted weather data in queue detection algorithms.

Functional

RQ
-
11.1.3

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time and
predicted road surface data in queue detection algorithms.

Functional

RQ
-
11.2

x

x

x

Traffi c Mgmt Enti ty
-
based Q
-
WARN
appl ication

The TME
-
based Q
-
WARN appl ication shall have a queue detecti on
capability for known fixed queue generation l ocations.

Functi onal

RQ
-
11.2.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall have a false positive
identification rate of no more than 1% of all queue detection events at
known fixed queue generation locations.

Performance

RQ
-
11.2.2

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall have a missed detection rate
no more than 1% of all formed queues at known fixed queue
generation locations.

Performance

RQ
-
11.2.3

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall detect formed queues within
5 seconds of formation at known fixed queue generation locations.

Performance

RQ
-
11.3

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the l ane(s)
i mpacted by the formed queue.

Functi onal

RQ
-
11.3.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the lane(s)
impacted by the formed queue within 5 seconds of queue detection.

Performance

Q
-
WARN
User Need
11:

Detect
a formed
queue (continued)

39

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
11.4

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the l ength of the
formed queue.

Functi onal

RQ
-
11.4.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the length of the
formed queue to within 10 ft.

Performance

RQ
-
11.4.2

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the length of the
formed queue within 5 seconds of queue detection.

Performance

RQ
-
11.4.3

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the current queue
length estimation once per second.

Performance

RQ
-
11.5

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the number of
vehi cl es in the formed queue.

Functi onal

RQ
-
11.5.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the number of
vehicles in the formed queue within 5 seconds of queue detection.

Performance

RQ
-
11.5.1.2

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall update the current car count
esti mation once per second.

Performance

RQ
-
11.6

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the traveling
speed and di rection of the formed queue.

Functi onal

RQ
-
11.6.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the traveling
speed of the formed queue within 5 seconds of queue detection.

Performance

RQ
-
11.6.2

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the estimation of the
traveling speed of the queue once per second.

Performance

RQ
-
11.6.3

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the traveling
speed of the formed queue to within 5 mph.

Performance

Q
-
WARN
User Need
12:

Predict impending queue
formation

40

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
12.1





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall be capable of fusing and processing
data from various sources to perform queue predi ction.

Functi onal

RQ
-
12.1.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time, predicted, and
historical traffic data in queue prediction algorithms.

Functional

RQ
-
12.1.2





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time and predicted
weather data in queue prediction algorithms.

Functional

RQ
-
12.1.3





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize real
-
time and predicted road
surface data in queue prediction algorithms.

Functional

RQ
-
12.1.4





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize online and offline modeling in
queue prediction algorithms.

Functional

RQ
-
12.2





x

Traffi c Mgmt Enti ty
-
based Q
-
WARN
appl ication

The TME
-
based Q
-
WARN appl ication shall have a queue predi ction capability
for known fi xed queue generation l ocations.

Functi onal

RQ
-
12.2.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall have a false positive identification
rate of no more than 5% of all queue detection events at known fixed queue
generation locations.

Performance

RQ
-
12.2.2





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall have a missed prediction rate no
more than 5% of all formed queues at known fixed queue generation locations.

Performance

RQ
-
12.3





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the ti me of formati on of
the predi cted queue.

Functi onal

RQ
-
12.3.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the time of formation of
the predicted queue to within 5 seconds of actual queue formation.

Performance

RQ
-
12.4





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the l ane(s) i mpacted by
the predi cted queue.

Functi onal

RQ
-
12.4.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the lane(s) impacted by
the predicted queue within 5 seconds of queue determination.

Performance

Q
-
WARN
User Need
12:

Predict impending queue
formation (
con’t
)

41

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
12.5





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the l ength of the
predi cted queue.

Functi onal

RQ
-
12.5.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the length of the
predicted queue to within 20 ft of actual formed queue length.

Performance

RQ
-
12.5.2





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the length of the
predicted queue within 5 seconds of queue determination.

Performance

RQ
-
12.5.3





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the current queue length
prediction once per second.

Performance

RQ
-
12.6





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the expected duration
of the predi cted queue.

Functi onal

RQ
-
12.6.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the expected duration of
the predicted queue once per second.

Performance

RQ
-
12.7





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the number of vehi cles
i n the predi cted queue.

Functi onal

RQ
-
12.7.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the number of vehicles
in the predicted queue within 5 seconds of queue determination.

Performance

RQ
-
12.7.2





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the car count estimation for
the predicted queue once per second.

Performance

RQ
-
12.8





x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall determi ne the traveling speed and
di rection of the predi cted queue.

Functi onal

RQ
-
12.8.1





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the traveling speed of
the predicted queue within 5 seconds of queue determination.

Performance

RQ
-
12.8.2





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall update the estimated traveling
speed of the predicted queue once per second.

Performance

RQ
-
12.8.3





x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall determine the traveling speed of
the predicted queue to within 10 mph of the speed of the actual formed
queue.

Performance

Q
-
WARN
User Need 13: Generate queue warning
response strategies for upstream vehicles

42

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
13.1



x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall have a queue warning response
strategy generation capability.

Functi onal

RQ
-
13.1.1



x

x

TME
-
based Q
-
WARN application, SPD
-
HARM application, EnableATIS
application, FRATIS application

The TME
-
based Q
-
WARN application shall generate queue warning
response strategies that include speed reduction, lane change, and
diversion recommendations.

Functional

RQ
-
13.1.1.1



x

x

TME
-
based Q
-
WARN appl ication, SPD
-
HARM appl ication

The TME
-
based Q
-
WARN appl ication shall i nterface wi th the TME
-
based
SPD
-
HARM appl ication to generate appropriate speed reduction targets.

System
-
to
-
system Interface

RQ
-
13.1.1.2



x

x

TME
-
based Q
-
WARN appl ication, SPD
-
HARM appl ication

The TME
-
based Q
-
WARN appl ication shall i nterface wi th the TME
-
based
SPD
-
HARM appl ication to generate appropriate l ane change
recommendati ons.

System
-
to
-
system Interface

RQ
-
13.1.1.3



x

x

TME
-
based Q
-
WARN appl ication,
Enabl eATIS application, FRATIS
appl ication

The TME
-
based Q
-
WARN appl ication shall i nterface wi th the TME
-
based
Enabl eATIS and/or FRATIS applications to generate appropriate route
di version recommendations.

System
-
to
-
system Interface

RQ
-
13.1.2



x

x

TME
-
based Q
-
WARN application,
Weather Data Environment, RSE,
Connected Vehicles

The TME
-
based Q
-
WARN application shall generate target speed
strategies that consider distance to end of queue, estimated duration of
the queue, other descriptions of the queue condition, downstream traffic
conditions, predicted future traffic conditions, weather, and local roadway
surface conditions.

Functional

RQ
-
13.1.3



x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall utilize online and offline
modeling to generate queue warning response recommendations.

Functional

RQ
-
13.2

x

x

x

TME
-
based Q
-
WARN appl ication

The TME
-
based Q
-
WARN appl ication shall take into account anticipated
l evel s of driver compliance when generati ng specific queue warnings.

Functi onal

RQ
-
13.3

x

x

x

Traffi c Management Enti ty

The
Traffi c Management Enti ty
shall provide user education on the need
to compl y wi th queue warning response recommendations.

Pol icy

Q
-
WARN
User Need
14:

Disseminate
queue warnings

43

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
14.1

x

x

x

TME
-
based Q
-
WARN application

The TME
-
based Q
-
WARN application shall have a queue warning
and queue information dissemination capability.

Functional

RQ
-
14.1.1

x

x

x

TME
-
based Q
-
WARN appl ication, RSE

The TME
-
based Q
-
WARN appl ication shall dissemi nate queue
warni ngs and queue i nformation to DMS l ocations.

Functi onal

RQ
-
14.1.2



x

x

TME
-
based Q
-
WARN appl ication,
Connected Vehi cl es

The TME
-
based Q
-
WARN appl ication shall dissemi nate queue
warni ngs and queue i nformation to connected vehicles.

Functi onal

RQ
-
14.1.3

x

x

x

TME
-
based Q
-
WARN appl ication,
Travel er Information Systems

The TME
-
based Q
-
WARN appl ication shall dissemi nate queue
warni ngs and queue i nformation to traveler i nformation systems
(e.g., 511).

Functi onal

Q
-
WARN
User Need
15:

Analyze
performance of the Q
-
WARN system

44

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
15.1

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Monitoring Subsystem

The TME
-
based Performance Monitoring Subsystem shall have the
capability to conduct segment
-
specific and network
-
wide
operational performance analysis.

Functional

RQ
-
15.1.1

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based SPD
-
HARM application shall conduct operational
performance analysis in terms of travel ti me rel iability, travel del ay,
and capacity drop.

Functi onal
/
Performance

RQ
-
15.1.2

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Moni toring Subsystem

The TME
-
based Performance Moni toring Subsystem shall conduct
operati onal performance analysis uti lizing macro
-
, meso
-
, and
mi cro
-
simulation.

Functi onal
/
Performance

RQ
-
15.2

x

x

x

TME
-
based Q
-
WARN application, TME
Performance Monitoring Subsystem

The TME
-
based Q
-
WARN application shall provide a means to
identify, track, and analyze unidentified or mis
-
identified queue
formation events.

Functional
/
Performance

RQ
-
15.3





x

TME
-
based Q
-
WARN application, TME
Performance Monitoring Subsystem

The TME
-
based Q
-
WARN application shall provide a means to
compare predicted versus actual queue occurrences and
characteristics.

Functional
/
Performance

RQ
-
15.4

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Monitoring Subsystem

The TME
-
based Performance Monitoring Subsystem shall generate
trends and historical performance reports.

Functional/
Performance

RQ
-
15.5

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Monitoring Subsystem

The TME
-
based Performance Monitoring Subsystem shall have the
capability to assess the reliability of data.

Functional

RQ
-
15.6

x

x

x

TME
-
based SPD
-
HARM application, TME
Performance Monitoring Subsystem

The TME
-
based SPD
-
HARM application shall be modifiable such that
algorithms and software performance can be improved.

Design

Q
-
WARN
User Need 17: Disseminate signal
phasing information to approaching vehicles

45

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
17.1

x

x

x

Arterial Signal System, Connected
Vehicles

The Arterial Signal System shall have a dissemination capability to
provide approaching connected vehicles signal phasing information.

System
-
to
-
system
Interface

Q
-
WARN
User Need 18: Collect Q
-
WARN data and
disseminate relevant information to other
dynamic mobility applications

46

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
18.1

x

x

x

Q
-
WARN application, CACC application,
SPD
-
HARM application, DMAs, Data
Environment

The
Q
-
WARN application shall make Q
-
WARN
-
derived queue
warning information (queue location and characteristics,
recommended responses provided, user messages provided)
available to other dynamic mobility applications via the Data
Environment.

System
-
to
-
system
Interface

Q
-
WARN
User Need 19: Collect and
aggregate Q
-
WARN
related data and disseminate to freeway
and arterial traffic management entities

47

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RQ
-
19.1

x

x

x

Data Capture and Management

Environment

The
Data Capture and Management Environment shall collect,
aggregate, and disseminate queue warning related data to freeway
and arterial traffic management entities.

System
-
to
-
system
Interface

6. CACC Requirements

48

CACC User
Need
1:

Join
a CACC platoon

49

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RC
-
1.1

x

x

x

Connected Vehi cl e
-
based CACC
appl ication

The Connected Vehi cl e
-
based CACC application shall determine
recommended pl atoon entry l ocation and ti ming for vehicle
enteri ng a pl atoon.

Functi onal

RC
-
1.1.1

x

x

x

Connected Vehicle driver interface
system

The driver interface system shall provide the driver the means to
initiate a CACC platoon entry request.

Human
-
Machine
Interface

RC
-
1.1.2

x

x

x

Connected Vehicle
-
based CACC
application

The Connected Vehicle
-
based CACC application shall determine the
appropriate time to transfer longitudinal vehicle control from the
driver to the vehicle upon entry into the CACC platoon.

Functional

RC
-
1.1.3

x

x

x

Connected Vehicle
-
based CACC
application, Connected Vehicle driver
interface system

The driver interface system shall alert the driver of the transfer of
longitudinal control when entering a CACC platoon.

Human
-
Machine
Interface

RC
-
1.2.1

x

x

x

Connected Vehicle
-
based CACC
application, Target Connected Vehicle
communication system

The Connected Vehicle
-
based CACC application shall identify
potential platoons to join based on established vehicle
-
based
criteria for acceptable platoon speed and gap policies, performance
characteristics, and platoon sizes.

Functional

RC
-
1.2.2

x

x

x

Connected Vehicle
-
based CACC
application, Target Connected Vehicle
communication system

The Connected Vehicle
-
based CACC application shall be capable of
identifying the platoon in which it is joining or traveling.

Functional

RC
-
1.2.3

x

x

x

Connected Vehicle
-
based CACC
application, Target Connected Vehicle
communication system

The Connected Vehicle
-
based CACC application shall be capable of
identifying the number of vehicles in the platoon, the lane location
of the platoon, the spatial location of start and end points of the
platoon, and the performance characteristics of vehicles within a
platoon in which it is joining or traveling.

Functional

CACC User
Need 2
:

Establish
or accept a speed and gap policy

50

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RC
-
2.1

x

x

x

Connected Vehi cl e
-
based CACC
appl ication, Connected Vehi cle driver
i nterface system

The Connected Vehi cl e
-
based CACC application shall communicate
the current speed and gap policy to the dri ver i nterface system for
di splay to the dri ver.

Human
-
Machine
Interface

RC
-
2.2

x

x

x

Connected Vehi cl e driver interface
system

The Connected Vehi cl e dri ver interface system shall provide a
means for the dri ver to accept, reject, and modify a given speed and
gap pol icy.

Human
-
Machine
Interface

RC
-
2.3

x

x

x

Connected Vehi cl e
-
based CACC
appl ication, Connected Vehi cle driver
i nterface system

The Connected Vehi cl e
-
based CACC application shall modify the
current speed and gap policy based on i nstructions received by the
dri ver via the driver interface system.

Functi onal

CACC User
Need
3:

Exit a CACC platoon

51

Req.
ID

Application Evolution State

Systems/Subsystems Involved

Functional Requirement

Req.
Type

Near

Mi d

Long

RC
-
3.1

x

x

x

Connected Vehi cl e
-
based CACC
appl ication

The Connected Vehi cl e
-
based CACC application shall determine
recommended pl atoon exit l ocation and ti ming for vehi cle exiting a
pl atoon.