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.
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.
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
Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.
Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.
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.
Delivery of Software 1. SAP will deliver the Software as described in the Documentation and the Price List and will also provide the appropriate license key for the relevant End User. With regard to the features, quality and functionality of the Software the product description in the Documentation and the Price List is solely decisive. SAP does not own any additional features, quality or functionality. Distributor can, in particular, not assert any additional feature, quality or functionality from any public statements, publications or advertisements by SAP except to the extend SAP has expressly confirmed such additional feature, quality or functionality in writing. Any representation, warranty, undertaking or guarantee regarding additional features, quality or functionality is effective only if expressly confirmed by SAP’s management in writing.
2. After acceptance of an order, SAP will deliver to Distributor one copy of the relevant Software:
a) on discs or other data media (“Physical Shipment”); or
b) by making it available for downloading through the internet (usually on the SAP ServiceMarket Place (xxxx://xxxxxxx.xxx.xxx/swdc)) (“Electronic Delivery”).
3. The relevant Software and Documentation will be deemed delivered (including but not limited for the purpose of fixed delivery dates or timely delivery) and the risk passes to Distributor:
a) in case of Physical Shipment, when the relevant disc or other data media thereof is handed over to the freight carrier (FCA - Free Carrier (named place of delivery), Incoterms 2010); or
b) in case of Electronic Delivery, when SAP has made an electronic copy thereof available for downloading and has informed Distributor accordingly, (“Delivery”).
4. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant Open Ecosystem Partner instead (“Open Ecosystem Partner Delivery”). In case of Open Ecosystem Partner Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the Open Ecosystem Partner.
5. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant End User instead (“End User Delivery”). In case of End User Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the End User.
6. SAP might be entitled to suspend the delivery of the Software, Maintenance Services, applicable license key or both to Distributor, Open Ecosystem Partner or End User or both as further set out in this Sell On Premise Distribution Model as well as the Distribution GTCS.
7. If Distributor receives a new copy of the Software, Documentation and/or other SAP Materials that replaces previously provided Software, Documentation and/or other SAP Materials, Distributor must distribute that newest copy provided and either destroy or upon SAP’s request return previous copies.
8. Distributor must not make the Software, Documentation and/or other SAP Materials available to the Open Ecosystem Partner or End User by any means other than by delivering the Software, Documentation and/or other SAP Materials as originally provided by SAP. Distributor’s right to pass on the Software, Documentation and/or other SAP Materials is subject to the provisions of this Agreement.
Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.
Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.
LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
