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.
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
Construction materials (1) The restrictions of section 1605 of the American Recovery and Reinvestment Act of 2009 (Pub. L. 111-5) (Recovery Act) do not apply to Recovery Act designated country manufactured construction material. The restrictions of the Buy American statute do not apply to designated country unmanufactured construction material. Consistent with U.S. obligations under international agreements, this clause implements--
Software Products Save as otherwise set forth in the Agreement, the right to use any Software Product is personal to the Licensee, for its own internal use, and is non-transferable, except with the Licensor’s prior written consent, in which case the Licensee shall cause the assignee or sub-licensee to agree to the terms of this Software License.
Software Inclusions Restrictions
Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.
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.
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.
Records and Documentation The Sub-Recipient agrees to make available to AAAPP staff and/or any party designated by the AAAPP any and all contract related records and documentation. The Sub-Recipient shall ensure the collection and maintenance of all program related information and documentation on any such system designated by the AAAPP. Maintenance includes valid exports and backups of all data and systems according to AAAPP standards.
Source Documentation Accounting records must be supported by such source documentation as canceled checks, bank statements, invoices, paid bills, donor letters, time and attendance records, activity reports, travel reports, contractual and consultant agreements, and subaward documentation. All supporting documentation should be clearly identified with the Award and general ledger accounts which are to be charged or credited. (i) The documentation standards for salary charges to grants are prescribed by 2 CFR 200.430, and in the cost principles applicable to the entity’s organization (Paragraphs 7.4 through 7.7). (ii) If records do not meet the standards in 2 CFR 200.430, then Grantor may notify Grantee in PART TWO, PART THREE or Exhibit G of the requirement to submit Personnel activity reports. See 2 CFR 200.430(i)(8). Personnel activity reports shall account on an after-the-fact basis for one hundred percent (100%) of the employee's actual time, separately indicating the time spent on the grant, other grants or projects, vacation or sick leave, and administrative time, if applicable. The reports must be signed by the employee, approved by the appropriate official, and coincide with a pay period. These time records should be used to record the distribution of salary costs to the appropriate accounts no less frequently than quarterly. (iii) Formal agreements with independent contractors, such as consultants, must include a description of the services to be performed, the period of performance, the fee and method of payment, an itemization of travel and other costs which are chargeable to the agreement, and the signatures of both the contractor and an appropriate official of Grantee. (iv) If third party in-kind (non-cash) contributions are used for Grant purposes, the valuation of these contributions must be supported with adequate documentation.
