Virtus Group Statement of Work — Time & Materials (MASTER)

Document Metadata

Compliance Note

NZISM/PSR mapping is maintained centrally: see Security Overview. This document inherits the organisation’s Baselines document.

1. Introduction

1.1 Document Purpose

This document serves to outline the project requirements for the {Project Name}.

This document is intended for the following audience:

• {Client Full Name} Project Team
• VGL Project Team

1.2 Document Scope

This document contains the project requirements and costs for the {Project Name}.

This document will include exclusions to the deliverables and any assumptions made during the definition phase. Any requirement that is NOT clearly captured directly in this document will not be implemented without an accompanying project variation.

1.3 Requirements Definition Process

This document serves to outline the project requirements for the {Project Name}.

Use the block that applies.

Block 1:

• {Insert text}
• {Insert text}

Block 2:

• The requirements were not derived from other documents or contents.
• {Insert text as needed for context and to complement the statement above.}

2. Solution Overview

• Current State:
• Future State:
• Proposed Implementation Approach:
• Architecture/Diagram: {{ARCH_URL}}

3. Project Delivery

3.1 In Scope

The following is in scope for this project:

• <insert text>

3.2 Out of Scope

• <insert text>

3.3 Assumptions & Dependencies

The following assumptions have been made regarding this project:

• The project will be delivered without interruption or suspension
• VGL will not be delayed due to the procurement and installation of any required infrastructure (hardware and/or software)
• Change controls will be submitted and managed by {Client} with VGL providing technical input only
• Any representatives of {Client} that are involved at the various steps in the project are available as planned, adequately skilled and competent to execute the tasks required of them
• Any decision making representative nominated by {Client} is duly empowered to do so
• Any request from VGL to {Client} for functional or technical clarification will be responded to within a timely manner
• There are no other projects in progress that will hinder the implementation of this project
• Leave only the one that applies, remove everything else
• The work will be performed remotely through offsite activities
• The work will be performed onsite at {Client} premises.
• The majority of work will be performed during normal business hours
• {Client} will provide remote access to enable after-hours support (if required)
• {Client} will provide a suitable working environment (desktop, desk, chair, etc) to complete any onsite tasks or activities
• {Client} will document and perform all User Acceptance Testing (UAT)

3.4 Deliverables & Acceptance

3.5 Receivables

The receivables required from {Client Full Name} for this project are as follows: A Purchase Order for the full value of the project, as described in this Statement of Work

3.6 Project prerequisites

The pre-requisites for this project are listed below:

• <insert text>

3.7 Dependencies

This project has the following dependencies:

• <insert text>

3.8 Constraints

The constraints to this project are listed below:

• <insert text>

3.9 Risks

3.10 Roles & RACI Matrix

3.11 Deliverables and Acceptance Criteria

The following table shows the project deliverables, acceptance criteria and completion dates for the project:

Deliverable	Acceptance Criteria	Completion Date
		dd/mm/yy
		dd/mm/yy
		dd/mm/yy

3.12 Project Schedule

The following schedule represents the timing of key milestones, as well as the principal party responsible for delivery.

3.13 VGL Project Manager

VGL may appoint a Project Manager to:

• Co-ordinate the VGL resources
• Manage VGL tasks and deliverables
• Act as a point of contact for the {Client} Project Manager
• Provide status reporting at an agreed frequency

3.14 Project Status Reporting

If appointed, the VGL Project Manager will provide a status report to the {Client} Project Manager. This report will cover:

• Progress against milestones
• Activity planned for next period
• Risks/Issues
• Blockers/Escalations
• Variations
• Payment schedule

3.15 Completion Criteria

This Statement of Work will be deemed complete when either:

{Only for T&M – delete section if not relevant}

• The deliverables specified are complete, or
• {Client} provides VGL with 10 business days’ notice, in writing, that the engagement is no longer required.

4. Roles and Responsibilities

4.1 Project Teeam

The following table details the roles and responsibilities of the project team.

5. Project Financials

5.1 Time and Materials Estimates

The estimated time and materials investment for this engagement is shown in the table below.

Invoicing monthly based on actuals. Travel/expenses as per T&Cs.

The following overtime rates will be used for this engagement

• Outside standard business hours - 1.5x the specified hourly rate
• Public Holidays - 2x the specified hourly rate

This Statement of Work will be invoiced on a Time and Materials basis. An estimate for the hours and disbursements has been provided for budget purposes. VGL will charge {Client} for the actual time and expenses (plus 5% margin for administration) incurred each month.

