17 Threat AMS Routing As a result of Current problems Mitigate Start discussions Caltrans (??) inadequate exist already in with 3rd Party partnerships with 3rd the corridor providers party information Medium providers, motorists do not follow our recommendations 18 Threat AMS Signal As a result of This has been a Accept Continue to work this PATH and all Timing inability to agree or point of contention core Plans generate signal in the past stakeholders Medium timing plans the (Francois) launch date of the pilot may slip. 19 Threat Software IEN - Signal As a result of We have decided Mitigate We have decided to 2/9/2017 Control delivery dates for the to not use the not use the IEN for (Joe, Allen, IEN, signal lights will IEN. the pilot. Now the risk Jane) not be able to be moves to obtaining Medium controlled and we an alternative. will slip the launch date 20 Threat Software IEN - CMS As a result of We have decided Mitigate Strong management Control delivery dates for the to not use the IEN focus (Joe, Allen, IEN, local wayfinding but still need to Jane) signs will not be able determine a High to be controlled and solution for we will slip the wayfinding signs. launch date 21 Threat Software Call for As a result of the There is not a Mitigate Management focus Caltrans D7 Projects Call for Projects solid resourced (Allen) Software software portion not plan in place Medium being delivered on time the CC launch date will slip 22 Threat Software Data Hub As a result of the High because of Mitigate We are highly PATH (Brian) data hub not working critical focused on delivering the launch will be component, timing this on time. delayed requirements, High small funding risk and normal software risks. 23 Threat Software PEMS As a result of PEMS There seems to Mitigate Caltrans to answer Caltrans HQ not being updated be some (Raj) the project will not questions at HQ be able to properly regarding the Medium measure or visualize general way in results which these requirements should be met.
17 Threat AMS Routing As a result of inadequate partnerships with 3rd party information providers, motorists do not follow our recommendations Medium Current problems exist already in the corridor Mitigate Start discussions with 3rd Party providers Caltrans (??) 18 Threat AMS Signal Timing Plans As a result of inability to agree or generate signal timing plans the launch date of the pilot may slip. Medium This has been a point of contention in the past Accept Continue to work this PATH and all core stakeholders (Francois) 19 Threat Software IEN - Signal Control As a result of delivery dates for the IEN, signal lights will not be able to be controlled and we will slip the launch date Medium We have decided to not use the IEN. Mitigate We have decided to not use the IEN for the pilot. Now the risk moves to obtaining an alternative. (Joe, Allen, Jane) 2/9/2017 20 Threat Software IEN - CMS Control As a result of delivery dates for the IEN, local wayfinding signs will not be able to be controlled and we will slip the launch date High We have decided to not use the IEN but still need to determine a solution for wayfinding signs. Mitigate Strong management focus (Joe, Allen, Jane) 21 Threat Software Call for Projects Software As a result of the Call for Projects software portion not being delivered on time the CC launch date will slip Medium There is not a solid resourced plan in place Mitigate Management focus Caltrans D7 (Allen) 22 Threat Software Data Hub As a result of the data hub not working the launch will be delayed High High because of critical component, timing requirements, small funding risk and normal software risks. Mitigate We are highly focused on delivering this on time. PATH (Brian) 23 Threat Software PEMS As a result of PEMS not being updated the project will not be able to properly measure or visualize results Medium There seems to be some questions at HQ regarding the general way in which these requirements should be met. Mitigate Caltrans to answer Caltrans HQ (Raj)
i-210_pilot_-_project_management_plan_0.docx