Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsSerco Asia Pacific used BMC Helix as part of a broader shift toward cloud technology, product-oriented collaboration, hybrid delivery and AI-enabled innovation. In a January 2025 interview, the division’s chief digital officer said teams were using core Helix modules for operations and application monitoring while moving away from a traditional, waterfall-style approach. He described qualitative reliability and staff-focus benefits, but the interview gave no project metrics and did not establish that AI capabilities were in production.
What Serco wanted to change
The case concerns Serco Asia Pacific’s technology services supporting a hospital in Western Australia—not a quantified rollout across all of Serco. In a BMC-sponsored CIO.com interview published January 27, 2025, Jason Richardson, chief digital officer of Serco Asia Pacific, said the organization had revamped its technology strategy about three years earlier. The aim was to build on previous achievements while adapting to changing technology ecosystems. Richardson characterized the old approach simply: “We used to work in a traditional way.” Read the sponsored interview.
Richardson described four pillars behind the strategy:
- Cloud with security: adopt cloud technology without compromising the security posture.
- Product-driven collaboration: move beyond a traditional requirements-and-build model toward products that support collaboration across the company.
- Hybrid delivery: combine delivery approaches with attention to staff career opportunities and cost-effectiveness.
- AI and automation: accelerate innovation, with AI benefits to be explored as foundational capabilities are established.
How BMC Helix was introduced
Serco described its BMC Helix transition as a staged, module-by-module implementation developed with BMC. At interview time, teams were using core modules for operations and application monitoring. Richardson said Helix went “well beyond just capturing tickets and monitoring volumes and availability,” framing it as part of a broader technology-services approach.
Recommended Free Tools
The interview does not identify every module Serco configured or provide a detailed deployment timeline. BMC’s general Helix ITSM documentation describes functions such as service desk, asset management and change management, but those product capabilities do not establish which functions Serco used. The documentation’s 26.1 release page also lists newer features, including incident summaries and automated follow-ups; the interview does not say Serco deployed them. BMC Helix ITSM documentation.
What Serco reported—and what it did not measure
Richardson said the cloud transition was expected to improve reliability and reported fewer availability concerns than with the previous on-premises managed solution. He also said the change gave teams more time to focus on technology-service outcomes for hospital clients. These are Serco’s qualitative assessments in a BMC-sponsored interview, not independently verified findings.
The case provides no before-and-after availability figures, incident counts, cost savings, productivity measures or other numerical outcomes. It therefore supports a description of Serco’s objectives and reported experience, not a conclusion about the size of the benefits or how the approach would perform in another organization.
AI was an area of exploration, not a proven deployment
At the time of the interview, Serco’s immediate focus was on getting core Helix modules in place, with AI benefits to be explored afterward. Richardson also said teams were assessing generative AI platforms for government services and for Serco teams. The interview names no selected platform and reports no production deployment or measured productivity gains. In this case, “AI-powered operations” describes a direction under consideration, not an established result.
Rank #2
What the case can tell other organizations
Serco’s account offers a set of decision areas rather than a universal implementation recipe. An organization considering a similar transition can use them to frame its own planning:
- Define how cloud adoption will preserve the organization’s security requirements.
- Decide whether product-oriented collaboration addresses shortcomings in the existing requirements-and-project model.
- Assess hybrid delivery in terms of staffing, career development and cost-effectiveness; the interview does not quantify these trade-offs.
- Consider a staged rollout, and specify which capabilities must be working before adding further modules or exploring AI.
- Set baseline and follow-up measures—such as availability, service outcomes and staff time—so any claimed improvement can be evaluated. Serco’s interview did not publish these figures.
The useful distinction is between strategy and demonstrated outcome: the interview explains why Serco pursued cloud, collaboration, hybrid delivery and automation, and what Richardson said the transition felt like. It does not provide enough evidence to rank those choices against alternatives or to forecast financial returns.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
