Launch Vehicle Compatibility and Interface Validation Sample Clauses

Launch Vehicle Compatibility and Interface Validation. The Contractor shall perform all work necessary to ensure the compatibility of the spacecraft design with all required launch vehicles, and shall provide the evidence necessary to demonstrate and document such compatibility as required by INTELSAT. Design compatibility with these launch vehicles shall be maintained for all spacecraft throughout the duration of the spacecraft program. Unilateral requirement changes imposed by the launch vehicle agencies after EDC will be reviewed by the Contractor and the status of compatibility of the spacecraft with regard to launcher requirements shall be updated. This update shall include interface control documentation, safety submissions, mathematical models and any other analyses required justifying compatibility statements. Provided there is no impact on hardware or on contractual delivery dates, such changes will become part of the applicable requirements. The Contractor shall demonstrate that the spacecraft design is compatible with all interface recommendations and requirements (mechanical, electrical, RF, etc.), all environmental recommendations and requirements and conditions (loads, thermal, RF, etc.), and all constraints (operational, safety, etc.) associated with each of the required launch vehicles and in effect at the time of the spacecraft launches, as defined by the launch services suppliers (e.g., in the corresponding launch vehicle user’s manuals, launch site facilities guides and safety regulations). The Contractor shall also demonstrate compatibility with standard launch vehicle mission profiles and sequences, as defined by each of the launch services suppliers. The Contractor shall demonstrate that the spacecraft is designed to permit launch to occur on any day of the year on any of the launch vehicles with which spacecraft compatibility is required. In addition, the Contractor shall demonstrate that the spacecraft design is compatible with launch window constraints determined to be acceptable by INTELSAT and/or any of the launch services suppliers. Spacecraft-to-launch vehicle interfaces and design and operational data sufficient to demonstrate compatibility with all required launch vehicles and their associated services, facilities, etc. shall be presented in all system level design reviews. INTELSAT will elect a Contract option, as described in Section 11.3 (“Optional Launch Support and Integration Services”) of this exhibit, for the additional detailed launch vehicle compatibility and interface ...
AutoNDA by SimpleDocs

Related to Launch Vehicle Compatibility and Interface Validation

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

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

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Technical Support State Street will provide technical support to assist the Fund in using the System and the Data Access Services. The total amount of technical support provided by State Street shall not exceed 10 resource days per year. State Street shall provide such additional technical support as is expressly set forth in the fee schedule in effect from time to time between the parties (the “Fee Schedule”). Technical support, including during installation and testing, is subject to the fees and other terms set forth in the Fee Schedule.

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