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.
Failure to Meet Timelines Failure by the Union to comply with the timelines will result in the automatic withdrawal of the grievance. Failure by the Employer to comply with the timelines will entitle the Union to move the grievance to the next step of the procedure.
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.
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.
Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before December 31, 2020 Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.
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.
Commercial Milestones (a) Within [*****] calendar days after the end of the first Calendar Year in which aggregate annual Net Sales for that Calendar Year for the Licensed Product in the Territory reach any threshold indicated in the Commercial Milestone Events listed below, EverInsight shall notify VistaGen of the achievement of such Commercial Milestone Event and VistaGen shall invoice EverInsight for the corresponding non-refundable, non-creditable Milestone Payment set forth below and EverInsight shall remit payment to VistaGen within [*****] Business Days after the receipt of the invoice, as described in Section 8.6 (Currency; Exchange Rate; Payments). Annual Net Sales Milestones for Licensed Product Milestone Payments (in Dollars) (each a “Commercial Milestone Event”): (1). [*****] (2). [*****] (3). [*****] (4). [*****] (5). [*****] (b) For the purposes of determining whether a Net Sales Milestone Event has been achieved, Net Sales of Licensed Product(s) in the Territory shall be aggregated. For clarity, the annual Net Sales Milestone Payments set forth in this Section 8.3 (Commercial Milestones) shall be payable only once, upon the first achievement of the applicable Commercial Milestone Event, regardless of how many times such Commercial Milestone Event is achieved. (c) If a Commercial Milestone Event in Section 8.3 (Commercial Milestones) is achieved and payment with respect to any previous Commercial Milestone Event in Section 8.3 has not been made, then such previous Commercial Milestone Event shall be deemed achieved and EverInsight shall notify VistaGen within fifteen (15) calendar days of such achievement. VistaGen shall then invoice EverInsight for such unpaid previous Commercial Milestone Event(s) and EverInsight shall pay VistaGen such unpaid previous milestone payment(s) within thirty (30) Business Days of receipt of such invoice. (d) In the event that, VistaGen believes any Commercial Milestone Event under Section 8.3(a) has occurred but EverInsight has not given VistaGen the notice of the achievement of such Commercial Milestone Event, it shall so notify EverInsight in writing and shall provide to EverInsight data, documentation or other information that supports its belief. Any dispute under this Section 8.3(d) (Commercial Milestones - subsection (d)) that relates to whether or not a Commercial Milestone Event has occurred shall be referred to the JSC to be resolved in accordance with ARTICLE 3 (Governance) and shall be subject to resolution in accordance with Section 14.10 (Dispute Resolution). The Milestone Payments made for each Commercial Milestone Event shall be non-creditable and non-refundable.
Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service xxxx, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.
Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.
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.
