Information Technology Agreement Guidelines

Transcription

1 Information Technology Agreement Guidelines Box 1710, Wellington. Phone: , Fax: , info@itanz.org.nz

2 Table of Contents Guidelines 1. Introduction Objectives Setting the Scene The Agreement Managing the Agreement Ongoing Relationship Conclusion Other Guidelines in this series...8 Sample Agreement System Supply Agreement ii Information Technology Agreement Guidelines

3 Information Technology Agreement Guidelines 1. Introduction T his paper is one of a series prepared by the Information Technology Association of New Zealand (ITANZ) to assist organisations undertaking technology purchases. The first paper (Information Technology Procurement Guidelines) dealt with the procurement process and recommended actions which purchasers might adopt to identify the best solution for a specified business need. This paper follows on from the identification of a preferred supplier in the procurement process and addresses the contract negotiation stage that would normally follow. Due to the convergence and inter-linking of computing and telecommunications, this guideline series applies equally to both these technologies (collectively referred to as Information Technology or IT below). For example, PABXs are increasingly computer-like software-controlled devices integrating voice with data at a user s workstation. A user will take voice calls via a headset linked to the PC. The voice call may initiate the retrieval and display of data relating to the caller from a sales database. Voice and data are no longer separate parts of a system. The nature and scope of agreements used in the computing and telecommunications industries are very wide because the requirements of purchasers differ considerably. Agreements between purchaser and suppliers can range from simple transactions involving the delivery of standard hardware to large-scale multi-vendor projects involving the delivery, implementation and support of complex systems over an extended period of time. Although each agreement must be tailored to meet the requirements of a particular acquisition, this paper seeks to provide practical guidance and advice on the general principles of contract preparation. It is expected that organisations undertaking contract negotiation would also seek legal advice as required. There is a growing trend to lease IT equipment, especially in the telecommunications arena. In a leasing agreement, the purchaser will usually decide to use the supplier s own lease agreement, therefore the sample agreement attached to these guidelines is restricted to an agreement to purchase. Attached is a sample system supply agreement, which follows the approach outlined in these guidelines. This agreement could be adapted for the acquisition of a small to medium sized computer system, PABX or call centre system together with associated software and services. Other sample generic technology agreements in this series, are listed in section 8 Other Guidelines in this series. Information Technology Agreement Guidelines 1

4 2. Objectives T he ITANZ paper IT Procurement Guidelines identified the major objective of the purchaser in the procurement process as identifying the best solution to meet a stated business need. Similarly, the major objective of the purchaser at contract negotiation time should be to achieve agreement with the supplier on the best commercial terms and conditions for the supply of the preferred solution. A well drafted system supply agreement should achieve five goals to meet this objective: 1. Provide a clear statement on the rights and obligations of both parties, so that each party knows what it must do under the agreement and what benefits it will receive in return. 2. Set out the plan and timetable that will apply to the delivery and implementation of the products and services specified in the agreement. 3. Provide a clear procedure for the parties to control changes to the project, and agree on the impact that any changes will have on the timetable and the price. 4. Set out the basis by which the purchaser shall accept when the supplier has completed delivery and implementation as specified and the payment(s) that will then apply. 5. Define the procedures to resolve any disputes promptly and provide effective and commercially realistic remedies for both parties in the event of contractual default by the other. The major objective is the building of a business relationship between the parties, with each benefiting from the agreement on an I Win/You Win basis. It is essential to avoid a point scoring approach to contract negotiations that works on the You Lose /I Win basis. If the purchaser does not achieve value for money and/or the supplier does not profit from the sale of its products or services, what then happens to the mutually beneficial business relationship that parties set out to build? 3. Setting the Scene P rior to commencing negotiations, both parties should have spent time in preparation. The size and scope of the agreement will determine the extent of the preparation but the following checklist and key points should be considered: The Procurement Stage As outlined in the ITANZ paper IT Procurement Guidelines, contract negotiations should have been preceded by the preparation of the specification or statement of user requirements, an invitation for proposals, and the selection of the preferred supplier. These stages should have already established a clear understanding and agreement on the purchaser s requirements and of the supplier s technical and business proposal. The parties should therefore be entering into negotiations without any major unresolved or new issues. The purchaser s requirements as specified at the procurement stage and the supplier s proposal will normally be the basis of an agreement between the parties. Neither party 2 Information Technology Agreement Guidelines

