Registration of CUSTOMER’s Satellite Sample Clauses

Registration of CUSTOMER’s Satellite. CUSTOMER shall be responsible to ensure that the Satellite is properly registered by a state of registry in accordance with the Convention on Registration of Objects Launched into Outer Space of 1974 either (i) directly, if CUSTOMER is a state or the state designated by an international intergovernmental organization for the purposes of registration, or (ii) if CUSTOMER is not a state, through a state having jurisdiction and control over CUSTOMER. Commercial in Confidence
AutoNDA by SimpleDocs
Registration of CUSTOMER’s Satellite. In accordance with the Convention on Registration of Objects Launched into Outer Space of U.N.O., Customer:

Related to Registration of CUSTOMER’s Satellite

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

  • REGISTRATION OF EZ2BID 3.1 E-bidders will log in into ESZAM AUCTIONEER SDN BHD secured website. E-bidders shall provide true, current and accurate information to register as a user.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Registration Compliance; No Stop Order No order suspending the effectiveness of the Registration Statement shall be in effect, and no proceeding for such purpose or pursuant to Section 8A under the Securities Act shall be pending before or threatened by the Commission; the Prospectus and each Issuer Free Writing Prospectus shall have been timely filed with the Commission under the Securities Act (in the case of an Issuer Free Writing Prospectus, to the extent required by Rule 433 under the Securities Act) and in accordance with Section 4(a) hereof; and all requests by the Commission for additional information shall have been complied with to the reasonable satisfaction of the Representatives.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer. Confidentiality

  • Registration of Agreement 1.04 (1) The City shall be entitled, in its sole discretion, to file and maintain caveats evidencing the City’s interest under this Agreement against each and every Certificate of Title within the Development Area.

  • Registration Not Required Notwithstanding the foregoing, the General Partner shall not be required to file or maintain the effectiveness of a registration statement covering the resale of Redemption Shares if, in the opinion of counsel to the General Partner, such Redemption Shares could be sold by the holders thereof pursuant to Rule 144 under the Securities Act, or any successor rule thereto.

  • Registration of Notes The Company shall keep at its principal executive office a register for the registration and registration of transfers of Notes. The name and address of each holder of one or more Notes, each transfer thereof and the name and address of each transferee of one or more Notes shall be registered in such register. Prior to due presentment for registration of transfer, the Person in whose name any Note shall be registered shall be deemed and treated as the owner and holder thereof for all purposes hereof, and the Company shall not be affected by any notice or knowledge to the contrary. The Company shall give to any holder of a Note that is an Institutional Investor promptly upon request therefor, a complete and correct copy of the names and addresses of all registered holders of Notes.

  • Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).

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