13.07.2015 Views

Hardware Acquisition and Maintenance Contract - Australian ...

Hardware Acquisition and Maintenance Contract - Australian ...

Hardware Acquisition and Maintenance Contract - Australian ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Hints for useThis Schedule is divided into sections for ease of use <strong>and</strong> general guidance.However, the format of this Schedule is provided as an example only <strong>and</strong> may bevaried to suit the requirements of each project. Customers may need to attachadditional pages to the Schedule, which can be done by way of an Annexure. It isnot recommended that documents are incorporated into a <strong>Contract</strong> by reference.The parties should have particular regard to the following items:(a)(b)<strong>Hardware</strong>Details of all <strong>Hardware</strong> to be provided should be inserted in section 2. Ifthe <strong>Contract</strong>or is to deliver <strong>and</strong> install the <strong>Hardware</strong>, the relevantcolumns should be completed.SpecificationsThe technical, functional <strong>and</strong> performance specifications for eachDeliverable (including the <strong>Hardware</strong>) should be set out at section 3 orattached as an Annexure to this Schedule, along with any particularsystem requirements.In many instances, the parties will negotiate the Specifications to beincluded in the <strong>Contract</strong>, based on a combination of:(i)(ii)the statement of functional <strong>and</strong> technical requirements (or similar)that was released by the Customer in its approach to market; <strong>and</strong>the response received from the <strong>Contract</strong>or to that statement ofrequirements.It is important that both parties work together to clearly define thefunctional <strong>and</strong> technical requirements of each Deliverable to help avoidfuture disputes.If the Specifications are likely to vary over the <strong>Contract</strong> Period (forexample, additional functionality is added), this should be clearly stated.Any variation to the Specification should be agreed via the changecontrol process set out in clause 21 of the model <strong>Contract</strong>.(c)ServicesA description of each Service to be provided should be included insection 4. Details of the <strong>Maintenance</strong> Services should be included in thetables in section 5, with additional pages added as an Annexure, ifrequired.Service Levels apply in respect of Preventative <strong>and</strong> Remedial<strong>Maintenance</strong>. As the definition of Service Levels refers specifically tothose set out in the Statement of Work, sections 5.2 <strong>and</strong> 5.3 must becompleted for the Service Level clauses to be effective.If payments are to be linked to the achievement of Milestones, theMilestone dates specified for Services or Deliverables in this Scheduleshould be the same as those specified in Schedule 3 – Payment.© Commonwealth of Australia 2012 page 6SourceIT | User Notes | <strong>Hardware</strong> <strong>Acquisition</strong> & <strong>Maintenance</strong> <strong>Contract</strong> - Schedules | Release version 2.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!