My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
POSITRON -2004
Clerk
>
Contracts / Agreements
>
P
>
POSITRON -2004
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/23/2017 8:46:28 AM
Creation date
1/9/2006 5:04:16 PM
Metadata
Fields
Template:
Contracts
Company Name
Positron
Contract #
A-2004-229
Agency
Police
Council Approval Date
10/18/2004
Insurance Exp Date
12/31/2200
Notes
PER LAURA SHEEDY IPC IS FOR POSITRON. SHE WILL REQUEST LETTER FOR FILE AFFIRMING THIS.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
151
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
<br />Exhibit A: Statement of Work <br /> <br />'-' <br /> <br />(Le., level 1 or 2 system problems). <br /> <br />Assist the training staff in utilizing the subsystem and the computer operations staff in supporting <br />the subsystem. <br /> <br />d. <br /> <br />Santa Ana shall: <br /> <br />a. Place the software into production within five (5) calendar days following certification and begin <br />operational use in consultation with Positron and in accordance with the Project Schedule. <br /> <br />Completion Criteria: <br />This task is considered complete when CAD is placed into production operation. <br /> <br />Task 12: <br /> <br />CAD SUbsystem Reliability Testing <br /> <br />Objective: <br /> <br />Verify the level of reliability of CAD in a production environment. <br /> <br />\... <br /> <br />Task Description: <br /> <br />Verify that the CAD subsystem demonstrates reliable operation in a production environment prior to the <br />start of the application software warranty period. <br /> <br />CAD will demonstrate critical subsystem availability levels of 99.9% or better for a thirty (30) calendar day <br />Reliability Testing period. <br /> <br />At the end of this test period, if subsystem availability has not met or exceeded this required level, the <br />Reliability Testing period will continue until this level of reliability has been demonstrated for at least thirty <br />(30) consecutive calendar days. <br /> <br />The CAD subsystem will be considered "down" if there is a failure of any CAD redundant or fault-tolerant <br />computer hardware or software module or component that prevents critical event entry, dispatch or status <br />mon~oring functions to operate at a level that allows operation to continue. Functional problems that do <br />not prevent productive use of the subsystem are not considered downtime. Software problems of this type <br />are documented by Santa Ana on an "action item Iisr' to be fixed during this phase. Downtime will begin at <br />the time that the designated Positron contact person has been notified of the failure. <br /> <br />The subsystem shall not be considered down during any manual or automated fail-over process, or if it is <br />operational in a backup mode or via replacement w~h spares, pending the receipt of replacement <br />components and repair of the failed component. <br /> <br />Failures in individual communication lines, terminals, workstations, PCs, non-Positron PC licensed <br />software, modems, data communications or problems that involve non-redundant or fault-tolerant <br />hardware or remote workstation or terminal sites do not constitute downtime. They will be repaired as <br />expediently as possible, and operations will then continue. <br /> <br />CAD Reliabil~ Testing will not be delayed or interrupted if there are failures in systems that are not the <br />responsibility of Positron (communication lines, extemal databases, etc.). Also, the reliability test and <br />subsystem certification will not be delayed if any user-provided peripheral components encounter a failure <br />or have not been made available for implementation and testing according to the project schedule. <br />Scheduled subsystem unavailability for purposes of software update, performance tuning, file backups and <br />other processes typical in a production environment is not considered as downtime. <br /> <br />In the event that the subsystem is considered to be 'down' during this test period, one of the following will <br />\...- occur: <br /> <br /> <br />24 <br />
The URL can be used to link to this page
Your browser does not support the video tag.