Laserfiche WebLink
<br />ALTERNETNETWORKSPROP~ETARY <br /> <br />compliance with these requirements shall be in accordance with the Next Generation <br />Surveillance System Test and Production Plans. <br />As a part of the Next Generation Surveillance System Test, the Consultant shall conduct a <br />maintenance demonstration of mean time to repair SAPD selected failure conditions. <br />Until SAPD's Final Acceptance of the Next Generation Surveillance System RFPs, the <br />Consultant shall maintain failure records on each failed software and hardware system which <br />shall become a part of the test report. Upon request, these failure records shall include the serial <br />number of the unit, estimated running time, identification of the component that failed, and an <br />analysis of the particular failures, including root cause and recommended corrective action, and <br />direction of the Next Generation Surveillance System for RFPs. <br /> <br />4.3 Hardware Identification <br />The Consultant shall maintain a system for identifying the inspection status of all equipment. <br />Identification may be accomplished by means of stamps, tags, routing cards, move tickets, or <br />other normal control devices. This identification shall include the revision level of the <br />documentation used for inspection. <br />Serial numbers shall be assigned to all major sub-assemblies in accordance with Consultants' <br />tagging policies, and to any assembly that contains a serialized or repairable sub-assembly. <br /> <br />4.4 Reeeivine: Inspection <br />Receiving inspection shall be performed by the Consultant to assure that procured items for the <br />design and engineering phases meet the requirements of the contract and procurement documents <br />prior to their being incorporated into deliverable RFPs. The extent of inspection shall be <br />consistent with the nature and intended application of each article <br /> <br />4.5 Software Identification <br />The Next Generation Surveillance System shall include a method of identifying the versions of <br />all software modules in the Security System. Identification of all field downloadable software <br />components must be accomplished by means of software query. Identification of software <br />components which cannot be changed in the field must be accomplished by means of software <br />query or stamps, tags, routing cards, move tickets, or other normal control devices. <br /> <br />4.6 On-Site Liaison <br />The Consultant shall, if required, provide an on-site liaison to aid the PM during the design, <br />engineering and/or testing phases. The representative shall act as an employee of the Consultant <br />under the direction of the Consultant and employment shall be terminated with the liaison at any <br />time either by the request ofSAPD or at Consultant's discretion. <br /> <br />4.7 Chane:e Review Process <br />SAPD and the Consultant shall jointly participate in a Change Review Board ("CRB") which is <br />chaired by SAPD. The CRB will review and approve/disapprove potential changes in the <br />contract baseline documentation. Contract baseline documentation consists of all Interface <br />Control Documents and Functional Specifications (lCD's listed in Table 1). The CRB shall meet <br />as often as required to expeditiously address accumulated change proposals. For changes <br />impacting the scope of the SOW, the CRB approval does not constitute contractual go ahead for <br />a change until such changes are incorporated into a contract change order issued through SAPD, <br /> <br />14 <br />