My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TRITECH SOFTWARE SYSTEMS 3a
Clerk
>
Contracts / Agreements
>
INACTIVE CONTRACTS (Originals Destroyed)
>
T (INACTIVE)
>
TRITECH SOFTWARE SYSTEMS 3a
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2024 2:42:24 PM
Creation date
11/10/2009 10:39:44 AM
Metadata
Fields
Template:
Contracts
Company Name
TRITECH SOFTWARE SYSTEMS
Contract #
A-2009-155
Agency
Fire
Council Approval Date
9/8/2009
Expiration Date
5/31/2010
Insurance Exp Date
5/1/2010
Destruction Year
2015
Notes
Amends A-2009-057
Document Relationships
TRITECH SOFTWARE SYSTEMS 3
(Amends)
Path:
\Contracts / Agreements\ INACTIVE CONTRACTS (Originals Destroyed)\T (INACTIVE)
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
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. TriTech Responsibilities <br />i. Change Orders will be prepared for submission to the Client when material changes <br />to the SOW are required. <br />Where Project changes require Engineering -level modifications, TriTech will perform <br />requirements capture necessary to prepare required documentation including a <br />HLEE or an OSD for Client review and approval. <br />ill. Where Project changes require Engineering -level modifications, Client will be <br />informed of the delivery mechanism (version and schedule). <br />b. Client Responsibilities <br />When applicable, the Client will identify the services or deliverables that will be <br />subject to a Change Order, per the Agreement between both parties. <br />ii. When applicable, the Client will identify changes to features or functionality related <br />to CAD, Mobile, Interface or any other Subsystem that will require a change order. <br />This process may also include participation with the requirements process. <br />ill. Client will approve and process Change Orders as in a timely manner. <br />3.1 Task Completion Reports <br />As part of the Project controlling process, upon completion of significant milestones and or tasks, TriTech <br />will submit a Task Completion Report CTCR' to the Client. The TCR serves as a formal tool for the purpose <br />of verifying with the Client that work has been completed according to the requirements specified within the <br />SOW and/or related documents. TCRs are presented to the Client by TriTech's Project Manager for <br />signature. Some TCRs may trigger a Project payment, in accordance with the payment terms within the <br />Agreement. Upon execution of a TCR that is tied to a Project payment milestone, the Client will receive an <br />invoice from TriTech's accounting department which must be paid based on the terms and conditions of the <br />Agreement. <br />a. TriTech Responsibilities <br />L TriTech will prepare and submit TCRs for Client's signature upon completion of the <br />applicable task. <br />b. Client Responsibilities <br />i. Client will process TCRs within a five (5) business day period from the time of <br />receipt less any challenges to the validity of the report. <br />J. In the event that Client disagrees with a TCR, Client shall submit to TriTech a <br />written explanation detailing why the Client believes that the subject of the TCR <br />and/or tasks have not been completed in accordance with the Agreement or this <br />SOW. Such notification from the Client shall be provided to the TriTech Project <br />Manager within five (5) business days of receipt of the TCR. <br />Copyright ® 2009 TriTech Software Systems — Based on SOW Template March 2009 <br />Unpublished: Rights reserved under the copyright law of the United States. <br />Confidential <br />
The URL can be used to link to this page
Your browser does not support the video tag.