SYSTEM READINESS Sample Clauses

POPULAR SAMPLE Copied 1 times
SYSTEM READINESS. 2.2.2.6.1 The Contractor will define and test modifications to the Contractor’s system(s) required to support the business functions of the contract. The Contractor will produce data extracts and receive data transfers and 2.2.2.6.2 If any errors or deficiencies are evident, the Contractor will develop resolution procedures to address the problem identified. The Contractor will provide LDH, or designated contractor, with test data files for systems and interface testing for all external interfaces. Administration & Contract Management
View Source
SYSTEM READINESS. 2.2.1. The General Contractor shall verify that systems are installed, complete and operable before the commencement of TAB work. The General Contractor and the Owner’s Independent Performance Assurance Contractor, shall insure the following conditions: 1. Systems are started and operating in a safe and normal condition. 2. Direct Digital Control System and temperature controls are installed complete and operable including verification of proper end device operation and installation of required software and programming. 3. Proper thermal overload protection is in place for electrical equipment 4. Final filters are new and in place. 5. Coil fins are clean and combed if needed 6. Duct systems are clean of debris. 7. Fans are rotating correctly 8. Motors and bearings are properly lubricated. 9. Any excessive vibration has been corrected. 10. Fire/Smoke and volume dampers are in place, open, and operating properly. 11. All ductwork connections are complete, access doors are closed, and duct end caps are in place. 12. Air outlets are installed and connected. 13. Duct system leakage is minimized per the Specifications. 14. Water systems have been flushed, refilled, and vented. 15. Strainers or filters are in place and clean. 16. Control valves, check valves, and flow meters are installed and operating properly. 17. All manual valves, balancing devices, and control valves are open. 18. Pump rotation is correct and water is flowing. 19. System make-up water pressure is properly adjusted. 2.2.2. NMPSFA Approved Pre-Functional Checklist forms to verify the readiness of systems for TAB work are provided following the end of this Section. The General Contractor shall have personnel with direct knowledge complete the individual checklists to verify that systems are installed, complete and operable prior to the commencement of TAB work. These checklists do not replace any manufacturer recommended procedures. 2.2.3. Prior to commencement of TAB work, the General Contractor shall submit a written request to the Owner, including completed Pre-Functional Checklists forms for mechanical inspection of the project. This inspection shall be conducted by a duly appointed representative of the Mechanical Engineer’s office, the Mechanical Contractor’s Superintendent, and the Owner’s PAC Services Contractor. The inspection shall establish to the satisfaction of all parties that the systems are ready for testing and balancing. 2.2.4. Prior to commitment of TAB work, the General Cont...
View SourceView Similar (4)
SYSTEM READINESS. 2.1. Test conditions (a) The vehicle shall be left in a parked parking status until it is ensured that all electronic systems are de-activated; or for a minimum of 30 minutes. (b) It is permissible for the test person or equipment to be already situated within the vehicle. (c) Ensure the vehicle gear selector is in neutral or forward gear. (d) The test may start with opening the driver door. Once the door is opened, it shall be closed again.
View SourceView Similar (2)
SYSTEM READINESS. At the completion of the Work, the Contractor and each subcontractor along with Management's Building maintenance personnel shall direct the evaluation of utilities, operation systems, and equipment for readiness; shall assist in their initial start-up and testing by subcontractors; and shall provide general familiarization training for Management personnel.
View Source
SYSTEM READINESS. During this test, the Broker will ensure the following, through representation to or demonstration for FSSA as requested: a) The telephone systems are fully operational b) The computer system is fully operational c) The staffing is in compliance with the Contract d) All deliverables required in the Contract are available for review and approval thirty
View Source
SYSTEM READINESS. System Readiness will occur on a Phase-by-Phase basis when Motorola, in concurrence with the Authority, demonstrates to the Authority’s reasonable satisfaction that the applicable Phase of the System is ready for use in compliance with the terms of this Agreement. Although FCC licensing matters and compliance with FCC requirements are the responsibility of the Authority, System Readiness will include evidence that the System complies with FCC requirements as they exist .when testing described in Section 8.1 commences. Upon that demonstration, Motorola will memorialize this event by promptly executing a System Readiness Certificate by Phase (Exhibit H) and delivering a copy to the Authority. Minor omissions or variances in the Phase of the System that do not materially impair the operation of the Phase of the System will not postpone System Readiness for that particular Phase, but will be corrected according to a punch list schedule developed by Motorola which is mutually agreed upon by the Authority and Motorola. The concurrence by the Authority on a System Readiness Certificate (as evidenced by execution) will not be unreasonably delayed or withheld. In the event that the Authority does not concur that System Readiness has occurred, the Authority shall provide a notice of deficiency in writing to Motorola setting forth the deficiency in reasonable detail. The Parties will negotiate in good faith regarding the steps necessary and timelines for the correction of a deficiency or any dispute as to whether a deficiency exists. In the event that the Parties cannot agree, then either Party may exercise the Dispute resolution process described in Section 11 below.
View Source

Related to SYSTEM READINESS

  • System Timeout The system providing access to PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must provide an automatic timeout, requiring re-authentication of the user session after no more than 13 twenty (20) minutes of inactivity.

  • 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. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • Calibration The comparison of a measurement system or device of unverified accuracy with a measurement system of known and greater accuracy to detect deviation of the unverified measurement system from required performance specifications (of the unverified measurement system or device) and to quantify all measured values to applicable units of the international system of units.

  • 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.

  • Commissioning Commissioning tests of the Interconnection Customer’s installed equipment shall be performed pursuant to applicable codes and standards. The ISO and Connecting Transmission Owner must be given at least five Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.