My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25E - AMEND AGMT FOR POJECTDOX
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2020
>
12/15/2020
>
25E - AMEND AGMT FOR POJECTDOX
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/10/2020 4:44:24 PM
Creation date
12/10/2020 4:37:38 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Planning & Building
Item #
25E
Date
12/15/2020
Destruction Year
2025
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
24
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).
View images
View plain text
a ✓o"\IV e, <br />software <br />3. Customer and its third parties and/or subcontractors will fulfill any hardware/software requirements, as identified to allow <br />communication between Avolve Software and the Customer's permitting system in a timely fashion in order to keep the Project <br />Plan on schedule. <br />4. Customer and its third parties and/or subcontractors will fulfill the hardware requirements, as outlined in the System <br />Implementation Guides (standard end user document(s) that accompany each version of the Software) in a timely fashion in <br />order to keep the Project Plan on schedule. <br />5. This best approach package to implementation relies on partnership with the jurisdiction to achieve desired go -live and pape less <br />goals. To that end, a not to exceed 314 hours (+178 hours if all optional services are purchased) have been allocated to services <br />and training on this project. In the event scope expands or delays account for incremental hours to be required, a Change <br />Request(s) will be issued for the incremental costs associated with delay or expansion. Should the customer cause or contribute <br />to the delay of any Deliverable, Avdve may elect to revise the Project Plan accordingly to compensate for the delay and invoice <br />for any applicable milestone payments to that point of the project. <br />6. Al parties will reasonably prioritize their efforts to meet the Project Plan schedule in order to achieve a rapid roll out model. In <br />doing so, it is understood by all parties that multiple tasks may be in process at one time and Avdve may have more than one <br />Professional Services team member working on the project at one time. <br />7. Client will provide adequate Project management for their own resources, and/or third parties, to collaborate with Avolve's project <br />manager. Client subject matter experts and applicable users will be accessible and available in a timely fashion and for adequate <br />and reasonable durations. Avdve will make sure that scheduling of interviews and meetings are adequately in advance of these <br />resource allocations. <br />8. Customizations/Extensions required may result in increased schedule and budget, but only if documented and approved within <br />Assurance Services ancilor a Change Request. <br />9. Avolve is planning to fully leverage ProjectDox as is, utilizing all built in configuration features to meet the business needs. <br />10. Any optional items chosen in the Purchase Agreement/Sales Order are not included here and would require a modification to this <br />Statement of Work. <br />11. Customer understands that an ePlan Life Cycle implementation is a very significant digital transformation enterprise project that <br />requires dedicated change management from the Customers staff. This will be key for the success of the Customer. <br />12. Work will not begin until an executed copy of all paperwork is complete. Work will begin at the earliest possible date at which <br />Avolve resources and Customer resources are available or as otherwise agreed to. <br />13. Avolve and Customer agree to cooperate in good faith to complete the Services and Deliverables in a timely and efficient <br />manner. <br />14. Recording of Avolve provided training or UAT (user acceptance testing) sessions is not permitted. <br />15. Al training classes unless otherwise noted are limited to 12 persons maximum per class <br />"Configuration options are as described by ProjectDox documentation and as evidenced by ProjectDox administration screens. Minor <br />changes to Avolve ProjectDox Best Practices (Best in Class) workflows are changes to activate/deactivate and/orparametrize with <br />variables, existing steps in the Best Practices workflows. Customization of additional products and modules are to be within the <br />bounds and scope of the respective core product(s) and modifications are limited to those that are allowed by core product design. <br />25E-19 Page 14of19 <br />
The URL can be used to link to this page
Your browser does not support the video tag.