5 can expect to gain the confidence of the other if they seek to change the rules on reaching the negotiating table. This includes changing or introducing new specifications or user requirements, announcing new conditions relating to the sale or purchase or looking to renege on any prior offer, statement or claim made to the other. Time invested by the parties during the procurement stage to properly specify requirements, prepare a proposal and evaluate solutions is likely to considerably reduce the time of the contract negotiation stage. The parties may both be disadvantaged if there are issues to be resolved during negotiations that should have been dealt with during the procurement stage. The Negotiating Team The parties should appoint members to their negotiating team with one representative nominated as the team leader. Ideally, the team leader should have authority to commit their team without the need to refer outside of the meetings. The team representation should include a balance of commercial and technical skills and be empowered to make decisions in respect to their areas of expertise. For continuity, the team should include representatives from the procurement stage and should remain consistent throughout the process. Unless the other party proposes to have legal advice at meetings, it is usually not necessary to include a lawyer on the negotiating team but legal advice and support to the team should be available throughout the process. Objectives and Plan The team must all be agreed on the objectives for contract negotiations and have a strategy and plan prepared. The team leader must ensure that all members of the team understand the objectives, the strategy and the plan and that the requirement for strict confidentiality is understood and agreed. One team member should have the responsibility for documentation and in particular recording agreements, action items and responsibilities resulting from meetings. This person should also ensure that each meeting has an agenda that is agreed in advance between the parties to avoid unstructured discussions and wasted time. Resources The venue for negotiation meetings should be agreed and the logistics and resources identified. For larger more complex negotiations, a neutral site away from interruption can help the parties to focus their attention. The venue should have white boards and access to breakaway rooms for separate team meetings as required. 4. The Agreement T he first tasks for the team leaders are to establish a starting point for the agreement, the responsibilities for initial drafting, managing revisions, final print and collation of schedules. In some instances a standard agreement held by either party may be a reasonable starting point. Alternatively, it may be necessary to seek legal assistance to draft an agreement customised to a particular acquisition. Information Technology Agreement Guidelines 3

6 ITANZ has developed a suite of generic IT agreements that could be used by the parties as a basis for negotiations. To minimise the costs and time associated with developing an agreement, the parties should endeavour to identify a starting point that is close to their respective positions. This will enable them to concentrate on the changes or additions that need to be made to an existing agreement for a similar acquisition. Any such agreement should include clauses covering the following provisions: Rights and Obligations The general terms and conditions of the agreement set out the majority of the rights and obligations of each party. In a purchase agreement the general terms and conditions should include: Preamble Definitions Interpretations Scope Charges and Payments Title Risk Confidentiality Publicity Documentation Services A full description of the parties, the processes leading up to the agreement stage and the essence of the agreement. A precise definition of the terms used within the agreement. Any clarifications relating to gender, references, schedules and appendices, other documents, conflicts between documents, etc. General description of what is to be supplied (the deliverables), any additional services to be provided and any options. A reference to the schedule to the agreement which should specify all deliverables, including hardware, software, delivery, services (e.g. installation, training ) and documentation, with the price for each. Specifies when title and ownership of any products passes to the purchaser and identifies terms that apply to licensed products. Specifies at what point during shipment, delivery or installation of the deliverables, the risk and responsibility for loss and/or damage passes to the purchaser. Requires the parties to keep confidential information they acquire with respect to each other. Sets out the rules with respect to either party wishing to make any use of the name of the other or to publicise that the parties have entered into a contract. A reference to the schedule to the agreement that should specify what documentation is to be supplied with the products and services. The services to be supplied e.g. training, configuring, installation, operational testing, maintenance. 4 Information Technology Agreement Guidelines

