Checklist approach Sample Clauses

Checklist approach. 178. In EC – Bed Linen, the European Community objected to what it termed the "checklist" approach to the list of factors under Article 3.4 and argued that the relevance of some factors may be apparent early in the investigation. The Panel concluded that "as long as the lack of relevance or materiality of the factors not central to the decision is at least implicitly apparent from the final determination, the Agreement's requirements are satisfied. While a checklist would perhaps 236 Panel Report, Guatemala – Cement II, para. 8.283. 237 Appellate Body Report, EC – Tube or Pipe Fittings, para. 131. 238 Appellate Body Report, EC – Tube or Pipe Fittings, para. 157. 239 Appellate Body Report, EC – Tube or Pipe Fittings, paras. 161-162.
AutoNDA by SimpleDocs

Related to Checklist approach

  • Checklist The Service will be able to respond more quickly to a VCP request if the request is carefully prepared and complete. The checklist in Appendix C is designed to assist Plan Sponsors and their representatives in preparing a submission that contains the information and documents required under this revenue procedure. The checklist in Appendix C must be completed, signed, and dated by the Plan Sponsor or the Plan Sponsor's representative, and should be placed on top of the submission. A photocopy of this checklist may be used.

  • Inspection Checklist (check one) ☐ In order to avoid disagreements about the condition of the Premises, at the time of accepting possession of the Premises, Tenant will complete the Inspection Checklist incorporated herein by reference and attached hereto as Exhibit B and record any damage or deficiencies that exist at the commencement of the Term. Landlord will be liable for the cost of any cleaning or repair to correct damages found at the time of the inspection. Tenant will be liable for the cost of any cleaning and/or repair to correct damages found at the end of the Term if not recorded on the inspection checklist, normal wear and tear excepted. ☐ The Tenant is NOT required to complete an inspection checklist.

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Escrow Format Specification 3.1. 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.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

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

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