12 Threat System System As a result of the Years of Accept Ensure proper PATH (Joe) Integration Integration complexity of the experience have resources and focus Conflicts integration taught us that are placed on the requirements the complex project by Medium 210 system will not integration management at all be completed on projects often stakeholders time have unexpected occurrences 13 Threat System System As a result of the There are two Accept Ensure proper PATH (Joe) Integration Integration timing requirements challenges here. resources and focus Timing for integration the 1) Data will arrive are placed on the 210 system will not so late it is difficult project by be completed on to integrate it management at all time correctly. 2) The stakeholders High data hub may hit some challenges that mean we cannot load it with data early enough to integrate the data correctly 14 Threat AMS Rules As a result of There is risk when Mitigate We have decided to 2/9/2017 Engine inadequate two programs not merge the (Joe, Allen, coordination, the need to work DSS/Rules Engines Dan) rules engine will not together and there of the two programs be shared across is little programs and may Low communication. not work correctly There is also risk resulting in improper due to future response plans or procurements the need to delay the launch 15 Threat AMS Code As a result of Current Mitigate PATH has received PATH/D7/HQ 2/9/2017 Sharing inadequate sharing experience the needed code. (Joe, Allen, of code among Mike J) Caltrans systems and vendors the system may not Low work correctly resulting in improper response plans or the need to delay the launch 16 Threat AMS Routing As a result of Unknown risks Accept Commission a study PATH (Joe) inadequate or with a high on this and look at ineffective signage potential for the and messaging Medium disrupting our recommendations motorists do not success. Would follow our like more signs on recommendations freeway.
12 Threat System Integration System Integration Conflicts As a result of the complexity of the integration requirements the 210 system will not be completed on time Medium Years of experience have taught us that complex integration projects often have unexpected occurrences Accept Ensure proper resources and focus are placed on the project by management at all stakeholders PATH (Joe) 13 Threat System Integration System Integration Timing As a result of the timing requirements for integration the 210 system will not be completed on time High There are two challenges here. 1) Data will arrive so late it is difficult to integrate it correctly. 2) The data hub may hit some challenges that mean we cannot load it with data early enough to integrate the data correctly Accept Ensure proper resources and focus are placed on the project by management at all stakeholders PATH (Joe) 14 Threat AMS Rules Engine As a result of inadequate coordination, the rules engine will not be shared across programs and may not work correctly resulting in improper response plans or the need to delay the launch Low There is risk when two programs need to work together and there is little communication. There is also risk due to future procurements Mitigate We have decided to not merge the DSS/Rules Engines of the two programs (Joe, Allen, Dan) 2/9/2017 15 Threat AMS Code Sharing As a result of inadequate sharing of code among Caltrans systems and vendors the system may not work correctly resulting in improper response plans or the need to delay the launch Low Current experience Mitigate PATH has received the needed code. PATH/D7/HQ (Joe, Allen, Mike J) 2/9/2017 16 Threat AMS Routing As a result of inadequate or ineffective signage and messaging motorists do not follow our recommendations Medium Unknown risks with a high potential for disrupting our success. Would like more signs on freeway. Accept Commission a study on this and look at the recommendations PATH (Joe)
i-210_pilot_-_project_management_plan_0.docx