SYSTEMS ENGINEERING ANALYSIS BR to NO ITS - TIM Phase 1 Design-Build Project September 2007 Presented to: Louisiana Department of Transportation And Development FOR INFORMATIONAL PURPOSES ONLY
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SYSTEMS ENGINEERING ANALYSIS
BR to NO ITS - TIM
Phase 1
Design-Build Project
September 2007
Presented to
Louisiana Department of Transportation And Development
FOR INFORMATIO
NAL PURPOSES ONLY
Baton Rouge to New Orleans Intelligent Transportation Systems ndash
Traffic Incident Management Phase 1 Design-Build Project
Systems Engineering Analysis
Presented to
Louisiana Department Of Transportation And Development
Prepared by
September 2007
TABLE OF CONTENTS
1 Introduction 1 2 Acronyms and Abbreviations 3 3 Systems Engineering Approach 4 4 Project Physical Architecture 5 5 Concept of Operations 8
51 Purpose 8 52 Scope 8 53 Justification for the ITS Project 9 54 Existing Operations 9
541 TrafficRoadway Management 11 542 Incident Management 13 543 Emergency Management 13
55 System Overview 13 551 ITS Equipment Operations 15 552 Center-to-Center Operations 15
56 Stakeholders 15 57 Operational Environment 16 58 Operational Scenarios 16
581 Traffic Incident Management Operations (TIM) 16 582 Emergency Management Operations 17
59 Summary of Impacts 17 6 Requirements 18
61 Traffic ManagementTraffic Incident Management 18 62 Emergency Management System 35 63 Requirements Traceability Matrix 55
7 System Design 55 71 High-Level Design 55
711 Project Organization 55 72 Detailed Design 56
8 Alternative Communication Configurations 56 81 Communication Technologies 57
811 Fiber Optic Cable (Single Mode) 57 812 Cellular Digital Packet Data (CDPD) 58 813 Global System for Mobile Communication (GSM) 58 814 Radio Frequency (Spread Spectrum) 59 815 Terrestrial Microwave Links 60 816 Area Radio Network (ARN) 60 817 Telephone Lease Lines Line 61 818 Code-Division Multiple Access (CDMA) 61 819 Orthogonal Frequency Division Multiplexing (OFDM) 62
82 Project Communications 63 9 Power Configuration 64 10 Software Alternative Configurations 64 11 Procurement Options 65
111 Procurement Options of ITS Technologies 65 1111 Non-Exempt Commodities 65 1112 Exempt Commodities 66
112 ITS Hardware Technologies 66 113 Software 67
SE Analysis September 2007 ii
SE Analysis September 2007 iii
114 Communications 67 115 Project Procurement Methods Available for Use by LADOTD 67 116 Procurement Method for Project 68
12 ITS Standards 68 121 Project Standards 69
1211 Center-to-Field Standards 69 122 Standards Applicable to the Project 70
13 Testing 72 14 Maintenance 73
141 Life-Cycle Funding 73
1 Introduction To assure interoperability of physical systems and a coherent traffic management program the implementation of an Intelligent Transportation System (ITS) project requires consideration as to how the project will fit into the National State and Regional ITS Architectures (specifically the Louisiana State ITS Implementation and Telecommunication Plan 2002) The Federal Highway Administration (FHWA) has developed and mandated that a ldquoSystems Engineeringrdquo process be used whenever ITS technologies are to be deployed This process will give the implementing agency confidence that resources are being used optimally returning the maximum value for transportation dollars spent LADOTD supported by the Federal Highway Administration has requested the implementation of the Baton Rouge to New Orleans ITS Traffic Incident Management (TIM) Phase I project This project is 17 miles in length and the first of three (3) project phases to deploy ITS technologies along the Interstate 10 (I-10) corridor from Baton Rouge to New Orleans The goal of Phase I is to deploy an ITS system that will provide LADOTD and the Louisiana State Police (LSP) with traffic surveillance and management tools to more effectively facilitate traffic and incident management activities on I-10 across the Bonnet Carre Spillway and its designated alternative route US 61 (Airline Highway) ITS equipment will provide LADOTD and LSP with the ability to detect verify advise affected motorists respond manage traffic and clear traffic incidents within the project limits The project will result in improved mobility and safety for all motorists A unique aspect of this project is that the Design-Build (DB) contracting method will be used for the first time by LADOTD to implement a fully operational ITS project LADOTD has prepared a functional specification that will be used by the Design-Builder in order to develop their specific system design and build it There are a number of advantages for LADOTD using this contracting technique First it allows the design-builder the flexibility of implementing an ITS system with the most recently tested and effective technologies Second the overall responsibility for designing constructing testing and implementing the ITS system falls to the Design-Builder Third this process should reduce project implementation time Section 6 of this document contains the project requirements Both the Design-Builder and the stakeholders are required to implementfulfill these requirements The Design-Builder will be responsible for the requirements only contained in the contract documents The centers operating the ITS equipment will be the LADOTD ITS Statewide TMC in Baton Rouge the LADOTD District 02 (Bridge City) The LSP Troop B office in Kenner will only have monitoring capability LADOTD is currently constructing the New Orleans Transportation Management Center (RTMC) at the corner of West End Blvd and Veteranrsquos Blvd For the purposes of this analysis the RTMC has been included with the District 02 (Bridge City) office as the role of the ITS operator will be the same whether at the Bridge City site or the RTMC facility Figure 1 shows the project area and physical limits of the ITS project implementation along the I-10 corridor
SE Analysis September 2007 1
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
Baton Rouge to New Orleans Intelligent Transportation Systems ndash
Traffic Incident Management Phase 1 Design-Build Project
Systems Engineering Analysis
Presented to
Louisiana Department Of Transportation And Development
Prepared by
September 2007
TABLE OF CONTENTS
1 Introduction 1 2 Acronyms and Abbreviations 3 3 Systems Engineering Approach 4 4 Project Physical Architecture 5 5 Concept of Operations 8
51 Purpose 8 52 Scope 8 53 Justification for the ITS Project 9 54 Existing Operations 9
541 TrafficRoadway Management 11 542 Incident Management 13 543 Emergency Management 13
55 System Overview 13 551 ITS Equipment Operations 15 552 Center-to-Center Operations 15
56 Stakeholders 15 57 Operational Environment 16 58 Operational Scenarios 16
581 Traffic Incident Management Operations (TIM) 16 582 Emergency Management Operations 17
59 Summary of Impacts 17 6 Requirements 18
61 Traffic ManagementTraffic Incident Management 18 62 Emergency Management System 35 63 Requirements Traceability Matrix 55
7 System Design 55 71 High-Level Design 55
711 Project Organization 55 72 Detailed Design 56
8 Alternative Communication Configurations 56 81 Communication Technologies 57
811 Fiber Optic Cable (Single Mode) 57 812 Cellular Digital Packet Data (CDPD) 58 813 Global System for Mobile Communication (GSM) 58 814 Radio Frequency (Spread Spectrum) 59 815 Terrestrial Microwave Links 60 816 Area Radio Network (ARN) 60 817 Telephone Lease Lines Line 61 818 Code-Division Multiple Access (CDMA) 61 819 Orthogonal Frequency Division Multiplexing (OFDM) 62
82 Project Communications 63 9 Power Configuration 64 10 Software Alternative Configurations 64 11 Procurement Options 65
111 Procurement Options of ITS Technologies 65 1111 Non-Exempt Commodities 65 1112 Exempt Commodities 66
112 ITS Hardware Technologies 66 113 Software 67
SE Analysis September 2007 ii
SE Analysis September 2007 iii
114 Communications 67 115 Project Procurement Methods Available for Use by LADOTD 67 116 Procurement Method for Project 68
12 ITS Standards 68 121 Project Standards 69
1211 Center-to-Field Standards 69 122 Standards Applicable to the Project 70
13 Testing 72 14 Maintenance 73
141 Life-Cycle Funding 73
1 Introduction To assure interoperability of physical systems and a coherent traffic management program the implementation of an Intelligent Transportation System (ITS) project requires consideration as to how the project will fit into the National State and Regional ITS Architectures (specifically the Louisiana State ITS Implementation and Telecommunication Plan 2002) The Federal Highway Administration (FHWA) has developed and mandated that a ldquoSystems Engineeringrdquo process be used whenever ITS technologies are to be deployed This process will give the implementing agency confidence that resources are being used optimally returning the maximum value for transportation dollars spent LADOTD supported by the Federal Highway Administration has requested the implementation of the Baton Rouge to New Orleans ITS Traffic Incident Management (TIM) Phase I project This project is 17 miles in length and the first of three (3) project phases to deploy ITS technologies along the Interstate 10 (I-10) corridor from Baton Rouge to New Orleans The goal of Phase I is to deploy an ITS system that will provide LADOTD and the Louisiana State Police (LSP) with traffic surveillance and management tools to more effectively facilitate traffic and incident management activities on I-10 across the Bonnet Carre Spillway and its designated alternative route US 61 (Airline Highway) ITS equipment will provide LADOTD and LSP with the ability to detect verify advise affected motorists respond manage traffic and clear traffic incidents within the project limits The project will result in improved mobility and safety for all motorists A unique aspect of this project is that the Design-Build (DB) contracting method will be used for the first time by LADOTD to implement a fully operational ITS project LADOTD has prepared a functional specification that will be used by the Design-Builder in order to develop their specific system design and build it There are a number of advantages for LADOTD using this contracting technique First it allows the design-builder the flexibility of implementing an ITS system with the most recently tested and effective technologies Second the overall responsibility for designing constructing testing and implementing the ITS system falls to the Design-Builder Third this process should reduce project implementation time Section 6 of this document contains the project requirements Both the Design-Builder and the stakeholders are required to implementfulfill these requirements The Design-Builder will be responsible for the requirements only contained in the contract documents The centers operating the ITS equipment will be the LADOTD ITS Statewide TMC in Baton Rouge the LADOTD District 02 (Bridge City) The LSP Troop B office in Kenner will only have monitoring capability LADOTD is currently constructing the New Orleans Transportation Management Center (RTMC) at the corner of West End Blvd and Veteranrsquos Blvd For the purposes of this analysis the RTMC has been included with the District 02 (Bridge City) office as the role of the ITS operator will be the same whether at the Bridge City site or the RTMC facility Figure 1 shows the project area and physical limits of the ITS project implementation along the I-10 corridor
SE Analysis September 2007 1
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
TABLE OF CONTENTS
1 Introduction 1 2 Acronyms and Abbreviations 3 3 Systems Engineering Approach 4 4 Project Physical Architecture 5 5 Concept of Operations 8
51 Purpose 8 52 Scope 8 53 Justification for the ITS Project 9 54 Existing Operations 9
541 TrafficRoadway Management 11 542 Incident Management 13 543 Emergency Management 13
55 System Overview 13 551 ITS Equipment Operations 15 552 Center-to-Center Operations 15
56 Stakeholders 15 57 Operational Environment 16 58 Operational Scenarios 16
581 Traffic Incident Management Operations (TIM) 16 582 Emergency Management Operations 17
59 Summary of Impacts 17 6 Requirements 18
61 Traffic ManagementTraffic Incident Management 18 62 Emergency Management System 35 63 Requirements Traceability Matrix 55
7 System Design 55 71 High-Level Design 55
711 Project Organization 55 72 Detailed Design 56
8 Alternative Communication Configurations 56 81 Communication Technologies 57
811 Fiber Optic Cable (Single Mode) 57 812 Cellular Digital Packet Data (CDPD) 58 813 Global System for Mobile Communication (GSM) 58 814 Radio Frequency (Spread Spectrum) 59 815 Terrestrial Microwave Links 60 816 Area Radio Network (ARN) 60 817 Telephone Lease Lines Line 61 818 Code-Division Multiple Access (CDMA) 61 819 Orthogonal Frequency Division Multiplexing (OFDM) 62
82 Project Communications 63 9 Power Configuration 64 10 Software Alternative Configurations 64 11 Procurement Options 65
111 Procurement Options of ITS Technologies 65 1111 Non-Exempt Commodities 65 1112 Exempt Commodities 66
112 ITS Hardware Technologies 66 113 Software 67
SE Analysis September 2007 ii
SE Analysis September 2007 iii
114 Communications 67 115 Project Procurement Methods Available for Use by LADOTD 67 116 Procurement Method for Project 68
12 ITS Standards 68 121 Project Standards 69
1211 Center-to-Field Standards 69 122 Standards Applicable to the Project 70
13 Testing 72 14 Maintenance 73
141 Life-Cycle Funding 73
1 Introduction To assure interoperability of physical systems and a coherent traffic management program the implementation of an Intelligent Transportation System (ITS) project requires consideration as to how the project will fit into the National State and Regional ITS Architectures (specifically the Louisiana State ITS Implementation and Telecommunication Plan 2002) The Federal Highway Administration (FHWA) has developed and mandated that a ldquoSystems Engineeringrdquo process be used whenever ITS technologies are to be deployed This process will give the implementing agency confidence that resources are being used optimally returning the maximum value for transportation dollars spent LADOTD supported by the Federal Highway Administration has requested the implementation of the Baton Rouge to New Orleans ITS Traffic Incident Management (TIM) Phase I project This project is 17 miles in length and the first of three (3) project phases to deploy ITS technologies along the Interstate 10 (I-10) corridor from Baton Rouge to New Orleans The goal of Phase I is to deploy an ITS system that will provide LADOTD and the Louisiana State Police (LSP) with traffic surveillance and management tools to more effectively facilitate traffic and incident management activities on I-10 across the Bonnet Carre Spillway and its designated alternative route US 61 (Airline Highway) ITS equipment will provide LADOTD and LSP with the ability to detect verify advise affected motorists respond manage traffic and clear traffic incidents within the project limits The project will result in improved mobility and safety for all motorists A unique aspect of this project is that the Design-Build (DB) contracting method will be used for the first time by LADOTD to implement a fully operational ITS project LADOTD has prepared a functional specification that will be used by the Design-Builder in order to develop their specific system design and build it There are a number of advantages for LADOTD using this contracting technique First it allows the design-builder the flexibility of implementing an ITS system with the most recently tested and effective technologies Second the overall responsibility for designing constructing testing and implementing the ITS system falls to the Design-Builder Third this process should reduce project implementation time Section 6 of this document contains the project requirements Both the Design-Builder and the stakeholders are required to implementfulfill these requirements The Design-Builder will be responsible for the requirements only contained in the contract documents The centers operating the ITS equipment will be the LADOTD ITS Statewide TMC in Baton Rouge the LADOTD District 02 (Bridge City) The LSP Troop B office in Kenner will only have monitoring capability LADOTD is currently constructing the New Orleans Transportation Management Center (RTMC) at the corner of West End Blvd and Veteranrsquos Blvd For the purposes of this analysis the RTMC has been included with the District 02 (Bridge City) office as the role of the ITS operator will be the same whether at the Bridge City site or the RTMC facility Figure 1 shows the project area and physical limits of the ITS project implementation along the I-10 corridor
SE Analysis September 2007 1
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
SE Analysis September 2007 iii
114 Communications 67 115 Project Procurement Methods Available for Use by LADOTD 67 116 Procurement Method for Project 68
12 ITS Standards 68 121 Project Standards 69
1211 Center-to-Field Standards 69 122 Standards Applicable to the Project 70
13 Testing 72 14 Maintenance 73
141 Life-Cycle Funding 73
1 Introduction To assure interoperability of physical systems and a coherent traffic management program the implementation of an Intelligent Transportation System (ITS) project requires consideration as to how the project will fit into the National State and Regional ITS Architectures (specifically the Louisiana State ITS Implementation and Telecommunication Plan 2002) The Federal Highway Administration (FHWA) has developed and mandated that a ldquoSystems Engineeringrdquo process be used whenever ITS technologies are to be deployed This process will give the implementing agency confidence that resources are being used optimally returning the maximum value for transportation dollars spent LADOTD supported by the Federal Highway Administration has requested the implementation of the Baton Rouge to New Orleans ITS Traffic Incident Management (TIM) Phase I project This project is 17 miles in length and the first of three (3) project phases to deploy ITS technologies along the Interstate 10 (I-10) corridor from Baton Rouge to New Orleans The goal of Phase I is to deploy an ITS system that will provide LADOTD and the Louisiana State Police (LSP) with traffic surveillance and management tools to more effectively facilitate traffic and incident management activities on I-10 across the Bonnet Carre Spillway and its designated alternative route US 61 (Airline Highway) ITS equipment will provide LADOTD and LSP with the ability to detect verify advise affected motorists respond manage traffic and clear traffic incidents within the project limits The project will result in improved mobility and safety for all motorists A unique aspect of this project is that the Design-Build (DB) contracting method will be used for the first time by LADOTD to implement a fully operational ITS project LADOTD has prepared a functional specification that will be used by the Design-Builder in order to develop their specific system design and build it There are a number of advantages for LADOTD using this contracting technique First it allows the design-builder the flexibility of implementing an ITS system with the most recently tested and effective technologies Second the overall responsibility for designing constructing testing and implementing the ITS system falls to the Design-Builder Third this process should reduce project implementation time Section 6 of this document contains the project requirements Both the Design-Builder and the stakeholders are required to implementfulfill these requirements The Design-Builder will be responsible for the requirements only contained in the contract documents The centers operating the ITS equipment will be the LADOTD ITS Statewide TMC in Baton Rouge the LADOTD District 02 (Bridge City) The LSP Troop B office in Kenner will only have monitoring capability LADOTD is currently constructing the New Orleans Transportation Management Center (RTMC) at the corner of West End Blvd and Veteranrsquos Blvd For the purposes of this analysis the RTMC has been included with the District 02 (Bridge City) office as the role of the ITS operator will be the same whether at the Bridge City site or the RTMC facility Figure 1 shows the project area and physical limits of the ITS project implementation along the I-10 corridor
SE Analysis September 2007 1
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
1 Introduction To assure interoperability of physical systems and a coherent traffic management program the implementation of an Intelligent Transportation System (ITS) project requires consideration as to how the project will fit into the National State and Regional ITS Architectures (specifically the Louisiana State ITS Implementation and Telecommunication Plan 2002) The Federal Highway Administration (FHWA) has developed and mandated that a ldquoSystems Engineeringrdquo process be used whenever ITS technologies are to be deployed This process will give the implementing agency confidence that resources are being used optimally returning the maximum value for transportation dollars spent LADOTD supported by the Federal Highway Administration has requested the implementation of the Baton Rouge to New Orleans ITS Traffic Incident Management (TIM) Phase I project This project is 17 miles in length and the first of three (3) project phases to deploy ITS technologies along the Interstate 10 (I-10) corridor from Baton Rouge to New Orleans The goal of Phase I is to deploy an ITS system that will provide LADOTD and the Louisiana State Police (LSP) with traffic surveillance and management tools to more effectively facilitate traffic and incident management activities on I-10 across the Bonnet Carre Spillway and its designated alternative route US 61 (Airline Highway) ITS equipment will provide LADOTD and LSP with the ability to detect verify advise affected motorists respond manage traffic and clear traffic incidents within the project limits The project will result in improved mobility and safety for all motorists A unique aspect of this project is that the Design-Build (DB) contracting method will be used for the first time by LADOTD to implement a fully operational ITS project LADOTD has prepared a functional specification that will be used by the Design-Builder in order to develop their specific system design and build it There are a number of advantages for LADOTD using this contracting technique First it allows the design-builder the flexibility of implementing an ITS system with the most recently tested and effective technologies Second the overall responsibility for designing constructing testing and implementing the ITS system falls to the Design-Builder Third this process should reduce project implementation time Section 6 of this document contains the project requirements Both the Design-Builder and the stakeholders are required to implementfulfill these requirements The Design-Builder will be responsible for the requirements only contained in the contract documents The centers operating the ITS equipment will be the LADOTD ITS Statewide TMC in Baton Rouge the LADOTD District 02 (Bridge City) The LSP Troop B office in Kenner will only have monitoring capability LADOTD is currently constructing the New Orleans Transportation Management Center (RTMC) at the corner of West End Blvd and Veteranrsquos Blvd For the purposes of this analysis the RTMC has been included with the District 02 (Bridge City) office as the role of the ITS operator will be the same whether at the Bridge City site or the RTMC facility Figure 1 shows the project area and physical limits of the ITS project implementation along the I-10 corridor
SE Analysis September 2007 1
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
Figure 1 Project Area and Physical Limits
Project Area ndash Phase 1
Included within the projects limits of the Baton Rouge to New Orleans ITS TIM Phase I project
bull I-10 LA 3188 Belle Terre Blvd (Exit 206) to LA 49 Williams Blvd (Exit 223) bull US Highway 61 Airline Highway US 51 to I-310 bull I-310 I-10 (Exit 1) to US Highway 61 Airline Highway (Exit 2) bull US 51 I-10 to US Highway 61 Airline Highway and bull Traffic Management Centers LADOTD District 02 (Bridge City)RTMC LADOTD ITS
Statewide TMC and LSP Troop B
SE Analysis September 2007 2
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
2 Acronyms and Abbreviations Wherever the following abbreviations or acronyms are used in this SE document they are interpreted as follows AASHTO American Association of State Highway and Transportation Officials ADC Analog-to-Digital Conversion ADSL Asymmetric Digital Subscriber ARN Area Radio Network ATIS Advanced Traveler Information Systems ATMS Advanced Traffic Management System C2C Center-to-center C2F Center-to-field CAD Computer Aided Dispatch CCTV Closed Circuit TV CDMA Code Division Multiple Access CDPD Cellular Digital Packet Data CONOPS Concept of Operations DARC Data Radio Channel System DATEX-ASN Data Exchange ASN1 DB Design Build DCM Data Collection and Monitoring DMS Dynamic Message Sign E9-1-1 Enhanced 9-1-1 EDGE Enhanced Data for Global Evolution EM Emergency Management EMC Emergency Management Center EMS Emergency Medical Services EOC Emergency Operations Center FDM Frequency Division Multiplexing FCC Federal Communications Commission FHWA Federal Highway Administration FR Functional Requirement GHz Gigahertz GIS Geographic Information System GSM Global System for Mobile Communication IEEE Institute of Electrical and Electronic Engineers IM Incident Management ISO International Standards Organization ITE Institute of Transportation Engineers ITS Intelligent Transportation Systems Kbps Kilobits per Second LADOTD Louisiana Department of Transportation and Development LCS Lane Control Signals LONI Louisiana Optical Network Initiative LSP Louisiana State Police MHz Megahertz MPH Miles per Hour MPO Metropolitan Planning Organization
SE Analysis September 2007 3
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
NEC National Electric Code NEMA National Electrical Manufactures Association NTCIP National Communications for ITS Protocol NS Network Surveillance OampM Operations and Maintenance OER Octet Encoding Rules OFDM Orthogonal Frequency Division Multiplexing PAR Peak-to-Average Ratio PC Personal Computer PCS Personal Communications Services POTS Plain Old Telephone Service PR Performance Requirement RS Roadway Subsystem RTMC Regional Transportation Management Center (New Orleans) RVD Radar Vehicle Detector SCP Signal Control and Prioritization SDO Standard Development Organizations SE Systems Engineering SI Systeme Internacionale or International System of Units SNMP Simple Network Management Protocol STIC Sub carrier Traffic Information Channel System STMF Simple Transportation Management Framework STMP Simple Transportation Management Protocol SOSP Scope of Services Package SSC Surface Street Control TCPIP Transmission Control ProtocolInternet Protocol TD Traffic Detector TIS Traveler Information System TIM Traffic Incident Management TMC Traffic Management Center TMP Transportation Management Protocols TMS Traffic Management Subsystem TOC Traffic Operations Center TSS Transportation Sensor Systems US United States USDOT United States Department of Transportation WAN Wide Area Network WLAN Wireless Local Area Network 3 Systems Engineering Approach The Systems Engineering approach offers a structured way of thinking to achieve project goals and objectives This approach combines skills associated with engineering project management and soft sciences (economic social and legal) It helps to address all project issues and provide completeness to the system Systems Engineering also provides for ldquotraceabilityrdquo which is important when considering future changes to the system design operation verification and testing Traceability is the capacity to track every requirement in the system to the system component that satisfies it Through the Systems Engineering approach a traceability matrix is deployed This matrix provides the basis for construction testing and acceptance by the Project
SE Analysis September 2007 4
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
Engineer as well as the link between completion of individual pay items and implementation of the basic purpose and scope of the project Figure 2 the ldquoVrdquo Diagram or Model1 is a visual illustration of the Systems Engineering process used for ITS with each step involved as the project progresses through development
Figure 2 ldquoVrdquo Diagram Illustrating Systems Engineering Process
The left side of the ldquoVrdquo Diagram provides a lsquotop-downrsquo approach for system planning and design development while the right side provides lsquobottom-uprsquo implementation approach for systems testing and verification The left side of the ldquoVrdquo must take into account the corresponding processes across on the right side of the ldquoVrdquo The ldquoVrdquo diagram is a composition of three different perspectives namely userrsquos perspective engineerrsquos perspective and contractorrsquos perspective The Stakeholderrsquos (userrsquos) perspective helps to present the list of requirements These requirements provide detailed definitions need to support system design The perspective of a systems engineer is focused on detailed subsystem components design to achieve stated requirements The perspective of a contractor is focused on the actual deployment of the system components which ensures compliance with the design specifications 4 Project Physical Architecture It is essential that a project physical architecture be developed to illustrate the important ITS interfaces and the major system components The physical architecture assigns processes from the logical architecture to subsystems and it groups data flows from the logical architecture into architecture flows These flows and corresponding communication requirements define the
1 Source Systems Engineering ITS Guide FHWA 2005 httpopsfhwadotgovpublicationsseitsguideimagesimage021jpg
SE Analysis September 2007 5
SE Analysis September 2007 6
interfaces which are a main focus of the project ITS standards The subsystems identified for this project are the following
bull LADOTD ITS Statewide TMC Operator bull LADOTD District 02 (Bridge City)RTMC ITS Operator bull LSP Troop B Dispatch Operator bull DMSs bull TDs and bull CCTVs
Figure 3 illustrates the project physical architecture under consideration It depicts the overall understanding of the physical architecture components associated with the project
Figure 3 Project Physical Architecture
LADOTD Dist 02LADOTD Dist 02 (Bridge City) New Orleans Regional Transportation
Management ITS Operator
LADOTD ITS DivisionLADOTD ITS Statewide TMC Operator
Louisiana State PoliceLSP Troop B Dispatch Operator
LADOTD Dist 02TDs
LADOTD Dist 02CCTVs
LADOTD Dist 02DMSs
traffic operator data
alert notificationtraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestroad network conditions
traffic information coordinationemergency routes
emergency traffic control informationroad network conditions
alert notificationemergency route request
emergency traffic control requesttraffic control coordination
alert notification coordinationalert status
emergency plan coordinationevacuation coordination
incident command information coordinationincident report
incident response coordinationincident response status
resource coordinationresource deployment status
resource requestalert status
emergency routesemergency traffic control information
road network conditionsemergency route request
emergency traffic control requestalert notification
alert notification coordinationemergency plan coordination
evacuation coordinationincident command information coordination
incident reportincident response coordination
incident response statusresource coordination
resource deployment statusresource request
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
data collection and monitoring controltraffic sensor control
roadside archive datatraffic flow
video surveillance controltraffic images
video surveillance controltraffic images
traffic images
roadway information system dataroadway information system status
roadway information system data
roadway information system status
SE Analysis September 2007 7
Planned
5 Concept of Operations Concept of Operations (ConOps) describes how the proposed system will function the environment in which it will operate and the people who will use and support the system ConOps identifies the stakeholders involved in the project and their responsibilities It also describes the roles and responsibilities for operations and maintenance of the various system users The ConOps is a non-technical discussion of the ITS system that should be understood by everyone involved in the project The ConOps presents a view of the operational system once the project is completed the intended benefits of the system and the impact the region in which it is deployed This ConOps is a general description of how the Baton Rouge to New Orleans ITS TIM Phase I will function and the operational responsibilities of each agency involved The system which cannot be used to transfer liability related to operating specific facilities identifies operational roles to each agency 51 Purpose The purpose of the Baton Rouge to New Orleans ITS TIM Phase I project is to reduce the negative impacts of traffic congestion and incidents along I-10 between LA 3188 (Belle Terre Blvd Exit 206) to LA 49 (Williams Blvd Exit 223) Also this project will enhance traffic operations and multi-agency coordination for normal and abnormal traffic conditions evacuation operations and further enhance the response to and command of incidents for EM and TIM purposes With the accomplishment of the system objectives the system is able
bull To detect verify and assess traffic congestion and incidents bull To distribute information to motorists in a timely manner bull To provide system monitoring and coordinated operations between the LADOTD ITS
Statewide TMC LADOTD District 02 (Bridge City)RTMC and the LSP Troop B office and
bull Allow for a more reliable power source for existing I-10 ndash 12 mile bridge (between LaPlace and Kenner) emergency cross-overs
52 Scope The Baton Rouge to New Orleans ITS TIM Phase I project provides for the interaction of six (6) primary subsystems as previously identified in the Project Physical Architecture The implementation of this project will provide capabilities to address improvements to the overall operations of traffic provide information to motorists and enhance coordination of agencies involved in transportation and incident management The scope of this project includes the deployment of the ITS equipment components communications and integration as previously identified to assist the responsible stakeholders in providing services requiring the indicated architecture flow
SE Analysis September 2007 8
53 Justification for the ITS Project I-10 is the major east-west controlled access freeway facility connecting major population centers across southern Louisiana It is a major transportation route that enhances commerce and economic development not only within the state of Louisiana but also other states along the Gulf Coast During emergencies it also serves as a major hurricane evacuation route for all of southern Louisiana The Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project is located along the I-10 Freeway corridor between Baton Rouge and New Orleans The importance of this project has significantly increased with the event of Hurricane Katrina in 2005 This hurricane inundated parts of the greater New Orleans area causing massive flooding destroying thousands of homes and business and severely impacting the Statersquos economy The hurricane caused a massive evacuation and relocation of Louisiana citizens working in the Greater New Orleans area With the destruction of so much residential housing the affected population relocated to other areas in the state specifically the River Parishes along the I-10 corridor identified herein The relocation of these people caused an increase travel demand into and out of the greater New Orleans area on a daily basis Since Hurricane Katrina daily traffic volumes for I-10 within the project area has increased 29 percent from 42000 to 53000 vehicles per day (as seen in August and December 2005 respectfully) The increase in daily traffic volume resulted in more congestion traffic incidents and lost mobility 54 Existing Operations Existing operations of the ITS equipment within the project limits are as identified in the following sections based on the operational role the equipment helps facilitate (ie TrafficRoadway Management Incident Management and Emergency Management) Figure 4a and Figure 4b show the existing ITS equipment within the project limits
SE Analysis September 2007 9
Figure 4a Existing LADOTD ITS Equipment Within Project Limits
Figure 4b Existing LADOTD ITS Equipment Within Project Limits
SE Analysis September 2007 10
541 TrafficRoadway Management LADOTD District 02 (Bridge City)RTMC and District 62 currently operate and maintain eleven (11) traffic signalized intersections (7 and 4 respectfully) in the project limits along US 51 and US 61 None of the existing traffic signals have remote communications with the District 02 or District 62 offices All timing changes are performed by District 02 or District 62 personnel in the field Currently there are two (2) DMS boards within the project limits operated by the District 02 Traffic Engineerrsquos office These DMSs use fiber optic hybrid flip disk technology to display a message This technology is no longer being manufactured and it limited in support The first location is on I-10 east of the I-310 interchange within the City of Kenner which provides information to motorists traveling west on I-10 The second location is on I-10 west of US 51 located in the City of LaPlace which provides information to motorists traveling west on US 61 and north on US 51 LADOTD personnel can communicate with the DMS boards via POTS lines using dial-up modems In addition to the DMS there is one CCTV site at US 51 that is used for roadway surveillance The 11 RVD sites and dynamic speed limit signs are currently not operational LADOTDrsquos current communication infrastructure uses fiber optic cable and microwave technology Within the project limits LADOTD currently has eight fibers (four are currently in use and four are non-active) installed in a duct bank coming from the north along I-55 to I-10 Then it continues running south along US 51 then turning east at US 61 This duct continues just east of the airport where it turns north along the Airport Access Rd till it reaches Veteran Blvd From Veteranrsquos Blvd it runs east to Illinois Ave (east of Williams Blvd) then north until it reaches I-10 From there it turns east towards New Orleans LADOTD maintains three microwave towers in the New Orleans area One located at the LaPlace scale facility one at the RTMC site and the other at the District 02 facility Additionally the LSP Troop B located in Kenner has an existing microwave tower Figure 5 shows the existing communication infrastructure LADOTD has ITS Operators monitoring traffic operations at the ITS Statewide TMC The staff consists of one Statewide Operation Supervisor and two full-time ITS Operators The LADOTD ITS Statewide TMC center is staffed from 600 AM to 1000 PM Monday through Friday LADOTD District 02 (Bridge City)RTMC will be staffed seven days a week from 530 AM until 1000 PM by two full time operators two part time operators and one full time supervisor
SE Analysis September 2007 11
Figure 5 Existing Communication Infrastructure
SE Analysis September 2007 12
LaP
lace
Sca
les
Dis
trict
Offi
ce
DO
TD A
cces
s -M
anho
le w
ith S
ervi
ce L
oop
Qw
est R
esou
rce
Sha
re F
iber
and
Con
duit
DO
TD fi
ber
Lege
nd
Loca
l ATM
EO
C
DO
TD R
egen
Site
Join
t Qw
estD
OTD
Reg
en S
ite
Qw
est R
egen
Site
-D
OTD
has
acc
ess
Sec
tion
45
12
6110
190
51
190
55
10
90
61
10
Old
Tro
op B
Mic
row
ave
Brid
ge C
ity
Dis
trict
02
1440
Hw
y 90
WIn
terim
New
Orle
ans
TMC
Site
Dis
trict
61
8100
Airl
ine
Hw
y
Bat
on R
ouge
AT
ME
OC
3773
Har
ding
Blv
d
Dis
trict
07
5827
Hw
y 90
E
Roa
noke
Dis
trict
62
685
N M
orris
on B
lvd
Sco
tt(L
afay
ette
)
Lake
Cha
rles
Lafa
yette
Dis
trict
03
428
Hug
h W
allis
Rd
415
397
Ham
mon
d
Pon
chat
oula
P
atch
cor
ds b
etw
een
in a
nd
out
pan
els
used
to p
ass
DO
TD s
trand
s th
roug
h fa
cilit
y
Futu
re T
MC
Site
Gra
nt S
treet
Vin
ton
DO
TD F
iber
Con
tinue
s W
I-10
past
Prop
erty in
side
Tex
as
and
Con
duit
est A
long
V
isito
r Cen
ter
to
1stR
egen
Site
51
51
110
24 S
trand
s(8
Fre
e)
24 S
trand
sC
urre
ntly
in u
se
Run
in re
sour
ce s
hare
con
duit
SC
pat
ch p
anel
at Q
wes
t Reg
enST
pat
ch p
anel
at A
TME
OC
24 S
trand
s
No
fiber
con
nect
ion
to D
istri
ct 0
2
Con
nect
ivity
to b
e pr
ovid
ed v
ia O
C-3
m
icro
wav
e lin
k to
O
ld T
roop
B
DO
TD fi
ber e
nds
at 6
50 P
oydr
as S
t
Futu
reN
ew O
rlean
sTM
C S
iteM
etai
rie
I-10
610
Inte
rcha
nge
10
55
Sou
th o
f Pon
chat
oula
fib
er is
laid
alo
ng w
est
shou
lder
of U
S 51
whi
ch
para
llels
ele
vate
d I-5
5
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
07
8 Ea
st 8
Wes
t
Splic
e in
to a
ll 8
stra
nds
to e
xten
d fib
er
thro
ugh
Dis
trict
62
8 Ea
st 8
Wes
t
Spl
ice
into
all
8 st
rand
s to
ext
end
fiber
thro
ugh
LaPl
ace
Scal
e H
ouse
8
Eas
t 8
Wes
t
Qw
est c
ondu
its o
n I-1
0 ru
n al
ong
sout
h sh
ould
er o
f EB
lane
sS
hortl
y be
fore
reac
hing
US
51
cond
uit v
eers
off
US
190
and
runs
alo
ng C
hurc
h St
to
US
51
N S
EW
1201
Cap
itol A
cces
s R
d
DO
TD
HQ
Betw
een
Sco
tt an
d B
aton
Rou
ge
the
4 da
rk s
trand
s ar
e re
serv
ed to
im
plem
ent n
orth
ern
SON
ET ri
ngut
ilizin
g fu
ture
I-49
fibe
r
Fibe
r goe
s so
uth
to U
S 6
1 to
avo
id
I-10
Lake
Pon
char
train
cau
sew
ay
Fibe
r run
s no
rthto
I-10
eas
t of
the
Airp
ort
New
Orle
ans
Inte
rnat
iona
lA
irpor
t
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
07
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Dis
trict
62
All 2
4 st
rand
s te
rmin
ated
in p
atch
pan
el w
ith S
C
conn
ecto
rs a
t Sca
le H
ouse
4 lit
4 re
serv
ed4
lit 4
dar
k
4 lit
4 d
ark
4 to
be
lit 4
dar
k
8 da
rk
Fibe
r M
ap -
Qw
est R
esou
rce
Shar
e Fi
ber
Alo
ng I-
10 C
orri
dor
8 da
rk
8 St
rand
s and
1 C
ondu
it (N
on-M
ultid
ucte
d)4
Stra
nds C
urre
ntly
Lit
Bet
wee
n L
ake
Cha
rles
and
LaP
lace
(as o
f Feb
ruar
y 20
04)
No
curr
ent f
iber
co
nnec
tion
to D
istri
ct 0
3
DS
-3 w
irele
ss li
nk
betw
een
Amba
ssad
or
Caf
fery
and
Dis
trict
03
to
be c
ompl
ete
2Q04
24 S
trand
s16
Dar
k
k)24
Stra
nds
(20
Dar
Butte
LaR
ose
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 St
rand
s co
ntin
ue th
roug
h A
TME
OC
to
DO
TD H
Q
Patc
h pa
nel w
ith S
C c
onne
ctor
s4
Stra
nds
in u
se to
con
nect
ATM
EO
C
8 S
trand
s co
ntin
ue th
roug
h AT
ME
OC
to
DO
TD D
istri
ct 6
1
24 S
trand
s
2 X
24
Stra
nds
All
48 s
trand
s te
rmin
ated
in p
atch
pan
el w
ith S
C c
onne
ctor
s
4 St
rand
s lit
to L
aPla
ce
Amba
ssad
or C
affe
ry
542 Incident Management LADOTD ITS Statewide TMC and District 02 operators provide incident detection and coordination where surveillance is available in the region On the 12 mile bridge there are two ldquocross-overrdquo locations with barrier gates for access control The cross-overs are 50 feet wide by 130 feet long areas of refuge that can be accessed by means of electronic card readers on both right hand shoulders across from each cross-over The cross-overs are used by emergency managers as helipads storage for inoperable vehicles emergency vehicle marshalling and access to the opposite direction of travel Currently the gates are powered by a solar power system Access to the cross-overs requires emergency vehicles to negotiate across high volume high speed lanes of traffic to utilize the cross-over 543 Emergency Management The EOC facilities include the LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP are responsible for coordinating the emergency management operations for events such as hurricanes fuel and chemical spills from trucks and tankers chemical discharges from plants and radiological discharges from the nearby nuclear power plant There are several independent emergency operation centers tasked with responding to the above mentioned emergency situations The ITS equipment available for trafficroadway management and incident management is used for emergency management as needed
55 System Overview The Baton Rouge to New Orleans ITS TIM Phase I ITS proposed architecture is based on a distributive system design with a centralized TMC computer server located at the LADOTD ITS Statewide TMC in Baton Rouge The system shall bring all data and video communication together on one backbone network making all data and video available to any system that also has access to the same backbone network Using standard network communications can provide a common format for all emergency management dispatchers and operations personnel to effectively coordinate operations Table 1 shows the agencies that are to be connected to the fiber backbone Table 2 identifies the agencies responsible for operating and maintaining elements of the various systems affected by this project It should be noted that this project will not provide architectural flows with some centers listed in Table 2 However these have been included to indicate their relationship with the project being implemented
SE Analysis September 2007 13
Table 1 Agencies to be Connected to Backbone
Center Address LADOTD ITS Statewide TMC 1201 Capitol Access Road Baton Rouge LA LADOTD District 02 1440 US Highway 90 Bridge City LA RTMC (Future) New Orleans LA
Table 2 Agency Responsibility
System Agency Traffic Management System2 Development LADOTD ITS Statewide TMC Traffic Management System2 Operations LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSP St Charles and St John the Baptist Parishes E-911s
Traffic Management System2 Maintenance LADOTD ITS Statewide TMC Incident Management Development LADOTD ITS Statewide TMC St Charles
and St John the Baptist Parishes E-911s Incident ManagementIncident Operation LADOTD ITS Statewide TMCLADOTD
District 02 (Bridge City)RTMC LSPSt Charles and St John the Baptist Parishes 911s and EOCs
Incident Management System2 Maintenance LADOTD ITS Statewide TMC St Charles Parish and St Johns the Baptist Parishes E-911s
Emergency Management System2 Development LADOTD Emergency Operations Section LSPSt Charles and St Johnrsquos Parishes 911s and EOCs
Emergency Management System2 Operation LADOTD Emergency Operations SectionLSPSt Charles and St John the Baptist Parishes 911s and EOCs
Emergency Management System2 Maintenance LADOTD ITS Statewide TMCLSPSt Charles and St John the Baptist Parishes 911s and EOCs
A distributed traffic incident and emergency management system requires a highly reliable and robust communications network As previously stated a fiber optic communications backbone along I-55 US 51 US 61 and I-10 is available to supplement the communication needs for the project limits Table 3 shows agency accessibility to the communications network
2 Traffic Management Incident Management and Emergency Management Systems are made up of various physical systems as well process and procedures These may include systems such as the ITS system deployed 511 911 CAD 700800MHz radio etc
SE Analysis September 2007 14
Table 3 Agency Accessibility
Agency ITS Access LADOTD Headquarters Annex (ITS Statewide EOC) NS TIS IM LADOTD District 02 (Bridge City)RTMC SSC NS TIS IM Louisiana State Police Troop B NSTIS IM
SSC-Surface Street Control NS-Network Surveillance TIS-Traveler Information System and IM-Incident Management
It is anticipated that stakeholders will continue to provide oversight and direction for this project as it is designed and implemented For further information regarding stakeholders please refer to section 56 The following section outlines the proposed operations of the agencies with regard to the deployment of this project Operations and maintenance outside of this section are anticipated to remain as currently performed 551 ITS Equipment Operations The operations of the ITS Equipment are provided through the existing traffic management software Cameleon ITS Interface with the Cameleon will be constrained or prioritized for those agencies Primary control of all devices will be held by LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC will have secondary control 552 Center-to-Center Operations Implementation of a communication backbone between centers permits direct center-to-center communication and allows multiple agencies to access the ITS equipment This connection will allow for the transfer of data and images This will result in a more effective and efficient use of resources The intent of this connection is to better facilitate coordination between the agencies involved in Traffic Management Incident Management and Emergency Management 56 Stakeholders As can be seen from Table 3 the resulting envisioned system may involve the interaction of numerous individual agencies located within the region It is anticipated that project deployment will provide the tools that will allow these stakeholders to facilitate their traffic and transportation management roles Currently no written agreements have been developed on the interaction of the agencies involved in Traffic Management Incident Management and Emergency Management All agencies have representatives known as stakeholders The operations and utilization of the system by the agencies shall be as directed and agreed upon in the Memorandum of Understanding developed for this project
SE Analysis September 2007 15
57 Operational Environment The operational environment for the Baton Rouge to New Orleans ITS Traffic Incident Management Phase I project includes a description of operational procedures skills and experience of personnel security issues and processes communications data management and ownership The project has a distributed architecture as mentioned before that does not require permanent co-location of agency operations staff 58 Operational Scenarios The Operational Scenarios describes a sequence of events and activities that are carried out by the user system and environment Operational Scenarios identify what event or action initiates the sequence who or what performs each step when communications occur and to whom or what For this project each function consists of a process used to respond to traffic incidents and access ITS equipment components 581 Traffic Incident Management Operations (TIM) TIM operations within the project limit area are generally a multi-staged approach Figure 6 summarizes the primary process for traffic incident management operation Since LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC are connected to the communications backbone benefits of the system will be gained In the occurrence of an incident if the given location is near a CCTV camera the operator will have the ability to detect and verify the incident without having to visit the field LSP operators can monitor CCTV cameras in the system through its remote virtual private network (VPN) connection with LADOTDrsquos network CCTV cameras that are located along the 12 mile bridge on I-10 east and west are used for incident detection and vehicle detection This also applies for alternate routes on US 61 US 51 and I-310 However cameras at alternate routes are located at major signalized intersections The ITS operators at LADOTD ITS Statewide TMC and LADOTD District 02 (Bridge City)RTMC will have the ability to post messages on DMS boards DMS boards shall be located at decision points which are defined as points where motorists can make a decision whether or not to take an alternate route or remain on the bridge Alternate routing will be provided in the occurrence of an incident andor emergency The ITS operators at LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP will have the ability to use traffic detectors (TDs) for their operations Traffic detectors will be located along the 12 mile bridge These detectors along with other existing detectors outside of the project will be used to determine travel times gather traffic data and detect traffic incidents LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC and LSP shall have the ability to view data from the TDs via compiled reports and the graphical user interface that is part of the existing traffic management software Data gathered from the TDs shall be collected at the LADOTD ITS Statewide TMC and accessed by LADOTD District 02 (Bridge City)RTMC and LSP
SE Analysis September 2007 16
A future ITS deployment may consist of Lane Control Signals (LCS) along the 12 mile bridge These special overhead signals will permit or prohibit the use of a specific travel lane(s) The future implementation will allow the 12 mile bridge to have three operational lanes of traffic The third lane is anticipated to be used during peak hours and emergencies only The specific operations and implementation of the LCS shall be determined by LADOTD prior to its implementation
Figure 6 Concept of Operations Functions ndash Traffic Incident Management
Fiber Wireless
Fiber Wireless
FiberWireless
582 Emergency Management Operations During emergency situations automated messages being posted to DMS will be discontinued and the ITS operator will post emergency specific messages on DMSs For smaller emergencies the LADOTD District 02 (Bridge City) RTMC ITS Operator will operate the system from the District 02 officeRTMC For regional based emergencies (ie hurricane evacuation) the LADOTD ITS Statewide TMC will assume control and operate the CCTVs TDs and DMS boards 59 Summary of Impacts Table 4 shows the project impacts of deployment resulting from this study document for each agency below This table includes the local agency connections regional to statewide connections and the connections that will be established as a part of this project It should be noted that additional operations and maintenance will vary for each agency based on the level of use chosen If connections are made to the local and statewide backbone the regional ITS architecture will need to be updated to show the connection
SE Analysis September 2007 17
Table 4 Summary of Impacts
Center Impact
Connected Centers
Access to other centers on local and
statewide backbone
Network surveillance
(Monitor CCTV
cameras)
Network surveillance
(Control CCTV
cameras)
Post messages to DMS
Monitor Traffic
Detectors LADOTD ITS Statewide TMC LADOTD District 02 (Bridge City)RTMC Louisiana State Police Troop B
6 Requirements Requirements provide a foundation of information needed to move from the conceptual view presented in the ConOps to the concrete view which defines what must be done and included in the project design These requirements form the basis for design implementation testing and operations 61 Traffic ManagementTraffic Incident Management Traffic Incident Management monitors and controls traffic in case of an incident (please refer to the ConOps for further details and definitions) LADOTD ITS Statewide TMC (ITS Division) and the LADOTD District 02 (Bridge City)RTMC serve as traffic management centers that exchange incident management information To facilitate efficient flow of information all requirements have been identified as being either performance (PR) or functional (FR)
FR1 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR11 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for traffic management purposes
FR111 LADOTD District 02 (Bridge City)RTMC shall provide traffic conditions to the LADOTD ITS Statewide TMC Operator
FR112 LADOTD District 02 (Bridge City)RTMC shall provide operating status of field equipment to the LADOTD ITS Statewide TMC Operator
FR113 LADOTD District 02 (Bridge City)RTMC shall provide maintenance activity status to the LADOTD ITS Statewide TMC Operator
FR114 LADOTD District 02 (Bridge City)RTMC shall provide incident status to the LADOTD ITS Statewide TMC Operator
SE Analysis September 2007 18
FR12 LADOTD District 02 (Bridge City)RTMC shall coordinate traffic information with LADOTD ITS Statewide TMC for traffic management purposes
FR121 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with incident information
FR13 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for traffic management purposes
FR131 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with current traffic information
FR132 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with forecasted traffic information
FR133 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR134 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR135 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information
FR14 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR141 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR142 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident
FR15 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR151 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR1511 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR1512 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR1513 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR1514 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
SE Analysis September 2007 19
FR152 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR1521 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR1522 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR1523 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR1524 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR16 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR161 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of the incident status
FR1612 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR1615 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
FR17 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR171 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR172 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR173 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR174 LADOTD District 02 (Bridge City)RTMC shall coordinate recovery plans with LADOTD ITS Statewide TMC
SE Analysis September 2007 20
FR175 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuation plans with LADOTD ITS Statewide TMC
FR18 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for traffic management purposes
FR181 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
FR182 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems used to provide the alert
FR2 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR21 LADOTD ITS Statewide TMC shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR211 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR212 LADOTD ITS Statewide TMC shall provide to LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR22 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR221 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR2211 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR22111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
SE Analysis September 2007 21
FR2212 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR22121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2213 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR22131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR22133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR2214 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR22141 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR22142 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 22
FR22143 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR22144 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR3 LADOTD District 02 (Bridge City)RTMC shall communicate with LSP Troop B Dispatch Operator
FR31 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for traffic incident management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures
FR312 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident
FR32 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for traffic incident management purposes
FR321 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR3211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an incident
FR3212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an incident
FR3213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an incident
FR3214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an incident
FR322 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR3221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for use in the occurrence of an incident
FR3222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for use in the occurrence of an incident
FR3223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for use in the occurrence of an incident
FR3224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for use in the occurrence of an incident
FR33 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for traffic incident management purposes
SE Analysis September 2007 23
FR331 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR3311 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR3312 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR3313 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR3314 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
FR3315 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR34 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for traffic management purposes
FR341 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR342 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR343 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR344 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans
FR345 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP evacuation plans
FR35 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for traffic management purposes
FR351 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR3511 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR36 LADOTD District 02 (Bridge City)RTMC shall provide road network conditions with LSP for traffic management purposes
FR361 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD LSP with current traffic information
FR362 LADOTD District 02 (Bridge City)RTMC shall provide LSP with forecasted traffic information
FR363 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
SE Analysis September 2007 24
FR364 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR365 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information
FR37 LADOTD District 02 (Bridge City)RTMC (Bridge City)RTMC shall provide emergency traffic control information to LSP for traffic management purposes
FR371 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR372 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR373 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR38 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for traffic management purposes
FR381 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR382 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR383 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR384 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR385 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR386 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR4 Louisiana State Police Troop B (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR41 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR411 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR4111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR41111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
SE Analysis September 2007 25
FR41112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR41121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR41131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR41133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR4114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR41141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR41142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
SE Analysis September 2007 26
FR41143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR41144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instructions on how to respond to the alert
FR42 LSP shall request an emergency route from District 02 in the occurrence of an emergency for traffic management purposes
FR421 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR422 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
FR423 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR424 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR43 LSP shall request emergency traffic control from District 02 for traffic management purposes
FR431 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR432 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR44 LSP shall coordinate traffic control with LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR441 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable remote monitoring of traffic management devices
FR442 LSP shall provide to the LADOTD District 02 (Bridge City)RTMC information transfers that enable control of traffic management devices
FR5 LSP shall communicate with LADOTD ITS Statewide TMC
FR51 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for traffic management purposes
FR511 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR5111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR51111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
SE Analysis September 2007 27
FR51112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR51121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR51131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR51132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR51133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR51134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR5114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR5115 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR5116 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR5117 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
SE Analysis September 2007 28
FR5118 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instructions on how to respond to the alert
FR52 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR521 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures
FR522 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident
FR53 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR531 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR5311 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an incident
FR5312 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an incident
FR5313 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an incident
FR5314 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an incident
FR532 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR5321 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in the occurrence of an incident
FR5322 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an incident
FR5323 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an incident
FR5324 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an incident
FR54 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for traffic incident management purposes
FR541 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR5411 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
FR5412 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
SE Analysis September 2007 29
FR5413 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR5414 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR5415 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR55 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for traffic management purposes
FR551 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR552 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR553 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR554 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans
FR555 LSP shall coordinate with LADOTD ITS Statewide TMC evacuation plans
FR56 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency for traffic management purposes
FR561 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR562 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR563 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR564 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR57 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for traffic management purposes
FR571 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR572 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR6 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR61 LADOTD ITS Statewide TMC shall provide an alert status to LSP for traffic management purposes
FR611 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
SE Analysis September 2007 30
FR6111 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR62 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for traffic management purposes
FR621 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR622 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR623 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information
FR63 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for traffic management purposes
FR631 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR632 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR633 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR64 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for traffic management purposes
FR641 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR642 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR643 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR644 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR645 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR646 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR7 TDs shall communicate with LADOTD ITS Statewide TMC
FR71 TDs shall provide traffic flow information to LADOTD ITS Statewide TMC
FR711 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR712 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR72 TDs shall provide roadside archive data to LADOTD ITS Statewide TMC
SE Analysis September 2007 31
FR721 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR722 TDs shall provide environmental conditions derived from roadside sensors to LADOTD ITS Statewide TMC
FR8 LADOTD ITS Statewide TMC shall communicate with TDs
FR81 LADOTD ITS Statewide TMC shall provide traffic sensor control information to TDs
FR811 LADOTD ITS Statewide TMC shall provide information used to configure traffic sensor systems
FR812 LADOTD ITS Statewide TMC shall provide shall provide information used to control traffic sensor systems
FR82 LADOTD ITS Statewide TMC shall control data collection and monitoring to TDs
FR821 LADOTD ITS Statewide TMC shall provide to TDs information used to configure data collection
FR822 LADOTD ITS Statewide TMC shall provide to TDs information used to control data collection
FR823 LADOTD ITS Statewide TMC shall provide to TDs information used to configure monitoring systems
FR824 LADOTD ITS Statewide TMC shall provide to TDs information used to control monitoring systems
FR9 LADOTD ITS Statewide TMC shall communicate with CCTVs
FR91 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs
FR10 CCTVs shall communicate with LADOTD ITS Statewide TMC
FR101 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR11 LADOTD ITS Statewide TMC shall communicate with DMSs
FR111 LADOTD ITS Statewide TMC shall provide roadway information system data to DMSs for traffic management purposes
FR1111 LADOTD ITS Statewide TMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1112 LADOTD ITS Statewide TMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1113 LADOTD ITS Statewide TMC shall provide information to DMSs used to control roadside systems that provide driver information
FR12 LADOTD District 02 (Bridge City)RTMC shall communicate with DMSs
FR121 LADOTD District 02 (Bridge City)RTMC shall provide roadway information system data to DMSs for traffic management purposes
SE Analysis September 2007 32
FR1211 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to initialize roadside systems that provide driver information
FR1212 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to configure roadside systems that provide driver information
FR1213 LADOTD District 02 (Bridge City)RTMC shall provide information to DMSs used to control roadside systems that provide driver information
FR13 DMSs shall communicate with LADOTD ITS Statewide TMC
FR131 DMSs shall provide status of the roadway information system to LADOTD ITS Statewide TMC for traffic management purposes
FR1311 DMSs shall provide information to LADOTD ITS Statewide TMC indicating the current operating status of the dynamic message signs
FR14 DMSs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR141 DMSs shall provide status of the roadway information system to LADOTD District 02 (Bridge City)RTMC for traffic management purposes
FR1411 DMSs shall provide information to LADOTD District 02 (Bridge City)RTMC indicating the current operating status of the dynamic message signs
FR15 TDs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR151 TDs shall provide traffic flow information to LADOTD District 02 (Bridge City)RTMC
FR1511 TDs shall provide raw traffic detector data which allows the derivation of traffic flow variables
FR1512 TDs shall provide processed traffic detector data which allows the derivation of traffic flow variables
FR152 TDs shall provide roadside archive data to LADOTD District 02 (Bridge City)RTMC
FR1521 TDs shall provide current traffic conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR1522 TDs shall provide environmental conditions derived from roadside sensors to LADOTD District 02 (Bridge City)RTMC
FR16 LADOTD District 02 (Bridge City)RTMC shall communicate with TDs
FR161 LADOTD District 02 (Bridge City)RTMC shall control data collection and monitoring to TDs
FR1611 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure data collection
FR1612 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control data collection
SE Analysis September 2007 33
FR1613 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to configure monitoring systems
FR1614 LADOTD District 02 (Bridge City)RTMC shall provide to TDs information used to control monitoring systems
FR162 LADOTD District 02 (Bridge City)RTMC shall provide traffic sensor control information to TDs
FR1621 LADOTD District 02 (Bridge City)RTMC shall provide information used to configure traffic sensor systems
FR1622 LADOTD District 02 (Bridge City)RTMC shall provide shall provide information used to control traffic sensor systems
FR17 LADOTD District 02 (Bridge City)RTMC shall communicate with CCTVs
FR171 LADOTD District 02 (Bridge City)RTMC shall control video surveillance of CCTVs
FR18 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC
FR181 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR19 CCTVs shall communicate with LSP Troop B
FR191 LSP Troop B shall receive traffic images supplied by CCTVs
FR20 LADOTD ITS Statewide TMC shall develop operation guidelines prior to project development
FR201 LADOTD District 02 (Bridge City)RTMC shall have control of LCS operations
FR2011 The bottom of the signal housing of any lane control signal face shall be at least 46m (15 ft) but no more than 58m (19 ft) above the pavement grade
FR2012 LCS faces shall be located over each controlled lane at frequent intervals if the area to be controlled is more than 700 m (2300 ft) in length or if the vertical or horizontal alignment is curved
PR1 The color of LCS indications shall be clearly visible for 700 m (2300 ft) at all times under normal atmospheric conditions unless otherwise physically obstructed
SE Analysis September 2007 34
62 Emergency Management System The Emergency Management represents public safety and other allied agency systems that support incident management disaster response and evacuation security monitoring and other security and public safety-oriented ITS applications This system does not operate from a specific center rather all of the emergency response centers that are connected to the fiber backbone communicate in order to make efficient decisions and allow operability within different organizations
FR21 System shall provide access of high speed communication transmission for emergency coordination between connected agencies
FR22 LADOTD District 02 (Bridge City)RTMC shall communicate with LADOTD ITS Statewide TMC
FR221 LADOTD District 02 (Bridge City)RTMC shall exchange traffic operator data with LADOTD ITS Statewide TMC for emergency management purposes
FR222 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LADOTD ITS Statewide TMC for emergency management purposes
FR2221 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with road conditions
FR2222 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with weather conditions
FR2223 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with traffic incident information for emergency management purposes
FR223 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2231 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2232 LADOTD District 02 (Bridge City)RTMC shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
FR224 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2241 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR22411 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 35
FR22412 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR22413 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR22414 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2242 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR22421 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR22422 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR22423 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR22424 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR225 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LADOTD ITS Statewide TMC for emergency management purposes
FR2251 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2252 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2253 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2254 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR2255 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the responses that service requests
FR226 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2261 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC an identified incident
SE Analysis September 2007 36
FR2262 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident location
FR2263 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident type
FR2264 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident severity
FR2265 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR227 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2271 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR22711 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC a summary of incident status
FR22712 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22713 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR22714 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC current response activities
FR22715 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC planned response activities
FR228 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2281 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR22811 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC a summary of incident status
FR22812 LADOTD District 02 (Bridge City)RTMC shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR22813 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR22814 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC current response activities
FR22815 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC planned response activities
SE Analysis September 2007 37
FR229 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2291 LADOTD District 02 (Bridge City)RTMC shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR22911 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC resource deployment status
FR22912 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC traffic conditions
FR22913 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC road conditions
FR22914 LADOTD District 02 (Bridge City)RTMC shall report to LADOTD ITS Statewide TMC weather conditions
FR22915 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with evacuation advice
FR22916 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR22917 LADOTD District 02 (Bridge City)RTMC shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2210 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR22101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR221011 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
FR221012 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221013 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221014 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221015 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR22102 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR221021 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation zones
SE Analysis September 2007 38
FR221022 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation times
FR221023 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of evacuation routes
FR221024 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR221025 LADOTD District 02 (Bridge City)RTMC shall inform LADOTD ITS Statewide TMC of reentry times
FR2211 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR22111 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR22112 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR22113 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency response plans
FR22114 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2212 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR22121 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR221211 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR221212 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR221213 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR221214 LADOTD District 02 (Bridge City)RTMC shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR2213 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LADOTD ITS Statewide TMC for emergency management purposes
FR22131 LADOTD District 02 (Bridge City)RTMC shall provide information to LADOTD ITS Statewide TMC indicating the current status of the emergency alert
SE Analysis September 2007 39
FR22132 LADOTD District 02 (Bridge City)RTMC shall identify to LADOTD ITS Statewide TMC the driver information systems that are being used to provide the alert
FR23 LADOTD ITS Statewide TMC shall communicate with LADOTD District 02 (Bridge City)RTMC
FR231 LADOTD ITS Statewide TMC shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2311 LADOTD ITS Statewide TMC shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR23111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR231111 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231114 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR23112 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
FR231121 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231122 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231123 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231124 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 40
FR23113 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR231131 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR231132 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR231133 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR231134 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR232 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR2321 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR2322 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR2323 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR2324 LADOTD ITS Statewide TMC shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR24 LADOTD District 02 (Bridge City)RTMC shall communicate with Louisiana State Police (LSP)
FR241 LADOTD District 02 (Bridge City)RTMC shall exchange resource request information with LSP for emergency management purposes
FR2411 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to implement special traffic control measures in the occurrence of an emergency
FR2412 LADOTD District 02 (Bridge City)RTMC shall request LSP resources to verify an incident for emergency management purposes
FR242 LADOTD District 02 (Bridge City)RTMC shall exchange resource deployment status information with LSP for emergency management purposes
FR2421 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of individual resource deployment
FR24211 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of vehicles used in the occurrence of an emergency
SE Analysis September 2007 41
FR24212 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of equipment used in the occurrence of an emergency
FR24213 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of materials used in the occurrence of an emergency
FR24214 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of personnel used in the occurrence of an emergency
FR2422 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the availability of individual resources
FR24221 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the vehicles available for usage in emergency management purposes
FR24222 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the equipment available for usage in the occurrence of an emergency
FR24223 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the materials available for usage in the occurrence of an emergency
FR24224 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the personnel available for usage in the occurrence of an emergency
FR243 LADOTD District 02 (Bridge City)RTMC shall exchange resource coordination information with LSP for emergency management purposes
FR2431 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource inventory information
FR2432 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific resource status information
FR2433 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the coordination of resource prioritization
FR2434 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the specific requests for resources
FR244 LADOTD District 02 (Bridge City)RTMC shall exchange incident response status information with LSP for emergency management purposes
FR2441 LADOTD District 02 (Bridge City)RTMC shall inform LSP of the status of current incident response
FR24411 LADOTD District 02 (Bridge City)RTMC shall provide LSP a summary of incident status
FR24412 LADOTD District 02 (Bridge City)RTMC shall report LSP the impact of the incident on the transportation system
FR24413 LADOTD District 02 (Bridge City)RTMC shall provide LSP traffic management strategies for the site
FR24414 LADOTD District 02 (Bridge City)RTMC shall provide LSP current response activities
SE Analysis September 2007 42
FR24415 LADOTD District 02 (Bridge City)RTMC shall provide LSP planned response activities
FR245 LADOTD District 02 (Bridge City)RTMC shall coordinate incident response with LSP for emergency management purposes
FR2451 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR24511 LADOTD District 02 (Bridge City)RTMC shall report to LSP a summary of incident status
FR24512 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on the transportation system
FR24513 LADOTD District 02 (Bridge City)RTMC shall report to LSP the impact of the incident on infrastructure
FR24514 LADOTD District 02 (Bridge City)RTMC shall report to LSP current response activities
FR24515 LADOTD District 02 (Bridge City)RTMC shall report to LSP planned response activities
FR246 LADOTD District 02 (Bridge City)RTMC shall exchange incident reports with LSP for emergency management purposes
FR2461 LADOTD District 02 (Bridge City)RTMC shall report to LSP an identified incident
FR2462 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident location
FR2463 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident type
FR2464 LADOTD District 02 (Bridge City)RTMC shall report to LSP the incident severity
FR2465 LADOTD District 02 (Bridge City)RTMC shall report to LSP all information necessary to initiate an appropriate incident response
FR247 LADOTD District 02 (Bridge City)RTMC shall coordinate incident command information with LSP for emergency management purposes
FR2471 LADOTD District 02 (Bridge City)RTMC shall provide to LSP information that supports local management of an incident
FR24711 LADOTD District 02 (Bridge City)RTMC shall report to LSP resource deployment status
FR24712 LADOTD District 02 (Bridge City)RTMC shall report to LSP traffic conditions
FR24713 LADOTD District 02 (Bridge City)RTMC shall report to LSP road conditions
SE Analysis September 2007 43
FR24714 LADOTD District 02 (Bridge City)RTMC shall report to LSP weather conditions
FR24715 LADOTD District 02 (Bridge City)RTMC shall provide LSP with evacuation advice
FR24716 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement a safe incident response
FR24717 LADOTD District 02 (Bridge City)RTMC shall provide LSP with all information that enables emergency personnel in the field to implement an efficient incident response
FR248 LADOTD District 02 (Bridge City)RTMC shall coordinate evacuations with LSP for emergency management purposes
FR2481 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding a pending evacuation
FR24811 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24812 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24813 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24814 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24815 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR2482 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP information regarding an in-process evacuation
FR24821 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation zones
FR24822 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation times
FR24823 LADOTD District 02 (Bridge City)RTMC shall inform LSP of evacuation routes
FR24824 LADOTD District 02 (Bridge City)RTMC shall inform LSP of forecast network conditions
FR24825 LADOTD District 02 (Bridge City)RTMC shall inform LSP of reentry times
FR249 LADOTD District 02 (Bridge City)RTMC shall coordinate emergency plans with LSP for emergency management purposes
SE Analysis September 2007 44
FR2491 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency management plans
FR2492 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the continuity of operations plans
FR2493 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency response plans
FR2494 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP recovery plans evacuation plans
FR2410 LADOTD District 02 (Bridge City)RTMC shall coordinate alert notifications with LSP for emergency management purposes
FR24101 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP emergency alerts to be distributed to the public
FR241011 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a natural disaster to the public
FR241012 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a man-made disaster to the public
FR241013 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a civil emergency to the public
FR241014 LADOTD District 02 (Bridge City)RTMC shall coordinate with LSP the notification of a child abduction to the public
FR2411 LADOTD District 02 (Bridge City)RTMC shall provide an alert status to LSP for emergency management purposes
FR24111 LADOTD District 02 (Bridge City)RTMC shall provide information to LSP indicating the current status of the emergency alert
FR241111 LADOTD District 02 (Bridge City)RTMC shall identify to LSP the driver information systems that are being used to provide the alert
FR2412 LADOTD District 02 (Bridge City)RTMC shall exchange road network conditions with LSP for emergency management purposes
FR24121 LADOTD District 02 (Bridge City)RTMC shall provide LSP with road conditions
FR24122 LADOTD District 02 (Bridge City)RTMC shall provide LSP with weather conditions
FR24123 LADOTD District 02 (Bridge City)RTMC shall provide LSP with traffic incident information for emergency management purposes
FR2413 LADOTD District 02 (Bridge City)RTMC shall provide emergency traffic control information to LSP for emergency management purposes
FR24131 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
SE Analysis September 2007 45
FR24132 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
FR24133 LADOTD District 02 (Bridge City)RTMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR2414 LADOTD District 02 (Bridge City)RTMC shall provide emergency routes to LSP for emergency management purposes
FR24141 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to the scenes
FR24142 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access between the scenes
FR24143 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested ingress routes for access to staging areas
FR24144 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to the scenes
FR24145 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access between the scenes
FR24146 LADOTD District 02 (Bridge City)RTMC shall provide LSP with suggested egress routes for access to staging areas
FR25 Louisiana State Police (LSP) shall communicate with LADOTD District 02 (Bridge City)RTMC
FR251 LSP shall provide an alert notification to LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR2511 LSP shall provide notification to LADOTD District 02 (Bridge City)RTMC of a major emergency
FR25111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a natural disaster to the public
FR251111 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25112 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a man-made disaster to the public
SE Analysis September 2007 46
FR251121 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251122 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251123 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251124 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25113 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a civil emergency to the public
FR251131 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251132 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251133 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251134 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR25114 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the notification of a child abduction to the public
FR251141 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the alert originator
FR251142 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the nature of the emergency
FR251143 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the identification of the effective time period of the alert
FR251144 LSP shall coordinate with LADOTD District 02 (Bridge City)RTMC the information provided to the public with instruction on how to respond to the alert
FR252 LSP shall request an emergency route from District 02 in the occurrence of an emergency
FR2521 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response vehicles
FR2522 LSP shall request LADOTD District 02 (Bridge City)RTMC for ingress access routes for emergency response equipment
SE Analysis September 2007 47
FR2523 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response vehicles
FR2524 LSP shall request LADOTD District 02 (Bridge City)RTMC for egress access routes for emergency response equipment
FR253 LSP shall request emergency traffic control from District 02 for emergency management purposes
FR2531 LSP shall request LADOTD District 02 (Bridge City)RTMC to place a public safety message on a dynamic message sign
FR2532 LSP shall request LADOTD District 02 (Bridge City)RTMC to place an emergency message on a dynamic message sign
FR26 LSP shall communicate with LADOTD ITS Statewide TMC
FR261 LSP shall provide an alert notification to LADOTD ITS Statewide TMC for emergency management purposes
FR2611 LSP shall provide notification to LADOTD ITS Statewide TMC of a major emergency
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR261111 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261112 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261113 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261114 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261122 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261123 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261124 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
SE Analysis September 2007 48
FR261131 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261132 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261133 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261134 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR261141 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
FR261142 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the nature of the emergency
FR261143 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the effective time period of the alert
FR261144 LSP shall coordinate with LADOTD ITS Statewide TMC the information provided to the public with instruction on how to respond to the alert
FR262 LSP shall coordinate alert notifications with LADOTD ITS Statewide TMC for emergency management purposes
FR2621 LSP shall coordinate with LADOTD ITS Statewide TMC emergency alerts to be distributed to the public
FR26211 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a natural disaster to the public
FR26212 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a man-made disaster to the public
FR26213 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a civil emergency to the public
FR26214 LSP shall coordinate with LADOTD ITS Statewide TMC the notification of a child abduction to the public
FR263 LSP shall exchange resource request information with LADOTD ITS Statewide TMC for emergency management purposes
FR2631 LSP shall request LADOTD ITS Statewide TMC resources to implement special traffic control measures in the occurrence of an emergency
FR2632 LSP shall request LADOTD ITS Statewide TMC resources to verify an incident for emergency management purposes
SE Analysis September 2007 49
FR264 LSP shall exchange resource deployment status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2641 LSP shall inform LADOTD ITS Statewide TMC of the status of individual resource deployment
FR26411 LSP shall inform LADOTD ITS Statewide TMC of the status of vehicles used in the occurrence of an emergency
FR26412 LSP shall inform LADOTD ITS Statewide TMC of the status of equipment used in the occurrence of an emergency
FR26413 LSP shall inform LADOTD ITS Statewide TMC of the status of materials used in the occurrence of an emergency
FR26414 LSP shall inform LADOTD ITS Statewide TMC of the status of personnel used in the occurrence of an emergency
FR2642 LSP shall inform LADOTD ITS Statewide TMC of the availability of individual resources
FR26421 LSP shall inform LADOTD ITS Statewide TMC of the vehicles available for usage in emergency management purposes
FR26422 LSP shall inform LADOTD ITS Statewide TMC of the equipment available for usage in the occurrence of an emergency
FR26423 LSP shall inform LADOTD ITS Statewide TMC of the materials available for usage in the occurrence of an emergency
FR26424 LSP shall inform LADOTD ITS Statewide TMC of the personnel available for usage in the occurrence of an emergency
FR265 LSP shall exchange resource coordination information with LSP for emergency management purposes
FR2651 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource inventory information
FR2652 LSP shall inform LADOTD ITS Statewide TMC of the specific resource status information
FR2653 LSP shall inform LADOTD ITS Statewide TMC of the coordination of resource prioritization
FR2654 LSP shall inform LADOTD ITS Statewide TMC of the specific requests for resources
FR266 LSP shall exchange incident response status information with LADOTD ITS Statewide TMC for emergency management purposes
FR2661 LSP shall inform LADOTD ITS Statewide TMC of the status of current incident response
FR26611 LSP shall provide LADOTD ITS Statewide TMC a summary of incident status
SE Analysis September 2007 50
FR26612 LSP shall report LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26613 LSP shall provide LADOTD ITS Statewide TMC traffic management strategies for the site
FR26614 LSP shall provide LADOTD ITS Statewide TMC current response activities
FR26615 LSP shall provide LADOTD ITS Statewide TMC planned response activities
FR267 LSP shall coordinate incident response with LADOTD ITS Statewide TMC for emergency management purposes
FR2671 LSP shall report to LADOTD ITS Statewide TMC the incident response procedures that are shared between allied response agencies to support a coordinated response to incidents
FR26711 LSP shall report to LADOTD ITS Statewide TMC a summary of incident status
FR26712 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on the transportation system
FR26713 LSP shall report to LADOTD ITS Statewide TMC the impact of the incident on infrastructure
FR26714 LSP shall report to LADOTD ITS Statewide TMC current response activities
FR26715 LSP shall report to LADOTD ITS Statewide TMC planned response activities
FR268 LSP shall exchange incident reports with LADOTD ITS Statewide TMC for emergency management purposes
FR2681 LSP shall report to LADOTD ITS Statewide TMC an identified incident
FR2682 LSP shall report to LADOTD ITS Statewide TMC the incident location
FR2683 LSP shall report to LADOTD ITS Statewide TMC the incident type
FR2684 LSP shall report to LADOTD ITS Statewide TMC the incident severity
FR2685 LSP shall report to LADOTD ITS Statewide TMC all information necessary to initiate an appropriate incident response
FR269 LSP shall coordinate incident command information with LADOTD ITS Statewide TMC for emergency management purposes
FR2691 LSP shall provide to LADOTD ITS Statewide TMC information that supports local management of an incident
FR26911 LSP shall report to LADOTD ITS Statewide TMC resource deployment status
FR26912 LSP shall report to LADOTD ITS Statewide TMC traffic conditions
SE Analysis September 2007 51
FR26913 LSP shall report to LADOTD ITS Statewide TMC road conditions
FR26914 LSP shall report to LADOTD ITS Statewide TMC weather conditions
FR26915 LSP shall provide LADOTD ITS Statewide TMC with evacuation advice
FR26916 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement a safe incident response
FR26917 LSP shall provide LADOTD ITS Statewide TMC with all information that enables emergency personnel in the field to implement an efficient incident response
FR2610 LSP shall coordinate evacuations with LADOTD ITS Statewide TMC for emergency management purposes
FR26101 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding a pending evacuation
FR261011 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261012 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261013 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261014 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261015 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR26102 LSP shall coordinate with LADOTD ITS Statewide TMC information regarding an in-process evacuation
FR261021 LSP shall inform LADOTD ITS Statewide TMC of evacuation zones
FR261022 LSP shall inform LADOTD ITS Statewide TMC of evacuation times
FR261023 LSP shall inform LADOTD ITS Statewide TMC of evacuation routes
FR261024 LSP shall inform LADOTD ITS Statewide TMC of forecast network conditions
FR261025 LSP shall inform LADOTD ITS Statewide TMC of reentry times
FR2611 LSP shall coordinate emergency plans with LADOTD ITS Statewide TMC for emergency management purposes
FR26111 LSP shall coordinate with LADOTD ITS Statewide TMC emergency management plans
FR26112 LSP shall coordinate with LADOTD ITS Statewide TMC the continuity of operations plans
FR26113 LSP shall coordinate with LADOTD ITS Statewide TMC emergency response plans
SE Analysis September 2007 52
FR26114 LSP shall coordinate with LADOTD ITS Statewide TMC recovery plans evacuation plans
FR2612 LSP shall request an emergency route from LADOTD ITS Statewide TMC in the occurrence of an emergency
FR26121 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response vehicles
FR26122 LSP shall request LADOTD ITS Statewide TMC for ingress access routes for emergency response equipment
FR26123 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response vehicles
FR26124 LSP shall request LADOTD ITS Statewide TMC for egress access routes for emergency response equipment
FR2613 LSP shall request emergency traffic control from LADOTD ITS Statewide TMC for emergency management purposes
FR26131 LSP shall request LADOTD ITS Statewide TMC to place a public safety message on a dynamic message sign
FR26132 LSP shall request LADOTD ITS Statewide TMC to place an emergency message on a dynamic message sign
FR27 LADOTD ITS Statewide TMC shall communicate with Louisiana State Police (LSP)
FR271 LADOTD ITS Statewide TMC shall provide an alert status to LSP for emergency management purposes
FR2711 LADOTD ITS Statewide TMC shall provide information to LSP indicating the current status of the emergency alert
FR2712 LADOTD ITS Statewide TMC shall identify to LSP the driver information systems that are being used to provide the alert
FR272 LADOTD ITS Statewide TMC shall exchange road network conditions with LSP for emergency management purposes
FR2721 LADOTD ITS Statewide TMC shall provide LSP with road conditions
FR2722 LADOTD ITS Statewide TMC shall provide LSP with weather conditions
FR2723 LADOTD ITS Statewide TMC shall provide LSP with traffic incident information for emergency management purposes
FR273 LADOTD ITS Statewide TMC shall provide emergency traffic control information to LSP for emergency management purposes
FR2731 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to an emergency traffic control request
FR2732 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for emergency access routes
SE Analysis September 2007 53
FR2733 LADOTD ITS Statewide TMC shall provide LSP with the status of a system activation implemented in response to a request for evacuation
FR274 LADOTD ITS Statewide TMC shall provide emergency routes to LSP for emergency management purposes
FR2741 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to the scenes
FR2742 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access between the scenes
FR2743 LADOTD ITS Statewide TMC shall provide LSP with suggested ingress routes for access to staging areas
FR2744 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to the scenes
FR2745 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access between the scenes
FR2746 LADOTD ITS Statewide TMC shall provide LSP with suggested egress routes for access to staging areas
FR28 LADOTD ITS Statewide TMC shall communicate with DMSs for emergency management purposes
FR29 LADOTD ITS Statewide TMC shall communicate with CCTVs for emergency management purposes
FR291 LADOTD ITS Statewide TMC shall control video surveillance of CCTVs for emergency management purposes
FR30 CCTVs shall communicate with LADOTD ITS Statewide TMC for emergency management purposes
FR301 LADOTD ITS Statewide TMC shall receive traffic images supplied by CCTVs
FR31 CCTVs shall communicate with LADOTD District 02 (Bridge City)RTMC for emergency management purposes
FR311 LADOTD District 02 (Bridge City)RTMC shall receive traffic images supplied by CCTVs
FR32 CCTVs shall communicate with LSP Troop B for emergency management purposes
FR321 LSP Troop B shall receive traffic images supplied by CCTVs
SE Analysis September 2007 54
63 Requirements Traceability Matrix The purpose of the requirements traceability matrix is to identify the section of the Concept of Operations document from which the requirement is derived as well as the high level and associated detailed requirements As design and implementation are completed the matrix contains the linking information to the design specifications and implementation information that addresses requirements The Requirements Traceability Matrix is provided in Appendix A Table A-1 7 System Design As part of a Systems Engineering process a system design is required for an ITS project The system design process defines how a system will be built The design activities supported in a LADOTD ITS project result in a design document that contains both high-level and detailed design specifications as well as any supporting information needed to implement and integrate ITS facilities A system design is developed from the system requirements For the Baton Rouge to New Orleans Phase 1 project these requirements have been previously defined (please refer to Section 6) Since the previous requirements section has defined what the system will do the requirements will be translated into a hardware and software design that can be deployed The system design process has two phases The first phase is High-Level Design where High Level requirements are translated into decisions about how the system will be built how subsystems are organized and how verification should be handled at a high level In the High-Level Design process design concepts are developed During the second phase of design plan sets and top-level specifications are defined in detail at a level where implementation is supported As part of this project design concepts are satisfied and detailed design specifications are developed 71 High-Level Design The high level design process will give way to the development of an overall system design prior to working out the details of an individual system The Concept of Operations and System Requirements of the project have defined the purpose and the need for the ITS project (sections 5 and 6 respectively) Please refer to these sections for clarifications on the purpose of the system system development operation and maintenance identification of stakeholders and the current and planned operating sites 711 Project Organization This section will describe how the project is divided into subsystems Each subsystem has its purpose functionality and interface with other sub-systems and component parts As previously stated subsystem organization can be seen in the Project Physical Architecture
SE Analysis September 2007 55
The Baton Rouge to New Orleans Phase 1 project will provide communication connection and data flow between subsystems From the Project Physical Architecture the following have been defined as subsystems
1 LADOTD ITS Statewide TMC Operator 2 LADOTD District 02 (Bridge City)RTMC ITS Operator 3 LSP Troop B Dispatch Operator 4 TDs 5 DMSs 6 CCTVs
All of these subsystems communicate through the communications backbone or by remote connection These subsystems exchange information ranging from traffic operations and incident detection to incident reports The information that these centers exchange has been previously defined in the Concept of Operations and Requirements section of this document Please refer to these documents and the Project Physical Architecture for further information 7111 Hardware and Software Components The hardware and software component of each subsystem is either directly or remotely connected to the communication backbone These components have been defined in the Functional Specification section of the Scope of Services Package (ie the request for proposal) A communications alternative section has been developed as part of this System Engineering analysis Please refer to Alternative Communications Configurations section for information regarding connections between subsystems hardware components and software implementation Please note that different types of communication connectivity were explored 72 Detailed Design As previously stated the detailed design provides the detailed plans and configuration needed for system implementation For the Baton Rouge to New Orleans Phase 1 project please refer to section 8 for the Alternative Communications Configurations section Functional Specifications and to the resulting detail design plans 8 Alternative Communication Configurations An important component of the SE analysis for the Baton Rouge to New Orleans Phase 1 project is the communication and alternative analysis This analysis evaluates a number of communication technologies to determine their application to this project Satisfaction of the project communication needs requires the identification of a transmission media that accommodates the current information demand and provides capacity to meet future system demand The selected transmission media must be capable of handling system communication needs at a high operational performance level
SE Analysis September 2007 56
81 Communication Technologies There are a number of different types of communication technologies available for ITS network applications that LADOTD should be aware of Some of the technologies cited below are not applicable for this project However it is important that LADOTD be aware of the variety of technologies currently being used throughout the communication industry They are
bull Fiber optic cable (Single Mode) bull Cellular Digital Packet Data (CDPD) bull Global System for Mobile Communication (GSMEDGE) Enhanced Data for Global
Evolution bull Radio Frequency (Spread Spectrum) bull Terrestrial Microwave Links bull Area Radio Network (ARN) bull Telephone Lease Lines bull Code-Division Multiple Access (CDMA) and bull Orthogonal Frequency Division Multiplexing (OFDM)
The critical factors in the selection of a preferred alternative are the following bull High reliability and availability bull Low capital and operating (ie maintenance) costs bull Provisions for high bandwidth capacity and transmission speed with flexibility to
accommodate future expansion and bull Protection of the interconnected server workstations and controllers from unauthorized
access and malicious intent
General advantages of direct wire connection versus a wireless connection bull Bandwidth is limited only by the edge devices bull Life span of 15 years+ bull Connection can only be interrupted by invasive measures (eg break in the fiber) and bull Maintenance is generally less than that of wireless
General disadvantages of direct wire connection versus a wireless connection
bull Susceptible to being broken during construction bull Requires costly conduitduct (eg structure mounted bullet resistant conduit) and bull Installation cost is higher than that of wireless
811 Fiber Optic Cable (Single Mode) The advantages of single mode fiber optic cable are the following
bull Allowable distance between transmission equipment transmission rate and bandwidth capacity is significantly greater than any other communication method thereby providing nearly unlimited future System expansion
bull Lightning protection devices are not required
SE Analysis September 2007 57
bull Ratio of cable diameter to bandwidth capacity is very small bull Provides highest level of security when properly monitored bull Not susceptible to electro-magnetic and radio frequency interference bull Not susceptible to corrosion and bull Provides high transmission reliability if quality materials are specified and testing is
performed to verify compliance The disadvantages of single mode fiber optic cable are the following
bull Splicing and connector termination requires specialized equipment and skilled technician bull Technician training required repairing replacing and testing fiber cable bull Test equipment is more complex and expensive relative to copper test equipment bull Susceptible to breaking if the fiber bends are smaller than the recommended bending
radius or excessive load is applied bull Requires devices to convert from optical to electrical end user equipment and bull Substantial capital cost of installation
812 Cellular Digital Packet Data (CDPD) CDPD is a packet-switched full duplex data communication system that cellular carriers use specifically for data transmission and as a means of filling unused voice channel capacity The advantages of CDPD are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference and limited susceptibility to radio
frequency interference and bull Maximum flexibility in locating and moving the required modem (assuming adequate
cell coverage) The disadvantages of CDPD are the following
bull Requires payment of a recurring service fee (payment is only for data sent and received in packets not minutes)
bull Major carriers plan to discontinue CDPD service with the migration to 3G technologies bull Transmission Speed limited to 288 Kbps bull Dependent on cellular coverage provided by existing infrastructure Connection likely to
be lost if signal strength falls below ndash105 dBm bull Requires separate modem for each controller and bull Unencrypted data is susceptible to eavesdropping
813 Global System for Mobile Communication (GSM) CDMA is the dominant technology for cellular andor PCS networks in North America (see section 818 for CDMA) GSM is the dominant technology for cellular andor PCS networks in
SE Analysis September 2007 58
Europe Cellular and PCS differ primarily in their respective operational frequency bands 800 MHz for cellular and 1900 MHz for PCS The advantages of GSM are the following
bull Lower cost of data rate plans for wireless WANs Prices for these plans have fallen significantly creating a more compelling reason to switch to wireless data networks for remote device communications
bull New technology gives wireless gateways the ability to maintain an ldquoalways onrdquo connection without being charged for total airtime so users pay only for the data they actually send over the wireless connection
bull Maximum flexibility in locating and moving the required gateway (assuming adequate cell coverage) and
bull Transmission speeds of 30 Mbps can be achieved with EDGE technology where service is available
The disadvantages of GSM are the following
bull Airtime cost excessive for continuous communication service bull Only two providers in one area bull Actual data throughput reduced due to protocol overhead and bull Remote areas may not have service
814 Radio Frequency (Spread Spectrum) Spread spectrum uses wideband modulation to impart noise-like characteristics to an RF signal The bandwidth is spread by means of a code which is independent of the data The independence of the code distinguishes this from standard modulation schemes in which the data modulation will always spread the spectrum The receiver synchronizes to the transmitter code to recover the data The use of an independent code and synchronous reception allows multiple users to access the same frequency band at the same time without interference Frequency hopping and direct sequence systems are the most widely used implementations of this technology and the associated equipment is commercially available The advantages of radio frequency transmission are the following
bull Eliminates need for incurring underground cable installation costs bull Not susceptible to electro-magnetic interference bull Provides a low probability of intercept and includes anti-jam features bull Radio frequency interference with narrowband communications is minimized by use of
lower spectral power density and for a frequency hopping implementation an ability to reconstruct the data when some frequencies are blocked and
bull Does not require a FCC license to operate The disadvantages of radio frequency transmission are the following
bull Requires overhead locations to mount antennas that maintain line of sight bull Requires routing cable and conduit from antenna to modem installed in cabinet
SE Analysis September 2007 59
bull Requires separate modem for each controller bull Limited susceptibility to radio frequency interference bull Requires the highest equipment expenditure that includes sufficient spares (Also
expected to have the highest total cost consisting of initial capital cost and net present value of operatingmaintenance cost)
bull Antenna is susceptible to vandalism bull Requires special skills and equipment to maintain and bull Requires the most training to maintain
815 Terrestrial Microwave Links Terrestrial microwave is a line-of-sight technology that cannot extend beyond the earthrsquos horizon Long distance terrestrial transmission of data is accomplished using relay points know as ldquohops) Typically each hop consists of a tower with one antenna for receiving and another for transmitting Terrestrial microwave systems operate in the low-gigahertz range typically at 4-6 GHz and 21- 23 GHz The advantages of terrestrial microwave links are as follows
bull Useful as a point-to-point trunk bull Can transmit data and a limited number of full motion video channels bull Can control groups of traffic control devices bull Can use both analog and digital transmission and bull Offers the highest data throughput rates of any wireless technology
The disadvantages of terrestrial microwave links are as follows
bull Line-of ndashsight may be required based on the frequency bull In most cases requires FCC license bull Channel availability limited bull May have little choice in operating frequency bull Possible interference due to rain snow and atmospheric effects bull May require antenna tower bull Available bandwidth usually limited and bull Typically most expensive wireless technology to implement
816 Area Radio Network (ARN) Area Radio Network (ARN) is representative of a radio network usually operating in the UHFVHF frequency bands These networks are normally used for in-house communications of equipment devices and maintenance staff and personnel The advantages of ARN are as follows
bull Can operate traffic controllers or other devices bull Can provide voice communications to highway maintenance vehicles
SE Analysis September 2007 60
bull Can support 9600 baud data rate and bull Can prove cost effective depending on application
The disadvantages of ARN are as follows
bull Terrain may be limited bull Limited channel availability in urban area bull Requires antenna at each site bull Turnaround time excessive for some applications and bull Service reliability may limit use for some applications (Example CTV video)
817 Telephone Lease Lines Line The advantages of telephone line are as follows
bull Can operate traffic controllers or other devices bull Can provide video transmission at low fps and bull Asymmetric Digital Subscriber (ADSL) can support full motion video
The disadvantages of telephone are as follows
bull ADSL leasing cost and bull Limited video availability
818 Code-Division Multiple Access (CDMA) CDMA (Code-Division Multiple Access) refers to any of several protocols used in so-called second-generation (2G) and third-generation (3G) wireless communications As the term implies CDMA is a form of multiplexing which allows numerous signals to occupy a single transmission channel optimizing the use of available bandwidth The technology is used in ultra-high-frequency (UHF) cellular telephone systems in the 800-MHz and 19-GHz bands CDMA employs analog-to-digital conversion (ADC) in combination with spread spectrum technology Audio input is first digitized into binary elements The frequency of the transmitted signal is then made to vary according to a defined pattern (code) so it can be intercepted only by a receiver whose frequency response is programmed with the same code so it follows exactly along with the transmitter frequency There are trillions of possible frequency-sequencing codes which enhance privacy and makes cloning difficult The CDMA channel is nominally 123 MHz wide CDMA networks use a scheme called soft handoff which minimizes signal breakup as a handset passes from one cell to another The combination of digital and spread-spectrum modes supports several times as many signals per unit bandwidth as analog modes CDMA is compatible with other cellular technologies this allows for nationwide roaming The original CDMA standard also known as CDMA One and still common in cellular telephones in the US offers a transmission speed of only up to 144 Kbps in its single channel form and up to 115 Kbps in an eight-channel form CDMA2000 and wideband CDMA deliver data many times faster
SE Analysis September 2007 61
The advantages of CDMA are as follows
bull Frequency diversity bull Multi-path resistance bull Privacysecurity and bull Graceful degradation
The disadvantages of CDMA are as follows
bull Self jamming3 bull Near-far problem bull Soft hand-off and bull Not suitable for very high bit rate (like in WLAN) and bull Monthly service subscription
819 Orthogonal Frequency Division Multiplexing (OFDM) OFDM is an FDM modulation technique for transmitting large amounts of digital data over a radio wave OFDM works by splitting the radio signal into multiple smaller sub-signals that are then transmitted simultaneously at different frequencies to the receiver This spacing provides the orthogonality technique which prevents the demodulators from seeing frequencies other than their own OFDM reduces the amount of crosstalk in signal transmissions 80211a WLAN 80216 and WiMAX technologies use OFDM OFDM is best used in high dense area where multipath effect is severe (in a building or in a city where multipath is severe) OFDM should not be implemented in areas where multipath is not an issue such as open space rural areasLOS The advantages of OFDM are as follows
bull High bandwidth efficiency bull Robust in multipath environments (typically urban) bull Suitable for very high bit rate systems like (WLANS) and bull Offers flexibility in modulation and multiple accesses
The disadvantages of OFDM are as follows
bull Sensitive to carrier frequency offset causing incorrect carrier frequency bull Large Peak-to-Average ratio (PAR) which causes amplifier non-linearity and bull Sensitive to channel fade (flat fade)
3 Self-jamming is a phenomena that arises because the sequence in which multiple user signals received are not exactly orthogonal which results in an elevated noise floor and a higher bit error rate in regards to the receiving end otherwise known as the up-link
SE Analysis September 2007 62
82 Project Communications Implementation of the Baton Rouge to New Orleans ITS TIM Phase 1 project directly connects ITS field equipment to LADOTD ITS Statewide TMC the District 02 TMC and remotely connects the LSP Troop B office The connection of the centers and ITS field equipment is in compliance with the requirements for the LADOTD Statewide ITS Plan which promotes maximizing interoperability for the statewide ITS network For this project LADOTD is using a design-build contracting process The DB contracting process provides a proposing firm with a functional specification of the project The proposing firm develops a specific design approach to the project along with a cost estimate This project SE analysis offers three viable communications technologies for consideration They are fiber optics radio frequency wireless and microwave Each one (or a combination) can provide the data transmission capacity reliability and scalability to address the communications needs per the different applications identified for the project The primary element of differentiation for these technologies is the cost and reliability associated with their implementation The existing fiber backbone described in section 54 of this document was provided to LADOTD as part of a permit filed by Enron Communications Inc in 1999 LADOTD received 1 - 125rdquo vacant conduit and 8 dark strands of long haul fiber in the Enron duct LADOTD envisions the use of the vacant conduit as a feasible means of expand it communication infrastructure to ITS field equipment Existing pull boxes (access points) to the conduit are limited The use of this conduit requires installation of additional access points and coordination with Qwest Communications International Inc (the current owner of the Enron duct) Also LADOTD and LSP currently own towers within the project limits that may allow for wireless expansion to cover communications to field devices as well These communication options are presented in the Scope of Services Package (ie request for proposal) for the plan design and construction of the project Table 6 presents a brief description of the three communication alternatives for connecting the project with the statewide communication backbone with corresponding cost estimates Please note that since this is a design-build project the cost of the design as well as construction is typically presented in the proposal documents and may not necessarily reflect the typical cost associated with the design-bid-build type projects Also it should be noted that there may be an unforeseen cost increase due to the current demand on contractorsengineers as well as the limited local contractors who specialize in ITS construction
Life Cycle Cost analyses has been provided for this project See section 141 of this document for information pertaining to the Life Cycle Cost analysis
SE Analysis September 2007 63
9 Power Configuration Electrical power for the Baton Rouge to New Orleans Phase 1 project is a significant component in its implementation The criteria for power design is primarily determined by the power needs of the overall ITS field equipment (DMS CCTV vehicle detections cross-over gates and future LCS devices) required for the project and the ease of accessing commercial power This project is unique in that the I-10 roadway spans the Bonnet Carre Spillway a distance of approximately 12 miles Consequently the cost of supplying commercial power to ITS field components is substantial LADOTD has deemed that in order to obtain the reliability required to operate the ITS equipment accommodate the cross-overs and deploy future LCS commercial power is required along the 12 mile bridge Table 6 includes the estimated cost for power along the 12 mile bridge section It should be noted that the conduit for the 12 mile bridge is included in just the cost shown for the power Also the actual cost associated with the power may vary based on the number of devices immediately connecting to each power source
Table 6 Communications and Power Design Options
10 Software Alternative Configurations An important component of the Baton Rouge to New Orleans Phase 1 project is the system software necessary to communicate with and manage the different ITS field components associated with the project LADOTD first deployment of integrated system software for TMCs was a software packaged developed by PB Faradyne titled Management Information System for Transportation (MIST) This software allowed operators to manage and monitor ITS field devices located within the Baton Rouge metropolitan area
SE Analysis September 2007 64
More recently LADOTD began implementing traffic management software product by 360 Surveillance 360 titled Cameleon ITS v4 at the LADOTD ITS Statewide TMC and District 02 TMC Cameleon is a systems integration software that allows operators to monitor and manage ITS field devices from a central (or multiple) TMC LADOTD envisions Cameleon as an interim solution as they better define their statewide ITS software integration needs Software alternative configuration information is presented in the SOSP for design and construction of the project It is a requirement of this project that the system to be deployed be integrated with the Cameleon traffic management software operating at the LADOTD ITS Statewide TMC This would also require the installation of this software at the LSP Troop B and District 02 TMC locations In addition LADOTD requires the installation of all vendor supplied software for remote access as well as device diagnostics 11 Procurement Options The implementation of the Baton Rouge to New Orleans Phase 1 project will include the deployment of numerous ITS technologies These technologies will be used by LADOTD to monitor traffic operations within the project limits (Figure 1) detect and evaluate incidents to determine the need for traffic diversion and communicate roadway conditions to the motoring public Once the traffic incident is resolved the roadway facility can return to its normal operating conditions This section identifies the procurement options for the ITS hardware software and communication technologies that are available to LADOTD to satisfy previously identified requirements 111 Procurement Options of ITS Technologies Based on review of the LADOTD procurement regulations ITS technologies are procured under the Louisiana Administrative Code Title 70 XXIII Chapter 3 Commodities purchased by the LADOTD Procurement Section fall into two categories either non-exempt commodities or exempt commodities 1111 Non-Exempt Commodities Non-exempt commodities are defined as materials and supplies that will not become a component part of any road highway bridge or appurtenance thereto These commodities are subject to the requirements of the Louisiana Procurement Code and such regulations promulgated by the Commissioner of Administration and are governed by the rules and regulations adopted by the Director of State Purchasing Purchases of less than $50000 (or the amount set in the latest Governors Executive Order whichever is higher) do not require competitive bids All Request for Quotations covering non-exempt commodities that exceed the non-competitive dollar limit but do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price
SE Analysis September 2007 65
quotation solicited from at least three bona fide qualified bidders All Request for Quotations covering non-exempt commodities having an estimated cost which exceeds $500000 but which do not exceed $2000000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchases of non-exempt commodities having an estimated cost which exceeds $2000000 (or the latest delegated purchasing authority whichever is higher) are prepared and forwarded to the Office of State Purchasing for bid solicitation 1112 Exempt Commodities Exempt commodities are defined in RS391572 as materials and supplies that will become a component part of any road highway bridge or appurtenance as defined in RS 391572 Purchases of exempt commodities having an estimated cost which exceeds the non-competitive dollar limit of $500 (or the amount set in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are also referred to as Request for Quotations All Request for Quotations covering exempt commodities which exceed the non-competitive dollar limit but which do not exceed $500000 (or the dollar limits listed in the latest Governors Executive Order whichever is higher) are awarded on the basis of the lowest responsive price quotation from at least three bona fide qualified bidders All Request for Quotations covering exempt commodities having an estimated cost which exceeds $500000 (or the dollar limit listed in the latest Governors Executive Order whichever is higher) but which do not exceed $2500000 (or the latest revision to RS 48205 whichever is higher) are awarded on the basis of the lowest responsive price quotation solicited from at least five bona fide qualified bidders Purchase of exempt commodities having an estimated cost which exceeds $2500000 (or the latest revision to RS 48205 whichever is higher) will be processed as Sealed Bids and shall be advertised in accordance with RS 48205 112 ITS Hardware Technologies
ITS hardware technologies can be segmented into three categories traffic monitoring incident evaluation and communications with the traveling public ITS technologies used by transportation agencies for monitoring traffic operations are primarily achieved with remote sensory devices TDs These devices employ radar video imaging and magnetic inductance to ldquosenserdquo the presence and movement of vehicles traveling along the roadway facility These devices are located at strategic points and at specific distances along the roadway They can be non-intrusively mounted on existing light and sign structures (radar and video) or placed inside the roadway service (wire loops) CCTV technologies are primarily used by operators to locate and evaluate traffic incidents and traffic monitoring This technology allows traffic management personnel to visually observe traffic operations on a roadway facility and determine how traffic is moving There are many more product options with CCTV as there are many other applications than highway transportation DMS are an effective way of disseminating real-time
SE Analysis September 2007 66
traffic conditions to the traveling public A DMS is an electronically controlled message board located at a strategic location near or over the travel lanes of the roadway 113 Software
All of these ITS technology system components typically come with software as part of the hardware purchase (vendor software) This software allows operators to control manage and diagnose the hardware components located along the roadway Typically these component systems can be integrated with existing traffic management system operating software For this project LADOTD has specified the use of 360 Surveillancersquos Cameleon ITS v4 The deployment of this project will require the integration of the equipment with the existing software Since the component software is considered a component of the hardware system it would be typically purchased as an exempt commodity However the system integration software could be considered a non-exempt commodity since it is not part of the roadway 114 Communications
The communications network (or plant) used to integrate the ITS technology hardware manage data flows and receive video images is comprised of land-lines (fiber optic cable and twisted wire pairs) spread spectrum radio and microwave or wireless technology The communications plant connects the TOC to the various ITS components located along the roadway facility This allows operators to receive information from the field and display it numerically graphically and visually The information can be used by operators to determine roadway congestion vehicle travel speeds lane capacity and to evaluate incidents Additionally operators can use the communication network to send information and communicate with motorists about driving conditions lane closures and roadway detours The communication network built as a component of the ITS network for traffic management is typically purchased as an exempt commodity The physical communication plant is placed in conduits and equipment cabinets in the roadway right-of-way However this may not be the case for microwave towers and equipment that are constructed outside of roadway right-of-way but on other LADOTD properties Another method used by LADOTD to procure communications is that of leasing communications services from private communications companies The procurement of communication services would be done in the same manner as the purchase of telephone services for LADOTD Prices for these services are typically negotiated on a per connection per month basis 115 Project Procurement Methods Available for Use by LADOTD The procurement of ITS technologies and services associated with this project can be acquired by LADOTD using one of or a combination of four different procurement methods They are
bull Sealed Bid (or Design-Bid-Build) ndash LADOTD prepares a detailed project design and advertises for interested parties to submit a sealed bid to build the project The lowest bidder offering a fixed price (all else being equal) is awarded the project Any changes to
SE Analysis September 2007 67
the project made by LADOTD that result in additional work is subject to a negotiated change order Time value may be considered in the project
bull DesignndashBuild ndash LADOTD advertises a Notice of Intent and short list teams (maximum of
5) based on their interest and qualifications LADOTD prepares a Scope of Services Package which includes a functional specification for the short listed teams to submit proposals for the detail design and implementation of the project The team with the lowest calculated adjusted score based on their bid price plus time value divided by the technical score is awarded the project Time value may be considered in the project Any changes to the project made by LADOTD that result in additional work is subject to a negotiated change order
bull Request for Quotation ndash This is used primarily in the procurement of different types of
ITS hardware The LADOTD prepares a specification and solicits bids from three or five bona fide bidders (depending on the purchase amount) The bidder with the lowest price (all else being equal) is the successful bidder
bull Lease ndash Leasing is used by LADOTD for ITS projects primarily to secure communication
services such as an existing privately owned communications provider that can provide the necessary bandwidth for the ITS network Where there is only one provider sole sourcing is used
The selection of a contracting method(s) for use in this project is influenced by a number of factors including legal and administrative constraints quality control liability and responsibility of the contractor procurement schedule familiarity of the LADOTD project manager and past experience An evaluation of the positive and negative attributes for each method previously identified provides a basis for determining which method(s) should be used for this project 116 Procurement Method for Project LADOTD has elected to use the Design-Build Contracting method for this project This project will be the first ITS project (and the second for any LADOTD project) to use the design-build method of contracting 12 ITS Standards Standards are specifications that define how the different ITS sub-components interconnect and interact within the established parameters of the National ITS Architecture Specifically they stipulate how the different technologies interoperate to automatically share information LADOTD benefits from ITS standards for this project in several ways including bull Reducing the risk of equipment obsolescence bull Reducing the risk of a single point of supply and proprietary products bull Lowering prices for equipment bull Minimizing design and implementation confusion and bull Assuring quality
SE Analysis September 2007 68
Additionally federal regulations require that ITS projects must conform to the National ITS Architecture and the standards if they are financed using funds from the Highway Trust Fund The architecture currently identifies 13 key standards areas that can be found in the ITS Standards Requirements Document (SRD) ITS projects that are currently deployed by LADOTD incorporate standards developed by a number of standards developing bodies The American Association of State Highway and Transportation Officials (AASHTO) Institute of Transportation Engineers (ITE) and National Electrical Manufactures Association (NEMA) have taken the lead in developing standards for traffic management devices and their interoperability These devices include DMS traffic signals traffic sensors etc The Institute of Electrical and Electronic Engineers (IEEE) and the International Standards Organization (ISO) primarily provide the standards for communication infrastructure This includes communication cables switches nodes etc Finally the National Electric Code (NEC) provides standards to all related electrical and power requirements associated with ITS projects It should be noted that the development of standards is an ongoing and evolving process Therefore standards will need to be continually reviewed as LADOTD implements future projects The purpose of this chapter is to identify the standards that will be used in developing design concepts detail design and operational procedures associated with this project 121 Project Standards The most significant set of standards for ITS projects is the National Transportation Communications for ITS Protocol (NTCIP) This family of standards will establish the parameters for the development design and implementation of the ITS component of the project AASHTO ITE and NEMA have taken the lead in developing NTCIP standards NTCIP is a family of communication protocols (protocol is a system of rules and procedures governing communications between two devices) and data definition standards that serve and address the diverse needs of the various subsystems and user services presented in the national state and regional ITS architectures NTCIP consists of a whole family of protocols covering the spectrum from point-to-point commandresponse to sophisticated object oriented techniques NTCIP provides standards for two different ITS applications center-to-field (C2F) and center-to-center (C2C) both of which are applicable to this project 1211 Center-to-Field Standards There are two existing application protocols (and one protocol under development) for C2F communications the Internetrsquos Simple Network Management Protocol (SNMP) and the Simple Transportation Management Protocol (STMP) These protocols use the getset-messaging model Each protocol has its advantages SNMP is the simplest to implement The STMP is the most flexible and band width efficient Table 7 presents the comparison of the two protocols
SE Analysis September 2007 69
Table 7 SNMP and STMP Comparisons
Characteristic SNMP STMP Can send any base date element Yes Yes Bandwidth Efficiency Worse Better (uses
dynamic objects) Supports routing and dial-up Options Options Message Set Supported Limited to 13 Ease of Implementation Easy Hard
Devices with either of the two protocols can use the same communications line with other devices using the same protocols The manufacturer or type of device (traffic signals DMS etc) is not important Each device is assigned an address that is unique on that line or channel which allows the management system to communicate with that device The communication link for C2F can be any type of medium fiber optics cable spread spectrum radio etc It does not matter whether the communications medium is owned or leased by LADOTD The only requirement assumes that communication is a half-duplex poll and response and the time for transmission and the response time for the end device are within the tolerances the devices need to communicate Although STMP is designed to use communication channels with slow transmission rates it is not as bandwidth efficient as proprietary protocols used in the past 122 Standards Applicable to the Project A number of technical standards must be considered in the development of this project There are over 80 ITS standards now being developed by different standards development organizations (SDOs) ITS designers are encouraged by United States Department of Transportation (US DOT) to use SDO approved standards when developing ITS projects Mapping the applicable ITS standards to the project architecture provides a clearer understanding as to how each standard should be considered in design of the project There are three architectural components to which the standards must be applied for this project Center to Field Center-to-Center and Center-to-VehicleTraveler Adhering to these standards will assure interoperability and interchangeability of the projectrsquos components and its overall integration with current ITS operations Table 8 presents the relevant standards for each architectural component that may be used in the implementation of this project
SE Analysis September 2007 70
Table 8 ITS Standards Applicable to Project
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 1101 Simple Transportation Management
Framework (STMF) bull
NTCIP 1102 Octet Encoding Rules (OER) bull
bull
NTCIP 1103 Transportation Management Protocols (TMP)
bull bull
NTCIP 1104 Center-to-Center Having Convention Specification
bull
NTCIP 1201 Global Object Definitions bull NTCIP 1202 Object Definitions for Actuated Traffic
Signal Controller bull
NTCIP 1203 Object Definitions for Dynamic Message Signs
bull
NTCIP 1205 Object Definitions for CCTV Camera Control
bull
NTCIP 1206 Object Definitions for Data Collection and Monitoring (DCM) Devices
bull
NTCIP 1208 Object Definitions for CCTV Switching bull NTCIP 1209 Object Definitions for Transportation
Sensor Systems (TSS) bull
NTCIP 1210 Field Management Stations - Part 1 Object Definitions for Signal System Masters
bull
NTCIP 1211 Object Definitions for Signal Control and Prioritization (SCP)
bull
NTCIP 1400 TCIP Framework Standard bull bull NTCIP 1402 TCIP Incident Management Objects bull bull NTCIP 2101 Pointndashto-Point Using RS-232 Subnetwork
Profile bull
NTCIP 2102 Point-to-Multi-Point Protocol Using FSK Modem Subnetwork Profile
bull
NTCIP 2103 Subnet Profile for Point-to-Point Over RS-232
bull
NTCIP 2104 Ethernet Subnetwork Profile bull NTCIP 2202 Internet (TCPIP and UDPIP) Transport
Profile bull bull
NTCIP 2301 Application Profile for Simple Transportation Management Framework (STMF)
bull
NTCIP 2302 Application Profile for Trivial File Transfer Protocol
bull
NTCIP 2303 Application Profile for File Transfer Protocol
bull bull
SE Analysis September 2007 71
Standard Number
Standard Name C2F C2C Center to VehTraveler
NTCIP 2304 Application Profile for Data Exchange ASN1 (DATEX-ASN)
bull
NTCIP 8003 Profile Frame Work bull bull NTCIP 9001 NTCIP Guide bull bull bull EIA-794 Data Radio Channel (DARC) System bull EIA-795 Sub carrier Traffic Information Channel
(STIC) System bull
IEEE Std 1404
bull bull
IEEE Std 1488 2000
Trail-Use Standard for Message Set Template for ITS
bull bull bull
IEEE Std 1489 1999
Data Dictionaries for ITS bull bull bull
IEEE Std 1512 2000
Common Incident Management Sets for Use by Emergency Management Centers
bull bull
IEEE SH 94633-94638
Analysis of Existing Standards and Those Under Development Applicable to the needs of ITS Short Range and Wide Area Wireless Communications
bull bull bull
ITE-AASHTO TM 103
Traffic Management Data Dictionary bull bull
ITE-AASHTO TM 201
Message Sets for External Traffic Management Center Communications
bull bull
SAE J1763 General Reference Model bull bull bull SAE J2353 Advance Traveler Information Systems
(ATIS) Data Dictionary bull bull
SAE J2354 Advanced Traveler Information Systems (ATIS) Message Sets
bull bull
SAE J2369 ATIS Message Sets Delivered Over Bandwidth Restricted Media
bull
13 Testing Testing fulfills the system engineering requirements of verification and validation Verification can be simple described as ldquowas the system built correctlyrdquo While validation may be described as ldquowas the correct system builtrdquo Testing through the project development until the completion of the project provides for a successful project The use of traceability matrices allows for the stakeholders to ensure the envision system described in the ConOps is the actual functional system deployed During the construction of the project equipment must be tested at various stages to ensure its operability function and performance These tests are detailed in the
SE Analysis September 2007 72
specification document developed to accompany the detail design plans Also once the system is constructed tests on integrating the equipment into the existing system shall be required These tests are also as defined and required by the specifications It is envisioned that during the detail design of this project an advanced traceability matrix will be provided to trace the conception of the project through the testing phase This matrix will allow for LADOTD personnel to check off the project deployment requirement and ensure ultimately a successful final system 14 Maintenance LADOTD shall be the agency responsible for maintaining the equipment deployed as part of this project Currently LADOTD uses contract and agency personnel to provide maintenance on ITS equipment through LADOTDrsquos ITS Division The LADOTD Maintenance Supervisor has been tasked with approximately 30 staff members to ensure the continued function of the various ITS systems statewide LADOTD currently has an anticipated annual budget of $25 million dollars for maintenance for the state It is expected that the maintenance budget will be divided to facilitate each region If any region doesnrsquot use its total amount allocated the money may be shifted to another region for maintenance Also for each project deployment an extended maintenance agreement accompanies the construction contract documents This extended maintenance agreement (contract) requires 1 year of warranty and maintenance service on the system Thereafter that required 1 year LADOTD has the option to extend the warranty through the contractor for an additional 3 years This project is anticipated to include the extended maintenance requirement agreement 141 Life-Cycle Funding Life-cycle funding from the systems engineering prospective is a total project process In other words the total costs (ie need for funding in constant of inflated dollars) associated with the successful development implementation operation and maintenance for the ldquoliferdquo of an ITS project must be determined A life-cycle analysis provides LADOTD with a realistic perspective of funding needs for their ITS projects and programs This information is used to develop future funding requests and in developing benefitcost analysis for their ITS program and individual projects A life-cycle funding analysis for this comprised of three components equipment installation operations and maintenance Equipment installation refers to the actual procurement and installation of ITS equipments For example the purchase and installation for a pedestal mounted DMS is approximately $200000 per sign Additionally estimating the life-cycle funding for ITS equipment must take into account the useful life expectancy of each component For example the useful life-expectancy of a DMS is 8 to 10 years The useful life of fiber optic cable is 20 years and the life expectancy for conduit and structures is 20 years plus One way to estimate equipment cost is to use the component that has the longest life expectancy as a base line Then estimate the replacement
SE Analysis September 2007 73
cycle of other components with shorter life expectancies An example would be if the conduit system lasts 20 years and the DMS only last 5 years then DMS replacement costs will occur 4 times during the project life cycle Estimating cost of operations is straight forward If the project is estimated to last 20 years (before replacement or decommissioning) then LADOTD will need to determine how many staff persons (or contracted maintenance) will be required over that period of time Presented in Appendix B are life cycle cost analyses for this project It should be noted that the quantity of equipment and locations in the life cycle cost analyses are approximated based on conceptual designs The exact quantity and locations of ITS field equipment devices will be further defined in the SOSP and by the Design-Builders actual design Three life cycle cost analyses have been provided in Appendix B The life cycle cost analyses presents the deployed system in 3 scenarios Table B-1 Fully Fiber Table B-2 Fully Wireless and Table B-3 Hybrid Wireless and Fiber Also each scenario uses operations and maintenance (OampM) cost based on the data obtained from the USDOT ITS Unit Cost Database when available The costs are in terms of 2005 dollars The price per unit is based on current LADOTD project estimates The cells are highlighted in yellow where USDOT numbers are used Although some equipment presented has a longer life cycle then 10 years only the first 10 years have been presented It should be noted any replacement cost for equipment that has a life cycle less than 10 years is covered under the cost of OampM Also it is assumed that there is no salvage value at the end of the equipmentrsquos life Maintenance funding for an ITS project is determined by the complexity (ie the type and quantity of devices) and the operational life of the project The longer the system operations the greater the maintenance costs Additionally maintenance costs will be skewed as the equipment ages The older the equipment the more maintenance (staff time and replacement parts) will be required to keep it functioning with in specified limits For planning purposes a general rule-of-thumb for estimating overall annual maintenance costs for an ITS system is 5 percent of the total capital costs Also the 10 year total life cycle cost has been provided in 2 ways First is linear where the annual OampM is continuous for the 10 year period In the second OampM is inflated at an exponential rate of 2 per year
SE Analysis September 2007 74
APPENDIX A
TRACEABILITY MATRIX
SE Analysis September 2007 75
Table A-1 Traceability Matrix
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic ManagementTIM Requirements
61 Traffic ManagementTraffic Incident Management
FR1 Center communication
61 Traffic ManagementTraffic Incident Management
FR11 Exchange of traffic operator data
581 Traffic Incident Management Operations (TIM)
FR111 Traffic conditions
581 Traffic Incident Management Operations (TIM)
FR112 Operating status of field equipments
581 Traffic Incident Management Operations (TIM)
FR113 Maintenance activity status
581 Traffic Incident Management Operations (TIM)
FR114 Incident status
552 Center-to-Center Operations FR12 Traffic information 552 Center-to-Center Operations FR121 Incident information 552 Center-to-Center Operations FR13 Road network conditions for traffic management purposes 552 Center-to-Center Operations FR131 Current traffic information 552 Center-to-Center Operations FR132 Forecasted traffic information 552 Center-to-Center Operations FR133 Road conditions 552 Center-to-Center Operations FR134 Weather conditions 552 Center-to-Center Operations FR135 Traffic incident information 552 Center-to-Center Operations FR14 Exchange of resource request information 552 Center-to-Center Operations FR141 Request of resources to implement special traffic control
measures 552 Center-to-Center Operations FR142 Request of resources to verify an incident 552 Center-to-Center Operations FR15 Exchange of resource deployment status information 552 Center-to-Center Operations FR151 Status of individual resource deployment 552 Center-to-Center Operations FR1511 Status of vehicles 552 Center-to-Center Operations FR1512 Status of equipment 552 Center-to-Center Operations FR1513 Status of materials 552 Center-to-Center Operations FR1514 Status of personnel 552 Center-to-Center Operations FR152 Availability of individual resources 552 Center-to-Center Operations FR1521 Vehicles available 552 Center-to-Center Operations FR1522 Equipment available 552 Center-to-Center Operations FR1523 Materials available 552 Center-to-Center Operations FR1524 Personnel available 552 Center-to-Center Operations FR16 Exchange of incident response status information 552 Center-to-Center Operations FR161 Status of current incident response 552 Center-to-Center Operations FR1611 Summary of the incident status 552 Center-to-Center Operations FR1612 Impact of the incident on the transportation system 552 Center-to-Center Operations FR1613 Traffic management strategies 552 Center-to-Center Operations FR1614 Current response activities 552 Center-to-Center Operations FR1615 Planned response activities 552 Center-to-Center Operations FR17 Coordination emergency plans 552 Center-to-Center Operations FR171 Coordination of emergency management plans 552 Center-to-Center Operations FR172 Continuity of operations plans 552 Center-to-Center Operations FR173 Emergency response plans 552 Center-to-Center Operations FR174 Recovery plans 552 Center-to-Center Operations FR175 Evacuation plans with LADOTD ITS Statewide TMC 552 Center-to-Center Operations FR18 Provide an alert status 552 Center-to-Center Operations FR181 Current status of the emergency alert
SE Analysis September 2007 76
552 Center-to-Center Operations FR182 Driver information systems used to provide the alert
LADOTD ITS Statewide TMC - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR2 Center communication 552 Center-to-Center Operations FR21 Traffic control 551 ITS Equipment Operations FR211 Information transfers that enable remote monitoring of traffic
management devices 551 ITS Equipment Operations FR212 Information transfers that enable control of traffic management
devices 552 Center-to-Center Operations FR22 Alert notification 552 Center-to-Center Operations FR221 Notification of a major emergency 552 Center-to-Center Operations FR2211 Notification of a natural disaster to the public 552 Center-to-Center Operations FR22111 Identification of the alert originator 552 Center-to-Center Operations FR22112 Identification of the nature of the emergency 552 Center-to-Center Operations FR22113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2212 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR22121 Identification of the alert originator 552 Center-to-Center Operations FR22122 Identification of the nature of the emergency 552 Center-to-Center Operations FR22123 Effective time period of the alert 552 Center-to-Center Operations FR22124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2213 Notification of a civil emergency to the public 552 Center-to-Center Operations FR22131 Identification of the alert originator 552 Center-to-Center Operations FR22132 Identification of the nature of the emergency 552 Center-to-Center Operations FR22133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR2214 Notification of a child abduction to the public 552 Center-to-Center Operations FR22141 Identification of the alert originator 552 Center-to-Center Operations FR22142 Identification of the nature of the emergency 552 Center-to-Center Operations FR22143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR22144 Information provided to the public with instructions on how to
respond to the alert
LADOTD District 02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR3 Center communication 542 Incident Management FR31 Exchange resource request information 542 Incident Management FR311 Request of resources to implement special traffic control
measures 542 Incident Management FR312 Request of resources to verify an incident 542 Incident Management FR32 Exchange resource deployment status information 542 Incident Management FR321 Status of individual resource deployment 542 Incident Management FR3211 Status of vehicles 542 Incident Management FR3212 Status of equipment 542 Incident Management FR3213 Status of materials 542 Incident Management FR3214 Status of personnel 542 Incident Management FR322 Availability of individual resources 542 Incident Management FR3221 Vehicles available
SE Analysis September 2007 77
542 Incident Management FR3222 Equipment available 542 Incident Management FR3223 Materials available 542 Incident Management FR3224 Personnel available 542 Incident Management FR33 Incident response status information 542 Incident Management FR331 Status of current incident response 542 Incident Management FR3311 Summary of incident status 542 Incident Management FR3312 Impact of the incident on the transportation system 542 Incident Management FR3313 Traffic management strategies 542 Incident Management FR3314 Current response activities 542 Incident Management FR3315 Response activities 543 Emergency Management
System FR34 Emergency plans
543 Emergency Management System
FR341 Emergency management plans
543 Emergency Management System
FR342 Continuity of operations plans
543 Emergency Management System
FR343 Emergency response plans
543 Emergency Management System
FR344 Recovery plans
543 Emergency Management System
FR345 Evacuation plans
552 Center-to-Center Operations FR35 Alert status 552 Center-to-Center Operations FR351 Current status of the emergency alert 552 Center-to-Center Operations FR3511 Driver information systems 552 Center-to-Center Operations FR36 Road network conditions 552 Center-to-Center Operations FR361 Current traffic information 552 Center-to-Center Operations FR362 Forecasted traffic information 552 Center-to-Center Operations FR363 Road conditions 552 Center-to-Center Operations FR364 Weather conditions 542 Incident Management FR365 Traffic incident information 552 Center-to-Center Operations FR37 Emergency traffic control information 552 Center-to-Center Operations FR371 Status of a system activation implemented in response to an
emergency traffic control request 552 Center-to-Center Operations FR372 Status of a system activation implemented in response to a
request for emergency access routes 552 Center-to-Center Operations FR373 Status of a system activation implemented in response to a
request for evacuation 552 Center-to-Center Operations FR38 Emergency routes 552 Center-to-Center Operations FR381 Ingress routes for access to the scenes 552 Center-to-Center Operations FR382 Ingress routes for access between the scenes 552 Center-to-Center Operations FR383 Ingress routes for access to staging areas 552 Center-to-Center Operations FR384 Egress routes for access to the scenes 552 Center-to-Center Operations FR385 Egress routes for access between the scenes 552 Center-to-Center Operations FR386 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR4 Center communication 552 Center-to-Center Operations FR41 LSP shall provide an alert notification to LADOTD District 02 for
traffic management purposes 552 Center-to-Center Operations FR411 Notification of a major emergency 552 Center-to-Center Operations FR4111 Notification of a natural disaster to the public
SE Analysis September 2007 78
552 Center-to-Center Operations FR41111 Identification of the alert originator 552 Center-to-Center Operations FR41112 Identification of the nature of the emergency 552 Center-to-Center Operations FR41113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR41121 Identification of the alert originator 552 Center-to-Center Operations FR41122 Identification of the nature of the emergency 552 Center-to-Center Operations FR41123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41124 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR41131 Identification of the alert originator 552 Center-to-Center Operations FR41132 Identification of the nature of the emergency 552 Center-to-Center Operations FR41133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR4114 Notification of a child abduction to the public 552 Center-to-Center Operations FR41141 Identification of the alert originator 552 Center-to-Center Operations FR41142 Identification of the nature of the emergency 552 Center-to-Center Operations FR41143 Identification of the effective time period of the alert 552 Center-to-Center Operations FR41144 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR42 Request of an emergency route 552 Center-to-Center Operations FR421 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR422 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR423 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR424 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR43 Request emergency traffic control 552 Center-to-Center Operations FR431 Public safety message on a dynamic message sign 552 Center-to-Center Operations FR432 Place an emergency message on a dynamic message sign 552 Center-to-Center Operations FR44 Coordination of traffic control 552 Center-to-Center Operations FR441 Information transfers that enable remote monitoring of traffic
management devices 552 Center-to-Center Operations FR442 Information transfers that enable control of traffic management
devices
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Traffic Management TIM Requirements
55 System Overview FR5 Center communication 552 Center-to-Center Operations FR51 Alert notification 552 Center-to-Center Operations FR511 Notification of a major emergency 552 Center-to-Center Operations FR5111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR51111 Identification of the alert originator 552 Center-to-Center Operations FR51112 Identification of the nature of the emergency 552 Center-to-Center Operations FR51113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51114 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR51121 Identification of the alert originator 552 Center-to-Center Operations FR51122 Identification of the nature of the emergency 552 Center-to-Center Operations FR51123 Identification of the effective time period of the alert
SE Analysis September 2007 79
552 Center-to-Center Operations FR51124 Information provided to the public with instructions on how to respond to the alert
552 Center-to-Center Operations FR5113 Notification of a civil emergency to the public 552 Center-to-Center Operations FR51131 Identification of the alert originator 552 Center-to-Center Operations FR51132 Identification of the nature of the emergency 552 Center-to-Center Operations FR51133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR51134 Information provided to the public with instructions on how to
respond to the alert 552 Center-to-Center Operations FR5114 Notification of a child abduction to the public 552 Center-to-Center Operations FR5115 Identification of the alert originator 552 Center-to-Center Operations FR5116 Identification of the nature of the emergency 552 Center-to-Center Operations FR5117 Identification of the effective time period of the alert 552 Center-to-Center Operations FR5118 Information provided to the public with instructions on how to
respond to the alert 542 Incident Management FR52 Exchange resource request information 542 Incident Management FR521 Request resources to implement special traffic control measures 581 Traffic Incident Management
Operations (TIM) FR522 Request resources to verify an incident
542 Incident Management FR53 Exchange resource deployment status information 542 Incident Management FR531 Status of individual resource deployment 542 Incident Management FR5311 Status of vehicles 542 Incident Management FR5312 Status of equipment 542 Incident Management FR5313 Status of materials 542 Incident Management FR5314 Status of personnel 542 Incident Management FR532 Availability of individual resources 542 Incident Management FR5321 Vehicles available 542 Incident Management FR5322 Equipment available 542 Incident Management FR5323 Materials available 542 Incident Management FR5324 Personnel available 542 Incident Management FR54 Incident response status information 542 Incident Management FR541 Status of current incident response 542 Incident Management FR5411 Summary of incident status 542 Incident Management FR5412 Impact of the incident on the transportation system 542 Incident Management FR5413 Traffic management strategies 542 Incident Management FR5414 Current response activities 542 Incident Management FR5415 Planned response activities 552 Center-to-Center Operations FR55 Emergency plans 552 Center-to-Center Operations FR551 Emergency management plans 552 Center-to-Center Operations FR552 Continuity of operations plans 552 Center-to-Center Operations FR553 Emergency response plans 552 Center-to-Center Operations FR554 Recovery plans 552 Center-to-Center Operations FR555 Evacuation plans 552 Center-to-Center Operations FR56 Request an emergency route 552 Center-to-Center Operations FR561 Ingress access routes for emergency response vehicles 552 Center-to-Center Operations FR562 Ingress access routes for emergency response equipment 552 Center-to-Center Operations FR563 Egress access routes for emergency response vehicles 552 Center-to-Center Operations FR564 Egress access routes for emergency response equipment 552 Center-to-Center Operations FR57 Request emergency traffic control 552 Center-to-Center Operations FR571 Request to place a public safety message on a dynamic
message sign 552 Center-to-Center Operations FR572 Request to place an emergency message on a dynamic message
sign
SE Analysis September 2007 80
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Traffic ManagementTIM Requirements
55 System Overview FR6 Center communication 552 Center-to-Center Operations FR61 Alert status 552 Center-to-Center Operations FR611 Current status of the emergency alert 552 Center-to-Center Operations FR6111 Driver information systems that are being used to provide the
alert 552 Center-to-Center Operations FR62 Exchange road network conditions 552 Center-to-Center Operations FR621 Road conditions 552 Center-to-Center Operations FR622 Weather conditions 552 Center-to-Center Operations FR623 Traffic incident information 552 Center-to-Center Operations FR63 Emergency traffic control information 552 Center-to-Center Operations FR631 Status of a system activation 552 Center-to-Center Operations FR632 Status of a system activation 552 Center-to-Center Operations FR633 Status of a system activation 552 Center-to-Center Operations FR64 Emergency routes 552 Center-to-Center Operations FR641 Ingress routes for access to the scenes 552 Center-to-Center Operations FR642 Ingress routes for access between the scenes 552 Center-to-Center Operations FR643 Ingress routes for access to staging areas 552 Center-to-Center Operations FR644 Egress routes for access to the scenes 552 Center-to-Center Operations FR645 Egress routes for access between the scenes 552 Center-to-Center Operations FR646 Egress routes for access to staging areas
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations FR7 TDs communication with center 551 ITS Equipment Operations FR71 Traffic flow information 551 ITS Equipment Operations FR711 Raw traffic detector data 551 ITS Equipment Operations FR712 Processed traffic detector data 551 ITS Equipment Operations FR72 Roadside archive data 551 ITS Equipment Operations FR721 Current traffic conditions 551 ITS Equipment Operations FR722 Environmental conditions derived form roadside sensors 551 ITS Equipment Operations FR8 Center communication TDs 551 ITS Equipment Operations FR81 Traffic sensor control information 551 ITS Equipment Operations FR811 Configuration of traffic sensor systems 551 ITS Equipment Operations FR812 Control traffic sensor systems 551 ITS Equipment Operations FR82 Control data collection and monitoring 551 ITS Equipment Operations FR821 Information used to configure data collection 551 ITS Equipment Operations FR822 Information used to control data collection 551 ITS Equipment Operations FR823 Information used to configure monitoring systems 551 ITS Equipment Operations FR824 Information used to control monitoring systems 551 ITS Equipment Operations FR9 Center communication to CCTVs 551 ITS Equipment Operations FR91 Control video surveillance 551 ITS Equipment Operations FR10 CCTVs communication with center 551 ITS Equipment Operations FR101 Traffic images supplied 551 ITS Equipment Operations FR11 Center communication to DMSs 551 ITS Equipment Operations FR111 Roadway information system data 551 ITS Equipment Operations FR1111 Roadside systems that provide driver information 551 ITS Equipment Operations FR1112 Roadside systems that provide driver information 551 ITS Equipment Operations FR1113 Roadside systems that provide driver information 551 ITS Equipment Operations FR12 Center communication with DMSs 551 ITS Equipment Operations FR121 Roadway information system data 551 ITS Equipment Operations FR1211 Roadside systems that provide driver information
SE Analysis September 2007 81
551 ITS Equipment Operations FR1212 Roadside systems that provide driver information 551 ITS Equipment Operations FR1213 Roadside systems that provide driver information 551 ITS Equipment Operations FR13 DMSs communication with center 551 ITS Equipment Operations FR131 Status of the roadway information system 551 ITS Equipment Operations FR1311 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR14 DMSs communication with center 551 ITS Equipment Operations FR141 Status of the roadway information system 551 ITS Equipment Operations FR1411 Current operating status of the dynamic message signs 551 ITS Equipment Operations FR15 TDs shall communicate with LADOTD District 02 551 ITS Equipment Operations FR151 Traffic flow information 551 ITS Equipment Operations FR1511 Raw traffic detector data 551 ITS Equipment Operations FR1512 Processed traffic detector data 551 ITS Equipment Operations FR152 Roadside archive data 551 ITS Equipment Operations FR1521 Current traffic conditions derived from roadside sensors 551 ITS Equipment Operations FR1522 Environmental conditions derived from roadside sensors 551 ITS Equipment Operations FR16 Center communication with TDs 551 ITS Equipment Operations FR161 Control data collection and monitoring 551 ITS Equipment Operations FR1611 Data collection 551 ITS Equipment Operations FR1612 Control data collection 551 ITS Equipment Operations FR1613 Configuration of monitoring systems 551 ITS Equipment Operations FR1614 Control monitoring systems 551 ITS Equipment Operations FR162 Traffic sensor control information 551 ITS Equipment Operations FR1621 Configuration of traffic sensor systems 551 ITS Equipment Operations FR1622 Control traffic sensor systems 551 ITS Equipment Operations FR17 Center communication with CCTVs 551 ITS Equipment Operations FR171 Video surveillance 551 ITS Equipment Operations FR18 CCTVs communication with center 551 ITS Equipment Operations FR181 Traffic images supplied 551 ITS Equipment Operations FR19 CCTVs communication with center 551 ITS Equipment Operations FR191 Traffic images supplied 551 ITS Equipment Operations FR20 Develop operation guidelines prior to project development 551 ITS Equipment Operations FR201 Center control of LCS operations 551 ITS Equipment Operations FR2011 Signal housing location 551 ITS Equipment Operations FR2012 LCS faces interval
Center - ITS Equipment Communications Concept of Operations Traffic ManagementTIM Requirements
551 ITS Equipment Operations PR 1 LCS indication visibility
LADOTD District 02 (Bridge City)RTMC - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR21 High speed communication 55 System Overview FR22 Center communication 543 Emergency Management
System FR221 Traffic operator data
543 Emergency Management System
FR222 Road network conditions
543 Emergency Management System
FR2221 Road conditions
543 Emergency Management System
FR2222 Weather conditions
SE Analysis September 2007 82
543 Emergency Management System
FR2223 Traffic incident information
543 Emergency Management System
FR223 Exchange resource request information
543 Emergency Management System
FR2231 Request of resources to implement special traffic control measures
543 Emergency Management System
FR2232 Request of resources to verify an incident
543 Emergency Management System
FR224 Resource deployment status information
543 Emergency Management System
FR2241 Status of individual resource deployment
543 Emergency Management System
FR22411 Status of vehicles
543 Emergency Management System
FR22412 Status of equipment
543 Emergency Management System
FR22413 Status of materials
543 Emergency Management System
FR22414 Status of personnel
543 Emergency Management System
FR2242 Availability of individual resources
543 Emergency Management System
FR22421 Vehicles available
543 Emergency Management System
FR22422 Equipment available
543 Emergency Management System
FR22423 Materials available
543 Emergency Management System
FR22424 Personnel available
543 Emergency Management System
FR225 Exchange resource coordination information
543 Emergency Management System
FR2251 Resource inventory information
543 Emergency Management System
FR2252 Specific resource status information
543 Emergency Management System
FR2253 Coordination of resource prioritization
543 Emergency Management System
FR2254 Specific requests for resources
543 Emergency Management System
FR2255 Responses that service request
543 Emergency Management System
FR226 Exchange incident reports
543 Emergency Management System
FR2261 Identified incident
543 Emergency Management System
FR2262 Incident location
543 Emergency Management System
FR2263 Incident type
543 Emergency Management System
FR2264 Incident severity
543 Emergency Management System
FR2265 Appropriate incident response
552 Center-to-Center Operations FR227 Coordination of incident response
SE Analysis September 2007 83
552 Center-to-Center Operations FR2271 Coordinated response to incidents 552 Center-to-Center Operations FR22711 Summary of incident status 552 Center-to-Center Operations FR22712 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22713 Impact of the incident on infrastructure 552 Center-to-Center Operations FR22714 Current response activities 552 Center-to-Center Operations FR22715 Planned response activities 552 Center-to-Center Operations FR228 Exchange incident response status information 552 Center-to-Center Operations FR2281 Status of current incident response 552 Center-to-Center Operations FR22811 Summary of incident status 552 Center-to-Center Operations FR22812 Impact of the incident on the transportation system 552 Center-to-Center Operations FR22813 Traffic management strategies for the site 552 Center-to-Center Operations FR22814 Current response activities 552 Center-to-Center Operations FR22815 Planned response activities 552 Center-to-Center Operations FR229 Incident command information 552 Center-to-Center Operations FR2291 Information that supports local management of an incident 552 Center-to-Center Operations FR22911 Resource deployment status 552 Center-to-Center Operations FR22912 Traffic conditions 552 Center-to-Center Operations FR22913 Road conditions 552 Center-to-Center Operations FR22914 Weather conditions 552 Center-to-Center Operations FR22915 Evacuation advice 552 Center-to-Center Operations FR22916 Safe incident response 552 Center-to-Center Operations FR22917 Efficient incident response 543 Emergency Management
System FR2210 Evacuations
543 Emergency Management System
FR22101 Information regarding a pending evacuation
543 Emergency Management System
FR221011 Evacuation zones
543 Emergency Management System
FR221012 Evacuation times
543 Emergency Management System
FR221013 Evacuation routes
543 Emergency Management System
FR221014 Forecast network conditions
543 Emergency Management System
FR221015 Reentry times
543 Emergency Management System
FR22102 In-process evacuation
543 Emergency Management System
FR221021 Evacuation zones
543 Emergency Management System
FR221022 Evacuation times
543 Emergency Management System
FR221023 Evacuation routes
543 Emergency Management System
FR221024 Forecast network conditions
543 Emergency Management System
FR221025 Reentry times
543 Emergency Management System
FR2211 Emergency plans
543 Emergency Management System
FR22111 Emergency management plans
543 Emergency Management System
FR22112 Continuity of operations plans
SE Analysis September 2007 84
543 Emergency Management System
FR22113 Emergency response plans
543 Emergency Management System
FR22114 Recovery plans
552 Center-to-Center Operations FR2212 Alert notifications 552 Center-to-Center Operations FR22121 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR221211 Natural disaster to the public 552 Center-to-Center Operations FR221212 Man-made disaster to the public 552 Center-to-Center Operations FR221213 Civil emergency to the public 552 Center-to-Center Operations FR221214 Child abduction to the public 552 Center-to-Center Operations FR2213 Alert status 552 Center-to-Center Operations FR22131 Current status of the emergency alert 552 Center-to-Center Operations FR22132 Driver information systems
LADOTD ITS Statewide TMC - LADOTD District 02 Communications Concept of Operations Emergency Management Requirements
55 System Overview FR23 Center communication 552 Center-to-Center Operations FR231 Alert notification 552 Center-to-Center Operations FR2311 Notification of a major emergency 552 Center-to-Center Operations FR23111 Notification of a natural disaster to the public 552 Center-to-Center Operations FR231111 Identification of the alert originator 552 Center-to-Center Operations FR231112 Identification of the nature of the emergency 552 Center-to-Center Operations FR231113 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231114 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23112 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR231121 Identification of the alert originator 552 Center-to-Center Operations FR231122 Identification of the nature of the emergency 552 Center-to-Center Operations FR231123 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231124 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR23113 Civil emergency to the public 552 Center-to-Center Operations FR231131 Identification of the alert originator 552 Center-to-Center Operations FR231132 Identification of the nature of the emergency 552 Center-to-Center Operations FR231133 Identification of the effective time period of the alert 552 Center-to-Center Operations FR231134 Information provided to the public with instruction on how to
respond to the alert 552 Center-to-Center Operations FR232 Notification of a child abduction to the public 552 Center-to-Center Operations FR2321 Identification of the alert originator 552 Center-to-Center Operations FR2322 Identification of the nature of the emergency 552 Center-to-Center Operations FR2323 Identification of the effective time period of the alert 552 Center-to-Center Operations FR2324 Information provided to the public with instruction on how to
respond to the alert
LADOTD District02 (Bridge City)RTMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR24 Center communication 543 Emergency Management
System FR241 Exchange resource request information
543 Emergency Management System
FR2411 Request resources to implement special traffic control measures
SE Analysis September 2007 85
543 Emergency Management System
FR2412 Request resources to verify an incident
543 Emergency Management System
FR242 Exchange resource deployment status information
543 Emergency Management System
FR2421 Status of individual resource deployment
543 Emergency Management System
FR24211 Status of vehicles
543 Emergency Management System
FR24212 Status of equipment
543 Emergency Management System
FR24213 Status of materials
543 Emergency Management System
FR24214 Status of personnel
543 Emergency Management System
FR2422 Availability of individual resource
543 Emergency Management System
FR24221 Vehicles available
543 Emergency Management System
FR24222 Equipment available
543 Emergency Management System
FR24223 Materials available
543 Emergency Management System
FR24224 Personnel available
543 Emergency Management System
FR243 Exchange resource coordination information
543 Emergency Management System
FR2431 Coordination of resource inventory information
543 Emergency Management System
FR2432 Resource status information
543 Emergency Management System
FR2433 Resource prioritization
543 Emergency Management System
FR2434 Specific requests for resources
543 Emergency Management System
FR244 Exchange incident response status information
543 Emergency Management System
FR2441 Status of current incident response
543 Emergency Management System
FR24411 Summary of incident status
543 Emergency Management System
FR24412 Impact of the incident on the transportation system
543 Emergency Management System
FR24413 Traffic management strategies
543 Emergency Management System
FR24414 Current response activities
543 Emergency Management System
FR24415 Planned response activities
543 Emergency Management System
FR245 Incident response
543 Emergency Management System
FR2451 Incident response procedures
543 Emergency Management System
FR24511 Summary of incident status
SE Analysis September 2007 86
543 Emergency Management System
FR24512 Impact of the incident on the transportation system
543 Emergency Management System
FR24513 Impact of the incident on infrastructure
543 Emergency Management System
FR24514 Current response activities
543 Emergency Management System
FR24515 Planned response activities
543 Emergency Management System
FR246 Exchange incident reports
543 Emergency Management System
FR2461 Identified incident
543 Emergency Management System
FR2462 Incident location
543 Emergency Management System
FR2463 Incident type
543 Emergency Management System
FR2464 Incident severity
543 Emergency Management System
FR2465 Appropriate incident response
543 Emergency Management System
FR247 Incident command information
543 Emergency Management System
FR2471 Local management of an incident
543 Emergency Management System
FR24711 Resource deployment status
543 Emergency Management System
FR24712 Traffic conditions
543 Emergency Management System
FR24713 Road conditions
543 Emergency Management System
FR24714 Weather conditions
543 Emergency Management System
FR24715 Evacuation advice
543 Emergency Management System
FR24716 Safe incident response
543 Emergency Management System
FR24717 Efficient incident response
543 Emergency Management System
FR248 Evacuations
543 Emergency Management System
FR2481 Pending evacuation
543 Emergency Management System
FR24811 Evacuation zones
543 Emergency Management System
FR24812 Evacuation times
543 Emergency Management System
FR24813 Evacuation routes
543 Emergency Management System
FR24814 Forecast network conditions
543 Emergency Management System
FR24815 Reentry times
543 Emergency Management System
FR2482 In-process evacuation
SE Analysis September 2007 87
543 Emergency Management System
FR24821 Evacuation zones
543 Emergency Management System
FR24822 Evacuation times
543 Emergency Management System
FR24823 Evacuation routes
543 Emergency Management System
FR24824 Forecast network conditions
543 Emergency Management System
FR24825 Reentry times
543 Emergency Management System
FR249 Emergency plans
543 Emergency Management System
FR2491 Emergency management plans
543 Emergency Management System
FR2492 Continuity of operations plans
543 Emergency Management System
FR2493 Emergency response plans
543 Emergency Management System
FR2494 Recovery plans
552 Center-to-Center Operations FR2410 Alert notifications 552 Center-to-Center Operations FR24101 Emergency alerts to be distributed to the public 552 Center-to-Center Operations FR241011 Notification of a natural disaster to the public 552 Center-to-Center Operations FR241012 Notification of a man-made disaster to the public 552 Center-to-Center Operations FR241013 Civil emergency to the public 552 Center-to-Center Operations FR241014 Child abduction 552 Center-to-Center Operations FR2411 Alert status 552 Center-to-Center Operations FR24111 Current status of the emergency alert 552 Center-to-Center Operations FR241111 Driver information systems 543 Emergency Management
System FR2412 Road network conditions
543 Emergency Management System
FR24121 Road conditions
543 Emergency Management System
FR24122 Weather conditions
543 Emergency Management System
FR24123 Traffic incident information
543 Emergency Management System
FR2413 Emergency traffic control information
543 Emergency Management System
FR24131 Status of a system activation
543 Emergency Management System
FR24132 Status of a system activation
543 Emergency Management System
FR24133 Status of a system activation
543 Emergency Management System
FR2414 Emergency routes
543 Emergency Management System
FR24141 Ingress routes for access to the scenes
543 Emergency Management System
FR24142 Ingress routes for access between the scenes
543 Emergency Management System
FR24143 Ingress routes for access to staging areas
SE Analysis September 2007 88
543 Emergency Management System
FR24144 Egress routes for access to the scenes
543 Emergency Management System
FR24145 Egress routes for access between the scenes
543 Emergency Management System
FR24146 Egress routes for access to staging areas
LSP Troop B - LADOTD District 02 (Bridge City)RTMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR25 Center communication 543 Emergency Management
System FR251 Alert notification
543 Emergency Management System
FR2511 Notification of a major emergency
543 Emergency Management System
FR25111 Notification of a natural disaster to the public
543 Emergency Management System
FR251111 Identification of the alert originator
543 Emergency Management System
FR251112 Identification of the nature of the emergency
543 Emergency Management System
FR251113 Identification of the effective time period of the alert
543 Emergency Management System
FR251114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25112 Notification of a man-made disaster to the public
543 Emergency Management System
FR251121 Identification of the alert originator
543 Emergency Management System
FR251122 Identification of the nature of the emergency
543 Emergency Management System
FR251123 Identification of the effective time period of the alert
543 Emergency Management System
FR251124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25113 Notification of a civil emergency to the public
543 Emergency Management System
FR251131 Identification of the alert originator
543 Emergency Management System
FR251132 Identification of the nature of the emergency
543 Emergency Management System
FR251133 Identification of the effective time period of the alert
543 Emergency Management System
FR251134 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR25114 Notification of a child abduction to the public
543 Emergency Management System
FR251141 Identification of the alert originator
543 Emergency Management System
FR251142 Identification of the nature of the emergency
543 Emergency Management System
FR251143 Identification of the effective time period of the alert
543 Emergency Management System
FR251144 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 89
543 Emergency Management System
FR252 Request an emergency route
543 Emergency Management System
FR2521 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR2522 Ingress access routes for emergency response equipment
543 Emergency Management System
FR2523 Egress access routes for emergency response vehicles
543 Emergency Management System
FR2524 Egress access routes for emergency response equipment
543 Emergency Management System
FR253 Request emergency traffic control
543 Emergency Management System
FR2531 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR2532 Request to place an emergency message on a dynamic message sign
LSP Troop B - LADOTD ITS Statewide TMC Communications Concept of Operations Emergency Management Requirements
55 System Overview FR26 Center communication 543 Emergency Management
System FR261 Alert notification
543 Emergency Management System
FR2611 Notification of a major emergency
543 Emergency Management System
FR26111 Notification of a natural disaster to the public
543 Emergency Management System
FR261111 Identification of the alert originator
543 Emergency Management System
FR261112 Identification of the nature of the emergency
543 Emergency Management System
FR261113 Identification of the effective time period of the alert
543 Emergency Management System
FR261114 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26112 Notification of a man-made disaster to the public
543 Emergency Management System
FR261121 LSP shall coordinate with LADOTD ITS Statewide TMC the identification of the alert originator
543 Emergency Management System
FR261122 Identification of the nature of the emergency
543 Emergency Management System
FR261123 Identification of the effective time period of the alert
543 Emergency Management System
FR261124 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR26113 Notification of a civil emergency to the public
543 Emergency Management System
FR261131 Identification of the alert originator
543 Emergency Management System
FR261132 Identification of the nature of the emergency
543 Emergency Management System
FR261133 Identification of the effective time period of the alert
543 Emergency Management System
FR261134 Information provided to the public with instruction on how to respond to the alert
SE Analysis September 2007 90
543 Emergency Management System
FR26114 Notification of a child abduction to the public
543 Emergency Management System
FR261141 Identification of the alert originator
543 Emergency Management System
FR261142 Identification of the nature of the emergency
543 Emergency Management System
FR261143 Identification of the effective time period of the alert
543 Emergency Management System
FR261144 Information provided to the public with instruction on how to respond to the alert
543 Emergency Management System
FR262 Alert notifications
543 Emergency Management System
FR2621 Alerts to be distributed to the public
543 Emergency Management System
FR26211 Notification of a natural disaster
543 Emergency Management System
FR26212 Notification of a man-made disaster
543 Emergency Management System
FR26213 Notification of a civil emergency
543 Emergency Management System
FR26214 Notification of a child abduction
543 Emergency Management System
FR263 Resource request information
543 Emergency Management System
FR2631 Request resources to implement special traffic control measures
543 Emergency Management System
FR2632 Request resources to verify an incident
543 Emergency Management System
FR264 Resource deployment status information
543 Emergency Management System
FR2641 Status of individual resource deployment
543 Emergency Management System
FR26411 Status of vehicles
543 Emergency Management System
FR26412 Status of equipment
543 Emergency Management System
FR26413 Status of materials
543 Emergency Management System
FR26414 Status of personnel
543 Emergency Management System
FR2642 Availability of individual resources
543 Emergency Management System
FR26421 Vehicles available
543 Emergency Management System
FR26422 Equipment available
543 Emergency Management System
FR26423 Materials available
543 Emergency Management System
FR26424 Personnel available
543 Emergency Management System
FR265 Resource coordination information
543 Emergency Management System
FR2651 Resource inventory information
SE Analysis September 2007 91
543 Emergency Management System
FR2652 Specific resource status information
543 Emergency Management System
FR2653 Resource prioritization
543 Emergency Management System
FR2654 Specific requests for resources
543 Emergency Management System
FR266 Incident response status information
543 Emergency Management System
FR2661 Status of current incident response
543 Emergency Management System
FR26611 Summary of incident status
543 Emergency Management System
FR26612 Impact of the incident on the transportation system
543 Emergency Management System
FR26613 Traffic management strategies
543 Emergency Management System
FR26614 Current response activities
543 Emergency Management System
FR26615 Planned response activities
543 Emergency Management System
FR267 Incident response
543 Emergency Management System
FR2671 Incident response procedures
543 Emergency Management System
FR26711 Summary of incident status
543 Emergency Management System
FR26712 Impact of the incident on the transportation system
543 Emergency Management System
FR26713 Impact of the incident on infrastructure
543 Emergency Management System
FR26714 Current response activities
543 Emergency Management System
FR26715 Planned response activities
543 Emergency Management System
FR268 Exchange incident reports
543 Emergency Management System
FR2681 Identified incident
543 Emergency Management System
FR2682 Incident location
543 Emergency Management System
FR2683 Incident type
543 Emergency Management System
FR2684 Incident severity
543 Emergency Management System
FR2685 Appropriate incident response
543 Emergency Management System
FR269 Incident command information
543 Emergency Management System
FR2691 Local management of an incident
543 Emergency Management System
FR26911 Resource deployment status
543 Emergency Management System
FR26912 Traffic conditions
SE Analysis September 2007 92
543 Emergency Management System
FR26913 Road conditions
543 Emergency Management System
FR26914 Weather conditions
543 Emergency Management System
FR26915 Evacuation advice
543 Emergency Management System
FR26916 Safe incident response
543 Emergency Management System
FR26917 Efficient incident response
543 Emergency Management System
FR2610 Evacuations
543 Emergency Management System
FR26101 Pending evacuation
543 Emergency Management System
FR261011 Evacuation zones
543 Emergency Management System
FR261012 Evacuation times
543 Emergency Management System
FR261013 Evacuation routes
543 Emergency Management System
FR261014 Forecast network conditions
543 Emergency Management System
FR261015 Reentry times
543 Emergency Management System
FR26102 In-process evacuation
543 Emergency Management System
FR261021 Evacuation zones
543 Emergency Management System
FR261022 Evacuation times
543 Emergency Management System
FR261023 Evacuation routes
543 Emergency Management System
FR261024 Forecast network conditions
543 Emergency Management System
FR261025 Reentry times
543 Emergency Management System
FR2611 Coordinate emergency plans
543 Emergency Management System
FR26111 Emergency management plans
543 Emergency Management System
FR26112 Continuity of operations plans
543 Emergency Management System
FR26113 Emergency response plans
543 Emergency Management System
FR26114 Recovery plans
543 Emergency Management System
FR2612 Request an emergency route
543 Emergency Management System
FR26121 Ingress access routes for emergency response vehicles
543 Emergency Management System
FR26122 Ingress access routes for emergency response equipment
543 Emergency Management System
FR26123 Egress access routes for emergency response vehicles
SE Analysis September 2007 93
543 Emergency Management System
FR26124 Egress access routes for emergency response equipment
543 Emergency Management System
FR2613 Emergency traffic control
543 Emergency Management System
FR26131 Request to place a public safety message on a dynamic message sign
543 Emergency Management System
FR26132 Request to place an emergency message on a dynamic message sign
LADOTD ITS Statewide TMC - LSP Troop B Communications Concept of Operations Emergency Management Requirements
55 System Overview FR27 Center communication 543 Emergency Management
System FR271 Alert status
543 Emergency Management System
FR2711 Current status of the emergency alert
543 Emergency Management System
FR2712 Driver information systems that are being used to provide the alert
543 Emergency Management System
FR272 Exchange road network conditions
543 Emergency Management System
FR2721 Road conditions
543 Emergency Management System
FR2722 Weather conditions
543 Emergency Management System
FR2723 Traffic incident information
543 Emergency Management System
FR273 Emergency traffic control information
543 Emergency Management System
FR2731 Status of a system activation
543 Emergency Management System
FR2732 Status of a system activation
543 Emergency Management System
FR2733 Status of a system activation
543 Emergency Management System
FR274 Emergency routes
543 Emergency Management System
FR2741 Ingress routes for access to the scenes
543 Emergency Management System
FR2742 Ingress routes for access between the scenes
543 Emergency Management System
FR2743 Ingress routes for access to staging areas
543 Emergency Management System
FR2744 Egress routes for access to the scenes
543 Emergency Management System
FR2745 Egress routes for access between the scenes
543 Emergency Management System
FR2746 Egress routes for access to staging areas
SE Analysis September 2007 94
SE Analysis September 2007 95
Center - ITS Equipment Communications Concept of Operations Emergency Management Requirements
582 Emergency Management Operations
FR28 Center communication with DMSs
582 Emergency Management Operations
FR29 Center communication with CCTVs
582 Emergency Management Operations
FR291 Control of video surveillance
582 Emergency Management Operations
FR30 CCTVs communication with center
582 Emergency Management Operations
FR301 Traffic images supplied
582 Emergency Management Operations
FR31 CCTVs communication with center
582 Emergency Management Operations
FR311 Traffic images supplied
582 Emergency Management Operations
FR32 CCTVs communication with center
582 Emergency Management Operations
FR321 Traffic images supplied
- 51 Purpose
- 52 Scope
- 53 Justification for the ITS Project
- 54 Existing Operations
-
- 541 TrafficRoadway Management
- 542 Incident Management
- 543 Emergency Management
-
- 55 System Overview
-
- 551 ITS Equipment Operations
- 552 Center-to-Center Operations
-
- 56 Stakeholders
- 57 Operational Environment
- 58 Operational Scenarios
-
- 581 Traffic Incident Management Operations (TIM)
- 582 Emergency Management Operations
-
- 59 Summary of Impacts
- 61 Traffic ManagementTraffic Incident Management
- 62 Emergency Management System
- 63 Requirements Traceability Matrix
- 71 High-Level Design
-
- 711 Project Organization
-
- 7111 Hardware and Software Components
-
- 72 Detailed Design
- 81 Communication Technologies
-
- 811 Fiber Optic Cable (Single Mode)
- 812 Cellular Digital Packet Data (CDPD)
- 813 Global System for Mobile Communication (GSM)
- 814 Radio Frequency (Spread Spectrum)
- 815 Terrestrial Microwave Links
- 816 Area Radio Network (ARN)
- 817 Telephone Lease Lines Line
- 818 Code-Division Multiple Access (CDMA)
- 819 Orthogonal Frequency Division Multiplexing (OFDM)
-
- 82 Project Communications
- 111 Procurement Options of ITS Technologies
-
- 1111 Non-Exempt Commodities
- 1112 Exempt Commodities
-
- 112 ITS Hardware Technologies
- 113 Software
- 114 Communications
- 115 Project Procurement Methods Available for Use by LADOTD
- 116 Procurement Method for Project
- 121 Project Standards
-
- 1211 Center-to-Field Standards
-
- 122 Standards Applicable to the Project
- 141 Life-Cycle Funding
-
Related Documents