7 Warranties Intellectual Property Rights Indemnity Limitation of Liability Force Majeure Waiver Severability Notices Assignment Amendments Survival Entire Agreement Specifies what either party is required to warrant with respect to the agreement. This can include: quality of services; personnel; fitness for purpose; performance against specification; conformance to standards; warranty maintenance period and service levels. Intellectual property is intangible property involving some degree of creative effort e.g. software design. This clause will protect both parties rights to retain control over their intellectual property including the rights to their use, publication and copying. The agreement may also include a clause setting out an indemnity that the supplier will give to the purchaser to protect the purchaser against claims of infringement with respect to any products supplied. Sets out the extent to which the supplier s liability may be limited. Allows the agreement to be suspended or terminated without liability in the event of circumstances arising that are outside of the control of either party. Allows the parties to retain any rights under the agreement that they may not elect to enforce in the first instance. Allows for a particular term or condition that subsequently proves to be illegal or unenforceable, to be excluded without compromising the rest of the agreement. How and where any formal correspondence between the parties with respect to the agreement must be delivered. Requires the parties to have the consent of the other prior to transferring their rights and obligations under the agreement to any other party. Specifies how any subsequent changes to the deliverables as requested by either party will be handled. Any clauses that continue after the term of the agreement. Details the boundaries of the agreement; usually excluding any previous agreements written or oral. Plan and Timetable The clauses in a system contract that relate to the plan and timetable for delivery and installation will include: Information Technology Agreement Guidelines 5

8 Delivery Installation Specification of the dates, locations, responsibilities and any conditions relating to delivery of products and services to the sites. Sets out the responsibility for any site preparation work required prior to delivery. Specification of the responsibilities, milestones and dates for installation by the supplier. Acceptance and Payment Schedule A key requirement of any agreement is a definition of what will constitute acceptance by the purchaser that the supplier has completed all obligations under the agreement, and how payments will apply. The related clauses will be: Acceptance This clause will specify when acceptance testing will commence, what will trigger the testing and who will undertake the tests. The clause will also lay out the consequences and remedies in the event: acceptance testing isn t commenced within an agreed period; any tests should fail and require correction and re-testing; testing cannot be successfully completed within an agreed period. Acceptance Plan It is usual to include a schedule to the agreement that lays out in detail: the tests and the acceptance criteria; the time table; notification and re-testing procedures; repair, maintenance and support of products during acceptance testing. Payment Schedule The payments, as agreed between the parties, for the major agreement milestones including signature, installation and/or acceptance as set out in a Payment Schedule. Disputes and Remedies In the event the parties cannot reach agreement or a party is in default, the following clauses are required to lay out the options and remedies: Dispute Resolution The requirement for both parties to seek to constructively resolve any disputes themselves prior to agreed procedures to appoint, and be bound, by a specified dispute resolution procedure. 6 Information Technology Agreement Guidelines

9 Termination The parties must agree and set out the basis for any termination of the agreement. This will usually only be for situations where one or other is in breach or default of its obligations as specified in the agreement. This clause will set out what notice is required to be given to the other party and will generally allow a period for the default or breach to be remedied before the other party is entitled to exercise remedies under the agreement. 5. Managing the Agreement B y the time the agreement is signed the parties will have invested significant time and effort in completing negotiations and assembling all the required schedules into the final document. Both parties should now put this investment to work for them to ensure that all stages of the delivery, installation and acceptance are completed in accordance with their agreement and as contemplated by both parties. Each party should appoint their own project manager or other representative who will be responsible to manage the agreement and monitor progress through each stage. The project managers should each have a clear understanding of the contractual requirements and processes. This management time should result in the early identification of any problems or issues arising and enable the parties to take any co-operative action required. With this understanding, the agreement can facilitate a successful and mutually beneficial working relationship between the parties. 6. Ongoing Relationship A 7. Conclusion good IT supply agreement will establish the basis for an ongoing relationship between the purchaser and the supplier. The purchaser will typically wish to acquire post-implementation support and maintenance services for the system. The terms of supply for those services may be defined in a separate agreement attached as an appendix to the System Supply Agreement. This agreement will define the nature and description of the services that the supplier will perform and the charges payable by the purchaser for those services. W e have taken this initiative to provide some constructive guidance for participants in the procurement process in order to help reduce the costs of contract negotiations. We hope the use of these documents by suppliers, consultants and purchasers will help them reach agreement more quickly on the terms and conditions of the contract. This will then allow them to focus their combined energies on ensuring that the system is installed on time so that the purchaser can maximise the benefits of the investment. Information Technology Agreement Guidelines 7

