Specification of Deliverables and Implementation Sample Clauses

Specification of Deliverables and Implementation. IL and AOL agree that ------------------------------------------------- the architecture design for the Auction Service shall be consistent with Schedule "F" (as amended by mutual agreement from time to time). AOL shall provide IL with a written request specifying any Deliverables to be performed in connection with AOL's right to direct AOL Users by way of an AOL Interactive Service. IL, acting in good faith, shall consider and shall provide AOL with a reasonable business proposal with respect thereto. Once agreed upon, the Parties shall set out a detailed statement of work, specifications and an implementation schedule in an addendum hereto. The Parties will also agree on an implementation schedule for the Deliverables. IL will provide AOL with technical support and training in connection with AOL's use of the Software. IL shall also provide all Services necessary or desirable to permit AOL to support the Deliverables without recourse to IL.
View SourceView Similar (2)

Related to Specification of Deliverables and Implementation

  • 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-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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 purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • 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 For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.