Service Specification and Technical Solution Sample Clauses

Service Specification and Technical Solution. 5.2.1 The Operator shall provide the Services: (a) so as to meet the Service Specification; (b) in accordance with the Technical Solution. 5.2.2 To avoid doubt, the obligations in Clauses 5.2.1(a) and 5.2.1(b) are independent obligations. In particular: (a) the fact that Operator has acted in accordance with the Technical Solution shall not be a defence to an allegation that the Operator has not met the Service Specification; and (b) the fact that Operator has met the Service Specification shall not be a defence to an allegation that the Operator has failed to provide the Services in accordance with the Technical Solution. 5.2.3 Without prejudice to Clause 5.2.1 if it should be found that the Technical Solution does not fulfil the Service Specification, the Operator shall at its own expense amend the Technical Solution and rectify the Services or any part affected.
AutoNDA by SimpleDocs

Related to Service Specification and Technical Solution

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

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

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

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

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

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

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

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

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