10 8. Other Guidelines in this series Guideline Topic Information Technology Procurement Information Technology Agreement System Maintenance Software Agreement Software Licensing Facilities Management Outsourcing System Integration Professional Services Scope The formal process for technology procurement. Follows on from the identification of a preferred supplier in the procurement process. Addresses the subsequent supply contract negotiations stage. It includes an agreement template. An agreement for the maintenance and support of systems. This may be for a new system acquisition or for an existing system. It includes an agreement template. The development of software by a supplier. Also, the purchase and enhancement of off-the-shelf application packages. It does not include the supply of general-purpose shrink-wrapped PC tools but it is applicable to developments using these tools. It includes an agreement template. The licensing of unmodified package software with the associated maintenance. It includes an agreement template. The contracting out and management of an organisation s own systems at their own locations. Also covers the supply of associated services. It assumes that the decision to engage a facilities manager has been made and the supplier selection is complete. It includes an agreement template. The management and provision of systems and services where the provider supplies a total service including the provision of all defined facilities (hardware, software etc.) at the supplier s location. The implementation by a supplier of a set of distinct and complementary IT products or services to provide a defined and seamless service or system to a client. The products could be hardware, software, communications networks, services and perhaps operations services. It includes an agreement template The provision of special knowledge, skills and experience to a client for a fee. Typically by rendering advice, helping to successfully implement a solution, and/or providing technical or managerial assistance with and for the client. 8 Information Technology Agreement Guidelines

11 System Supply Agreement Purchaser and Supplier Dated This agreement could be adapted for the acquisition of a small to medium sized computer and /or telecommunications system and associated software and services for installation on the purchaser s premises. 11 Information Technology Agreement Guidelines

12 System Supply Agreement DATE AGREEMENT made this day of BETWEEN The Purchaser (called the Purchaser ) AND The Supplier (called the Supplier ). Preamble A. The Purchaser has called for proposals for computer and telecommunications Equipment, Software and Services in the RFP. B. The Supplier along with other suppliers has responded with an offer to supply certain Products and Services to the Purchaser. C. The Purchaser has evaluated all proposals received and selected the offer from the Supplier on the basis that it is represented to satisfy the Purchaser s requirements as set out in the RFP and the Purchaser has satisfied itself that the proposal meets these requirements. D. The parties agree to the supply of the Products and Services on the following terms and conditions: 1. Definitions and Interpretations 1.1 In this Agreement, unless the context otherwise requires: Acceptance means the date on which the Purchaser certifies satisfactory completion of Acceptance Testing as provided in clause 5.3. Accepted has a corresponding meaning; Acceptance Testing means the tests, including the performance standards, procedures, time periods and test specifications, specified in Schedule D; Agreement means this Agreement and includes all Schedules and Appendices attached to it or incorporated in it by reference; Contractual Correspondence means any correspondence between the parties relating to this agreement as is included in Schedule H; Documentation means user manuals (including those in electronic form on any media), handbooks, maintenance libraries, education materials and other publications containing Product Descriptions or specifications to be supplied with the Products and Services; Effective Date means the date this Agreement comes into force being the date on which it is signed by both parties; Equipment means computer hardware, telecommunications hardware, accessories, attachments and alterations of and spare parts for that Equipment; 12 Information Technology Agreement Guidelines

