Schedule 1: General Order Form



Yüklə 0,6 Mb.
səhifə5/6
tarix25.06.2018
ölçüsü0,6 Mb.
#51831
1   2   3   4   5   6
part of a Milestone,

  • part of a Stage,

  • an LD Obligation (i.e. may be subject to liquidated damages); and/or

  • a Payment Milestone.

    Both parties should be able to determine what elements comprise a Deliverable (including which parts of the Contract Specifications are met by the Deliverable, when the Deliverable should be provided, how the Deliverable will be Accepted, when will payment be made, when support or maintenance will commence, and whether liquidated damages will apply, and if so, when is the trigger date for payment and for how long will LDs continue to be payable.

    Other Services

    If the Contractor is supplying other services such as:

    Professional services on a time and materials basis

    Data Management services

    Telecommunications services

    GTA Broadband Local Services

    Web Services

    Managed Services

    GTA ISM Services

    Systems Integration Services

    Major Project Systems Integration Services

    Project Management Services

    Knowledge Transfer Services

    Reseller Value Add Services

    Then identify the scope of the services and the standards/permance requirements for those services.

    Contract Period

    Specify the project’s Commencement Date and when the Contract Period will end. (Clause 2.5 Customer Contract and Item 10 General Order Form)

    contract Specifications

    List and provide details of the Contract Specifications.

    The totality of any technical or descriptive specification of functional, operational, performance or other characteristics required of a Deliverable provided by the Contractor under the Customer Contract must be set out in detail here.

    This section must be completed in using specify details, and avoiding generalities. Each requirement should be capable to being independently tested via the Acceptance Test process.

    Where the Contract Specifications has evolved over time and are included in more than one document, it is best practise to reduce the Contract Specification to a single document.

    In particular it is poor practise to simply state that the Contract Specifications is included in the Tender, as updated by the Contactor’s Response to Tender. This approach is highly likely to lead to contract disputes.



    Exclusions

    Specify any exclusions to the Contract Specifications.

    Assumptions

    Specify any assumptions to the scope of work.

    Specify the consequences of any of the assumptions not being true.

    Implementation

    Methodology

    Specify any approach and/or project methodology/quality standard which will be applied to the Services.

    Roles and responsibilities

    Specify the key roles and responsibilities of the parties within the project.

    Delivery

    If the Products or Services are to be physically delivered:

    specify the place of delivery and the hours during which delivery can be made.

    specify any delivery instructions.

    specify any other requirements in relation to the Site access.

    Where work performed (Site)

    Specify the Site where the work is to be performed.

    If the work is to be provided at the Customer’s Site:

    specify the address.

    specify the hours of access.

    any special requirements and any security arrangements that must be followed.



    Site Specification

    Note: Where it is stated in Item 18 of the General Order Form that a Site Specification is required.

    If a Site Specification is required:

    the Site Specification must include at least the following information: environmental, operational, safety and management requirement in relation to the Site that are necessary for the provision of the Deliverables.

    specify any requirements for the preparation and maintenance of the Site.

    specify the name of the person who will approve the Site Specification on behalf of the Customer.

    Implementation planning study

    If the Contractor is to provide an implementation planning study:

    specify the implementation planning study objectives and time for provision of the study.

    specify a date for delivery of the implementation planning study to the Customer.

    specify if the implementation planning study needs to undergo Acceptance Tests in accordance with clause 10.1(b) of the Customer Contract.

    Business Contingency Plan

    Note: A Business Contingency Plan details the nature and scope of the business contingency services to be provided by the Contractor to overcome any interruption to the Customer’s business, including as applicable, information about time-frames, scheduling, service levels, methodologies, systems, processes or programs for the implementation of such services and any other requirements stated in Item 24 of the General Order Form. (Clause 1.13 Part 3 Dictionary)

    Specify if and when a Business Contingency Plan is required.

    Specify the periods that the Business Contingency Plan must be reviewed and updated by the Contractor.

    Specify the time periods that the Contractor is to test the operability of the Business Contingency Plan.

    Provide a copy of the Business Contingency Plan as an attachment [insert attachment number and name].

    Project Management

    Issues Log

    Specify who is responsible for creating and maintaining the issues log.

    Specify what the issues log must contain and how regularly it is updated.

    Risk management plan

    Specify if a risk management plan is to be used. If so, it should be prepared and maintained in accordance with AS/NZS ISO 31000 Risk Management Standard or equivalent, unless agreed in writing.

    Specify who is responsible for creating and maintaining the risk management plan, and how regularly it is to be updated.

    Change MANAGEMENT

    Any changes made should be reflected over time in a new version of the PIPP must be implemented as a Change Request in accordance with the variations procedures stated in Schedule 4 – Variation Procedures, subject to clause 26.1 to 26.2 of the Customer Contract. Each Change Request must be agreed in writing and signed by both the Customer and Contractor to be valid.

    Where the Customer contract is entered into under a Head Agreement, the Customer must obtain the consent of the Contract Authority prior to agreeing to a variation that includes a variation to any other Protected Clause.

    Customer Supplied Items (CSI)



    Note: Customer Supplied Items (CSI) are items set out in Item 22 of the General Order Form to be supplied by the Customer under a Customer Contract. A CSI may be: office access, desks etc (specify location, standards, times of access; Hardware or software (specify equipment, capacity, versions of software and dates of availability); VPN access or other remote access (specify capacity and hours available).

    List of CSI’s

    Specify each CSI to be provided by the Customer.



    CSI maintenance and support contracts

    Specify if any CSI must be covered by maintenance and support contracts including the period of cover, the Contractor’s rights of access to any third party support help desk, the hours and service levels to which support and maintenance must be available to the Contractor.



    CSI requirements

    Specify any requirements to attach to any CSI (e.g. any standards that the CSI must meet).



    CSI verification

    Specify if the Contractor must conduct any verification checks of CSI’s to ensure they are satisfactory.

    If so, specify the verification check process for each CSI. Include: a process to manage satisfactory and unsatisfactory verification checks; a process to manage ‘reissued’ CSIs; a process to manage repeat CSI verification checks; a process to manage ‘draft’ or ‘incomplete’ and ‘updated’ CSIs; a process to manage rejected CSIs; a process to manage previously satisfactory CSI which becomes defective; a list of required verification check forms and/or registers and a corresponding data entry process; and a list of Customer and Contractor nominee/s for responsibility to undertake verification checks.

    Specified Personnel



    Note: Specified Personnel are the key personnel of the Contractor who are required to undertake the provision of the Deliverables or part of the work constituting the Deliverables. The identity and roles of any Specified Personnel are stated in Item 27 of the General Order Form. (Clause 8.8 Customer Contract)

    Contractor’s Specified Personnel identity, roles and responsibilities

    If there are any Specified Personnel:

    specify the identity and roles and responsibilities of any of the Contractor’s Specified Personnel.

    specify if their role is full time or part time.

    Customer Personnel

    Customer’s Personnel roles and responsibilities

    Specify the Customer’s Personnel who will be available to work with the Contractor and their roles and responsibilities.

    This section should specifically include consideration of any of the Customer’s subcontractors and any other Agency’s personnel and contractors.

    Customer’s Personnel times, duration and authority levels

    Specify the times and duration of the involvement for the Customer Personnel as well as their authority levels.

    Where there is a multi Agency arrangement, specify who has authority to act and make decisions on behalf of Agencies other than the Customer.

    Customer Assistance

    Specify whether the Customer is to be provided any instructions, information, data, documents, specifications, plans, drawings or other materials.

    Specify if the Contractor must conduct any verification checks of each item to ensure it is satisfactory.

    If so, specify the verification check process for each item. Include: a process to manage satisfactory and unsatisfactory verification checks; a process to manage ‘reissued’ item’s; a process to manage repeat verification checks; a process to manage ‘draft’ or ‘incomplete’ and ‘updated’ items; a process to manage rejected items; a process to manage previously satisfactory item which becomes defective; a list of required verification check forms and/or registers and a corresponding data entry process; and a list of Customer and Contractor nominee/s for responsibility to undertake verification checks.

    Subcontractors



    Note: This section only needs to include information for entities that are “Subcontractors” within the definition (See definition of Subcontractor – clause 8.15 of the Customer Contract)

    Specify the full legal name of any Subcontractor that is to provide Services.

    Provide an overview of the roles and responsibilities that each Subcontractor will undertake in the provision of the Services under the Customer Contract.

    Acceptance Testing



    Note: If a Deliverable is not to undergo Acceptance Testing, (as specified in Item 32 of the General Order Form), then the Deliverable will be Accepted 2 Business Days (or such other period as stated in Item 32 of the General Order Form as the Actual Acceptance Date (AAD)), following the delivery of the Deliverable as required in the Order Documents. (Clause 10.1(a) and Item 32 General Order Form).

    There is a detailed Acceptance Test process set out in clause 10 which must be followed.

    Acceptance

    Complete a table like this for each Deliverable that is to undergo Acceptance Testing.



    Deliverable

    Date for Acceptance Test Criteria to be provided to Contractor

    (Default period is 60 Business Days prior to start of Acceptance Test Period)



    Date for Acceptance Test Data to be provided to Contractor

    (Default period is 14 Business days prior to start of Acceptance Test Period)



    Acceptance Test Period

    (Default period is 10 Business Days from delivery to Customer)



    Acceptance Test Notification Period

    (Default period is 3 Business Days from the end of the Acceptance Test Period)



    Expected AAD























































    Conducting Acceptance Tests

    For each Deliverable that is to undergo Acceptance Tests, specify details of the Acceptance Testing requirements.

    Specify the identification of the Deliverable or part of the Deliverables to be tested.

    Specify the allocation of each Party’s responsibilities in relation to testing, including the Party responsible for conducting Acceptance Tests and who will attend the Acceptance Tests.

    Specify which Party is to provide the test environment, including hardware, software, power, consumables and other resources and when the environment and resources must be ready for use.

    Specify the methodology and process for conducting Acceptance Tests.

    Specify the scheduling of Acceptance Tests including data the Acceptance Criteria must be agreed, the date that the Acceptance Test Data must be agreed, the Acceptance Test Period and the Acceptance Test Notification Period.

    Specify the Acceptance Criteria used to test whether the Deliverable meets the Contract Specification and other requirements of the Customer Contract (and must not include any other criteria).

    Specify the Acceptance Test Data, or the process and timing for agreeing the Acceptance Test Data.

    If an Acceptance Test document has been created that addresses the above points it can be attached to the General Order Form by identifying the document and providing it as an attachment [insert attachment number and name].

    Acceptance Test Results

    Provide a definition of the Defect severity classifications.

    Specifically identify which severity level of Defects will be considered “Minor”. Note: A Minor Defect is:


            1. in respect of a Deliverable that is not a Document, a Defect that would not prevent the Deliverable from being used in a production environment even though there may be some inconvenience to less than 5% of users of the Deliverable provided that the Defect does not compromise security;

            2. in respect of a Deliverable that is a Document, errors that are limited to errors in formatting, style, spelling or grammar,

    unless otherwise agreed in the Order Documents. (Clause 1.60 Part 3 Dictionary)

    For example: Specify the Defect severity classifications according to the criteria in the following table.



    Severity Level

    Definition

    Minor”

    [Severity 1]




    [No]

    [Severity 2]




    [No]

    [Severity 3]




    [Yes]

    [Severity 4]




    [Yes]

    Project Plan

    High level project plan

    Provide a high level project plan as an attachment [insert attachment name and number].

    Note: The descriptors in the project plan must be consistent with the descriptor for the same thing used in other sections. They must also be consistent with the Customer Contract Dictionary. It is essential to identify the key Milestones, all Milestones where a payment is to be made (including any retention sum), start of the Acceptance Test Period for each Deliverable to undergo Acceptance Tests, ADD for each Deliverable, the end of the Warranty Period and the start of the period of support or maintenance.

    If the project is being delivered in Stages:

    specify which Milestones or groups of Milestone are included in each Stage.

    specify the period (from the end of the Stage) that the Customer has to provide written notice to the Contractor to move to the next State (10 Business Days is the default period).

    Detailed project plan

    A detailed project plan may be provided below or as an attachment [insert attachment name and number].

    The detailed project plan must include the items listed in the High Level Project Plan (using the same description) as well as the sub-tasks/sub-events within each high level Milestone.

    LIQUIDATED DAMAGES



    Note: An LD Obligation is a Milestone for which late completion by the Contractor may require payment of Liquidated Damages.

    Specify if Liquidated Damages (LD’s) will apply, and if so to which Milestone (typically the final Milestone).

    Insert a table showing the LD Obligation (Milestone), the Due Date for completion (the date by which an LD Obligation must be met, the period of weeks for the LD Obligation to be paid and the amount of the LD Obligation per week.

    For example:



    Milestone that is an LD Obligation

    Due Date

    Period of weeks for LD Obligation to be paid

    Amount of LD per week

    [Final System Acceptance]

    [30 May 2011]

    [12]

    $[ ]

    Yüklə 0,6 Mb.

    Dostları ilə paylaş:
  • 1   2   3   4   5   6




    Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©genderi.org 2024
    rəhbərliyinə müraciət

        Ana səhifə