My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Res 1994-016
San-Marcos
>
City Clerk
>
03 Resolutions
>
1990 s
>
1994
>
Res 1994-016
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/28/2007 9:06:24 AM
Creation date
6/28/2007 9:06:24 AM
Metadata
Fields
Template:
City Clerk
City Clerk - Document
Resolutions
City Clerk - Type
Agreement
Number
1994-16
Date
1/24/1994
Volume Book
114
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
94
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).
Show annotations
View images
View plain text
<br /> 7'5"A~ <br /> RIDER H <br /> _.-: . <br /> Schedule 2 <br /> SYSTEM REUABlUTY TEST <br /> Thè System Rèliability Tèst is a test to determine if the System under this Agreement is reliable and, therefore, <br /> suitable for USè by THE CITY. Successful completion of this test is necessary for Final System Acceptance. This <br /> test may be adnùnistered at any time that this Agreement is in effect. <br /> This test will be administered as follows: -- -- <br /> , <br /> (a) Upon receipt by THE CITY from DYNIX of (1) notice of the successful completion of the Hardware ! <br /> Functionality Test for Cataloging and Circulation, and (2) after the operational control of the system passes <br /> to THE CITY, THE CITY staff shall initiate the calculations necessary to perform the System Reliability Test. <br /> (b) The System Reliahility Test may he overlapped with other performance test procedures. <br /> (c) In order to successfully pass this test the Equipment must be available for 98 % of the Library hours of THE <br /> CITY for sixty (60) cons<xutive days over a ninety (90) day period. <br /> (d) All doWTltime shall he measured in increments of six (6) minutes, rounded to the nearest (up or down) <br /> increment. In calculating doWTltime, each occurrence shall be measured, calculated separately, and logged into <br /> the operations dov,rntime transaction log. At the conclusion of each 90-day test period, the downtime value <br /> resulting from each occurrence will be combined to arrive at the total amount of downtime. Under no <br /> circumstances will the doWTltime coefficient value more than 1.0 in calculating the minutes of doWTltime. <br /> The formula for calculating each occurrence of doWTltime is as follows: . <br /> FORMULA: (t) = (d) x (m) <br /> [where variables are ddìned as: I <br /> (d) = downtime coefficient value <br /> (m) = number of minutes of doWTltime <br /> (t) = total doWTltime (for that occurrence) <br /> (e) The doWTltime coefficient value shall be assigned according to the following table: <br /> I <br /> Class 1 Hardware Outage: Coefficient Value = 110 I <br /> ¡ <br /> (each device) <br /> "'Central pnx:c:ssing unit <br /> "'Disk drive(s)/controller <br /> "'Port controller(s) <br /> "'Main memory <br /> Class 2 Hardware Outage: Coefficient Value = 0.50 <br /> (each device) <br /> *Tape drive <br /> Class 3 Hardware Outage: Coefficient Value = 0.25 <br /> (each device) <br /> "'Line Printer <br /> CITY OF SA~ "1ARCOS - PAGE R-16 <br /> January 17, 1994 <br />
The URL can be used to link to this page
Your browser does not support the video tag.