13 Installation Date(s) means the date(s) by which installation of the Products must be completed, as specified in Schedule B; Installation Site(s) means the location(s) described in Schedule B at which the Products will be installed; Payment Schedule means Schedule E containing the period, percentage and conditions of payment for Equipment, Software and Services; Products means any of the Equipment, Software and Documentation supplied pursuant to this Agreement; Proposal means the Supplier s response to the RFP a copy of which is annexed in Schedule H; RFP means the Purchaser s Request for Proposal document inviting the Supplier to submit a proposal for the supply of Products and Services, and includes the Supplier s responses to the RFP, all of which are annexed as Schedule H; Services means all forms of installation, configuration, testing, maintenance and support for the Products, and advice, education and training to be supplied under this Agreement; Software means the object code version of computer programs or any necessary programming component which in combination with the Equipment is necessary to deliver the function of the System or Products and any related documentation to be licensed to the Purchaser pursuant to this Agreement; System means the Equipment and Software operating together; System Specification means the specification in Schedule F that specifies the operation of the Equipment and Software in combination to meet the requirements of the RFP. 1.2 For the purposes of interpretation and construction of this Agreement: Words importing one gender include the others; Words importing the singular or plural number include the plural and singular number respectively; References to Sections, Clauses, and Schedules are references to sections, clauses and schedules in this Agreement; Any Schedules, and the provisions and conditions contained in such Schedules, will have the same effect as if set out in the body of the Agreement. In the event of any conflict between the Schedules and the body of this Agreement, the provisions and conditions of the body of this Agreement will prevail; Headings and marginal notes are inserted for the sake of convenience of reference only and do not affect the interpretation of this Agreement; If there is any conflict of meaning between information contained in the documents referred to in this Agreement, the order of precedence will be as follows: (a) (b) (c) (d) (e) the body of this Agreement; the Schedules to this Agreement (other than the Contractual Correspondence, the Proposal and the RFP): the Contractual Correspondence; the Proposal; the RFP. 2. Scope 2.1 The Supplier agrees to supply, sell and licence Products and Services and the Purchaser agrees to acquire, purchase and licence these on the terms and conditions of this Agreement. Where Information Technology Agreement Guidelines 13

14 software is licensed, the license terms shall be set out in the agreements referred to in the Products Schedule (Schedule A). 2.2 The Products and Services which are the subject of this Agreement are as specified in the following Schedules: Schedule A Products Schedule Schedule B Implementation Plan Schedule C Services Schedule Schedule D Acceptance Testing and Plan Schedule E Payment Schedule Schedule F System Specification Schedule G Documentation Schedule H RFP, Proposal and Contractual Correspondence. 2.3 Change Order Procedure The Purchaser may change, alter or amend its order for Products and Services by written amending order at any time prior to Installation Dates. All such changed orders are subject to acceptance by the Supplier, such acceptance not to be unreasonably withheld. 3. Charges and Payments 3.1 Price The amount payable for the supply of the Products and Services will be as detailed in the Schedules to this Agreement. Unless specified, GST will be payable by the Purchaser, where applicable. 3.2 Payment The Supplier shall invoice the Purchaser for the Products and Services supplied in accordance with the Payment Schedule (Schedule E) to this Agreement and payment will become due [number of days] days following receipt of the invoice. 3.3 Total Charges Subject to any express term to the contrary in this Agreement, the Price specified in this Agreement is the total charge to the Purchaser. 4. Delivery and Installation 4.1 The Supplier will deliver the Products to the installation site(s) and in accordance with the implementation plan specified in Schedule B. 4.2 The Supplier will provide such instructions and environmental specifications as requested by the Purchaser to enable the Purchaser to prepare the Installation Site(s) for installation. 4.3 The Supplier will install all Products by the Installation Date(s). 4.4 Installation of the Products will be completed to the manufacturer s and the Supplier s specifications such that the Products are ready for use. 4.5 The installation will be deemed completed when the Supplier gives written notice to the Purchaser certifying the completion of installation as provided in clause 4.3 (called Installation Completion ). 14 Information Technology Agreement Guidelines

