My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25B - AGMT - PD SOFTWARE SYS
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2015
>
11/17/2015
>
25B - AGMT - PD SOFTWARE SYS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/12/2015 2:33:31 PM
Creation date
11/12/2015 1:58:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
25B
Date
11/17/2015
Destruction Year
2020
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.
/
204
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
5,3 �ha11� M�rl�gemet7� Prgce�s <br />Either party can request changes to the scope of the project at any time. Since a change may affect the price, <br />project deliverables, this SOW, and/or the supporting project schedule, both parties must approve each <br />change in writing. <br />The purpose of the Change Management Process is to manage any significant changes to the Project as <br />described in this SOW or related documents as referenced within the SOW. These changes may include, but <br />are not limited to a modification to Project scope, Standard or Custom products' functionality, TriTech and <br />Client's identified toles and responsibilities, Project payment terms, and modifications to the scope or <br />delivery location of services within the Project. All significant changes must be documented through the <br />Change Management Process. The type of documentation needed will depend on the nature and significance <br />of the change. <br />A Project Change Order will be the vehicle for communicating and approving of the changes, Whether <br />initiated by the Client or TriTech, all Change Orders will be documented by the TriTech Project Manager. <br />The Change Order shall describe the requested change, the party requesting the change, and the effect the <br />change will have on the project, including the price, project deliverables, this SOW, the supporting project <br />schedule. <br />All Change Orders must go through the TriTech's internal approval process before they can be presented to <br />the Client for review and approval. Once the Project Change Order is generated, the Client Project Manager <br />and TriTech Project Manager will review the proposed change and communicate as necessary to answer any <br />questions, and/or work to resolve any issues preventing acceptance of the Project Change Order by both <br />parties. Upon the approval by both parties the Project Change Order will be authorized for implementation. <br />The creation of some Project Change Orders may, depending upon the scope of the requested change, require <br />fees in order for TriTech to properly investigate and scope the requested change. If additional fees are <br />required by TriTech to create a Change Order, those fees will be identified and communicated to the Client <br />Project Manager prior to TriTech's investigation of the requested change. In such situations, TriTech will <br />only proceed with the investigation required to create the Change Order if the Client has agreed to pay the <br />additional fees associated with creation of the Change Order. <br />Additional deliverables or Project deletions in terms of Software and services will require a mutually agreed <br />upon Change Order. <br />53.1 TriTech Responsibilities <br />a) Change Orders will be prepared for submission to the Clicnt when required. <br />b) Where Project changes require Engineering -level modifications, TriTech will perform <br />requirements capture necessary to prepare required documentation including a high level <br />description of the change for Client review and approval, <br />c) Where Project changes require Engineering -level modifications, Client will be informed of the <br />delivery mechanism (version and schedule). <br />53.2 Client Responsibilities <br />a) When applicable, the Client will identify the services or deliverables that will be subject to a <br />Change Order, per the Agreement between both parties. <br />b) When applicable, the Client will identify changes to features or functionality related to CAD, <br />Mobile, Interface or any other Subsystem that will require a change order. This process may also <br />include participation with the requirements process. <br />o) Client will approve and process Change Orders in a timely manner. <br />15 <br />25B -61 <br />
The URL can be used to link to this page
Your browser does not support the video tag.