Managed IT Services

Summary

emPOWER Managed Services is blueAPACHE's IT operations pillar and its lead offer: outsourced or co-managed management of an organisation's technology environment, delivered from Australia with 24/7 help desk coverage and backed by blueAPACHE's own cloud and network platforms. The service dates from 1998, was renamed emPOWER Managed Services in 2003, and today bundles service desk, monitoring, automated patching and remediation, security operations, device lifecycle management and formal account governance under one accountable operating model. This hub explains what the pillar covers, the three service lines beneath it, how it is delivered and contracted, what support and service levels are and are not published, and how it connects to the Cloud, Connectivity, Collaboration and Security pillars. It is written for IT leaders and procurement teams evaluating a managed services provider for a mid-market or enterprise organisation.

Key facts

What the pillar covers

The emPOWER Managed Services brochure describes an integrated, enterprise-grade IT support ecosystem made up of an on-shore support team, a local account management team, regular strategic and technology reviews, application management, monitoring and reporting, proactive security management, backup and disaster recovery solutions, end-user device provisioning, and unlimited 24/7 support. The four service areas it names are:

The 2026 origin page reframes the same capability set around six themes: automation-led operations (proactive remediation, self-healing, automated patching), security-first delivery, experience-led support (real-time digital experience visibility across applications, devices and endpoints), AI-ready foundations, operational visibility, and governance and accountability. The consistent thread between the 2023 brochure and the 2026 page is that blueAPACHE sells the operating model, not a ticket queue: monitoring, patching, remediation, reporting and escalation are designed as one system with named owners.

Monitoring, reporting and environment reviews

Tooling is shared with the customer. blueAPACHE's managed services portal and toolset handle monitoring, alerting and capacity baselining, and customers are given access to the same toolset so they can see their whole production environment, managed and unmanaged. The published functions are:

• Management and reporting — system monitoring reviews, resource usage and reporting across servers, desktops and networks, co-authored by blueAPACHE specialists rather than generated unattended
• Lifecycle management — network, server and desktop management across the full lifecycle of infrastructure and devices, from provisioning through patching to maintenance
• Environment reviews — regular reviews of the customer environment that highlight key issues for closer examination, with predictive capacity monitoring used to manage growth before it becomes a constraint
• Remote monitoring and management — tooling across servers and endpoints driving automated patching and compliance

The environment review is the mechanism that distinguishes a managed service from a monitored one: monitoring tells you a threshold was crossed, a review tells you which thresholds are going to be crossed next and what to do about it. It feeds the monthly operational reviews and quarterly business reviews described in the Archers engagement.

Services in this pillar

Managed Service Bundles

Integrated bundles that combine the core operational capabilities (service desk, monitoring, patching, security operations, reporting) into a simpler service model with clearer ownership and predictable delivery. The origin page positions bundles as the standard entry point for organisations that want whole-of-environment ownership rather than a menu of individual services. Bundle contents and tiers are defined in the customer's Service Description and the Schedule 2 service catalogue, which is not published.

Advanced Infrastructure Managed Services

Specialist management of critical infrastructure across servers, storage, virtualisation and data centre environments, backed by blueAPACHE's operational engineers. This is the service line for organisations that keep application ownership in-house but want the platform layer run by a provider that also operates its own HPE-based private cloud and MPLS network. Under the General Terms and Conditions, Scheduled Maintenance for managed services means manufacturer-recommended routine maintenance of Customer Managed Equipment, carried out within the windows in the Schedule or on at least 3 Business Days' notice.

Field Services and Staff Augmentation

Flexible access to experienced technical resources for on-site field work, project delivery and additional capability when internal teams need extra hands. blueAPACHE's Global Capabilities brochure 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 and billed per that Schedule.

How it is delivered

Transition in. Immediately after the Service Commencement Date, blueAPACHE must confirm the start date, run a due diligence process to collect the information it needs on the systems and services to be supported, configure its monitoring platforms to report on availability and performance, provide documentation on how to use its support services, and agree a regular meeting and reporting schedule. The customer must promptly supply firewall, network, password and procedure details and approve documentation in a timely manner.

Operating rhythm. Each customer has an assigned account team. Account Executives own the strategic relationship and the commercial model; Service Delivery Managers own the operational relationship and are accountable for delivery; Technical Account Managers are accountable for technical service delivery; engineers do the work. The Archers case study describes this in practice as monthly operational reviews and quarterly business reviews focused on continual service improvement, run by an Account Executive, Service Delivery Manager and Portfolio Engineer.

Reporting and governance. Within 5 Business Days of the end of each month blueAPACHE provides its standard reports on performance against key delivery metrics, including Service Levels; additional reports can be agreed at additional fees. Each party appoints an Account Representative with authority to make binding day-to-day decisions, and the parties meet every 6 months to review the services. blueAPACHE retains records for the term plus 7 years and must allow customer audits on 5 Business Days' notice (1 Business Day for regulatory audits).