15 4.6 Failure to Install In addition to any other remedy available to the Purchaser, if the Supplier fails to complete the installation of any Product by its Installation Date, the Purchaser may at its absolute discretion elect to: set a later Installation Date; or terminate this Agreement in accordance with Clause Acceptance 5.1 Acceptance Testing Upon Installation Completion, the Purchaser and the Supplier together will perform Acceptance Testing on the installed Products. 5.2 Constructive Acceptance The Products will be deemed Accepted in the event that the Purchaser: unreasonably delays commencing Acceptance Testing. A delay of seven (7) days or greater from Installation Completion will be considered unreasonable provided such delay is not caused by the Supplier; uses the Product which is subject to Acceptance Testing for productive purposes prior to Acceptance, provided such use is not part of the Acceptance Testing; or unreasonably fails to provide any materials or resources reasonably required for testing. 5.3 Actual Acceptance If the Products satisfy the Acceptance tests the Purchaser will promptly confirm such satisfaction of the Acceptance tests to the Supplier in writing provided that if such notice is not given within three (3) days of completion of the Acceptance tests the tests will be deemed passed and the Products accepted. 5.4 Acceptance Testing Failure If the Products fails to satisfy the Acceptance Testing within the period specified in Schedule D, then in addition to any other remedy, the Purchaser may elect to: agree to an extension of time for the completion of the Acceptance Testing; terminate this Agreement in accordance with Clause Title Title to those Products that are intended to become the property of the Purchaser will pass to the Purchaser upon receipt of final payment of the Price. 7. Risk of Loss Risk of loss or damage will pass to the Purchaser upon delivery by the Supplier to the designated Installation Site. Information Technology Agreement Guidelines 15

16 8. Confidentiality Both parties agree that, unless they have the prior written consent of the other, they will not use or disclose to any third party (other than for the purpose of performing this Agreement) the terms and conditions of this Agreement or any information confidential to the other party. The obligations of this clause 8 shall survive termination or cancellation of this Agreement. 9. Publicity Neither party will advertise or publicly announce any matter relating to the existence of this Agreement, without the other s prior written consent, which will not be unreasonably withheld. 10. Documentation The Supplier will provide the Purchaser with Documentation as specified in Schedule G to this Agreement. 11. Access Security If requested by the Purchaser, the Supplier will comply with the Purchaser s security procedures for access to the Installation Site(s) and the Equipment but shall not be responsible for any delays resulting from delays in obtaining access. 12. Services The Supplier will provide the Purchaser with the Services in accordance with the plan as set out in Schedule C. Any further Services required by the Purchaser will be an additional charge to be agreed with the Supplier. 13. Warranties The Supplier warrants that: 13.1 upon payment of the full amount of the purchase price for the Equipment the Purchaser will obtain unencumbered title to the Equipment; 13.2 the Equipment and Software will be supplied with the manufacturer s warranty and at the warranty service response levels as specified in Schedule A; 13.3 all Services will be provided in a competent manner and in accordance with this Agreement; 13.4 the personnel supplied to undertake the Services will have all the requisite skills and expertise for the purpose and will carry out their duties with due care and skill. 14. Intellectual Property Rights Indemnity 14.1 The Supplier will indemnify the Purchaser against and will at its cost defend or settle any claim, suit, action or proceeding (collectively called Action ) brought against the Purchaser to the extent that the Action is based on a claim that the Purchaser s use of deliverables 16 Information Technology Agreement Guidelines

