Schematic Design Phase 1.2.1 Based on the mutually agreed upon Program of Requirements, Amount Available for the Construction Contract and the Project Schedule, the Architect/Engineer shall prepare sufficient alternative approaches utilizing BIM for design and construction of the Project to satisfy Owner’s project requirements and shall, at completion of this phase, submit Schematic Design Documents derived from the model in accordance with the BIM Execution Plan, “Facility Design Guidelines” and any additional requirements set forth in Article 15. The Architect/Engineer shall review alternative approaches to design and construction for the Project as they are being modeled at intervals appropriate to the progress of the Project with the Owner and Construction Manager at the Project site or other location specified by the Owner within the State of Texas. The Architect/Engineer shall utilize the model(s) to support the review process during Schematic Design. The Architect/Engineer shall provide the Construction Manager with a compact disc containing documents and data files derived from the model to assist the Construction Manager in fulfilling its responsibilities to the Owner.
1.2.2 Architect/Engineer shall provide all services necessary to perform the services of this phase (preparation of model(s), relevant data, decision support model views and Schematic Design Documents) including, without limitation, unless otherwise approved by Owner, the preparation and prompt delivery of all items specified in the BIM Execution Plan and “Facility Design Guidelines”.
1.2.3 Architect/Engineer shall work closely with Owner in preparation of schematic drawings and shall specifically conform to Owner’s requirements regarding aesthetic design issues.
1.2.4 The Architect/Engineer shall review the Estimated Construction Cost prepared by the Construction Manager, and shall provide written comments.
1.2.5 Before proceeding into the Design Development Phase, the Architect/Engineer shall obtain Owner’s written acceptance of the Schematic Design documents and approval of the Architect/Engineer’s preliminary Estimated Construction Cost and schedule.
1.2.6 The Architect/Engineer shall participate in a final review of the Schematic Design Documents and model(s) with the Owner and Construction Manager at the Project site or other location specified by Owner in the State of Texas. Prior to the Owner’s approval of the Schematic Design Documents, the Architect/Engineer shall incorporate such changes as are necessary to satisfy the Owner’s review comments, any of which may be appealed for good cause.
Design Standards Most recent edition of the “Owner’s Design Standards,” including any partial updates as may be directed by the Owner.
Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.
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.”
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
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.
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.
Design Criteria and Standards All Projects/Services shall be performed in accordance with instructions, criteria and standards set forth by the Director.
Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.
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.
