We launch managed service for AI-era operations

Summary

Channel Life reported on 2 October 2026 that we had launched IT Operations Excellence as a Service, a managed-services model organised around automation, operational visibility, security, governance and measurable business outcomes. The launch was presented under the banner “Managed Services. Re-engineered.” It responds to the pressure on Australian IT leaders to adopt artificial intelligence, manage cyber risk and give boards clearer evidence of operational control without assuming that staffing and budgets will grow at the same pace.

This summary describes the launch article's account. It does not replace a current service scope, service agreement or implementation plan. Organisations evaluating the model should confirm the current inclusions, responsibilities, support arrangements and technical design with us.

At a glance

What changed in the managed-services model

The launch marked a move beyond a conventional model centred on keeping infrastructure available and resolving incidents as tickets arise. We positioned the new model around the business outcomes produced by day-to-day technology operations. Automation is intended to reduce routine manual work, security is built into the operating model, and operational visibility is intended to help IT leaders show what is happening across their environment.

That distinction matters because uptime alone does not answer every question now put to an IT team. Leaders may also need to account for cyber resilience, policy enforcement, audit evidence, workforce experience and the operational impact of AI tools. We presented IT Operations Excellence as a Service as a response to that broader remit.

The underlying positioning is consistent with our current managed-services message: security first, automation led and delivered through an integrated operating model. Readers comparing the launch with the current portfolio can start with the Managed Services overview and the managed service bundles.

Six operating principles

The article names six operating principles:

1. Automation-led operations — routine operational work is automated where appropriate so people can focus on work that needs judgement.
2. AI-ready operations — one of the six named launch principles; confirm the AI-related requirements and delivery scope for a proposed engagement.
3. Operational visibility — IT leaders should be able to see and demonstrate service performance and activity across the environment.
4. Security-first operations — security is treated as part of normal operations rather than a separate afterthought.
5. Experience-led IT — one of the six named launch principles; confirm the user-experience measures and activities for a proposed engagement.
6. Governance and accountability — responsibilities, evidence and operational oversight are treated as part of delivery.

These are launch principles rather than a promise that every customer receives the same tools or service configuration. The applicable service scope remains the place to confirm which controls, platforms, reports and responsibilities apply to a particular environment.

Customer Zero and internal validation

Before taking the model to customers, we said we had applied the approach within our own business. We called this Customer Zero. The purpose described in the article was to test the operating principles internally before releasing them to the market.

For a prospective customer, the useful point is the validation method rather than the label. Due diligence can ask what we learned from the internal deployment, which processes were automated, how exceptions are handled and what evidence is available to show that security and governance controls operate as intended.

Role of the partner network

The programme around the launch brought together products and expertise from Microsoft, NinjaOne, Zoom, ControlUp, Huntress, HPE Networking, Mimecast and SoftwareOne. This broader partner structure supports functions across endpoint management, collaboration, networks, cyber security and operational visibility.

A multi-vendor model can widen functional coverage, but buyers still need a clear accountability model. The article itself notes that integration and accountability are reasonable questions. During evaluation, confirm which platforms apply to the proposed service, which party owns each operational task, how events move between tools and teams, and where escalation responsibility sits. Security-specific next steps are available through the emPOWER Security overview, while governance requirements can be explored through Governance, Risk and Compliance.

What decision-makers should verify

The launch defines the direction of the service. A current evaluation should turn that direction into an agreed operating design. Useful checks include:

• which outcomes will be measured and how the reporting demonstrates them;
• which routine activities are automated and where a person reviews or approves an action;
• what operational visibility is provided to the customer and how often it is updated;
• which security controls are included, which remain the customer’s responsibility and how incidents are escalated;
• how AI-related changes, policy exceptions and new risks enter the governance process;
• which partner platforms are used for the customer’s environment and how integrations are monitored;
• the onboarding sequence, dependencies, service boundaries, support windows and exit arrangements; and
• the contractual documents that govern service levels, responsibilities and exclusions.

These checks do not add promises beyond the article. They convert its outcome-based message into the questions needed for a current, environment-specific assessment.

Related next steps

• Review the current Managed Services portfolio.
• Compare the available managed service bundles.
• Review the emPOWER Security service.
• Examine Governance, Risk and Compliance.
• Contact blueAPACHE to confirm current scope, delivery arrangements and service terms.