Auction Specification Sample Clauses

Auction Specification. 1. The Allocation Platform shall publish the Auction Specification as set forth in paragraph 2 of this Article.
Sample 1Sample 2Sample 3See All (29)
AutoNDA by SimpleDocs
Auction Specification. 1. The Allocation Platform shall publish the Auction Specification as set forth in paragraphs 2 of this Article no later than 09:00 a.m. on the day preceding the delivery day.
Sample 1Sample 2Sample 3See All (20)
Auction Specification. 1. The Allocation Platform shall publish a provisional version of the Auction Specification and a final version of the Auction Specification as set forth in paragraphs 2 to 3 of this Article.
Sample 1Sample 2Sample 3See All (19)
Auction Specification. 1. If Shadow Auctions are triggered during a daily session of the MRC, no Auction Specification is published, only the Offered Capacity is published on the website
Sample 1Sample 2Sample 3See All (5)
Auction Specification. 1. Auction Specification is published 15 minutes before the opening of bidding period.
Sample 1Sample 2Sample 3
Auction Specification. 1. The Allocation Platform shall publish the Auction Specification no later than 15 minutes before the end of the Bidding Period of an Auction. The Auction Specification shall state in particular:
Sample 1Sample 2Sample 3
Auction Specification. 1. The Allocation Platform shall publish the Auction Specification in accordance with the provisions of this Rule 21.
Sample 1Sample 2
AutoNDA by SimpleDocs
Auction Specification. Information on a specific Auction provided on the Auction Website and/or Auction Tool/Auction System.
Sample 1Sample 2
Auction Specification. 1. The Allocation Platform shall publish the Auction Specification as set forth in paragraphs 2 of this Article no later than 09:00 a.m. on the day proceeding the delivery day. 2. The Auction Specification shall state in particular: (a) the code identifying the Auction in the Auction Tool; (b) identification of the Bidding Zone border(s) or a subset of the Interconnectors on the Bidding Zone border and direction covered; (c) the Product Period; (d) the Bidding Period which in case of regular operational conditions starts at 09:00 a.m. and ends at 09:30 a.m. on the day preceding the delivery day; (e) the deadline for the publication of the provisional Auction results which is in case of regular operational conditions 09:32 a.m. on the day preceding the delivery day; (f) the deadline for the publication of the final Auction results which is in case of regular operational conditions 10:00 a.m. on the day preceding the delivery day; (g) the Offered Capacity which shall include Cross Zonal Capacity released in accordance with Articles 55 and 56; and (h) any other relevant information or terms applicable to the product or the Auction.
Sample 1

Related to Auction Specification

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Classification Specifications The Employer agrees to supply the President of the Union or his/her designate with the classification specifications for those classifications in the Bargaining Unit.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

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

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

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

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

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