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.
Technical Specifications and Drawings a) The Goods and Related Services supplied under this Contract shall conform to the technical specifications and standards mentioned in Section VI, Schedule of Requirements and, when no applicable standard is mentioned, the standard shall be equivalent or superior to the official standards whose application is appropriate to the Goods' country of origin. b) The Supplier shall be entitled to disclaim responsibility for any design, data, drawing, specification or other document, or any modification thereof provided or designed by or on behalf of the Procuring Entity, by giving a notice of such disclaimer to the Procuring Entity. c) Wherever references are made in the Contract to codes and standards in accordance with which it shall be executed, the edition or the revised version of such codes and standards shall be those specified in the Schedule of Requirements. During Contract execution, any changes in any such codes and standards shall be applied only after approval by the Procuring Entity and shall be treated in accordance with GCC Clause 33.
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. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client 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 (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client 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. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.
General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:
Drawings and Specifications 9.1 A complete list of all Drawings that form a part of the Contract Documents are to be found as an index on the Drawings themselves, and/or may be provided to Developer and/or in the Table of Contents. 9.2 Materials or Work described in words that so applied have a well-known technical or trade meaning shall be deemed to refer to recognized standards, unless noted otherwise. 9.3 Trade Name or Trade Term It is not the intention of the Contract Documents to go into detailed descriptions of any materials and/or methods commonly known to the trade under “trade name” or “trade term.” The mere mention or notation of “trade name” or “trade term” shall be considered a sufficient notice to Developer that it will be required to complete the work so named, complete, finished, and operable, with all its appurtenances, according to the best practices of the trade. 9.4 The naming of any material and/or equipment shall mean furnishing and installing of same, including all incidental and accessory items thereto and/or labor therefor, as per best practices of the trade(s) involved, unless specifically noted otherwise. 9.5 Contract Documents are complementary, and what is called for by one shall be binding as if called for by all. As such, Drawings and Specifications are intended to be fully cooperative and to agree. However, if Developer observes that Drawings and Specifications are in conflict with the Contract Documents, Developer shall promptly notify District and Architect in writing, and any necessary changes shall be made as provided in the Contract Documents. 9.6 Figured dimensions shall be followed in preference to scaled dimensions, and Developer shall make all additional measurements necessary for the work and shall be responsible for their accuracy. Before ordering any material or doing any work, each Developer shall verify all measurements at the building and shall be responsible for the correctness of same. 9.7 Should any question arise concerning the intent or meaning of the Contract Documents, including the Plans and Specifications, the question shall be submitted to the District for interpretation. If a conflict exists in the Contract Documents, these Construction Provisions shall control over the Facilities Lease, which shall control over the Site Lease, which shall control over Division 1 Documents, which shall control over Division 2 through Division 49 documents, which shall control over figured dimensions, which shall control over large-scale drawings, which shall control over small-scale drawings. In no case shall a document calling for lower quality and/or quantity of material or workmanship control. However, in the case of discrepancy or ambiguity solely between and among the Drawings and Specifications, the discrepancy or ambiguity shall be resolved in favor of the interpretation that will provide District with the functionally complete and operable Project described in the Drawings and Specifications. 9.8 Drawings and Specifications are intended to comply with all laws, ordinances, rules, and regulations of constituted authorities having jurisdiction, and where referred to in the Contract Documents, the laws, ordinances, rules, and regulations shall be considered as a part of the Contract Documents within the limits specified. 9.9 As required by Section 4-317(c), Part 1, Title 24, CCR: “Should any existing conditions such as deterioration or non-complying construction be discovered which is not covered by the DSA-approved documents wherein the finished work will not comply with Title 24, California Code of Regulations, a construction change document, or a separate set of plans and specifications, detailing and specifying the required repair work shall be submitted to and approved by DSA before proceeding with the repair work.”
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.
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.
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.
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.