Automation and security. The origin page describes automation delivered through governed workflows with experienced specialists and clear escalation, so that manual effort is reduced without losing control. Security is embedded in the same model: integrated monitoring, automated patching, operational controls and defined governance. Where a customer wants dedicated detection and response, that is provided through the Security pillar's MDR service rather than assumed within a managed services bundle.

Customer Zero. The origin page states that blueAPACHE applies the same service architecture, automation workflows and reporting inside its own environment before scaling them to customers, so that what is delivered has been validated in real operations. The same position is described on the Managed Detection and Response page for the security stack.

Support and service levels

What is published. Unlimited 24/7 help desk access, with Australian-based staff during business hours and blueAPACHE's global team after hours. The first point of contact is always a blueAPACHE team member and no part of the help desk is outsourced. The General Terms and Conditions define Business Hours as 0700 to 1900 AEST/AEDT on Business Days, and Customer Operating Hours default to the same window unless the Service Order says otherwise.

What is not published. blueAPACHE develops a bespoke priority and escalation matrix with each customer, so that, for example, a business-critical system receives tighter alert thresholds and higher prioritisation. It publishes no default response or resolution time. The General Terms and Conditions define a "Compliance Target" as the target time to resolve each call to the Support Centre by priority, but state that obligations not written under the heading "Service Level" in the Service Description are not Service Levels. There is no service credit regime in the General Terms and Conditions; any credits are in Schedule 2. Response, resolution and credit figures for a given customer therefore come from that customer's Service Order and Schedule, and are not stated on this site.

How Service Levels operate. blueAPACHE must meet or exceed any applicable Service Level except to the extent a failure arises from, or is contributed to by, a Reasonable Excuse: a long defined list that includes customer-supplied scripts and equipment, customer-directed outages, third-party software used by blueAPACHE, Emergencies, and acts of third parties. Service Levels are measured with blueAPACHE's tools and the results are final and binding. During a three-month holdover after an unrenewed term, Service Levels do not apply.

Related obligations worth knowing. Anti-virus on customer equipment is the customer's responsibility unless the Service Description says otherwise. Backups are only an obligation where the Schedule expressly includes them, and even then the obligation is to run the software at agreed intervals and re-run reported failures. A customer wanting blueAPACHE to participate in its business continuity plan requests an Action Plan, which is chargeable as a Professional Service.

How it integrates with the other pillars

• Cloud. Managed services customers commonly run workloads on emPOWER Cloud IaaS, which brings the platform, backup and DRaaS obligations under the same provider. Honan Insurance and Archers both combined emPOWER Managed Services with emPOWER Cloud. See the Cloud hub.
• Connectivity. blueAPACHE monitors and manages customer networks as part of the pillar, and where the WAN is emPOWER Connectivity the carriage, firewalls and monitoring sit under one accountable party. Archers' private MPLS WAN and FortiGate security uplift were delivered inside its managed services engagement. See the Connectivity hub.
• Collaboration. Telephony is inside help desk scope, and Microsoft Teams calling migrations were part of both the Archers and Berry Street engagements. See the Collaboration hub.
• Security. Proactive security management and Security Gap Analysis audits are part of the managed services scope; 24/7 managed detection and response is the Security pillar's MDR service. See the Security hub.
• Procurement and Microsoft Practice. End-user device provisioning, Intune zero-touch deployment and licensing optimisation appear in managed services engagements and draw on the Procurement and Microsoft Practice hubs.

Evidence

The origin page also lists Sealy of Australia as a related case study; that engagement was an international network deployment and is covered on the Connectivity hub.

Making operational ownership explicit

Translate the proposal into a responsibility list for each system: monitoring, incident handling, patch approval, lifecycle decisions and communications. Include the interfaces to retained internal IT and directly contracted suppliers. Reduced fragmentation depends on these boundaries being clear. During transition, check that access, escalation contacts, support instructions and reporting arrangements are in place before assuming a system has entered normal service. A bundle name is not a substitute for that handover.

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.

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.

Responsibility across the delivery chain

The published terms allow blueAPACHE to subcontract all or part of the Service Agreement without customer consent or a notification requirement. Clause 27.5 nevertheless makes blueAPACHE liable for its subcontractors’ acts and omissions to the same extent as for its employees. This differs from a third-party supplier contracted directly by the customer. Identify which arrangement applies to each dependency in the design. Where supplier identity, delivery location or change notification matters, request a documented supplier list and put any agreed notification or approval requirement in the Service Order; the general clause does not supply that visibility automatically.

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.

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; confidentiality; subcontracting and assignment; non solicitation restraint; 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.

Related

• Managed Service Bundles
• Advanced Infrastructure Managed Services
• Field Services and Staff Augmentation
• Cloud hub
• Connectivity hub
• Collaboration hub
• Security hub
• Managed Detection and Response
• Archers case study
• Honan Insurance case study
• Brotherhood of St. Laurence case study
• Not for Profit industry page
• Financial Services industry page
• Service agreement
• Support
• Home

