IT Field Services & Staff Augmentation

Summary

Field Services and Staff Augmentation provides flexible access to experienced technical resources — on-site field work, project delivery, and additional capability when internal teams need extra hands.

blueAPACHE's Global Capabilities material describes on-the-ground support delivered through a field services network across Australia, the United States and the United Kingdom. Work of this kind is typically contracted as Professional Services under Schedule 1, which is excluded from the default 36-month Minimum Service Period.

Key facts

When organisations use it

• Site work that cannot be done remotely — hardware installation, decommissioning, cabling, physical device refresh
• Project surge — a migration or rollout that needs more hands than the internal team has, for a defined period
• Specialist capability gaps — a skill needed occasionally but not enough to justify hiring
• Geographic reach — sites in locations where the customer has no local presence
• Cover — leave, vacancy or parental leave in a small team where one absence removes a capability entirely

The common thread is that all five are temporary or intermittent. That is what makes them awkward to solve by hiring, and what makes the Schedule 1 exclusion from the 36-month term commercially relevant — you are not committing to three years of a resource you need for six weeks.

How it complements the managed services

Field Services is the physical counterpart to remote management. Managed Services covers monitoring, patching and the help desk; someone still has to attend the site when hardware fails, a new office opens, or a device refresh lands.

In practice the combination is what enables:

• Device rollouts — Procurement sources the hardware, Intune zero-touch provisioning configures it, field services deploys it. The Archers engagement describes exactly this pattern.
• Site openings and closures — network install, firewall deployment and cutover coordinated with Connectivity
• Migrations — additional capacity during a cloud or WAN transition without permanent headcount

Where it sits alongside Consulting and Advisory

Both are contracted as Professional Services, but they answer different needs:

If you know what to do and lack capacity, this is the service. If you are deciding what to do, that is advisory.

Commercial points

No 36-month default. Professional Services are excluded from the Minimum Service Period that applies to managed services, so engagements are scoped on their own terms.

Deliverables are licensed, not owned. Anything produced as Professional Services — including documentation, scripts and configurations — is licensed for internal use during the Service Period once paid for, and that licence ends at termination. If a field engagement produces build documentation you need to keep, negotiate a surviving licence on the Service Order.

Customer obligations still apply. The customer must provide access, keep software properly licensed, and give blueAPACHE direct telephone access to its own support providers during Business Hours.

Charging. Per the Service Order, with Time and Materials Rates applying to some work. No rates are published.

What is not published

• Rates — hourly, daily or call-out
• Geographic coverage detail — which specific regions or cities are serviced within Australia, the US and the UK, and where subcontractors are used
• Response times for on-site attendance — no call-out SLA is published
• Minimum engagement duration for augmented resources
• Screening and vetting standards for personnel attending customer sites
• Whether resources are employees or contractors

The last two matter more than they appear. For regulated environments, or sites with security clearance requirements, who physically attends and how they were vetted is a question worth answering before the first visit rather than after.

Integration with other emPOWER services

Because this is Professional Services rather than a standing operational service, it typically appears as a supporting element of other engagements rather than as a standalone purchase:

• Managed Service Bundles and Advanced Infrastructure Managed Services — remote management still needs a physical response for hardware failure, refresh or site work; field services is the on-site counterpart to both
• Procurement — hardware sourced through procurement is deployed by field services, the pattern described in the Archers engagement
• Connectivity — site openings, closures and network cutovers combine connectivity design with field services labour
• Consulting and Advisory — both are Professional Services excluded from the 36-month default, and a consulting engagement's recommendations are frequently delivered on the ground by field services

Typical engagement

Scoping. Because this is Professional Services under Schedule 1, engagements are scoped individually on a Service Order rather than provisioned through the standard Transition In Services process used for ongoing managed services. The scope, duration and Time and Materials or fixed-fee basis are agreed upfront.

Delivery. Work runs to the agreed scope — a rollout, a migration, an augmentation period, or ongoing site coverage. Customer obligations still apply during delivery: providing site access, keeping software properly licensed, and giving blueAPACHE direct telephone access to its own support providers during Business Hours where relevant.

Close-out. Because Professional Services sit outside the 36-month Minimum Service Period, there is no automatic holdover to plan around — the engagement ends on the agreed date or deliverable. Documentation and other deliverables produced are licensed for internal use during the Service Period; that licence ends at termination, so agree in the Service Order if you need it to survive.

Defining the resource assignment

Specify the role, skills, location, deliverables and person authorised to direct the resource. The published service does not establish universal dispatch times, geographic coverage or engagement minimums. Record travel, access, safety and approval requirements. Clause 3.2 addresses personnel suitability and escalation, while customer access and decision-making obligations still matter. Distinguish completing the assignment from providing general ongoing support.

Which document defines the commitment

The published General Terms v3.6 give the Service Order precedence over the General Terms, followed by the Schedules and then the Acceptable Use Policy (clause 2.3). Record the agreed scope, exclusions and negotiated departures in that document set. A brochure or a procurement discussion does not, by itself, define the customer-specific commitment. Keep the versions supplied at signing with the executed order and signed variations. Two offers with the same service name can cover different systems, operating hours or responsibilities.

Personnel continuity and a later move in-house