17 supplied by the Supplier constitutes a breach of any patent, copyright, trade secret or other proprietary right provided that: the Purchaser fully co-operates with the Supplier in defending or settling the Action and makes its employees available to give statements, advice and evidence as the Supplier may reasonably request; the Supplier is notified promptly in writing of any Action and is given complete authority and information required for the conduct of the defence or settlement of the Action; the Supplier shall have the sole control of the conduct of any Action and all negotiations for its settlement or compromise In order to fulfil its obligations under clause 14.1 the Supplier shall forthwith at its own expense either: obtain for the Purchaser the legal right to continue using the System or part of the System which is the subject of the claim; or modify the System to render it non-infringing; or replace the System (or the infringing parts of the System) with a reasonably equivalent System or part thereof. 15. Limitation of Liability 15.1 The warranties in clause 13 replace all other representations or warranties (statutory, express or implied) and all such representations and warranties (save any which may not lawfully be excluded) are expressly excluded, including, without limitation, the implied warranties of merchantability and fitness for any particular purpose. The foregoing exclusions do not apply to rights granted to the Purchaser under the Consumer Guarantees Act 1993 unless the Purchaser is acquiring the System for the purposes of a business in which case the provisions of the Consumer Guarantees Act 1993 shall not apply The Supplier will under no circumstances be liable under the law of tort, contract or otherwise for any loss of profits or savings or for any indirect or consequential loss or damage, however caused, arising out of or in connection with the performance or non-performance of this Agreement The Supplier s liability to the Purchaser arising out of any claim for damages for any cause whatsoever will under no circumstances exceed in aggregate the total amount of the sums actually paid by the Purchaser to the Supplier for the goods or services which gave rise to the claim No action arising out of this Agreement, regardless of form, may be brought by either party more than two years after the cause of action arose. 16. Termination 16.1 Immediate Termination Either party may terminate this Agreement forthwith if the other party: assigns its rights or obligations under the Agreement otherwise than in accordance with Clause 21; enters into a composition with its creditors, is declared bankrupt, goes into liquidation, or a receiver, or a receiver and manager, or statutory receiver is appointed in respect of it Termination by Either Party on Notice If one party defaults in the performance of any of its obligations under this Agreement and: Information Technology Agreement Guidelines 17

18 the default is capable of being remedied, and, within thirty (30) days of notice by the nondefaulting party specifying the default, is not remedied; or the default is not capable of being remedied, and, within thirty (30) days of notice by the nondefaulting party specifying the default, the defaulting party has not used its best endeavours to reinstate the positions of the parties as far as is possible and given an undertaking to use its best endeavours to prevent a recurrence of the default, the non-defaulting party may immediately terminate, or temporarily suspend the operation of, this Agreement, at its sole discretion Termination by Purchaser In addition to any other remedy, the Purchaser may terminate this Agreement immediately on giving notice: pursuant to Clause 4.6 (Failure to Install); pursuant to Clause 5.4 (Acceptance Testing Failure) If the Purchaser gives notice to the Supplier to terminate this Agreement, the Purchaser may, in addition to terminating this Agreement and any other specific rights: recover any sums paid to the Supplier on any account or for Services that have not been performed; request the Supplier, at its own expense, to remove all or any of the Products that have not been accepted from the Purchaser s premises; pursue any additional or alternative remedies provided by law Partial Termination Where the Purchaser has a right to terminate this Agreement under Clause 16.3, the Purchaser may at its discretion either terminate this Agreement, or terminate this Agreement in respect of those parts of the Agreement which can be severed from the remainder and which provide for the performance of those obligations which the Supplier has not performed. 17. Force Majeure 17.1 Neither party will be liable for any act, omission, or failure to fulfil its obligations under this Agreement if such act, omission or failure arises from any cause reasonably beyond its control including acts of God, strikes, lockouts, riots, acts of war, epidemics, governmental action after the date of this Agreement, fire, communication line failures, power failures, earthquakes or other disasters (called Force Majeure ) The party unable to fulfil its obligations due to Force Majeure will immediately: notify the other in writing of the reasons for its failure to fulfil its obligations and the effect of such failure; use all responsible endeavours to avoid or remove the cause and perform its obligations. 18. Waiver No delay, neglect or forbearance by either party in enforcing against the other any provision of this Agreement will be a waiver, or in any way prejudice any right, of that party. 18 Information Technology Agreement Guidelines

