Laserfiche WebLink
<br />Risk Statement <br />Impact (H,M,L)Impact Justification Probability (H,M,L)Symptom/Warning Signs <br />(that risk will or has occurred) <br />Response <br />Strategy <br />(Accept <br />Avoid <br />Mitigate <br />Transfer) <br />Response Strategy Measures <br />Contingency Plan <br />(plan if risk is realized; <br />enter 'none' if there is no <br />plan) <br />If Cities don't provide <br />sufficient, qualified <br />resources to meet project <br />needs during the selection <br />process, they may not end <br />up choosing the best fit <br />solution <br />H Cities could appoint high- <br />level staff to serve on the <br />selection committee, and <br />identify preference for <br />length of POCs <br />M At the end of the POC, the <br />Cities selection staff is unable <br />to select a winner <br />Accept The Cities could add additional <br />POC sessions (via WEBEX) <br />None <br />If the vendor or Cities are <br />unable to complete data <br />conversion activities, then <br />the ERP system may not <br />have necessary historical <br />and/or setup information <br />M Inability to convert data <br />may cause project delays <br />and/or impact resources <br />or project costs if manual <br />entry of data is required. <br />Note that impact will vary <br />depending on which data <br />is unable to be converted. <br />M Vendor conversions are not <br />working or testing indicates <br />inefficient/ineffective conversion <br />processes <br />Mitigate Work with selected vendor to <br />identify all data that needs to be <br />converted and document <br />conversion requirements <br />Limit historical data to <br />be converted <br />If Cities don't have sufficient <br />resources to meet project <br />needs and operational <br />responsibilities during <br />implementation, there may <br />be project delays <br />L The Cities could continue <br />to use current system <br />until the new ERP system <br />is ready for <br />implementation. There is <br />no firm deadline for when <br />the system must be <br />transitioned. <br />M Delays in project schedule Mitigate - Obtain Sponsor approval/support <br />for resource assignment to <br />project <br />- Backfill/cross train key SME <br />positions needed to support <br />project to allow SMEs to work on <br />project <br />None <br />If staff does not accept and <br />adapt to change brought <br />about by the new ERP <br />system, the Cities will not <br />realize full ROI and <br />employees will be <br />dissatisfied frustrated <br />H Employee frustration <br />reduces moral <br />H - Employees comments not <br />understanding the need for <br />change <br />- Employees not participating <br />in training <br />- Employees complaining <br />about new system <br />- Issues with acceptance <br />testing <br />- Employee surveys (if done) <br />indicate employees unhappy <br />- Employees continue to use <br />status quo systems and <br />processes <br />Mitigate - Ensure the Cities assigns <br />resources to support planning for <br />the change and providing direction <br />for helping employees understand <br />and embrace the change <br />- Provide coaching/training to <br />managers and supervisors to help <br />them guide employees through <br />the change <br />None <br />If new Chart of Accounts <br />design does not effectively <br />support business <br />requirments, system <br />implementation and <br />acceptance will be delayed <br />H Potential to significantly <br />delay project acceptance <br />or result in decreased <br />system usability <br />H - Issues mapping current GL to <br />new GL <br />- Issues developing use cases <br />for the new GL design <br />- During initial testing, users <br />find the new GL is not <br />supporting business needs <br />Mitigate - Build in sufficient time to design <br />chart of accounts <br />- Ensure appropriate SMEs are <br />assigned to the design process <br />- Engage SMEs in design of COA <br />to make sure it is acceptable to <br />them <br />- Engage vendor COA expert to <br />help Cities design COA <br />- Leverage outside COA <br />expertise, if available, in design of <br />COA <br />None <br />Attachment 1 to Exhibit A <br />REV: 06-15-17 JS <br />ATTY/AGR/2017.127/NEXLEVEL-FSR CONSULTANT <br />Page 28 of 28 <br />6.1.E. - Page 43