Vendor Interface Requirements (VIR Sample Clauses

Vendor Interface Requirements (VIR. The Contractor shall provide estimated or available interface requirements information with the proposal. The VIR submission shall include: • Equipment Dimensions • Weight • Locations for cable entrances • Locations for air exhaust and intake interfaces • Equipment (and location in EC) requiring removal or disassembly for repair or maintenance • Estimated Maintenance envelope • Estimated Shock envelope • Mounting requirements • The Contractor should provide a list of critical failures with demonstrated or predicted mean time between failure (MTBF) and mean time to repair (MTTR) data and describe the basis for those predictions. A critical failure shall be considered as any component or system failure that would cause an unscheduled loss of capability of the EC system. Predicted MTBF and MTTR shall be based on the duty cycle identified in the Technical Specification. CDRLs: A037, A040
Sample 1
AutoNDA by SimpleDocs

Related to Vendor Interface Requirements (VIR

  • Interface Requirements 9.3.1 BellSouth shall offer LIDB in accordance with the requirements of this subsection.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • ON SITE REQUIREMENTS While on Purchaser’s premises, Contractor, its agents, employees, or subcontractors shall comply, in all respects, with Purchaser’s physical, fire, access, safety, and other security requirements.

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Training Requirements Grantee shall:

  • Space Requirements The Construction Administrator will conduct a review of the adequacy of space allotments for maintenance of mechanical, telephone, and fire protection equipment.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!