Field notebook Sample Clauses

Field notebook. You will be asked to keep a well-organized field notebook that documents what you are doing at each step of the project. This is particularly important because a great deal of effort, time, and money is being expended to collect and analyze this data. When in doubt, write it down. These notebooks will remain with the lab and should be sufficiently clear to allow another student working on the project or myself to understand what you have done and what should be done next. General lab notebook guidelines apply. All notes should be written in non-erasable ink. All notes and numbers should be clearly legible. Data or material that is incorrect should be crossed out but left such that the original is still legible. Also, an explanation should be appended to clarify what the error was. At the end of each page, sign on the bottom of the page. At the end of your field season, your notebook will remain in the lab. However, you may take a copy of it with you.
AutoNDA by SimpleDocs

Related to Field notebook

  • Computer The Contractor shall maintain at its office for its use a computer with, at a minimum, a 1 GHz processor and an internet connection. The Contractor shall maintain individual email accounts for each of its project managers.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Devices BNY Mellon will restrict the transfer of Customer Data from its network to mass storage devices. BNY Mellon will use a mobile device management system or equivalent tool when mobile computing is used to provide the services. Applications on such authenticated devices will be housed within an encrypted container and BNY Mellon will maintain the ability to remote wipe the contents of the container.

  • MANUALS Each product delivered under contract to any Customer must be delivered with at least one (1) copy of a safety and operating manual and any other technical or maintenance manual. The cost of the manual(s) must be included in the price for the Product offered.

  • Software Title and ownership to Existing Software Product(s) delivered by Contractor under the Contract that is normally commercially distributed on a license basis by the Contractor or other independent software vendor proprietary owner (“Existing Licensed Product”), embedded in the Custom Products, shall remain with Contractor or the proprietary owner of other independent software vendor(s) (ISV). Effective upon acceptance, such Product shall be licensed to Authorized User in accordance with the Contractor or ISV owner’s standard license agreement, provided, however, that such standard license, must, at a minimum: (a) grant Authorized User a non-exclusive, perpetual license to use, execute, reproduce, display, perform, adapt (unless Contractor advises Authorized User as part of Contractor’s proposal that adaptation will violate existing agreements or statutes and Contractor demonstrates such to the Authorized User’s satisfaction) and distribute Existing Licensed Product to the Authorized User up to the license capacity stated in the Purchase Order or work order with all license rights necessary to fully effect the general business purpose(s) stated in the Bid or Authorized User’s Purchase Order or work order, including the financing assignment rights set forth in paragraph (c) below; and (b) recognize the State of New York as the licensee where the Authorized User is a state agency, department, board, commission, office or institution. Where these rights are not otherwise covered by the ISV’s owner’s standard license agreement, the Contractor shall be responsible for obtaining these rights at its sole cost and expense. The Authorized User shall reproduce all copyright notices and any other legend of ownership on any copies authorized under this clause. Open source software is developed independently of Contractor and may be governed by a separate license (“open source software”). If the open source software is governed by a separate License and provided under this Contract, Contractor shall provide a copy of that license in the applicable Documentation and the Authorized User's license rights and obligations with respect to that open source software shall be defined by those separate license terms and subject to the conditions, if any, therein. Nothing in this Contract shall restrict, limit, or otherwise affect any rights or obligations the Authorized User may have, or conditions to which the Authorized User may be subject, under such separate open source license terms.

  • Proprietary Materials Each of the Parties shall own its own intellectual property including without limitation all trade secrets, know-how, proprietary data, documents, and written materials in any format. Any materials created exclusively by IPS for the School shall be owned by IPS, and any materials created exclusively by Operator for the School shall be Operator’s proprietary material. The Parties acknowledge and agree that neither has any intellectual property interest or claims in the other Party’s proprietary materials. Notwithstanding the foregoing, materials and work product jointly created by the Parties shall be jointly owned by the Parties and may be used by the individual Party as may be agreed upon by both Parties from time to time.

  • Images If applicable, the CONSULTANT is prohibited from capturing on any visual medium images of any property, logo, student, or employee of the DISTRICT, or any image that represents the DISTRICT without express written consent from the DISTRICT.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

  • Firmware The Contractor shall deliver firmware required for production acceptance testing in accordance with CDRL A009 Contractor’s Supplier Configuration Management Plan. The Contractor shall use Government furnished software for testing. Deliverable Data Item (See DD-1423): CDRL A009: “Contractor’s Supplier Configuration Management Plan”

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

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