LAUNCH AND LAUNCH VEHICLE Sample Clauses

LAUNCH AND LAUNCH VEHICLE. Team shall produce its own launch vehicle, or shall secure any launch vehicle via a commercial purchase, that is fair and repeatable.
AutoNDA by SimpleDocs
LAUNCH AND LAUNCH VEHICLE. Team shall produce its own launch vehicle, or shall secure any launch vehicle via a commercial purchase, that is fair and repeatable. Team shall disclose to XPF its intent to attempt to launch no later than one hundred eighty (180) days prior to a Team’s scheduled launch date via the Notification of Launch Attempt package (such disclosure being the “Notification of Launch Attempt”). A template for the Notification of Launch Attempt package will be provided by XPF to Team on or around April 15, 2011 or after XPF accepts Team’s Registration Package and Agreement. Additionally, Team shall submit a notification of execution of any launch contract to XPF, to be kept confidential by XPF. Such notification shall include a summary of the relevant terms of the contract. Launches on government- owned or government-developed launch vehicles shall be permitted, so long as the launch contract is commercially reasonable, in the judgment of Judging Panel. In addition, a Launch Site Access Plan, based on a template to be provided by XPF upon reasonable request, shall be submitted for review to the Judging Panel no later than one hundred eighty (180) days prior to launch. XPF will treat Team’s launch as Confidential Information (as defined in the Standard Terms and Conditions) until three (3) months prior to the scheduled date, if desired by Team, after which time XPF will announce and promote Team’s launch attempt. Team shall notify XPF at the earliest opportunity of any launch delays. Team shall use commercially reasonable best efforts to provide XPF and its partners access to the launch facility and to relevant video and data feeds covering the launch and related activities. A Launch Site Access Plan, based on a template to be provided by XPF upon reasonable request, shall be submitted for review to the Judging Panel no later than one hundred eighty (180) days prior to launch. XPF will use reasonable efforts to work with Team in order to respect Team’s Intellectual Property and regulatory compliance. If multiple Teams request the same launch date in a manner that cannot reasonably be supported by XPF or the Judging Panel, priority will be given to Team that submitted its complete versions of both the Notification of Launch Attempt package and Launch Site Access Plan first. For purposes of clarity, a launch of Crafts from multiple Teams on the same launch vehicle at the same time is permitted, providing all other conditions in this Agreement are met. Team must reach agre...

Related to LAUNCH AND LAUNCH VEHICLE

  • Network Access Control The VISION Web Site and the Distribution Support Services Web Site (the “DST Web Sites”) are protected through multiple levels of network controls. The first defense is a border router which exists at the boundary between the DST Web Sites and the Internet Service Provider. The border router provides basic protections including anti-spoofing controls. Next is a highly available pair of stateful firewalls that allow only HTTPS traffic destined to the DST Web Sites. The third network control is a highly available pair of load balancers that terminate the HTTPS connections and then forward the traffic on to one of several available web servers. In addition, a second highly available pair of stateful firewalls enforce network controls between the web servers and any back-end application servers. No Internet traffic is allowed directly to the back-end application servers. The DST Web Sites equipment is located and administered at DST’s Winchester data center. Changes to the systems residing on this computer are submitted through the DST change control process. All services and functions within the DST Web Sites are deactivated with the exception of services and functions which support the transfer of files. All ports on the DST Web Sites are disabled, except those ports required to transfer files. All “listeners,” other than listeners required for inbound connections from the load balancers, are deactivated. Directory structures are “hidden” from the user. Services which provide directory information are also deactivated.

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

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

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

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

  • Project Implementation The Borrower shall:

  • Uncovering and Correction of Work 12.1 The Contractor shall promptly correct Work rejected by the Owner or failing to conform to the requirements of the Contract Documents, whether observed before or after Substantial Completion and whether or not fabricated, installed or completed, and shall correct any Work found to be not in accordance with the requirements of the Contract Documents within a period of two years from the date of Substantial Completion, or by terms of an applicable special warranty required by the Contract Documents. The provisions of this Article apply to work done by Subcontractors as well as to Work done by direct employees of the Contractor. 12.2 At any time during the progress of the work, or in any case where the nature of the defects shall be such that it is not expedient to have them corrected, the Owner, at their option, shall have the right to deduct such sum, or sums, of money from the amount of the contract as they consider justified to adjust the difference in value between the defective work and that required under contract including any damage to the structure.

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

  • PRODUCT SUPPORT Partners may provide support for Products and other value-added services, and Partner is responsible for the performance of any services it provides. If Customer purchases Microsoft Support Services through a Partner, Microsoft will be responsible for the performance of those services subject to the terms of this Agreement.

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