Other Use Obligations Sample Clauses

Other Use Obligations 
AutoNDA by SimpleDocs

Related to Other Use Obligations

  • Licensee Obligations 3.1 The Licensee is responsible for the installation, operation and maintenance of telecommunication lines, equipment, software and other arrangements necessary for the Licensee to receive the Licensed Data from the LME.

  • Maintenance Obligations In the event the Project includes construction then the following provisions are incorporated into this Agreement:

  • Joint Obligations A. The University and the student share the responsibility for ensuring the quality of life within the residence halls, their maintenance, furnishings and facilities, and for a physical environment secure from fire and other hazards. The University will work with students to promote effective security of persons and property in the residence halls.

  • Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.

  • Client Obligations 3.1 The Client shall:

  • Specific Obligations The HSP:

  • Recipient Obligations 2.1 The Recipient agrees to support the Project in accordance with this Agreement.

  • PROCUREMENT OBLIGATIONS Notwithstanding any other provisions of this Part B, where in this Part B the Customer accepts an obligation to procure that a Former Supplier does or does not do something, such obligation shall be limited so that it extends only to the extent that the Customer's contract with the Former Supplier contains a contractual right in that regard which the Customer may enforce, or otherwise so that it requires only that the Customer must use reasonable endeavours to procure that the Former Supplier does or does not act accordingly.

  • SAP OBLIGATIONS 3.1 Instructions from Customer. SAP will process Personal Data only in accordance with documented instructions from Customer. The Agreement (including this DPA) constitutes such documented initial instructions and each use of the Cloud Service then constitutes further instructions. SAP will use reasonable efforts to follow any other Customer instructions, as long as they are required by Data Protection Law, technically feasible and do not require changes to the Cloud Service. If any of the before-mentioned exceptions apply, or SAP otherwise cannot comply with an instruction or is of the opinion that an instruction infringes Data Protection Law, SAP will immediately notify Customer (email permitted).

  • Service Obligations The Supplier must supply the Services:

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