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.
General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.
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.
Changes to Specifications All Specifications and any changes thereto agreed to by the Parties from time to time shall be in writing, dated and signed by the Parties. No change in the Specifications shall be implemented by Cardinal Health, whether requested by Reliant or requested or required by any Regulatory Authority, until the Parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change. Cardinal Health shall respond promptly to any request made by Reliant for a change in the Specifications, and both Parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. If after initial Product qualification, Reliant requests a change in the Specifications for its own benefit or to comply with the requirements of a Regulatory Authority, the Specifications shall be amended as soon as [***]: Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. possible after a request is made for any change in Specifications, and Cardinal Health shall notify Reliant of the costs associated with such change and shall provide such supporting documentation as Reliant may reasonably require. Reliant shall pay all costs associated with such Reliant-requested changes or changes required by a Regulatory Authority as may be agreed upon by the Parties. Changes, agreed to between the Parties, for the benefit of Cardinal Health, shall be at the expense of Cardinal Health. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control.
Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.
Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.
Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.
Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.
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.
Class Specifications The Human Resources Division shall determine:
