By Vyom Bhuta
Negotiating vendor contracts is arguably the most challenging task in the packaged application selection process. Often, vendor contracts can be so awash with legalese that they can seem to protect the vendor more than you, the customer.
So what should you include in the contract that would ensure some level of security in your software purchase? The three critical areas you should make sure your contract covers are acceptance criteria, vendor support, and the problem escalation process. If these elements are not already included in the contract, don't sign it until those terms are added.
In this article, we'll discuss these areas and how you can include the appropriate language and terms in your contract to ensure you're fully protected.
Acceptance criteria usually focus on the usability, performance, compatibility, and security of the software. The objective of defining these terms is to make sure that the software, after implementation, satisfies the needs and wants that you have established.
Below is some potential language that can help you outline acceptance criteria in a vendor contract.
Delivery and Acceptance
[VENDOR] shall deliver the Licensed Software via FTP download and provide Documentation to [CLIENT] upon execution of this Agreement. Each Product shall be deemed accepted as defined in Product Acceptance upon the successful completion of Acceptance Testing conducted in accordance with [CLIENT]'s Acceptance Criteria. (Product Acceptance and Warranty are not the same thing. Warranty follows successful Acceptance Testing.)
- During the 120 calendar days following [CLIENT]'s installation of the Software, [CLIENT] will be subject to Acceptance Testing as defined in the Acceptance Criteria attachments (Attachment x-x) to determine that the Software is in substantial conformance with [CLIENT]'s requirements as evidenced by these Acceptance Criteria.
If, during the 120-day test period, [CLIENT] discovers an error in the Software or a substantial nonconformance to [CLIENT]'s requirements, [CLIENT] will notify [VENDOR] in writing, accompanied by documentation ("Error Reports") evidencing such error or nonconformance.
- [VENDOR] shall provide [CLIENT], or designee, a written remediation plan within three business days of [CLIENT]'s submission of the respective Error Report.
- [VENDOR] shall provide [CLIENT] remedial Software within 10 business days of the Error Report submission, whereupon [CLIENT] will initiate resumption of Acceptance Testing.
- If, within 30 calendar days following receipt of [CLIENT]'s written Error Report, [VENDOR] fails to remedy the reported error or nonconformance, [CLIENT] shall be entitled to terminate this Agreement by written notice to [VENDOR] and subsequently return to [VENDOR] all copies and materials relating to the Software delivered to [CLIENT] under this Agreement.
If [CLIENT], in accordance with Section 1.3 Product Acceptance, terminates this Agreement, [VENDOR] shall refund all license fee amounts paid by [CLIENT].
(Please make sure that you consult a lawyer before using the language suggested above.)
More on gantthead
"Software Development Vendor Contract Considerations"
"Package Evaluation Method Plan"
"Package Vendor Questionnaire and Checklist"
"Quality Review Checklist for Software Package Procurement" Related content:
Package Selection Department
"It's Okay To Be Subjective During Vendor Selection" by Vyom Bhuta
"Disappearing Software Vendors: What's Your Plan of Action?" by Vyom Bhuta NOTE: Items in bold are available only to gantthead premium members.
Vendor support and problem escalation process
Vendor support and the problem escalation process are usually defined by the vendor and should already be outlined in the contract the vendor has presented to you. However, you will need to closely evaluate the vendor's terms to make sure that they meet your expectations. Figure A below outlines the escalation procedures and the response time you should expect from a vendor.
Vyom Bhuta is the Pittsburgh Branch Partner for Titan Technology Partners and is a contributor to gantthead.
This article was originally published on gantthead on Sept. 26, 2001.