Licensing of Weapons Sample Clauses

Licensing of Weapons. Palestinian policemen entitled to carry handguns within the Palestinian wing in the course of their duty pursuant to Paragraph 2 above, shall be required to obtain a written license from all of the following: a. The Council; b. The Manager of the Palestinian wing; and c. The Director-General.
AutoNDA by SimpleDocs
Licensing of Weapons. Licensing of all weapons required by the Security Personnel will be the responsibility of Operator.

Related to Licensing of Weapons

  • Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.

  • COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Licensing Schemes and Geographic Scope The following provisions do not apply to the Quintiq Last Mile Edition (5MB-LEQ) nor to Quintiq Last Mile Shipments (for Retail) (5MP-LMQ) nor to Quintiq Last Mile Shipments (for Express) (5MP-LMQ-X) 3DS Offerings. For the Quintiq Last Mile Edition (5MB-LEQ), Quintiq Last Mile Shipments (for Retail) (5MP-LMQ) and Quintiq Last Mile Shipments (for Express) (5MP-LMQ-X) 3DS Offerings, please refer to section 5 hereinafter.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • CUTTING AND PATCHING OF WORK 4.14.1 The Contractor shall be responsible for all cutting, fitting or patching that may be required to complete the Work or to make its several parts fit together properly. 4.14.2 The Contractor shall not damage or endanger any portion of the Work or the work of the State or any separate contractors by cutting, patching or otherwise altering any work, or by excavation. The Contractor shall not cut or otherwise alter the work of the State or any separate contractor except with the written consent of the State and of such separate contractor. The Contractor shall not unreasonably withhold from the State or any separate contractor his consent to cutting or otherwise altering the Work.

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • SEXUAL EXPLOITATION 18.1 The Contractor shall take all appropriate measures to prevent sexual exploitation or abuse of anyone by it or by any of its employees or any other persons who may be engaged by the Contractor to perform any services under the Contract. For these purposes, sexual activity with any person less than eighteen years of age, regardless of any laws relating to consent, shall constitute the sexual exploitation and abuse of such person. In addition, the Contractor shall refrain from, and shall take all appropriate measures to prohibit its employees or other persons engaged by it from, exchanging any money, goods, services, offers of employment or other things of value, for sexual favors or activities, or from engaging in any sexual activities that are exploitive or degrading to any person. The Contractor acknowledges and agrees that the provisions hereof constitute an essential term of the Contract and that any breach of this representation and warranty shall entitle UNDP to terminate the Contract immediately upon notice to the Contractor, without any liability for termination charges or any other liability of any kind. 18.2 UNDP shall not apply the foregoing standard relating to age in any case in which the Contractor’s personnel or any other person who may be engaged by the Contractor to perform any services under the Contract is married to the person less than the age of eighteen years with whom sexual activity has occurred and in which such marriage is recognized as valid under the laws of the country of citizenship of such Contractor’s personnel or such other person who may be engaged by the Contractor to perform any services under the Contract.

  • Research License Each Collaborator shall allow the other Collaborator to practice any of its Non- Subject Inventions for the purpose of performing the Cooperative Work. No license, express or implied, for commercial application(s) is granted to either Collaborator in Non-Subject Inventions by performing the Cooperative Work. For commercial application(s) of Non-Subject Inventions, a license must be obtained from the owner.

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