System Testing. Upon contract execution, the Contractor shall provide a complete and comprehensive functional test plan to assure the Department of the system’s readiness to accept inmate calling traffic. This test plan shall include a checklist of items to be performed by the Contractor’s implementation team and verified by the Department’s staff.
System Testing. Contractor shall develop the a test program for conducting system testing of the NEPP System (the "Test Plan"). The NEPP Test Plan is to ensure that all Equipment, Software, Interfaces, supporting hardware, Smart Media, and other System Elements furnished under this Contract meet all requirements set forth in the Contract Documents. The NEPP Test Program shall be conducted in accordance with the requirements and procedures set forth in Section 19 (Deployment, Installation And Testing) of the Technical Specification.
System Testing. PBM agrees to have a testing process and corresponding written policies and procedures that are designed to identify and correct WellPoint, Plan and PBM configuration errors prior to implementation and to document the manner and extent to which it has performed such testing. PBM will provide testing results upon WellPoint’s request.
System Testing. Prior to LIFFE’s release to the CBOT of the Software for acceptance testing, LIFFE shall test the Components. Prior to the CBOT’s commencement of acceptance testing, the CBOT shall test all software required to be provided by the CBOT hereunder (the “CBOT Deliverables”) to ascertain whether such software materially conforms to the CBOT’s specifications for such CBOT Deliverables and those specifications for the Interfaces set forth on Schedule A. Acceptance testing shall not commence until (a) LIFFE has notified the CBOT in writing that LIFFE has reasonably determined that the Software materially conforms to the Specifications and (b) the CBOT has notified LIFFE in writing that the CBOT has reasonably determined that the CBOT Deliverables materially conforms to the CBOT’s specifications for such CBOT Deliverables and those specifications for the Interfaces comprising the Specifications. Between delivery of such notice to the other Party and the CBOT’s issuance of the Initial Acceptance Certificate, (i) LIFFE shall endeavor to provide the CBOT written notice of any modifications of the Software that may have a material impact on the functionality, performance or operation of the Software, and (ii) the CBOT shall endeavor to provide LIFFE written notice of any modifications to the CBOT Deliverables that may have material impact on the functionality, performance or operation of the CBOT Deliverables.
System Testing. Subject to all applicable laws and the confidentiality obligations in this Agreement, OBH may use data capture and analysis tools to analyse data and information in an aggregated form for the purpose of monitoring and improving system performance and generating statistics and system metrics.
System Testing. (a) Upon request, Grantee must advise Grantor of schedules and methods for testing the cable system on a regular basis to determine compliance with the provisions of applicable FCC technical standards.
(b) As required by FCC rules, Grantee must conduct proof-of-performance tests and cumulative leakage index tests designed to demonstrate compliance with FCC requirements. Upon request, Grantee must provide to Grantor summary written reports of the results of those tests.
(c) The Grantor has the right to inspect all work performed in the public rights-of-way. In addition, for initial and semi-annual FCC proof-of-performance tests, the Grantor must be given the opportunity to review test sites. Upon request, the tests may be witnessed by representatives of the Grantor. Grantee will notify the Grantor of the time and place of the next scheduled test and will cooperate in facilitating witnessing by the Grantor at the time of the tests.
(d) It is the responsibility of the Grantee to document that the system and its operation are in compliance with FCC technical specifications and performance requirements. If the Grantor has received subscriber complaints regarding the performance of the cable system, and the Grantor determines that the most efficient or only reasonable way to determine a question of franchise compliance involves specific electronic testing of the cable system in addition to tests required by the FCC, the Grantee may, upon 30 days written notice by the Grantor, perform that testing, give the Grantor an opportunity to witness that testing, and provide the Grantor with documentation of the test results.
System Testing. 1.2.1 Solectron agrees to fully test the identified deliverables to ensure that the system [ ]
System Testing. 2.6.1. ***. Silver Spring will ***.
System Testing. 2.6.1. Silver Spring will ***.
2.6.2. at ***, not currently listed in ***). ComEd acknowledges that *** for an *** to be *** in a separate SOW, and is distinct from the *** conducted at *** and in the *** as described in ***.
System Testing. 4.4.5.1 The Contractor must describe, in its response, how it performs standard system testing to ensure that the proposed Web-based Video Visitation/Communication System and its network services are fully implemented and ready to accept visitation traffic and MCSO use. This description must include the Contractor and industry standard methodologies, procedures and protocols consistent with the Web-based Video Visitation/Communication Kiosk System proposed for MCSO. After each facility is transitioned, our Project Manager and Field Service Technician will review our quality checklists with the Maricopa County Team. Weekly stakeholder meetings will be hosted by the Contractor Project Team and will involve participation from the Maricopa County Team. At the beginning of the implementation project, the Contractor Project Management Team will work with the Maricopa County Team to identify key stakeholders, primary points of contacts, and roles/responsibilities for the duration of the project. The Contractor Project Management Team will establish regular meeting forums and communication protocols that accommodate the requirements of the Maricopa County Team. Throughout the duration of the project, our Project Management Team will provide weekly installation progress reports. The reports will include updates on all active, completed, and pending installation activities. In addition to the personal communication from our Project Managers, Contractor can set-up automated email notifications for the Maricopa County Team. The automated email notifications are a great way for our customers to receive updates on status changes for major milestones and other tasks of interests.
4.4.5.2 The Contractor must describe what is required of MCSO personnel during this system testing. All hardware, software, software licensing, etc. required to perform this testing must be provided to MCSO at no cost. Contractor’ demand on MCSO personnel’s time is minimal, requiring only the following: • Escorts in appropriate areas for security purposes • Project management resources and time to finalize and approve installation plans • Project management resources and time approve work at key milestones • Project management resources and time for final approval of system installation • Project management resources and time for status meetings at regular intervals during installation Contractor will provide all hardware, software, software licensing, etc. to MCSO at no cost.
4.4.5.3 The Contra...
