My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
Agmt19 CherryRoad Technologies, Inc.
RedwoodCity
>
City Clerk
>
Agreements
>
2010-2019
>
2019
>
Agmt19 CherryRoad Technologies, Inc.
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/1/2026 4:35:19 PM
Creation date
5/30/2019 11:27:42 AM
Metadata
Fields
Template:
Agreement
Contractor Name
Cherryroad Technologies, Inc.
PROJECT NAME
Configuration, implementation and support of Oracle Fusion, Core and ADP software services ERP update
RMP File Number
304
Date
5/29/2019
MO Ref
19-110
Amendment
Yes
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
248
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
deliverable/milestone has an ID that will be referenced in the Statement of Work, project <br />schedule, project deliverables, and status reports. The table indicates if the item is a deliverable <br />or a milestone. It also indicates if the item is developed in Phase 1 only and applies to all project <br />phases, or if it is reproduced for each project phase. Lastly, the table lists both the City's role <br />and CherryRoad's role in the completion of the deliverable/milestone. <br />ID <br />Deliverable/Milestone <br />Name <br />Deliverable/ <br />Milestone <br />Phase <br />1 <br />Phase <br />2 <br />Phase <br />3 <br />City <br />Role <br />CR <br />Role <br />F01 <br />Init Discovery <br />Questionnaires <br />Deliverable <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />F02 <br />Conduct Prototype 1 <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />F03 <br />Gap Analysis <br />Deliverable <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />F04 <br />Conduct Prototype 2 <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />FOS <br />Conduct Prototype 3 <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />F06 <br />Module Configuration Doc <br />Deliverable <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />F07 <br />Complete System <br />Integration Test <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />FOS <br />Complete User Acceptance <br />Test <br />Milestone <br />Yes <br />Yes <br />Yes <br />Lead <br />Assist <br />F09 <br />Complete Production <br />Support <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />Appendix A, section A.2 includes the detailed definition for each Track 2 - Functional <br />deliverable/milestone listed in the table above. The definitions include the description, <br />acceptance criteria, Redwood City role, CherryRoad role, and assumptions that apply to the <br />individual deliverable/milestone. <br />2.1.3 Track 3 -Development Deliverables/Milestones <br />Track 3 - Development includes seven (7) deliverables/milestones listed below. Each <br />deliverable/milestone has an ID that will be referenced by the Statement of Work, project <br />schedule, project deliverables, and project status reports. The table indicates if the item is a <br />deliverable or a milestone. It also indicates if the item is developed in Phase 1 only and applies <br />to all project phases, or if it is reproduced for each project phase. Lastly, the table lists both the <br />City's role and CherryRoad's role in the completion of the deliverable/milestone. <br />ID <br />Deliverable/Milestone <br />Name <br />Deliverable <br />/ Milestone <br />Phase <br />1 <br />Phase <br />2 <br />Phase <br />3 <br />City <br />Role <br />CR <br />Role <br />D01 <br />Release 1 Prepared <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />D02 <br />Development Approach <br />Deliverable <br />Yes <br />No <br />No <br />Assist <br />Lead <br />D03 <br />Release 2 Prepared <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />D04 <br />Release 3 Prepared <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />DOS <br />Release 4 Prepared <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />D05 <br />Release S Pre ared <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />D67 <br />Production S stem Go Live <br />Milestone <br />Yes <br />Yes <br />Yes <br />Assist <br />Lead <br />Appendix A, section A.3, includes the detailed definition for each Track 3 - Development <br />deliverable/milestone listed in the table above. The definitions include the description, <br />acceptance criteria, Redwood City role, CherryRoad role, and assumptions that apply to the <br />individual deliverable/milestone. <br />EXHIBITA STATEMENTOF WORK <br />ATTY/AGR/2019.118/CHERRYROAD ERP IMPLEMENTATION SERVICES <br />REV: 05-13-19 PR Page 24 of 172 <br />A-10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.