csula dms power point presentation

Dynamic Messaging Traffic System

Los Angeles Civic Center Test Site

MGMT485 – Project PresentationMarch 9, 2009

Slide 3

Speaker Introduction

1. Judith Mederos2. Abraham Ceja 3. Hale Atwell4. Eddy Alvarado5. Nela Klepach

Dynamic Messaging Traffic SystemLos Angeles Civic Center Test Site



Slide 2

Presentation Agenda

1. Project Description2. Project Organizational Chart3. Work Breakdown Structure & Schedule4. Project Quality5. Risk Management Plan6. Communication Plan


Slide 4

Video Introduction


http://www.youtube.com/watch?v=qk9LpXUiX4A

http://www.youtube.com/watch?v=qk9LpXUiX4A


Slide 6

Defining the ProblemThe City of Los Angeles – Facts

1. 277 Auto Related Fatalities in 2008

2. 42,831 Auto Related Injuries in 2008



Slide 5

Defining the ProblemThe City of Los Angeles – Facts (con't)

1. 2nd largest City in the Nation 2. 4.5m Residents3. 1,433,200 Total Commuters In/Out

of Downtown Daily4. 365 hrs/yr commuting



Slide 8

Solution: Dynamic Messaging Traffic System

1. Notification of Emergencies and Evacuation Routes

2. Mitigate Traffic Congestion and Traffic Collisions3. Emergency Vehicle Prioritization through Signal

Preemption4. Interoperability among Emergency Services

Agencies



Slide 7

Why the City of Los Angeles Civic Center?

• Population• Geography• Symbolism



Slide 9

Dynamic Messaging Traffic System: Components

• Dynamic Messaging Sign • Intelligent Traffic Controller • Municipal Vehicle Transponder • System Management Software



Slide 10

Components (con't)Dynamic Message Sign (DMS)

1. Traffic Information / Conditions2. Emergency Vehicle Notification3. Evacuation Instructions / Routes4. Amber Alert / School Zone Notification5. Weather and Road Conditions6. Major Event Information



Slide 11

Components (con't)Intelligent Traffic Controller (ITC)

1. Emergency Vehicle Prioritization2. Wireless Communication

o DMSo TMC / EOC

3. Manual Intersection Control



Slide 12

Components (con't)Municipal Vehicle Transponder (MVT)

1. Wireless Activation of ITC2. GPS – Automatic Vehicle Location3. Vehicle to Vehicle Text-Based

Messaging(Backup Communications Interoperability)

4. Incident Data Collection (Speed, Direction, Time)

5. In-vehicle Display



Slide 13

Components (con't)System Management Software (SMS)

1. Wireless Public Message Broadcasting2. Web-Based Reporting3. Vehicle and Route Display4. Incident Data Display - Asset Tracking



Slide 15


Traffic Controllers

LADOT / LASD

Vehicle TranspondersLAPDLAFD

DHS / FPS


Slide 18



Slide 19

Defining the Test Site ProjectTest Site Specifications

1. 21 Intersections2. 84 Dynamic Signs3. 14 Vehicle Transponders4. 1 Systems Mgmt. Software5. $2.25m6. 20 Month Duration



Slide 20


Dynamic Messaging Traffic System

City of Los Angeles

City of L.A Parking Enforcement

L.A Dept. of Transportation

County of Los Angeles

U.S. Dept. of Homeland Security

Los Angeles Police Dept.

Los Angeles Fire Dept.

Traffic Control for Installation

Research and Specs Determination

Identification & selection of test

sites

-Vendor list-Selection-E-Views

-Purchase-Shipping

-Inspection-Training

-Software Procurement

Software Installation / Traffic

Mgmt Center

Street Installation DOT

Engineers

Software Training E-Views & DOT

Engineer

Vehicle Installation (8)


L.A. Co. Sheriff’s Dept.

Federal Protective

Service

Software Procurement

Software Installation Emergency Operations

Center


Officer Training E-Views & LAPD

Engineer

LAFD Training & Equipment Specialist

Software Training E-views & LASD Engineer

Software Training E-views & LASD

Engineer

Test Execution Full Deployment (6 months)

Defining theTest Site

ProjectOrganizationChart


Slide 21

Defining the Test Site ProjectCity of Los Angeles Parking Enforcement


1.Notify Commuters2.Direct Traffic3.Public Safety


Slide 22

Defining the Test Site ProjectLos Angeles Dept. of Transportation


• Research & Specs Determination

• Test Site Identification & Selection

• Vendor list, Selection, E-Views• Purchase, Shipping, Inspection,

Training• Street Installation & DOT

Engineers

• Software Procurement• TMC Software Installation• Software Training

E-Views & DOT Engineer• Test Execution, Full Deployment

(6 months)


Slide 23

Defining the Test Site ProjectFirst Responders


TestExecutionFull Deployment(6 Months)

1. LAPDo Vehicle Installation (8)o Officer Training E-Views & LAPD Engineer

2. LAFDo Vehicle Installation (4)o Firefighters Training & Equipment Specialist

3. FPSo Vehicle Installation (2)o Software Training E-views & LASD Engineer


Slide 24

Defining the Test Site ProjectLos Angeles Co. Sheriff’s Dept. (LASD)


1. Software Procurement.2. Software Installation

Emergency Operations Center3. Software Training

E-views & LASD Engineer4. Test Execution, Full Deployment

(6 months)


Slide 25

Defining the Test Site Project

Steering Committee



Slide 26

Defining the Test Site ProjectWork Break Down Schedule – Vendor Selection


1. 29 Day Duration2. Involves Manager, Purchasing Manager &

Engineer3. Developing Purchasing List4. Contacting Vendors5. Selecting Vendors


Slide 27

Defining the Test Site ProjectWork Break Down Schedule – Purchase Equipment


1. E-ViEWS Safety Systems2. One Week Duration3. Involves Purchase Manager4. Purchasing of DMS, Software, Controllers, &

Vehicle Transponders


Slide 28

Defining the Test Site ProjectWork Break Down Schedule – Shipping & Receiving


1. 5 Week Duration2. Involves Manger, Engineer & Technician3. Inspecting Equipment and Tagging it as

Government Property.


Slide 29

Defining the Test Site ProjectWork Break Down Schedule – Installation


1. 34 Week Duration2. Involves Manager, Engineer, Technician, &

Traffic Controllers3. Preparation of Infrastructures & Traffic Routing4. Installation & Connection of Hardware &

Software5. Quality Control Inspections


Slide 30

Defining the Test Site ProjectWork Break Down Schedule – Training


1. 4 Week Duration2. Involves Trainers, Operators, Police, Fire,

& Federal Officials3. Training for Both Hardware & Software

Usage


Slide 31

Defining the Test Site ProjectWork Break Down Schedule – Operations


1. 6 Month Duration2. Involves Operators, Police, Fire & Federal

Officials3. Consists of the in field testing of the equipment

and programs.


Slide 32

Defining the Test Site ProjectSchedule


1. Our resource pool consists of Engineers, Managers, Technicians, Purchasing Manager, Operators, Traffic Controllers, and Police, Fire & Federal Officers.

2. Due to the specific sequence of events that this project must undertake there are several instances where our resources our disproportionately spread, however at no time are we having to use overtime to meet demand.

3. Cost estimates were calculated using the numbers we have received from out main equipment supplier, E-Views, and the labor estimated were made based off of industry averages.


Slide 33

Defining the Test Site ProjectIntermediate Quality Measures


• Quality Controlo Remains at the quality level

• Cause-and-effect diagramo Collaborative ideaso Preventative solutions to problems


Slide 34

Defining the Test Site ProjectQuality Objectives


• Meets Requirement Specifications:1. Reduction in Traffic Hazards2. Prevents Accidents3. Lower Mortality rate4. Reduced Emergency Vehicle Response Time

• Quality assurance:1. Performing the planned activities2. Implementing the necessary actions3. Continuous process of monitoring


Slide 35

Defining the Test Site ProjectMeasuring Quality


• Determinates to Measure Final Product 1. Decreased Traffic Collisions2. Decreased Tort Claims 3. First Responder Safety Perception Surveys4. Government Employee Surveys

• Customer Expectations1. Defining Specific Customer Outcomes2. Key Measures


Slide 36

Defining the Test Site ProjectEnsuring Quality


• Agreement Between the Project Team and Customer

• Continuous Training• Configuration Management • Close Out (Post-Completion) Review • Everyone is Responsible for Quality

Responsibility


Slide 37


Risk Management Plan


Risk Likelihood Impact Overall

Unsuccessful Product

Low High Medium

Ineffective Software

Operator(s)

Low Medium Low

Improper Software Training

Low Medium Medium

Vain Security Measures

Low High Medium

Legend Risk LevelHigh 1

Medium 2

Low 3


Slide 38


Risk ResponsePlanning


Possible Risk Event Plans to Address Risk

Defective hardware/software Reduce risk:• Employ best technical team• Use mature computer aided system engineering

tools• Outside specialists 4 system review• Perform extensive tests & evaluations

Failing 2 Meet Project Deadline Reduce risk:• Stride to adhere to master project plan• Critical paths• Best workers

Traffic Collisions/(Unforeseen Events) Contingency plan:-Create public awareness -Training on systems- Alternative routes


Slide 39

Defining the Test Site ProjectCommunication Plan


1. LADOT* 2. E-Views3. LAPD4. LAFD5. LASD – Emergency Operations Bureau (EOB)6. DHS – Federal Protection Service*7. Los Angeles Parking Enforcement8. Government Employees9. Commuter Public*10.Downtown L.A. Neighborhood Council (DLANC)


Slide 40

Defining the Test Site ProjectCommunication Plan (Cont.)


Who LADOT

What • Purchasing, installation of hardware/software• Operation and monitoring of system

When /How

• Daily basis via personal, telephonic, electronic communication• Weekly meetings


Slide 41



Who Dept of Homeland Security – Federal Protective Service

What • Initiation of the project •installation of vehicle transponders• Experimentation process

When /How

• Bi-Weekly electronic communication & written performance evaluation


Slide 42



Who Commuter Public

What • Hardware installation- pre, during & after• Traffic controls – delays

When /How

• Local media news conference regarding launching of test sites • Road signs next to test sites (pre-installation)


Slide 43

“THE AGENDA”


Executive Office of the President of the United StatesThe Agenda – Homeland Security

Protect Americans from Terrorist Attacks and Natural Disasters:• Allocate Funds Based on Risk• Prepare Effective Emergency Response Plans• Support First Responders• Improve Interoperable Communications Systems• Working with State and Local Governments and the Private

Sector


Slide 14

Why DMTS?1. Wireless, Scalable, Upgradable Systems2. Modular Architecture – Incrementally Deployable3. Common Infrastructure for Multiple Applications4. Compatible w/ Existing Preemption Systems & Cabinets5. Compatible w/ most City Networks (Fiber, Ethernet, WiFi)6. Multi-Agency Solution for Municipalities7. Convenient Maintenance 8. All-inclusive Dynamic System



Slide 44

Summary


CRITICAL PUBLIC SAFETY TECHNOLOGY+ INCREASES PUBLIC AND FIRST RESPONDER COORDINATION & SAFETY+ ENHANCES TRAFFIC EFFICIENCIES WITHIN EXISTING INFRASTRUCTURE+ PROVIDES EMERGENCY AND OTHER IMPORTANT MUNIPCAL PUBLIC MESSAGING CAPABILITIES= COMPREHENSIVE & COST EFFECTIVE SOLUTION


Slide 45


AND THIS IS ONLY THE TIP OF THE ICEBERG…ANOTHER 90% IS BELOW THE SURFACE


Slide 46

Questions and Answers


csula dms power point presentation

Documents