Laserfiche WebLink
Exhibit A: Statement of Work <br />Abbey Group shall: <br />a. Assist Santa Ana staff in placing JCMS into a production status. <br />b. Monitor the initial operation of JCMS and answer any operational questions raised by Santa Ana. <br />c. Provide, at a minimum, the services of one (1) technical person and one (1) resource person for a <br />maximum of eight (8) hours per day for three (3) calendar days on-site to monitor the subsystem. <br />The exact hours will be determined by Santa Ana. Abbey Group will remain on site if conditions <br />warrant (i.e., level 1 or 2 system problems). <br />d. Assist the training staff in utilizing the subsystem and the computer operations staff in supporting <br />the subsystem. <br />Santa Ana shall: <br />a. Place the software into production within five (5) calendar days following certification and begin <br />operational use in consultation with Abbey Group and in accordance with the Project Schedule. <br />Completion Criteria: <br />This task is considered complete when JCMS is placed into production operation. <br />Task 10: ]CMS Subsystem Reliability Testing <br />Objective: Verify the level of reliability of JCMS in a production environment <br />Task Description: <br />Verify that the JCMS subsystem demonstrates reliable operation in a production environment prior to the <br />start of the application software warranty period. <br />JCMS will demonstrate critical subsystem availability levels of 99.9% or better for a thirty (30) calendar day <br />Reliability Testing period. <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 />The JCMS subsystem will be considered "down" if there is a failure of any JCMS redundant or fault- <br />tolerant computer hardware or software module or component that prevents functions to operate at a level <br />that allows operation to continue. Functional problems that do not prevent productive use of the subsystem <br />are not considered downtime. Software problems of this type are documented by Santa Ana on an "action <br />item list" to be fixed during this phase. Downtime will begin at the time that the designated Abbey Group <br />contact person has been notified of the failure. <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 with spares, pending the receipt of replacement <br />components and repair of the failed component. <br />Failures in individual communication lines, terminals, workstations, PCs, non-Abbey Group 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 />JCMS Reliability Testing will not be delayed or interrupted if there are failures in systems that are not the <br />17 <br />