Fujitsu — One global ServiceNow platform from a fragmented multi-instance estate

Fujitsu operated multiple ServiceNow instances, each shaped by its original project’s constraints. What it needed was one platform shaped by its customers’ requirements.

The challenge

Fujitsu Technology Services operated a Managed Service Provider offering that had evolved instance by instance — each implementation accumulating its own governance, DevOps habits, and interpretation of what a shared platform should look like. The result was an estate that could not present a consistent service model to customers, could not consolidate architectural decisions across the portfolio, and could not enforce quality standards at the point of design rather than the point of delivery. The objective was unambiguous: one global ServiceNow platform, one design authority, one Centre of Excellence, and a consolidated all-services model at MSP scale. The architectural challenge was equally clear: consolidation without destroying what each instance had built, and a governance model that would outlast the programme.

The Blu Wingu approach

Blu Wingu was engaged as Global Lead Architect and Strategic Product Advisor to the Programme Director, spanning Germany and the UK from March 2015 to June 2017. The mandate was the design-authority tier: establish the platform architecture, the governance model, and the Centre of Excellence that would govern all subsequent delivery.

The consolidation architecture aligned Fujitsu’s IT processes to a common operating model and established a Centre of Excellence with defined standards for governance, security, and release management. Multiple ServiceNow instances were consolidated under a unified platform, with the all-services model redesigned for MSP scale. Domain Separation was architected and implemented for a Managed Service Provider context — delivering the pattern that separates customer estates within a single instance without fragmenting the operational model.

The Global Design Authority and Platform Owners function was established and led by Blu Wingu as the formal approval mechanism for architectural decisions. Every architectural decision had an owner; every deviation from standard had a documented rationale; every standard evolved through a defined change process rather than accumulating as tribal knowledge. DevOps teams were established and led across multiple products; the operating model was designed for sustainability after programme close, not dependent on the programme team’s ongoing presence.

Blu Wingu advised the Programme Director on platform direction, emerging ServiceNow capability, and architecture decisions shaping Fujitsu’s competitive positioning in the managed-services market — executive-level advisory that shaped decisions rather than implemented them.

The outcome

Fujitsu’s fragmented multi-instance estate was consolidated onto a single global ServiceNow platform with a unified all-services MSP model. The Centre of Excellence and Global Design Authority provided an institutional governance mechanism that outlasted the programme — architectural coherence enforced by process rather than individual expertise. The Domain Separation architecture delivered the customer-estate isolation MSP operations require without the overhead of separate instances.

What’s defensible

The Global Lead Architect and Global Design Authority roles are documented in the programme record; the Domain Separation architecture for MSP context is a verifiable deliverable from the September 2014–January 2015 engagement window.

Cross-links: Enterprise Architecture