Revit Template Clause Samples

The Revit Template clause defines the requirements and standards for the use of a specific Revit template in a project. It typically specifies which template file must be used for all project modeling, ensuring consistency in elements such as families, parameters, and project settings. By mandating a uniform template, this clause helps maintain standardization across all project deliverables, reducing errors and streamlining collaboration among team members.
Revit Template. Queens University will provide a Revit Template file for the purposes of transferring Project Parameters to all discipline files. All disciplines involved in the project shall use Transfer Project Standards within Revit to transfer all Queen’s University project parameters into their working model. These project parameters will be applied to mechanical and electrical equipment. It is the responsibility of the discipline to ensure all parameter information is accurate at the time of submission. The content of these parameters will be subject to scrutiny during the Model Check. 8.3.7.1. Titleblock Queens University maintains three titleblock sizes – 24x36, 18x24, and 11x17. These will be provided as part of the Queen’s University Revit Template and shall be used by all disciplines.

Related to Revit Template

  • TEMPLATE A software file containing all possible prize values for a Game Set to be created, indicating the number of prizes for each prize value that will appear in the Game Set.

  • State Specific Contract Form Observe the state of the Seller on the Contract, if the Seller lists an address in Alaska, Arkansas, Delaware, North Carolina, Virginia, Maryland, Montana, Connecticut, Vermont, Louisiana or Mississippi, confirm the form number on the Contract is on the List of Approved Contract Forms, for the corresponding state.

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

  • Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”). Data Escrow. Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and