Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.
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.
Design Guidelines The Owner’s “Design Guidelines” are as published on the Owner’s website (xxxx://xxxxx.xxxxx.xxx/for-vendors/design-guidelines/). In addition to providing a guide to be used in the preparation of design documents for the Owner’s construction projects, the Design Guidelines also contain regulatory code compliance and other Owner requirements. The “Effective Date” (as noted in Section 2.7 of the Design Guidelines), determining which edition will be used for a given project, is set at the beginning of Design Development and will govern the preparation of construction documents for the project unless noted otherwise. Compliance with the Design Guidelines does not relieve the Design Professional from any of its responsibility.
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.
Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.
Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet
Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.
Intellectual Property Rights in Construction Documents, Drawings, and Models The drawings, Specifications and other documents prepared by the Design Professional pursuant to this Contract (including, without limitation, the Construction Documents), are the property of the Owner, whether or not the Project for which they are made commences or completes construction. Neither the Contractor nor any Subcontractor or material or equipment supplier shall own or claim a copyright in such drawings, Specifications, and other similar or related documents; Owner shall retain all common law, statutory, and other intellectual property rights with respect thereto. The Contractor must deliver remaining copies of such documents to the Owner upon request or upon completion of the Work, except that the Contractor may keep one copy of such documents for its files. The Contractor shall only use such drawings, Specifications and other documents for this Project. Neither the Contractor nor any Subcontractor or material or equipment supplier may use such drawings, Specifications, and other documents on other projects without the specific written consent of the Owner. All models are the property of the Owner.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
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.
