Scope Clarification Sample Clauses

Scope Clarification. The licenses and other rights granted in this Section 5.1 and the remainder of this Agreement will not grant or create (by implication, estoppel or otherwise) any license or right under any Aerpio Patent Rights, Aerpio Know-How, INDs listed on Exhibit D, or under the Aerpio In-License, to research, develop, manufacture or commercialize, make, use, sell, offer to sell or import any molecule that is not a Licensed Compound or any other molecule Covered by the Aerpio Patent Rights (including any other therapeutically active molecule in any Licensed Product).
AutoNDA by SimpleDocs
Scope Clarification. The high-level scope of this tender is to provide an integrated solution that fulfils the Document and Records Management functionality of the CCT. In addition to this requirement, the solution should also cater for the integration of a Case Management solution with the addition of a digital signature solution. The CCT also requires that the Workflow Engine should be capable to be utilised as an Enterprise-wide workflow engine. In addition to the above-mentioned requirements, the need for a digital signature, advanced search Engine and publish modules as defined in the functional requirements below. The emphasis of the various Document and Records management functions focus strongly on the provision of an integrated solution. The Document Management solution and the Record Management Solution can be from a single or two vendors, but these modules should be integrated and fulfil the functional requirements for these modules as stipulated in this document. The integration also includes integrations with any legacy systems or future systems that will come online during the RM&DM&CM implementation. . The Case Management module/system and the Digital Signature module/system should also integrate with the integrated RM&DM&CM solution and the current legacy systems or future systems.
Scope Clarification. Unless explicitly outlined in your Project Evaluation, these services are typically not included: 3D renderings; Construction Coordination, Monitoring, or Scheduling; Change orders; Reimbursable expenses (see below); Interviewing, Hiring or Firing of contractors or tradespeople; Merchandise Purchasing, Ordering, Storage, Delivery, Assembly, or Moving. Some of these services may be requested for an additional fee.
Scope Clarification. Scope Exclusions
Scope Clarification. (planting site distances, multi­stem measurements, natural areas, etc.)

Related to Scope Clarification

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Request for clarification of the report 1. Within 10 days of the release of the report, either of the disputing Parties may submit a written request to the Panel, a copy of which shall be sent to the other Party, for clarification of any items the Party considers requires further explanation or definition. 2. The Panel shall respond to the request within 10 days following the submission of such request. The clarification of the Panel shall only be a more precise explanation or definition of the original contents of the report, and not an amendment of such report. 3. The filing of this request for clarification will not postpone the effect of the Panel report nor the deadline for compliance of the adopted decision, unless the Panel decides otherwise.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Review Scope The parties confirm that the Asset Representations Review is not responsible for (a) reviewing the Receivables for compliance with the representations and warranties under the Transaction Documents, except as described in this Agreement or (b) determining whether noncompliance with the representations and warranties constitutes a breach of the Eligibility Representations. For the avoidance of doubt, the parties confirm that the review is not designed to determine why an Obligor is delinquent or the creditworthiness of the Obligor, either at the time of any Asset Review or at the time of origination of the related Receivable. Further, the Asset Review is not designed to establish cause, materiality or recourse for any Test Fail (as defined in Section 3.05).

  • Quality Assurance Program An employee shall be entitled to leave of absence without loss of earnings from her or his regularly scheduled working hours for the purpose of writing examinations required by the College of Nurses of Ontario arising out of the Quality Assurance Program.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

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