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.
Schematic Design Documents In accordance with the approved Preliminary Design and Construction Schedule and based upon approval of and comments made by the Owner regarding the Concept Design Studies, the Design Professional shall prepare and submit to the Owner Schematic Design Documents, including drawings and outline specifications. These documents shall represent a further development of the approved design concept, providing additional detail and specificity regarding the intended design solution. Typically, all such documents shall be drawn to scale, indicating materials and assemblies, as appropriate, to convey the design intent and to illustrate the Project’s basic elements, scale and relationship to the Site. All major pieces of furniture and equipment to be fixed or supplied by the CM/GC shall be illustrated to scale. (See ASTM Standard Practice E 1804-02, August 2007, Sections 6.3, 8.2 and 8.3 for guidance on information which is generally developed in Schematic Design.)
Schematic Design See Section 2, Part 1, Article 2.1.4, Paragraph 2.1.4.2.
General Application The rules set forth below in this Article VI shall apply for the purposes of determining each Member’s allocable share of the items of income, gain, loss and expense of the Company comprising Net Income or Net Loss for each Fiscal Year, determining special allocations of other items of income, gain, loss and expense, and adjusting the balance of each Member’s Capital Account to reflect the aforementioned general and special allocations. For each Fiscal Year, the special allocations in Section 6.03 hereof shall be made immediately prior to the general allocations of Section 6.02 hereof.
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.
JOB FAMILY: APPLICATIONS DEVELOPMENT Job Title: Director, Systems and Programming Job#: 1200 General Characteristics
Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.
Application of Funding Techniques to Programs 6.3.1 The State shall apply the following funding techniques when requesting Federal funds for the component cash flows of the programs listed in sections 4.2 and 4.3 of this Agreement. 6.3.2 Programs Below are programs listed in Section 4.2 and Section 4.3.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Provisional Application Upon signature of this Compact, and until this Compact has entered into force in accordance with Section 7.3, the Parties will provisionally apply the terms of this Compact; provided that, no MCC Funding, other than Compact Implementation Funding, will be made available or disbursed before this Compact enters into force.
