Laserfiche WebLink
All Oireelk <br />I[.)iiireck:nir of If'u.ublliic uJtiilliitiies <br />Alpiri1 2, 2020 <br />Through March 2020, we have spent 705 hours supporting data conversion activities, of which 80% of this <br />can be attributable to the increased workload caused by the staff changes, or approximately 560 hours. <br />Sott aui°�e Veandoui. IIIiniIlpact <br />S&S has struggled at times to meet project deliverables and statement of work commitments that have <br />impacted the overall project schedule, including: <br />• Abrupt project start with lack of detailed project plan caused inefficiency early in the project <br />• Poorly planned and initiated BIRD processes added time to the schedule <br />• Inability and unwillingness to produce an acceptable project schedule caused inefficiency and <br />significant effort on the part of the City staff and project management team to rectify this <br />• Unwillingness to start development until all BRDs were signed, which in our experience is atypical <br />• Lack of availability of key team resources <br />136IIhedL e IIIiniIlpacts <br />The preliminary project schedule included by S&S in the SOW consisted of an 11-month implementation <br />project followed by 3-months of post go -live support, but subject to change based on the detailed project <br />planning and establishment of a baseline project plan. The project was initiated in January 2019 and had a <br />planned system cut -over date of November 2019 and ultimate completion in February 2020. <br />After detailed project planning was performed, the baseline schedule projected a April 2020 cut -over, or a <br />15-month implementation. Then in consideration of the items discussed above the project schedule has <br />been extended further to a planned system cut -over date of October 2020. Thus, the implementation has <br />been extended to 22-months and still includes 3 months following for post -go live support. While this is a <br />longer duration than initially estimated, it is not out of line with other similar utility billing implementation <br />projects. The original schedule was an aggressive schedule that could not withstand these changes. <br />The schedule extension is the biggest driver for the contract amendment and has the biggest impact on <br />the additional project management hours required. <br />k L llltliiing Aii'ca is IIIiniIpa t <br />Project Management. Arcadis relied upon the preliminary schedule in the SOW as the basis for engaging <br />a project manager for slightly over 50% utilization for approximately 12 months, which would have carried <br />through the original 11-month system cut -over and provided 1 month of post go -live support. The detailed <br />project plan extended this to a 15-month implementation and then the changes extended the project <br />further to a 22-month implementation, or ultimately 11 additional months of project management. Many <br />project management activities are recurring in nature and occur on a weekly and monthly basis, so the <br />additional schedule requires more work to be performed by both the project manager and project team. <br />Due to our understanding of the City's limited funds, from the beginning we have approached this project <br />with an effort to keep our costs down for the City and provide just enough support. Typically for billing <br />system implementation projects project management support can vary from 50% to 100% utilization. While <br />we have worked hard to keep our project management efforts down, the changes and impacts above have <br />resulted in our actual project management support to be closer to 60% utilization and now extended over a <br />much longer period. We understand the City still needs this additional support. <br />Page: <br />3/5 <br />