Frequently asked questions

Can emPOWER Managed Services work alongside our internal IT team?

Yes. blueAPACHE offers the service either as a fully outsourced IT function or as an augmentation of an existing in-house team, where the customer selects individual services and resources. The Berry Street and Brotherhood of St. Laurence case studies both describe blueAPACHE acting as an extension of an internal ICT team rather than replacing it.

What hours is the help desk available?

The emPOWER Managed Services brochure advertises unlimited 24/7 support. Business-hours support staff are located in Australia; after-hours and follow-the-sun support comes from blueAPACHE's global team, and blueAPACHE states that no part of the help desk is outsourced. Contractually, Business Hours are 0700 to 1900 AEST/AEDT on Business Days, so confirm on the Service Order which coverage applies to which service.

What response and resolution times does blueAPACHE commit to?

None are published. A priority and escalation matrix is agreed with each customer and determines how the service desk treats each incident type. Any response or resolution commitment that counts as a Service Level must be written under that heading in the Service Description; obligations described elsewhere, including a Compliance Target, are not Service Levels under the General Terms and Conditions.

Are there service credits if a Service Level is missed?

The General Terms and Conditions v3.6 contain no service credit or rebate regime. If credits exist for emPOWER Managed Services they are set out in Schedule 2, which is not published. Service Levels are measured using blueAPACHE's own tools and the results are final and binding on the customer, subject to the Reasonable Excuse exclusions.

What is included in the monthly price?

The brochure describes predictable pricing with unlimited help desk access and no fluctuating costs, delivered as an integrated support ecosystem: on-shore support, local account management, strategic and technology reviews, application management and reporting, proactive security management, backup and disaster recovery solutions, and end-user device provisioning. The exact inclusions and exclusions for a given customer are defined in the Service Description and Schedule 2.

What is an environment review and how often does it happen?

A regular review of the customer environment that highlights key issues for closer examination, supported by predictive capacity monitoring to manage growth. The brochure does not publish a cadence; the Archers engagement describes monthly operational reviews and quarterly business reviews, and the General Terms require a service review every six months. Fix the cadence on the Service Order.

How long is the contract and what happens at the end?

The default is a 36-month Minimum Service Period starting on the Service Commencement Date, renewing in 36-month periods unless blueAPACHE advises otherwise. If the customer gives no Written Notice and keeps using the service, all services on the agreement extend for three months at full list price with Service Levels switched off. Early exit triggers an Early Termination Payment under Schedule 2.

Who owns patching and maintenance of our servers and devices?

Under emPOWER Managed Services, blueAPACHE manages the complete lifecycle of infrastructure and devices from provisioning to patching and maintenance, using remote monitoring and management tooling for automated patching and compliance. Scheduled Maintenance on Customer Managed Equipment follows manufacturer recommendations, within the windows in the Schedule or with at least 3 Business Days' notice.

Do we get visibility of what blueAPACHE is doing?

Yes. Customers are given access to the same monitoring and management toolset blueAPACHE uses, covering monitoring, alerting and capacity baselining, so they can view their entire production environment. blueAPACHE also provides standard monthly reports within 5 Business Days of month end, samples of which are available on request, and the parties meet every 6 months for a service review.

Is security included in managed services?

Proactive security management, Security Gap Analysis audits and managed detection and response built on leading tools are named in the managed services security scope. The dedicated 24/7 emPOWER Managed Detection and Response service, Human Risk Management and Exposure Management are sold through the Security pillar, and their inclusion in any bundle should be confirmed in writing on the Service Order.

Where does blueAPACHE deliver managed services from?

Business-hours support is delivered from Australia, with offices in Melbourne (head office), Sydney and Brisbane, and after-hours coverage from blueAPACHE's teams in the United States and United Kingdom. emPOWER Managed Services is within the scope of blueAPACHE's ISO/IEC 27001:2022 certificate, which lists the Melbourne, Sydney and Brisbane offices.

Source

This page draws on blueAPACHE's published material: the emPOWER Managed Services, emPOWER platform overview and emPOWER Managed Detection and Response brochures; the emPOWER service portfolio and Global Capabilities brochures; the company timeline; the ISO/IEC 27001:2022 certificate 202507-118; the General Terms and Conditions v3.6 (covering definitions and key terms, service delivery and service levels, reasonable excuse exclusions, scheduled maintenance and emergencies, backup and disaster recovery obligations, business continuity management, transition in and disengagement, reporting, review and audit rights, and service term, renewal and minimum service period); the Archers, Honan Insurance, Brotherhood of St. Laurence and Berry Street case studies; blueAPACHE's messaging and positioning material; and the origin page at https://www.blueapache.com/empower-services/managed-services/.

Knowledge Base