VGL will advise {Client} when this engagement reaches 75% of the value of the PO. If VGL is required to continue work over the value of the PO provided an approved variation will be required.

For quotes in USD delete this sentence and update the rate below. Delete if price in NZD:

Pricing is based on an exchange rate of US/NZ dollar 0.6200 (the "Base Rate"). Should the rate at the end of each billing period vary from the Base Rate by more than 2.0%, then VGL reserves the right to review pricing accordingly

5.2 Hardware Costs

Insert text/images or remove

5.3 Software License Costs

Insert text/images or remove

5.4 Financial Assumptions

The following financial assumptions have been made:

• <insert text>

5.5 Charge for Out of Scope Activities

{delete section if disbursements have been included in pricing}

No travel, disbursements or accommodation have been allowed for in this document. VGL will obtain {Client Short Name} prior consent before incurring any travel, disbursement or accommodation expenses.

5.6 Delays

In the event of any unscheduled delays due to {Client} failing to fulfil any of their obligations or suspending the project, VGL may invoice {Client} at VGL’s current hourly rate and associated costs, for any resources which are consequently made idle and, after reasonable efforts at reallocation, cannot be redeployed. VGL must be allowed additional time to re-allocate resources to the project after a period of delay if those resources have been assigned to alternative work

Financial Notes

Invoicing

Invoices will be sent to:

Name: <input text>

Title: <input text>

Client: {Client Full Name}

Postal Address: <input text>

VGL’s billing cycle runs from the 26th to the 25th of the month. Invoices will be presented during the first 5 business days following the end of the billing cycle. Invoices will be payable on the 15th of the month following the date of invoice.

5. Change Control

Changes controlled via CVO. Template: here.

6. Legal

Confidentiality

This document contains confidential and proprietary information of Virtus Group Ltd (“VGL”). {Client Full Name} (“{Client Short Name}”) may not disclose the confidential information contained herein to any third party without the written consent of VGL, save that {Client Short Name} may disclose the contents of this document to those of its agents, principals, representatives, consultants or employees who need to know its contents for the purpose of {Client Short Name}’s evaluation of the document. {Client Short Name} agrees to inform such persons of the confidential nature of this document and to obtain their agreement to preserve its confidentiality to the same extent as {Client Short Name}. As a condition of receiving this document, {Client Short Name} agrees to treat the confidential information contained herein with at least the same level of care as it takes with respect to its own confidential information, but in no event with less than reasonable care. This confidentiality statement shall be binding on the parties for a period of five (5) years from the issue date stated on the front cover unless superseded by confidentiality provisions detailed in a subsequent agreement.

Non‑solicitation

1.1 No solicitation of employees

Neither party may actively solicit for employment or contracting any employees or other personnel of the other party or placed by the other party during the life of this Agreement.

If one party (the “engaging party”) engages (employs or contracts) an individual who is either:

(a) currently engaged with the other party; or

(b) was engaged during the three (3) month period prior to the date of engagement with the other party, where such new engagement results from a direct approach to that individual by the engaging party (whether in conjunction with an advertisement or not),

then the engaging party will pay a finder's fee of 25% of the individual’s new annualised remuneration plus GST to the other party.

Within 30 days, of the Effective Date of this Agreement, and any subsequent change in personnel described in this item, {Client Full Name} will ensure that each of its IT managers are notified of {Client Full Name} obligations in this clause.

1.2 Genuine advertisement not solicitation

Clause 1.1 above does not prevent either party from employing any person who responds to a genuine advertisement placed by the other party as long as there is no concurrent approach in person by that party’s staff.

Terms & Conditions: See https://virtusgroup.co.nz/tacos/.

7. Acceptance

On-going Support (Please tick)

I require a separate agreement for On-going Support

I require a separate agreement for On-going Support

Please sign, scan, and email document to admin@virtusgroup.biz

8. SLAs & Baselines

• Tier: {{TIER}} • RTO/RPO: {{RTO}}/{{RPO}}
• Vulnerability SLAs: Critical ≤7d (≤72h internet-facing), High ≤14d, Medium ≤30d, Low ≤90d
• Restore testing: ≥1 verified restore/month/client; quarterly workload; annual full DR + semiannual tabletop
• Backups: 3‑2‑1‑1‑0; retention 30d/12m/7y
• Identity/Device: MFA for all, PAM JIT, FDE, EDR 100%, OS ≤14d, critical apps ≤7d

9. Evidence Links

• BCDR Summary
• Incident Response Plan
• Breach Response Procedure
• MDM Baseline
• Cloud Governance Baseline
• Vulnerability Management
• Runbooks (Ops)