Laserfiche WebLink
Porterhouse | City of Pleasanton, California | Statement of Work No. 001 | Page 19 <br />produces each cycle's document, including accessible, screen reader ready output, <br />structured to support GFOA Distinguished Budget Presentation Award submission. <br />2i. Training and Enablement <br />Training for the central budget office and department fiscal staff, with side-by-side support <br />during the first budget input cycle where timing allows. Pleasanton is a lean organization, so <br />training is not an afterthought: it is the primary product. Porterhouse manages the process so <br />departments without dedicated fiscal staff are supported directly. <br />3. Delivery Approach and Timeline <br />The engagement runs 16 weeks, milestone-based, with a target start of Monday, May 10, 2027 <br />and completion by Friday, August 27, 2027. This window follows the City's April biennial budget <br />workload and finishes ahead of the September and October year-end close and audit period, <br />leaving September for City-side fine-tuning and additional department training. Work does <br />not need to run continuously: Porterhouse plans stops and starts around the City's peak <br />periods, and because that flexibility is scoped up front it carries no cost impact. <br />Phase Weeks Window (2027) <br />Planning 1 May 10 to May 14 <br />Architect & Configure 7 May 17 to July 2 <br />Testing 4 July 5 to July 30 <br />Deploy 1 August 2 to August 6 <br />Post Production Support 3 August 9 to August 27 <br />Total 16 May 10 to August 27 <br /> <br />A week-by-week staffing plan showing when City staff are needed, for how many hours, and <br />when they are not needed at all accompanies this SOW in the Estimate and Timeline <br />workbook. <br />4. Deliverables, Milestones, and Acceptance <br />Delivery is milestone-based: discrete, tangible deliverables that are tested and signed off, not <br />hours on a clock. Per PSA Section 3.4, the milestone Deliverables marked "Yes" below are <br />subject to acceptance, and Porterhouse does not invoice the associated milestone until <br />acceptance. M1 is invoiced at SOW execution. <br />Docusign Envelope ID: 0FE3D53F-485C-88F0-83B1-0E900318BA33