19 19. Severability If any provision of this Agreement is held to be invalid, illegal or unenforceable, such provision will be severed and the remainder of the Agreement will remain in full force and effect. 20. Notices Any notice given pursuant to this Agreement will be sufficiently given if it is in writing and delivered, or sent by prepaid post or facsimile to the other party at the address as shown below: the Purchaser s address... the Supplier s address Assignment Neither party may assign or transfer its rights or obligations under this Agreement without the prior written consent of the other party, which may not be unreasonably withheld. 22. Amendments Any modification to or variation of this Agreement must be in writing and signed by authorised representatives of the Supplier and the Purchaser. 23. Entire Agreement The parties acknowledge that this Agreement contains the whole of the contract and understanding between them. There are no conditions, warranties or other understandings affecting the arrangements between the parties other than those set out herein and this Agreement replaces all prior Agreements and understandings (if any) with respect to the subject matter of this Agreement. 24. Disputes and Remedies The parties agree to use their best efforts to resolve any dispute that may arise under the Agreement through good faith negotiations. Except as provided in subclause 24.5, no party shall commence any arbitration or litigation in relation to this Agreement unless it has first invited the chief executive of the other party to meet with its own chief executive for the purpose of endeavouring to resolve the dispute on mutually acceptable terms Any dispute arising under this Agreement which cannot be settled by negotiation between the parties or their respective representatives shall be submitted to arbitration in accordance with the Arbitration Act The decision of the arbitrator shall be final In the absence of agreement concerning the appointment of an arbitrator, either party may request the President of the New Zealand Law Society to appoint a suitably qualified independent arbitrator to hear and determine the dispute The parties shall continue to perform their obligations under the Agreement as far as possible as if no dispute had arisen pending the final settlement of any matter referred to arbitration. Information Technology Agreement Guidelines 19

20 24.5 Nothing in this clause shall preclude either party from taking immediate steps to seek urgent equitable relief before a New Zealand Court. EXECUTED as an Agreement on the date first above written. SIGNED on behalf of the Supplier } by a duly authorised officer in the presence of: } } SIGNED on behalf of the Purchaser } by a duly authorised officer in the presence of: } } 20 Information Technology Agreement Guidelines

21 Schedule A Products Schedule A list of all of the deliverables and the associated cost for each. To include:! the warranty period for each;! the service levels applying during warranty;! a technical specification of each deliverable may be appropriate. Schedule B Implementation Plan The implementation plan consisting of the key dates including:! Start Date;! Installation Date(s);! Installation Site(s);! Testing Date(s);! Conversion Date(s);! Completion Date. Schedule C Services Schedule The list of all of the Services to be performed together with a specification of the scope of the Service, typically including: For each of the Installation and Conversion Services (if required) provide the following information:! Scope;! Responsibilities;! Assumptions;! Completion Criteria. Installation Services may typically include (but without limitation):! delivery;! unpacking;! configuring;! connection;! powering up;! removal of packing material;! labelling;! Software loading;! bringing to the most recent software maintenance level;! connected and powered up;! other. For Support and Maintenance provide:! what support is to be supplied;! how it will be given;! the scope of any maintenance;! how the maintenance will be performed. For Training Services provide: Information Technology Agreement Guidelines 21

22 ! details of all training courses;! numbers attending;! timetable if known. For Site Preparation provide:! what is to be done at each site and when. Service Level definition Any other Services to be performed. Schedule D Acceptance Testing and Plan The acceptance testing plan including:! test procedures;! responsibilities;! timetable. Schedule E Payment Schedule The payment milestones including:! at agreement signature;! on installation;! on acceptance;! on completion. Schedule F System Specification The specification for the System to meet the requirements of the RFP. Schedule G Documentation Documentation to be supplied. Schedule H RFP, Proposal and Contractual Correspondence Copies of, or references to the Purchaser s RFP, the Supplier s proposal and any relevant Contractual Correspondence that the parties agree to include. 22 Information Technology Agreement Guidelines

23

24 Copyright is reserved to ITANZ but copying for non commercial purposes in limited quantities is acceptable. This and the other guidelines in the series are available for downloading at no charge from the ITANZ homepage at: Printed copies and a diskette version are also available from: Box 1710, Wellington. Phone: , Fax: , info@itanz.org.nz