By: Kari Kelly Legal Counsel 5280 Solutions, a subsidiary of Nelnet, Inc. October 1, 2008.

Slides:



Advertisements
Similar presentations
© 2008 Oracle Corporation – Proprietary and Confidential.
Advertisements

G. Conti – Politecnico di Milano 2006 © 1/13 CRUI – WIPO 28 marzo 2006 Technology Transfer Office Setting up a license agreement: An Italian University.
Negotiating Technology License Agreements Tamara Nanayakkara.
© 2013 Sri U-Thong Limited. All rights reserved. This presentation has been prepared by Sri U-Thong Limited and its holding company (collectively, “Sri.
NEGOTIATING INFORMATION TECHNOLOGY SERVICE AGREEMENTS TOP TIPS TO CONSIDER © 2013, WILSON VUKELICH LLP. ALL RIGHTS RESERVED. Diane L. Karnay September.
Topics Changes Risk Assessments Cloud Data Security / Data Protection Licenses, Copies, Instances Limits of Liability and Indemnification Requests for.
IMPORTANT READ CAREFULLY BEFORE USING THIS PRODUCT LICENSE AGREEMENT AND LIMITED WARRANTY BY INSTALLING OR USING THE SOFTWARE, FILES OR OTHER ELECTRONIC.
NEGOTIATING SOFTWARE LICENSES FUNDAMENTALS © 2014, WILSON VUKELICH LLP. ALL RIGHTS RESERVED. Heather Whitten and Diane Karnay September 17, 2014.
Basics of Software Licensing The Good, the Bad, and the Dull (but necessary…) Hannah Alphey, September 2010.
Fosterswift.com PROTECTING AGAINST THE UNKNOWN : How to Successfully Review IT Contracts to Increase Your Rights and Avoid Potential Liability Samuel Frederick.
. Software Licenses T HE T EXAS A&M U NIVERSITY S YSTEM Nicholas E. Chremos, TAMUS Office of General Counsel November 8, 2012 O FFICE OF T ECHNOLOGY C.
Research Development for Android Coopman Tom. What is Android?  Smartphone operating system  Google  Popular  ‘Easy to develop’  Open-Source  Linux.
Jul The New Geant4 License J. Perl The New Geant4 License Makes clear the user’s wide- ranging freedom to use, extend or redistribute Geant4, even.
Copyright © 2004 by Prentice-Hall. All rights reserved. PowerPoint Slides to Accompany BUSINESS LAW E-Commerce and Digital Law International Law and Ethics.
By, Henry “Hank” Abromson, Esq.. Introduction  Henry “Hank” Abromson  Attorney with Miles & Stockbridge P.C. (Frederick)  Intellectual Property, Corporate,
A business law firm serving entrepreneurs, emerging growth companies and investors Licensing and Corporate Partnering An Overview of Licensing Agreements.
Constructing the “Price” of the Technology in IP Licensing Negotiations Sub Regional Training Program on IP Valuation Maribor November 5 to 7, 2012.
KEY PROVISIONS OF FRANCHISE AGREEMENTS Claro F. Certeza SPCMBLAW.
Software License Agreement Negotiation 101 Ray Hsu, C.P.M. Assistant Director, Procurement Services University of Washington.
WIPO NATIONAL WORKSHOP ON NEGOTIATING TECHNOLOGY LICENSING AGREEMENTS organized by The World Intellectual Property Organization (WIPO) in cooperation with.
Middleware Promises Warranties that Don’t Indemnities that Won’t Stephen Rubin, Esquire
Anastasiia Gordeeva The new regulation aimed at restriction of purchasing foreign-owned or foreign- originated software and databases by the.
DIRC Workshop on Software Quality and the Legal System 13 February 2004, Gray's Inn, London LEGAL ASPECTS OF SOFTWARE PROCUREMENT Jos Dumortier University.
March 27,2007CSMS - Savannah Negotiating a Fair Contract for Software and Services John Lateulere.
Richard E. Thompson II, Esq.
Contract Models for Virtual Teaching Helsinki University Porthania III 24 October 2001 Kristiina Harenko Attorneys at Law Borenius & Kemppinen Oy.
Andrew McNab - License issues - 10 Apr 2002 License issues for EU DataGrid (on behalf of Anders Wannanen) Andrew McNab, University of Manchester
Best Practices in Licensing Diane M. Reed Knobbe, Martens, Olson & Bear Rouz Tabaddor Vice President, Chief IP Counsel Corelogic Information Solutions,
Reasonable is in Eye of the Beholder Vendor, Customer, & Litigator Perspectives on Software License Provisions Aaron Brodsky Greg Leibold Peter Gergely.
Therapeutic area breakdown of lead projects in development for first launch in 2005 APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE METRICS PROGRAM ©
Custom Software Development Intellectual Property and Other Key Issues © 2006 Jeffrey W. Nelson and Iowa Department of Justice (Attach G)
Copyright 2008 The Prinz Law Office.1 Getting Started with Drafting a License Agreement: A Brief Guide to the Elements and Key Considerations By Kristie.
CRICOS No J a university for the world real R The OAK Law Project Queensland University of Technology CRICOS No J 1.
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 15 Sales and Lease Contracts: Performance, Warranties,
Proportion of biotech-derived active substances in development for first launch 31st December APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE.
International Telecommunication Union New Delhi, India, December 2011 ITU Workshop on Standards and Intellectual Property Rights (IPR) Issues Philip.
Mark Collins © 2015 Mark Collins.  Original, invented, creative, unique  Patents ◦ Protected through registration  Copyright ◦ Protected through litigation.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage Receipts.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage Supplier Returns.
Proportion of total R&D expenditure by therapeutic area in 2005 APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE METRICS PROGRAM © THOMSON REUTERS Your.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage and Disposition Inventory Returns.
Global R&D expenditure, development times, global pharmaceutical sales and new molecular entity output MARCH 2008 SOURCE: CMR INTERNATIONAL.
Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Inspect Material.
2005/2006 Expenditure on biotech derived entities had remained constant APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE METRICS PROGRAM © THOMSON REUTERS.
ANATOMY OF A LICENSE AGREEMENT. Licensor, Licensee and Licensed Property Title to the Intellectual Property being licensed Written agreement Licensing.
Top 10 Legal Minefields A University Perspective October 8, 2009 Catherine Shea Associate University Counsel University of Colorado.
Number of pharmaceutical patent applications and granted patents for 5 major patent issuing authorities JUNE 2008 SOURCE: DERWENT WORLD PATENTS.
Dino Tsibouris (614) Updates on Cloud, Contracting, Privacy, Security, and International Privacy Issues Mehmet Munur (614)
Oracle E-Business Suite R12.1 Accounts Payables Partner Boot Camp Training Courseware Part VIII – Transaction Taxes in Payables.
Regulatory approval times between submission and marketing authorization approval APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE METRICS PROGRAM.
Allocation of R&D expenditure in 2005 between chemical entity and biological or biotech active substances APRIL 2007 SOURCE: CMR INTERNATIONAL PERFORMANCE.
Key Legal Considerations for Agencies Wake Forest Business School Charlotte Campus June 12, 2013.
THE TOP TEN PITFALLS OF SOFTWARE CONTRACTING Texas K-12 CTO Council – Fall Meeting 2015 Lena Engel, Attorney.
1 Successful Technology Licensing: A Practical Guide.
HOW TO PROTECT YOUR INTEREST IN A SALE CONTRACT Focus on what you “get” when you sign!
Presented by: Tommy Mays, Legal Counsel Baptist Health Medical Center Health Contracting 101.
Intellectual Property And Data Rights Issues Domestic & Global Perspectives Bayh-Dole act -- rights in data Henry N. Wixon Chief Counsel National Institute.
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Oracle Proprietary and Confidential. 1.
Open Source Software Practices Quiz #8 October
Типичные ошибки и проблемы при лицензирования и продаже российских патентов в США by Dmitri Dubograev © 2010.
A Litigator’s View of Software License Agreements
Connectivity to bank and sample account structure
Customer Contracting/Licensing Obstacles & Pitfalls By: Mark E
Lecture 28 Intellectual Property(Cont’d)
Computer Law th class: Open Source.
מטלה 1-A-4 ניהול והכנת חוזים והזמנות
Customer Contracting/Licensing Obstacles & Pitfalls
Representations and Warranties Indemnification Liability Caps
WWEMA Water & Wastewater Equipment Manufacturers Association Inc
© 2013 Sri U-Thong Limited. All rights reserved
Presentation transcript:

By: Kari Kelly Legal Counsel 5280 Solutions, a subsidiary of Nelnet, Inc. October 1, 2008

 Introduction  Types of Licenses  End User License Agreement (EULA)  Click-Through / Click-Wrap Agreements / Shrink Wrap Agreements – "take it or leave it"  Negotiated software license agreements executed by the licensor and licensee  Software license terms included in negotiated agreements involving the purchase and sale of hardware or services  OEM  Reseller  Note: There is no "one-size-fits-all" software license agreement. Each deal will be different based on a number of factors. Page 2

 What is the business deal?  Who's using what, how, for how long?  What is the leverage?  How critical is the licensed software to the business?  Is there another source for the functionality?  How Licensed?  Per user/seat, per CPU, limited to a type of hardware or facility  License fee + maintenance and/or support  Subscription – monthly fee for usage Page 3

 Exclusive rights granted to owner of the copyright  To reproduce  To prepare derivative works  To distribute copies  To perform  To publicly display  Software constitutes a literary work Page 4

 Why used?  Copyright law only protects the expression of the idea but not the idea itself  Generally, courts are reluctant to interpret this right broadly  Patents can be used to prevent others from creating a competing program that uses the same ideas in an existing, patent-protected program  Limited due to bad patents where prior art was not adequately considered Page 5

 Terminology  Subject to the terms of this Agreement, Licensor grants to Licensee a perpetual, irrevocable, personal, non-assignable, non- exclusive license to use the Software in object form only solely for Licensee's internal business purposes in the Territory. Page 6

Licensee gets right to  Use  Use may be limited to a specific purpose e.g. Licensee's internal business only  Reproduce  Reproduction may be limited to archival purposes or a specified number of copies  Modify  Modification may be limited to specific purpose or a particular application so it is compatible with the system  Determine which party owns the modifications  Distribute  Right to distribute or redistribute may include rights to sublicense, promote or market  Licensor may want to limit to redistribution as a bundled product, stand alone, in a territory at a certain price limit  Which party is liable for claims in relation to end-users? Page 7

What words – not included  Exclusivity Rights  Means the ability of Licensee to exercise its rights to the exclusion of all others, including Licensor  Based on specified amount of royalties or  Scope: Territory, duration or particular fields of use  Perpetual  Unlimited duration or duration of the Licensor's underlying intellectual property rights  What effect does the termination of the Agreement have?  Irrevocable  Licensee may want to ensure that Licensor can't take back its rights after having paid for the Software  Licensor may "Subject to the terms of this Agreement" and will condition any permanency on Licensee's compliance Page 8

 Scope of License  Definition of Licensee – include affiliates  Adequate to cover business needs?  Object code only  Source code – right to modify  Hosted / ASP?  Can Affiliates use it?  Assignable – exclude affiliates so Licensee may grow by M&A (watch transfer clause in grant clause too)  Specified IP Rights  Is Grant under Licensor's patents and copyrights? Page 9

 Copy only for Archival Purposes  Licensee will not reverse engineer, decompile, disassemble or otherwise try to get the source code  Licensee wil not transfer, sublicense, distribute, sell or use for service bureau use  Transfer to unaffiliated third parties only? Means affiliated entities can use it – may expand scope of license or number of users  No Implied License Rights  May include language "Licensee may not use the Software except as expressly set forth in Section ___, License Grant."  Licensee generally obligated to reproduce all proprietary notices on copies of Software Page 10

 One-time license fees  Monthly or annual subscription fees  Each of these can be based on the number of computers, users, facilities, concurrent users, etc. Page 11

 Go hand in hand with payment structure  Considerations  Up front license fee  Installment payments on monthly or quarterly basis  Subscription style  Delivery  Determine when Licensor is to deliver the Software  Which version  Does install occur at one time or in multiple installations?  Acceptance Testing – Licensor wants to put a fence around this  What rights does Licensee have to test and for what period?  Software may be deemed accepted after certain number of days  Or upon use by Licensee in production  What notice of acceptance / non-acceptance is required?  Remedy  May limit to a refund of monies paid if Software fails acceptance test  Exclusive remedy may be Licensor's obligation to to repair, replace or somehow fix the Software without providing a refund Page 12

 Ownership  Works made for hire  License Back  Royalties  Licensor pays Licensee royalties on subsequent licenses on custom portion of the code Page 13

 Consider what is disclaimed  If third party or Open Source Software is embedded in the Software  Warranties should match the heightened risk  Determine responsibility for the security of data – particularly important if personally identifiable information is touched  Is licensor acting as insurance company for Licensee?  Licensor represents and warrants that:  Neither the Software, nor any component thereof, shall infringe any Intellectual Property, personal or other proprietary rights of any third party;  Licensor has the full authority to enter into this Agreement, it has the right to grant the rights set forth in this Agreement and that entering into this Agreement does not violate or conflict with any prior agreements with or other obligations owed by Licensor to any third parties;  Licensor is the owner of or otherwise has the right to use and distribute all materials and any third party products use by Licensor or provided to Customer in connection with this Agreement; and  Licensor will comply with all applicable federal, state and local laws as requried by Customer and communicated in writing by Customer to Licensor in the performance of this Agreement. Page 14

 Performance Warranty:  Licensor warrants that the software will function in a specified manner for some period of time  Substantially in compliance with docmentation provided to Licensee  Warranty period typically begins upon Acceptance  90 Days  Term of Agreement  Licensor should consider the warranty of performance when 3rd party software is included in the software (e.g., open source)  Warranty that software system will operate within service level parameters  Remedy: pre-agreed service level credits (liquidated damages)  Warranty that the Licensor is the owner of the software and has the right to grant the licenses granted (no infringement). What about Third Party code or Open Source embedded?  No viruses, time bombs, trap doors or other harmful or disabling code  Licensee might want to seek a warranty that Licensor has no plans to discontinue software  Licensors will want to disclaim implied warranties  Remedy: repair or replace the software, with a refund if replace/repair remedy fails  Licensors will want to limit the warranties to things within its control (e.g., not a failure of the computer system on which the software is running) Page 15

 Breach of Confidentiality  Licensor will want to limit its liability under the Agreement, including disclaiming consequential damages and capping overall liability  Licensee may also want to limit its liability  Pricing the risk  Increasing Licensor’s potential liability likely raises Licensor’s price  Cap on liability – key what is not covered  Exclusions - means unlimited liability  Indemnity  Breach of Confidentiality  Valid only if software approved or provided by Licensor or used in accordance with the terms of the Agreement (no unauthorized use)  Cover data loss? Page 16

 IP Infringement  Exclusions: Any Licensee modification to the software, Licensor modifies at the Licensee’s request, Licensee uses an old version, use of the software with third party software/hardware.  Licensor will want the right (even at its own cost) to make software noninfringing, obtain a license, provide functionally equivalent software or refund the license fees at its discretion  Control of defense  Licensee wants to pre-approve any settlement that obligates it  Privacy / PII data breach  Excluded from cap on liability?  May be limited to breach of third party IP rights within a defined Territory or for exmale to breach of a U.S. Patent  This excludes indemnity for any other type of IP right in other jurisdictions and for copyright violation Page 17

 How long will Licensor provide support and maintenance for the software?  While Licensee pays fees  Licensee: for so long as the Licensee is using the software  Licensor: a reasonable period of time  Licensees will also want to control support fee escalation over time. Limit the Licensor’s ability to increase support fees to some annual maximum  Support Fees (% of license fees) and Service Credits Page 18

 When Licensee has license for object code only that is critical to its business  Release Conditions are key. Depositor and Beneficiary agree that a Work Request for the release of the Deposit Material shall be based solely on one or more of the following conditions: (i) Depositor’s breach of the license agreement or other agreement between the Depositor and Beneficiary regulating the use of the Deposit Material covered under this Agreement; or (ii) Failure of the Depositor to function as a going concern or operate in the in the ordinary course; or (iii) Depositor is subject to voluntary or involuntary bankruptcy.  Does Licensor have an obligation to deposit updates, enhamcements and new releases into escrow? Page 19

 License Grant  License Restrictions  License Fees  Delivery & Acceptance  Ownership / Custom Code  Warranties  Limitation of Liability  Indeminty  Support & Maintenance  Escrow  Software License Checklist – Valuable Tool Page 20