Use of Unmanned Aircraft Systems Sample Clauses

Use of Unmanned Aircraft Systems. The Consultant shall adhere to Administrative Regulation 3580 as there are strict prohibitions outlined regarding the use of drones. For further reference and information please read AR 3580 located on the RSCCD website at xxxx://xxx.xxxxx.xxx/Trustees/Pages/AR-3581.aspx.
AutoNDA by SimpleDocs
Use of Unmanned Aircraft Systems. The ENGINEER shall not use or operate Unmanned Aircraft Systems (UAS) without the express written approval of the COMMISSION. Such approval shall be determined upon review and authorization of a written request from the ENGINEER by the COMMISSION’s Legal Department and UAS program managers. If approved, the ENGINEER shall execute a separate Authorization to Operate UAS or other applicable third-party agreement prepared by the COMMISSION’s Legal Department setting forth the necessary indemnification, release and insurance requirements. The Authorization shall define the requirements the ENGINEER must follow in order to operate UAS within COMMISSION right-of-way and property. All approved UAS operations shall be conducted using Small Unmanned Aircraft Rule (Part 107) (14 CFR Part 107) of the Federal Aviation Administration (FAA) Regulations.

Related to Use of Unmanned Aircraft Systems

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • OGS Centralized Contract: Terms and Conditions The terms and conditions set forth in this section are expressly incorporated in and applicable to the Contract. Captions are intended as descriptive and are not intended to limit or otherwise restrict the terms and conditions set forth herein. Appendix A Appendix A, Standard Clauses for New York State Contracts, dated January 2014, attached hereto, is hereby incorporated in, and expressly made a part of, this Contract. Appendix B Appendix B, Office of General Services General Specifications, dated January 2015 22772 Project Based Information Technology Consulting (Statewide), attached hereto, is hereby incorporated in, and expressly made a part of, this Contract.

  • Operational Support Systems (OSS 2.13.1 BellSouth has developed and made available the following electronic interfaces by which <<customer_name>> may submit LSRs electronically. LENS Local Exchange Navigation System EDI Electronic Data Interchange TAG Telecommunications Access Gateway

  • DELIVERY TERMS AND TRANSPORTATION CHARGES Deliverables shall be shipped F.O.B. point of delivery unless otherwise specified in the Supplemental Terms and Conditions. Unless otherwise stated in the Offer, the Contractor’s price shall be deemed to include all delivery and transportation charges. The City shall have the right to designate what method of transportation shall be used to ship the deliverables. The place of delivery shall be that set forth the purchase order.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

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

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

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