Laserfiche WebLink
1. General: Subsequent to a Field Functional Test, verifying substantial <br />completion of field installation and start-up, the system will be given a final 30- <br />day acceptance test. The 30 -day test must be successfully completed, <br />including resolution of punch -list items generated during the test period, prior to <br />- the date of substantial completion of the entire project. The system must run <br />continuously for 30 consecutive days. During this period, all system functions <br />shall be exercised, and any system interruption and accompanying component, <br />subsystem, or program failure shall be logged for cause of failure, as well as <br />time of occurrence and duration of each failure. The CONTRACTOR shall <br />provide a competently trained technician or programmer on call during all <br />normal working days and hours from the start of the acceptance test until final <br />acceptance of the system. <br />2. Testing: The systems to be tested on -line will include general operations as <br />specified. Each system function shall be exercised several times at a minimum, <br />and in a manner which approximates "normal" system operation. Failure of the <br />system during the above testing shall be considered as not meeting the <br />requirements of the specifications and corrective action shall be required before <br />restarting the acceptance test. Only those components, subsystems, and <br />systems covered in this specification and supplied under this contract shall be <br />considered for this acceptance test. <br />3. Failures: Failures shall be classified as either major or minor. A minor failure <br />would be a small and non - critical component failure, which can be corrected by <br />the CITY operators. This occurrence shall be logged but shall not be reason <br />enough for stopping the test and shall not be grounds for non - acceptance. <br />However, should the same or similar component failure occur repeatedly, this <br />may be considered as grounds for non - acceptance. A major failure shall be <br />considered to have occurred when a component, subsystem, or program fault <br />causes a halt in operation of the system and /or when a technician's work is <br />required to make a repair or to re- initiate operation of the system. A major <br />failure shall cause termination of the acceptance test. When the causes of a <br />major failure have been corrected, a new acceptance test shall be started. <br />4. Technician Report: Each time a technician is required to respond to a system <br />malfunction, he or she must complete a report which shall include details <br />concerning the nature of the complaint or malfunction and the resulting repair <br />-- - action required and taken. If a malfunction occurs which clears itself or which <br />the operator on duty is able to correct, no report shall be required (logged as <br />specified above). If a technician has performed work but no report is written, <br />then a major failure shall be considered to have occurred. Each report shall be <br />as specified above). Each report shall be submitted within- 24 hours to the <br />ENGINEER or its representative, and the CITY. <br />3.4 TRAINING AND INSTRUCTION <br />A. General: The CONTRACTOR shall retain the services of the SMS Supplier to <br />provide system maintenance and operator training courses by a qualified instructor <br />for all the camera, instrumentation, and computer monitoring and control furnished for <br />City of Santa Ana Security Management System General Requirements <br />Security Management System Project Page 17010 -13 <br />SantaAna_SMS_17010 <br />