Integrated System Test Sample Clauses

Integrated System Test. Test of dynamic function and operation of multiple systems. Integrated System Tests are conducted under various modes, such as fire alarm and emergency situations, life safety conditions, power failure, etc. Systems are integrally operated through all specified sequences of operation. Components are verified to be responding in accordance with Contract Documents. Integrated System Tests are executed after Functional Performance Tests are complete and prior to Substantial Completion. Integrated System Tests provide verification that the integrated systems will properly function according to the Contract Documents.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Integrated System Test i. CONTRACTOR shall clear database from data entered in the Functional Test.
Sample 1
Integrated System Test i. CONTRACTOR shall have all EMS PCR records received under Section I.C.1 (Functional Test) above processed through the TEMIS Scanning Solution program.
Sample 1
Integrated System Test i. CONTRACTOR shall have electronic PCRs downloaded from the Field site server to the TEMIS Central database.
Sample 1
Integrated System Test. 38 4.3.3 Electro Magnetic Compatibility (EMC) Test...............40 4.3.4 RF Health Check.........................................40 4.3.5 Electro Static Discharge (ESD) Test.....................41 4.3.6 Spacecraft Alignment Test...............................43 4.3.7
Sample 1
Integrated System Test. 1A The initial Integrated System Test (IST-1) is performed to verify specified operation of the spacecraft subsystems prior to application of environmental tests. This test provides a reference baseline of test data to which subsequent performance test results will be compared during and after environmental tests. Because the antennas are not installed on the spacecraft until after the thermal vacuum test, the IST-1 is broken into two parts designated IST-1A and IST-1B. IST-IB is conducted after the antennas are installed subsequent to the thermal test. IST-1A consists of initial alignments of subsystem support module (SSM) equipment a propulsion functional test and the performance test. Tables 6.1-1 through 6.1-4, Spacecraft Protoflight and Acceptance Test Matrices, describe the system level tests to be performed on the various subsystems during the IST-1A and subsequent system tests. Shown vertically on the left of each matrix are the major activities in the test sequence. Shown horizontally at the top of each matrix, organized by subsystem, are the measurements to be performed during the indicated activities. The places in the sequence where these test measurements are made are denoted by an X, or other symbol as defined in footnotes. Tables 6.1-5 through 6.1-13, at the end of this section, contain descriptions of the spacecraft test configurations. The test configurations are also keyed to the system test matrices.
Sample 1
Integrated System Test. 1B Interated Systems Test-1B (IST-1B) is conducted after antenna installation and initial alignment.
Sample 1
AutoNDA by SimpleDocs
Integrated System Test. The integrated system test shall verify the stability of the system hardware and software after the functional performance test has been successfully completed. During the integrated system test, all functions shall run concurrently and all AMISP-supplied equipment shall operate for a continuous 100-hour period. This minimum level of activity may be augmented, by other activities that represent normal day-to-day operation of the system as long as these activities are conducted in accordance with the documentation provided with the system. These other activities may include, but shall not be limited to, database, display, and report modifications, software development activities, configuration changes (including user-commanded server and device failovers), and the execution of any function described in this Specification. The integrated system test shall ensure that the computer system is free of improper interactions between software and hardware while the system is operating as an integrated unit. In case during the 100-hour period testing, un-commanded functional restart or server or device fail occurs the test shall be extended by 24 hours each time such a fail over occurs. Further the test shall not be conducted with the failed device. Unstructured Testing Periods of unstructured testing shall be allocated to allow AMISP to verify proper operation of the systems under conditions not specifically included in the test procedures. Unstructured testing shall be conducted in compliance with the following conditions: A minimum of 25 percent of the actual test period shall be reserved for unstructured test of the system The AMISP's test and QA/QC representative shall be present during unstructured test periods All simulation software, test cases, and other test facilities used during the structured portions of the factory tests shall be available for use during unstructured testing Unstructured testing shall not begin prior to the start of the functional performance test Unstructured testing shall be allowed at the discretion of QA/QC both at the end of a structured test segment and after completion of the functional performance test. Despatch of Material to Site The Material Inspection Clearance Certificate (MICC) for all hardware shall be issued only after successful completion of FAT as per specification. At least 10 Field Devices for each protocol shall relate to each central system and the remaining Field devices shall be simulated in the factory test en...
Sample 1

Related to Integrated System Test

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements. Acknowledging your access and consent to receive and sign documents electronically To confirm to us that you can access this information electronically, which will be similar to other electronic notices and disclosures that we will provide to you, please confirm that you have read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for your future reference and access; or (ii) that you are able to email this ERSD to an email address where you will be able to print on paper or save it for your future reference and access. Further, if you consent to receiving notices and disclosures exclusively in electronic format as described herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign system. By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm that: • You can access and read this Electronic Record and Signature Disclosure; and • You can print on paper this Electronic Record and Signature Disclosure, or save or send this Electronic Record and Disclosure to a location where you can print it, for future reference and access; and

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Outputs 8. The objectives and outcomes of this Agreement will be achieved through a range of outputs. The outputs include the:

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible mobile hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

Time is Money Join Law Insider Premium to draft better contracts faster.