At a glance
Data centres
Countries
Operational users
Site Operations solutions deployed
Operational Finance is increasing in depth as operating history accumulates
Mobilisation
Against a more typical window of around 90
Next scope
Deployment facts only. No efficiency, work-order or administrative-effort figure is recorded for this deployment, and none is claimed. Live duration is not disclosed.
01
The operating context
This is a colocation business that owns its estate and operates it for others — eleven data centres across four countries in the Middle East and North Africa, with major hyperscale customers among its tenants. Around three hundred people work on the estate day to day.
Operational delivery had been outsourced, and the business was in the middle of consolidating those arrangements. That is ordinary enough. What made it interesting was that the consolidation was happening at the same time as a longer-term question about the operating model itself.
02
The challenge
An owner that outsources execution keeps the asset and the liability, but the day-to-day understanding of how the estate actually behaves tends to migrate towards whoever is doing the work. Procedures get written inside the provider's systems. Maintenance history accumulates in the provider's tooling. Competency records, contractor governance, audit evidence and supplier performance all sit with the delivery arrangement rather than with the estate.
That is manageable while the arrangement is stable. It becomes expensive at exactly the moment the arrangement changes — at retender, at provider transition, or if the owner decides to bring some of the work back in-house. The knowledge has to be reconstructed, and it is reconstructed from whatever the outgoing party chooses to hand over.
How does an owner outsource execution without outsourcing its understanding of how the estate operates?
03
Why the existing model was not enough
Consolidating providers does not solve it. A smaller number of better-managed contracts still leaves the operating record distributed across the delivery arrangement rather than held by the owner. Fewer counterparties is a commercial improvement, not an informational one.
Nor does a single system for one domain. Asset and maintenance history without competency data does not tell you whether the right person did the work. Risk and audit evidence without supplier scope does not tell you who was accountable for it.
The knowledge lives in the connections. What an owner needs to retain is not four registers but the relationships between them — and a relationship cannot be held in a tool that only carries one side of it.
04
What changed
The complete Site Operations System of Work was deployed — all four solutions, mobilised together rather than sequenced over a longer programme.
01
Asset Management (CMMS)
Register, maintenance programmes and scheduling, work orders, asset history, and visibility of who performs which work, at what complexity, internally or by vendor.
02
Workforce & Competency
Structure, roles, competency and specialist capability, shift patterns, overtime, vacancies, attrition, training and toolbox talks.
03
Risk & Reliability
Audits, inspections, rounds and readings, risk controls, critical-system information, controlled documentation and evidence of compliance.
04
Operational Finance
Suppliers, contracts, scope, sourcing history, pricing, tenure and expenditure.
Deployed, and increasing in depth as operating history accumulates. Breadth of adoption and depth of adoption are not the same claim.
05
The connected operating model
Deploying the four together is the point rather than a scheduling convenience. Assets, workforce, competency, supplier scope, risk, procedures and provider performance now sit in one place rather than being held across the delivery arrangement.
That produces relationships the owner can interrogate directly: which work was done, on which asset, by whom, at what competency, under which risk control, against which supplier's scope, at what cost. Each of those is answerable from one record instead of assembled from four sources and a phone call.
Before
Held across the delivery arrangement
- Procedures written inside the provider's systems
- Maintenance history in the provider's tooling
- Competency and contractor governance with the deliverer
- Compliance evidence assembled on request
- Supplier scope and performance separate from the work
After
One record, held by the owner
- One asset and maintenance history across eleven sites
- Competency and authorisation attached to the work order
- Risk controls and inspection evidence against the asset
- Controlled documentation in one governed place
- Supplier scope, tenure and expenditure connected to delivery
06
The arrangement can change. The record does not.
The reason for building it this way is what happens at the moments an outsourced estate is normally most exposed.
Continuous underneath
Assets, maintenance history, competency, risk controls, procedures, supplier scope and provider performance — one accumulating record of how the estate actually runs.
07
Outcomes and evidence
Four tiers, in descending evidential strength. What is proven, what is early, what is qualitative, and what is deliberately not claimed.
Deployment facts supported by the source record.
- Estate-wide adoption. All four Site Operations solutions are deployed across eleven data centres in four countries, used by more than three hundred operational people.
- Mobilisation in approximately forty-five days. The full Site Operations environment was stood up in that window. Verify comparator The ~90-day figure it is compared against is industry-typical rather than a measured baseline for this customer.
Credible, still maturing, or commercially unconfirmed.
- A progressively richer institutional record. The owner now holds an accumulating account of how its estate runs. It is stronger now than at go-live and will be stronger again later — which is also why it cannot yet be quantified.
- Operational Finance is deepening rather than finished. Deployed, and increasing in depth as operating history accumulates. This page does not treat four-of-four adoption as four-of-four maturity.
- Expansion into Service Management. Successful adoption of Site Operations has led to an order to extend into the Service Management System of Work. Verify Commercial fact with no recorded date or disclosure permission.
Qualitative observation. Not measured, and not an endorsement.
- An unusual level of systemised control, as observed by a tenant. A major hyperscale tenant highlighted the level of systemised operational control as unusual compared with what it typically encounters across its wider colocation portfolio. Verify This is a reported observation about the estate, made by a tenant of the customer rather than by the customer. It is recorded as an observation, not as a testimonial or a third-party endorsement.
Where evidence does not exist, nothing is asserted in its place.
- No efficiency or financial outcome. No administrative-effort, work-order, maintenance-completion or cost outcome is claimed for this deployment. None is recorded, and this environment has not been running long enough for that class of evidence to have settled.
- No live duration. How long this deployment has been in production is not disclosed here, because no project source states it.
- No insourcing decision. The source describes future operating options available to the owner. It does not describe a decision, and neither does this page.
On the absence of efficiency metrics. Where an early deployment is concerned, deployment scale, mobilisation speed, adoption breadth and expansion are real evidence and efficiency percentages are not yet evidence at all. Clarisync case studies that carry measured efficiency outcomes publish them with their own method, separately from this one.
08
What comes next
Continuity across delivery-model change. The record supports continuity whether delivery remains outsourced, moves between providers, or is brought closer to the owner in future. That is stated as optionality, not as a decision the business has taken.
An ordered extension into Service Management. The second System of Work has been ordered on the strength of the first.
Execution can be outsourced. Understanding does not have to be.
09
Customer perspective
Attribution status
No approved customer statement exists for this deployment. The customer operates under confidentiality and has not been asked for, or granted, permission to be quoted or identified.
Where a named or attributed reference becomes appropriate, it will be added with written permission rather than paraphrased from internal material. A reference call with a peer operator can be arranged on request through the Proof Centre.
10
Evidence, method and governance
Anonymity
This customer is anonymised. No name, brand, site name or location appears anywhere in this asset, and none will be added without written permission.
The combination of details this case study does carry — colocation owner-operator, Middle East and North Africa, eleven data centres, four countries, hyperscale tenants, mobilisation window and future operating optionality — has been flagged internally as an identification risk for review before publication. The factual substance has not been altered to reduce that risk; that is a decision for the accountable human owner, not for the production process.
Evidence basis
Every figure and statement on this page traces to an internal source record for this deployment. Deployment facts — site count, country count, user count, solutions deployed, mobilisation window — are supported directly by that record.
Two items carry a verification flag. The ninety-day mobilisation comparator is an industry-typical figure with no stated source, scope or population, and is presented as a comparator rather than as a measurement. The Service Management extension is a commercial fact recorded without a date or disclosure permission.
The hyperscale-tenant observation is reported at second hand, is unattributed, concerns a tenant of the customer rather than the customer, and carries no permission. It appears here as a directional observation and must not be presented as a testimonial or as third-party endorsement.
Portfolio-wide reach figures published elsewhere by Clarisync are not attributable to this customer and are not used on this page.
Product and taxonomy notes
Solution and System-of-Work names follow the canonical product taxonomy. Site Operations comprises Asset Management (CMMS), Workforce & Competency, Risk & Reliability and Operational Finance.
This case study describes which capabilities were deployed. It does not redefine product scope, platform hierarchy or System-of-Work boundaries, and it makes no claim about applied AI, because the source records none for this deployment.