Laserfiche WebLink
12. Project Phase — The highest level in which project work is organized is identified as a project <br />phase. For the City of Redwood City project there are three project phases: Phase 1 Financial <br />Management System (FMS), Phase 2 Human Capital Management (HCM), and Phase 3 <br />Extended HCM. Each project phase aligns with a set of City business areas (i.e. General <br />Ledger, Vendor Management, Purchasing/e Procurement, etc.). The Statement of Work then <br />organizes the implementation approach, implementation timeline, implementation team, and <br />payment schedule by project phase. <br />13. Project Team — The project team is the joint group of City and CherryRoad staff assigned to <br />the Oracle Cloud implementation project for the City of Redwood City. <br />14. Prototype — For each project phase, three separate prototypes will be conducted. Prototypes <br />are a series of work sessions where CherryRoad team members will demonstrate designated <br />requirements by showing functions, features, and capabilities of the Cloud Applications. <br />15. Release—A release is a planned cycle of application configuration, reports, interfaces, <br />conversions, and security setup that is completed to prepare the non -production environment <br />for key project activities such as prototype sessions, test cycles, and end user training. Within <br />each project phase there will be five releases. <br />16. Requirements Traceability — Requirements traceability is the ability to follow the life of a <br />requirement through the implementation life cycle, identifying the functionality used to achieve <br />the requirement and the satisfactory testing and validation of that system functionality. <br />17. Requirements Traceability Matrix (RTM) —The requirements traceability matrix (RTM) is a <br />spreadsheet that links requirements and test results, thereby demonstrating the scope of <br />approved requirements has been achieved by the implementation of the Oracle Cloud system. <br />18. Redwood City Role — The Redwood City Role is the function the City serves in the completion <br />of project deliverables and milestones. The Redwood City Role is defined in Appendix A for all <br />project deliverables and milestones. <br />19. User Acceptance — User acceptance is the result of the completion of the User Acceptance <br />Test cycle. During the cycle of testing the City to ensures that the system is providing the <br />required functionality without error in a production environment. <br />20. Final Acceptance - Final Acceptance is signified by the completion of any conditionally <br />accepted issues from User Acceptance Testing and resolution, or mutually agreed upon <br />resolution plan, for issues identified during the Production Support period following go live. <br />21. Work Breakdown Structure (WBS) — The work breakdown structure is a hierarchically <br />organized representation of all the project work. The WBS divides the project tasks into <br />smaller, manageable work packages for maintaining better control of the project tasks. A WBS <br />numbering convention will be included in the project schedule, which is developed using <br />Microsoft Project. <br />22. Work Breakdown Structure (WBS) Diagram - In addition to the project schedule numbering <br />convention, a WBS diagram has been created to provide a graphical depiction of the project <br />phase deliverables and milestones. <br />EXHIBIT STATEMENT OF WORK <br />ATTY/AGR/2019.118/CHERRYROAD ERP IMPLEMENTATION SERVICES <br />REV: 05-13-19 PR Page 16 of 172 <br />A-2 <br />