Foreground design documentation and Purchaser Data Clause Samples

Foreground design documentation and Purchaser Data. The Parties agree that each IPR comprised in or protecting the Foreground Design Documentation, and any Purchaser Owned Developments, and/or Purchaser Data (in this Clause 6, together "Purchaser IPRs") shall be owned by the Purchaser. To this end: 6.1.1 the Contractor hereby assigns (partially by way of a future assignation of IPRs on creation) its entire right title and interest in each Purchaser IPR to the Purchaser; and 6.1.2 the Contractor hereby undertakes, at the request and expense of the Purchaser, to do all acts and to execute all documents, forms and authorisations required to transfer full title to each Purchaser IPR to the Purchaser; and 6.1.3 the Contractor hereby undertakes, at the request and expense of the Purchaser, to deliver to the Purchaser a copy of any manifestation of an Purchaser IPR then in its possession or control. The Purchaser hereby grants the Contractor a licence during the term of this Contract to use Purchaser IPRs solely for the purpose of performing the Contractor's obligations under this Contract.
View SourceView Similar (3)
Foreground design documentation and Purchaser Data. The Parties agree that each IPR comprised in or protecting the Foreground Design Documentation, and any Purchaser Owned Developments, and/or Purchaser Data (in this Clause 6, together "Purchaser IPRs") shall be owned by the Purchaser. To this end:
View Source

Related to Foreground design documentation and Purchaser Data

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

  • 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

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

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

  • Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.