Evaluating And Negotiating An IT Contract — The Buyer’s View Allan P. Weeks Attorney-At-Law Law Office of Allan Page Weeks Insert your logo in this area.

Slides:



Advertisements
Similar presentations
Basic Negotiating Skills
Advertisements

EuropeAid PARTICIPATORY SESSION 2: Managing contract/Managing project… Question 1 : What do you think are the expectations and concerns of the EC task.
Project Procurement Management
1. Among the most important advisors to a construction firm are: –Professional surety bond producer –Knowledgeable construction/surety attorney –Construction-oriented.
4/28/20151 PRESENTED BY NAKABAGO JOHN CONTRACT MANAGEMENT AND ADMINISTRATION IPPU PRESENTATION JOHN NAKABAGO.
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
Chapter 3 Project Initiation
Copyright Course Technology Chapter 11: Project Procurement Management.
1 INTERNAL CONTROLS A PRACTICAL GUIDE TO HELP ENSURE FINANCIAL INTEGRITY.
The Outsourcing Process
Out of school hours care Contract management plan information session.
Date: 03/05/2007 Vendor Management and Metrics. 2 A.T. Kearney X/mm.yyyy/00000 AT Kearney’s IT/Telecom Vendor Facts IT/Telecom service, software and equipment.
OGC LEGAL AFFAIRS EDUCATION PROGRAM CONTRACTING AND PURCHASING AT DEPAUL, FROM START TO FINISH A JOINT PRESENTATION BY ANASTASIA KATINAS, OFFICE OF THE.
TUTORIAL Grant Preparation & Project Management. Grant preparation What are the procedures during the grant preparations?  The coordinator - on behalf.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
INTRODUCTION TO PUBLIC PROCUREMENT
The Contract Review & Approval Form FINANCE & OPERATIONS BUSINESS CONTRACTS JANUARY 15, 2015.
5-1 McGraw-Hill/Irwin Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.
Licensing: A strategy for technology transfer. A contractual arrangement whereby the licensor (selling firm) allows the licensee (the buying firm) to use.
A SOUND INVESTMENT IN SUCCESSFUL VR OUTCOMES FINANCIAL MANAGEMENT FINANCIAL MANAGEMENT.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Chapter 07 Internal Control McGraw-Hill/IrwinCopyright © 2014 by The McGraw-Hill Companies, Inc. All rights reserved.
James Aiello PricewaterhouseCoopers Africa Utility Week 06 International Good Practice in Procurement.
Aspera License Management –
Contract Models for Virtual Teaching Helsinki University Porthania III 24 October 2001 Kristiina Harenko Attorneys at Law Borenius & Kemppinen Oy.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
Best Practices: Financial Resource Management February 2011.
ISO17799 Maturity. Confidentiality Confidentiality relates to the protection of sensitive data from unauthorized use and distribution. Examples include:
Information Technology Project Management Buying Packaged Software: RFPs and Vendor Selection.
Enterprise Solutions Knowledge Community Contract Development and Negotiation 14 February 2003 Tom McCullion.
Dino Tsibouris (614) Vendor Contracts: What You Need and What You May Be Missing.
Advanced Project Management Project Procurement/Contract Management Ghazala Amin.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Personal Budgets. Introduction Name Andrea Woodier Organisation Leicestershire County Council Telephone number address
Practice Management Quality Control
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 7 Business Aspects of Software Engineering.
Copyright 2009  Understand the importance of project procurement management and the increasing use of outsourcing for information technology projects.
What is conflict negotiation Communication designed to anticipate, contain, and resolve disputes so that the parties reach mutually acceptable solutions.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
CONCEPT OF MIS. Management “Management can be defined as a science of using resources rationally (utilization of resources in judicious manner using appropriate.
How To: A Process for Successful Partnerships. Partnership Definition A partnership IS: A written agreement between the parties. Mutual interest in, mutual.
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
Chapter 11: Project Procurement Management
Paul Goodman Introducing Software Metrics via Benchmarking.
Chapter 11: Alternative Approach - Purchasing Systems.
Project Management Birutė Markevičiūtė Joint Technical Secretariat Lead Partner Seminar 13 October 2008, Riga.
1 Business Aspects of Software Engineering SWE 513.
LAW for Business and Personal Use © 2012 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible.
INTRODUCTION Claims management is one of the most challenging business process in the insurance industry. A very important aspect of Insurance. Driving.
Copyright © 2012, Big I Advantage®, Inc., and Swiss Re Corporate Solutions. All rights reserved. (Ed. 08/12 -1) E&O RISK MANAGEMENT: MEETING THE CHALLENGE.
Improving Purchasing of Clinical Services* 21 st October 2005 *connectedthinking 
MGT 461 Lecture #27 Project Execution and Control Ghazala Amin.
1 A Seminar On Pharmaceutical Outsourcing A Seminar On Pharmaceutical Outsourcing.
UNIVERSITY OF DAR ES SALAAM t Selection and Employment of Consultants Negotiations with Consultants; Monitoring Performance of Consultants; Resolving Disputes.
3/9/20161 Select the Appropriate Strategic Approaches for Managing Conflict (LO 3) the role of communication in resolving conflict. the role of communication.
Chapter 3: Purchasing Research and Planning Strategic Planning for Purchasing Strategic planning for purchasing involves the identification of critical.
The Contract Management Process Post Award Activities.
HOW TO PROTECT YOUR INTEREST IN A SALE CONTRACT Focus on what you “get” when you sign!
COBIT. The Control Objectives for Information and related Technology (COBIT) A set of best practices (framework) for information technology (IT) management.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
© 2010 Pearson Education, Inc., publishing as Prentice-Hall 1 AGREEMENT © 2010 Pearson Education, Inc., publishing as Prentice-Hall CHAPTER 10.
1 Chapter 5 Consumer and Business Buyer Behavior.
EECS David C. Chan1 Computer Security Management Session 1 How IT Affects Risks and Assurance.
Session Overview Contract Basics & Best Practices
Model Contract for Health
A JOINT PRESENTATION BY
Presentation transcript:

Evaluating And Negotiating An IT Contract — The Buyer’s View Allan P. Weeks Attorney-At-Law Law Office of Allan Page Weeks Insert your logo in this area then delete this text box.

2 Introduction Presentation Objectives APW’s Core IT Contract Negotiation Concepts Shared IT Transaction Objectives Customer “Attitudes” That Cause Delay Vendor Caused Delays Customer Caused Delays Customer’s Need To Tailor Standard Vendor’s Contract (“War Stories”) The Lawyers Caused The Delays

3 Presentation Objectives The program description highlights the tension between: –Desire of both parties to quickly conclude an IT transaction, which seldom happens; –Customer’s perceived need to adapt the Vendor’s standard form contract’s terms to a particular transaction; and, –Vendor’s intention to use a standard form of IT agreement that should only be minimally altered. Presentation focuses on the Life Science Customer’s perceptions, biases, experiences and procedures about IT contract negotiations that are too long.

4 APW’s Core IT Contract Negotiation Concepts Operating Agreements Construction Contracts Competing Business Models Outsourcing Contracts Lawyer’s Proper Role

5 Operating Agreements IT product and services contracts are operating agreements. Requires careful attention to: –who will use the IT products; –where will they be used; –the functions performed by those products and services; –what is the output from their application; and, –especially for database licenses, who owns what part of the output.

6 Construction Contracts IT contracts, particularly those with a significant services component, such as software development, software customization and systems integration contracts, are similar to construction projects/contracts, with a major distinction—there may not be an alternative Vendor or IT product for the project. Primary Customer leverage is achieved by building in milestone testing and payment events.

7 Competing Business Models Vendor’s software license and other IT contracts reflect the Vendor’s business model for the license/sale of its product and any associated services. Customer needs an IT contract that matches the end- user’s business model for the IT products and services that are being acquired. Protracted negotiations about the legal or business terms of a software license often arise because the Vendor’s license bears little resemblance to the Customer’s business model for its use of the software.

8 Outsourcing Contracts Web-enabled access to various IT applications, as well as software hosting, means that many IT contracts are actually outsourcing agreements. The use of third party services leads to additional and complex negotiations about the third party’s control of the Customer’s operational responsibilities.

9 Lawyer’s Proper Role Customer’s lawyer should assure that: –the final IT contract is both legally sufficient and appropriately protective of the Customer’s interests; and, –the end-user(s) will be able to utilize the IT products (e.g., software or a database) in the manner expected when the IT project was authorized.

10 Shared IT Transaction Objectives Customers and Vendors usually want: –the IT contract signed as soon as possible; –the amount of money to be paid and received by each party to be within their reasonable expectations; and, –at contract signing, a sense of mutual satisfaction on each side of the table.

11 Customer Attitudes That Cause Delays Life Sciences personnel may not understand the important differences between an IT transaction and the more collegial collaboration agreements utilized for drug discovery and development. Too much or too little trust in IT Vendors. Lack of familiarity with the computer industry and the manner in which it sells IT products/services and negotiates its contracts. Risk allocation between a Customer and Vendor may seem unfair and/or over-reaching. Computer industry’s well-deserved reputation for over- promising product performance and project completion dates.

12 Vendor Caused Delays Submission of a contract that is too Vendor-biased. Negotiations handled by personnel not appropriately knowledgeable about IT transactions. The failure to be forthcoming in response to Customer’s questions, due to a desire to protect the sale. Desire to avoid or postpone detailed contract discussions, to keep the sale on track. If a database license is involved, a failure to understand the differences between a software license and a database license, particularly with respect to output ownership and post-contract retention matters.

13 Customer Caused Delays Failure to clearly communicate or define project requirements. Complicated and slow internal decision hierarchy. Lack of experience with IT contracts and their negotiation. Changes in operational needs or corporate policies that affect the process of negotiating the contract. Failure to involve knowledgeable persons early enough in the procurement process, e.g., IT and legal. If a database license is involved, a failure to understand the differences between a software license and a database license, particularly with respect to output ownership and post-contract retention matters.

14 Customer’s Need to Tailor Vendor’s Standard Contract – “War Stories” License grant would not permit the software to be utilized as expected. The output from processing a database could not be retained by the Customer if the database/software license was terminated. The centralized management of the software “keys” needed by the Customer was not permitted by the Vendor’s business model. The Vendor would not support software updates or new releases beyond the most recent release. The contract submitted by the Vendor’s sales person was not applicable to the transaction. The contract between the Vendor of outsourced software hosting and the vendor to which that Vendor had outsourced those services did not match the performance terms (i.e., SLA’s) in the proposed agreement between the Vendor and the Customer. Neither party understood the Customer’s corporate structure, resulting in an inaccurate identification of end-users and an incomplete license grant.

15 The Lawyers Caused The Delays The Vendor’s contract was not submitted by the Vendor until relatively late in the procurement process. The responsible Customer personnel did not send the contract for legal review until the last minute. The contract was sent to the lawyer(s) on a timely basis, but the IT transaction was not considered to be a priority.

16 For more information, contact: Allan P. Weeks Law Office of Allan Page Weeks 183 State Street, Suite 4B Boston, Massachusetts Tel: 617/ Cell: 617/