My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TRITECH SOFTWARE SYSTEMS 2
Clerk
>
Contracts / Agreements
>
INACTIVE CONTRACTS (Originals Destroyed)
>
T (INACTIVE)
>
TRITECH SOFTWARE SYSTEMS 2
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2024 2:41:48 PM
Creation date
10/9/2006 12:09:16 PM
Metadata
Fields
Template:
Contracts
Company Name
TRITECH SOFTWARE SYSTEMS 2
Contract #
A-2006-256
Agency
FIRE
Council Approval Date
9/5/2006
Insurance Exp Date
5/1/2007
Destruction Year
2015
Notes
Amended by A-2006-256A, A-2008-331
Document Relationships
TRITECH SOFTWARE SYSTEMS 2a
(Amended By)
Path:
\Contracts / Agreements\ INACTIVE CONTRACTS (Originals Destroyed)\T (INACTIVE)
TRITECH SOFTWARE SYSTEMS 2b
(Amended By)
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.
/
160
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
Exhibit A: Statement of Work <br />TriTech shall: <br />a. Review with Santa Ana personnel the specific TriTech CAD application functionality during an <br />onsite demonstration of the product. This onsite demonstration will be referred to as the system <br />orientation. During the system orientation, the TriTech appointed business analyst will gather <br />pertinent information necessary for the initial building of the client's base system. <br />b. Identify, in writing on the action item log, site -specific alterations that will be made as part of the <br />standard installation process (i.e., changing headers and footers to read "City of Santa Ana Fire <br />Department', etc.). The instrument used will be a document referred to as the "module building <br />sheet." This document outlines specific build requirements for the client's VisiCAD system. A <br />separate document will be provided that will be considered a working journal for the duration of the <br />project. This document details high level issues or tasks. Assigns the owner, classifies the issue, <br />and provides a section for comments. <br />C. Provide an on -site working demonstration of the product for review (not merely written material). <br />The onsite product will be delivered either following the onsite software demonstration following <br />the DOLF. Or, prior to the DOLF for the purposes of executing the DOLF at the client's site. <br />d. Review with City personnel outstanding configuration requirements and provide written assurance <br />that such changes will be included in the next available TriTech CAD version release. Versions <br />are released on an annual cycle. Changes will be considered so long as they are submitted within <br />the requirements capturing phase for the next version. <br />Santa Ana shall: <br />a. Assign dispatch personnel to attend the pre -configuration review. <br />b. Identify requirements for future implementation, based on TriTech's RFP responses. <br />Completion Criteria: <br />This task is considered complete when TriTech has identified all configurable options for the CAD <br />application, has documented the site -specific changes to be included in the base implementation and has <br />identified those modifications that will be provided as part of the next available TriTech CAD release. <br />Task i-D: GeoFile (MAP) Build Workshop <br />Objective: To initiate the development of a dynamic GIS process for use by the TriTech products. <br />Task Description: <br />The workshop will enable Santa Ana to provide existing ArcView Shape Files and other material to be <br />used for the creation of boundary maps. <br />Responsibilities: <br />TriTech shall: <br />a. Conduct an initial conference call to discuss and evaluate source data and source maps as <br />determined by the advance submission of the shape files (sent to TriTech on August 9, 2006). <br />b. Conduct an initial conference call to discuss service boundary delineation requirements and how <br />they are used in CAD. <br />
The URL can be used to link to this page
Your browser does not support the video tag.