Clause 22 contains a mutual non-solicitation restraint covering specified employees and contractors, including indirect engagement arrangements. It runs for 12 months after the last day of service performance and includes a look-back over the personnel involved. Prior written consent can permit an otherwise restricted arrangement. If a future operating model includes hiring a delivery specialist or moving managed work in-house, address that possibility before relying on it in an exit plan. Access to an engineer during an engagement does not establish a right to recruit that person afterwards.

Confidential information and access

Clause 16 provides mutual confidentiality protection. It covers information marked confidential, information identified orally and confirmed in writing within 30 days, and information that should reasonably be understood to be confidential. Customer Data, Customer Records and Customer Software are included; blueAPACHE’s agreement and fees are also confidential. Permitted disclosures include appropriately bound personnel on a need-to-know basis and specified professional advisers, with other exceptions in the clause. Identify who may receive operational reports, configuration details and commercial information. Access to information to deliver the service is not a general permission to circulate it.

Escalating a contractual dispute

A support escalation and a formal contractual dispute are different processes. Clause 26 begins with a Dispute Notice giving adequate particulars. Representatives meet within three Business Days; unresolved matters then move through the clause’s senior-representative referral and meeting stages before court proceedings. Urgent equitable relief and disputes over whether the agreement was validly terminated are exceptions. Keep incident records, service measurements, approvals and correspondence together so the disputed obligation and requested outcome can be identified. Raising a ticket does not necessarily satisfy a formal notice requirement; use the agreement’s notice process for contractual disputes.

How liability differs from service performance

Clause 19 separates performance obligations from financial liability. The general cap per claim is the greater of the fees paid in the preceding three months or $25,000, with exclusions and specific categories governed separately. Confidentiality, information security, privacy and the IP indemnity have a $1 million per-event and $2 million aggregate cap. Data-loss liability depends on whether blueAPACHE had, and breached, a contracted backup or disaster recovery obligation; the relevant measure is restoration cost to the applicable recovery point, not the value of every business consequence. Read these provisions alongside the negotiated Service Order and Schedule; an availability statement does not describe the liability regime.

Sources and scope

The contractual detail above summarises the published General Terms and Conditions v3.6, using the KB documents on service agreement formation and document precedence; non solicitation restraint; confidentiality; dispute resolution; liability and indemnity. The customer’s Service Order, Schedules and agreed variations determine the specific engagement. See the terms and conditions guide and Service Agreement.

Frequently asked questions

Where does blueAPACHE provide field services?

Through a field services network across Australia, the United States and the United Kingdom. Specific regional coverage is not published — confirm for your sites.

Is there a minimum term?

Not the 36-month default. Professional Services are excluded from it, so engagements are scoped individually.

What does it cost?

Not published. Charging is per the Service Order, with Time and Materials Rates for some work. Request the rate card, including any call-out or travel components.

How quickly can someone attend a site?

No on-site response time is published. If site attendance timing matters to your operations, get it written into the Service Description under the Service Level heading — only commitments under that heading are contractual.

Are the people employees or contractors?

Not stated in blueAPACHE's published material. Worth asking, along with vetting standards, if your sites have access or clearance requirements.

Do we keep documentation produced during a field engagement?

During the Service Period, yes, licensed for internal use. That licence ends at termination unless you negotiate otherwise on the Service Order.

Can we use this to cover a vacancy?

That is one of the stated uses — flexible access to experienced technical resources when internal capacity is constrained.

Does it include the hardware being installed?

No. Hardware is sourced through Procurement under Schedule 11; field services covers the labour to deploy it.

Is there a standard contract term?

No. As Professional Services under Schedule 1, engagements are excluded from the 36-month Minimum Service Period default and are scoped individually on the Service Order.

What happens if a field engagement runs past its agreed end date?

Because it is scoped as Professional Services rather than a standing Service, the holdover regime that applies to managed services does not automatically apply here — extension is agreed on its own terms, typically a revised Service Order.

Can we terminate a field services engagement early?

Terms depend on what is agreed on the Service Order for that engagement. General termination rights and consequences in the master terms still apply, including that termination does not excuse fees already due.

What happens to site access details and documentation afterwards?

Deliverables such as build documentation are licensed for internal use during the Service Period only; that licence ends at termination. Negotiate a surviving licence on the Service Order if ongoing access is needed.

Do field personnel handle our data?

They may, where work involves customer systems. The same Privacy Act obligations, 24-hour eligible data breach notification duty, and Australian data handling position that apply across blueAPACHE's services apply to Professional Services engagements.

What support window applies to field attendance?

None is published. No on-site response time or call-out SLA is stated in blueAPACHE's published material; if attendance timing matters operationally, get it written into the Service Description under the Service Level heading.

Related

Managed Services · Managed Service Bundles · Advanced Infrastructure Managed Services · Consulting and Advisory · Procurement · Connectivity · Glossary · Contact

Source

Drawn from blueAPACHE's Managed Services pages, the Global Capabilities brochure, the emPOWER Managed Services brochure, the ISO/IEC 27001:2022 certificate 202507-118, the General Terms and Conditions v3.6 (service term and minimum service period, intellectual property rights, consequences of termination, and customer obligations), and the Archers case study. Rates, coverage detail, on-site response times and personnel vetting standards are not in blueAPACHE's published material and are not inferred here. Also drawn from the General Terms and Conditions v3.6 (service term, renewal and minimum service period; transition in and disengagement services; consequences of termination; data protection and privacy) and blueAPACHE's data sovereignty and residency statement.

Knowledge Base