Responsibilities of All Users Sample Clauses

Responsibilities of All Users. 3.01 You agree that you, and your colleagues within your organization, are and will be the end users of the System. You solely bear all of the responsibility and liability associated with the possession and usage of the System, regardless of who ultimately interacts with it. 3.02 You are ultimately responsible for adhering to all of the procedures and protocols which are documented in Hylio's manuals and checklists (which have been provided to you electronically, in physical print, or both). These manuals and checklists may include, but are not limited to: Hylio AgroDrone Maintenance Checklist, Hylio AgroDrone Operations Manual, Hylio AgroDrone Pre-Flight Checklist, Hylio AgroDrone Training Process, Hylio AgroDrone US Regulations, Hylio AgroDrone GCS Software Manual. If needed, you can always email Hylio at xxxxxxx@xxx.xx or call Hylio at 000-000-0000 to obtain copies of Xxxxx's manuals and checklists. 3.03 You are ultimately responsible for ensuring that you comply with and conform to all applicable laws, ordinances, and regulations in any way relating to the use or possession of the System (“Applicable Laws”). Applicable Laws may include, but are not limited to, those which are set forth by the Federal Aviation Administration (FAA), Environmental Protection Agency (EPA), and the Department(s) of Agriculture (at both federal and state levels) pertaining to the use of aircraft in general, unmanned aircraft systems (“UAS”), chemicals, and agricultural procedures. Additionally, you acknowledge that the System provided under this Agreement may be subject to export laws and regulations of the United States and other countries, and any use or transfer of the System must be in compliance with all applicable export regulations. You may use the System only for lawful purposes and in accordance with this Agreement. 3.04 You are ultimately responsible for designating the individual that will operate the equipment (the “Remote Pilot in Command” or “RPIC”). The Remote Pilot in Command is responsible for assuring airworthiness of the equipment and ensuring the safe and effective operation of the equipment. You are ultimately responsible for ensuring that a Remote Pilot in Command: (i) complies with any Applicable Laws and the terms of this Agreement, and (ii) understands and exercises the correct information for the safe and effective operation of the equipment. 3.05 Hylio and its affiliates may, from time to time, provide or attempt to deliver its own understanding of...
Sample 1
AutoNDA by SimpleDocs
Responsibilities of All Users 
Sample 1

Related to Responsibilities of All Users

  • RESPONSIBILITIES OF PARTIES A. BellSouth will include billing number information associated with resold exchange lines or SPNP arrangements in its LIDB. The MPOWER will request any toll billing exceptions via the Local Service Request (LSR) form used to order resold exchange lines, or the SPNP service request form used to order SPNP arrangements. B. Under normal operating conditions, BellSouth shall include the billing number information in its LIDB upon completion of the service order establishing either the resold local exchange service or the SPNP arrangement, provided that BellSouth shall not be held responsible for any delay or failure in performance to the extent such delay or failure is caused by circumstances or conditions beyond BellSouth’s reasonable control. BellSouth will store in its LIDB an unlimited volume of the working telephone numbers associated with either the resold local exchange lines or the SPNP arrangements. For resold local exchange lines or for SPNP arrangements, BellSouth will issue line-based calling cards only in the name of MPOWER. BellSouth will not issue line-based calling cards in the name of MPOWER’s individual end users. In the event that MPOWER wants to include calling card numbers assigned by the MPOWER in the BellSouth LIDB, a separate agreement is required. C. BellSouth will provide responses to on-line, call-by-call queries to the stored information for the specific purposes listed in the next paragraph. D. BellSouth is authorized to use the billing number information to perform the following functions for authorized users on an on-line basis: 1. Validate a 14 digit Calling Card number where the first 10 digits are a line number or special billing number assigned by BellSouth, and where the last four digits (PIN) are a security code assigned by BellSouth. 2. Determine whether the MPOWER has identified the billing number as one which should not be billed for collect or third number calls, or both. Version1Q00:3/6/00 1. XXX Hosting, Calling Card and Third Number Settlement System (CATS) and Non- Intercompany Settlement System (NICS) services provided to MPOWER by BellSouth will be in accordance with the methods and practices regularly adopted and applied by BellSouth to its own operations during the term of this Agreement, including such revisions as may be made from time to time by BellSouth. 2. MPOWER shall furnish all relevant information required by BellSouth for the provision of XXX Hosting, CATS and NICS. 3. Applicable compensation amounts will be billed by BellSouth to MPOWER on a monthly basis in arrears. Amounts due from one Party to the other (excluding adjustments) are payable within thirty (30) days of receipt of the billing statement. 4. MPOWER must have its own unique XXX code. Requests for establishment of XXX status where BellSouth is the selected Centralized Message Distribution System (CMDS) interfacing host, require written notification from MPOWER to the BellSouth XXX Hosting coordinator at least eight (8) weeks prior to the proposed effective date. The proposed effective date will be mutually agreed upon between the Parties with consideration given to time necessary for the completion of required Telcordia (formerly BellCore) functions. BellSouth will request the assignment of an XXX code from its connecting contractor, currently Telcordia (formerly BellCore), on behalf of MPOWER and will coordinate all associated conversion activities. 5. BellSouth will receive messages from MPOWER that are to be processed by BellSouth, another LEC or CLEC in the BellSouth region or a LEC outside the BellSouth region. 6. BellSouth will perform invoice sequence checking, standard EMI format editing, and balancing of message data with the EMI trailer record counts on all data received from MPOWER.

  • RESPONSIBILITIES OF CITY City or its representative shall issue all communications to Contractor. City has the authority to request changes in the work in accordance with the terms of this Agreement and with the terms in Exhibit A – Scope of Work. City has the authority to stop work or to suspend any work.

  • Responsibilities of the Contractor The Contractor shall provide all technical and professional expertise, knowledge, management, and other resources required for accomplishing all aspects of the tasks and associated activities identified in the Scope of Work. In the event that the need arises for the Contractor to perform services beyond those stated in the Scope of Work, the Contractor and the City shall negotiate mutually agreeable terms and compensation for completing the additional services.

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