Skip to content

Nick Mudie

25+ years designing, transforming and operating telecom technology.

Across operators, vendors and managed-service environments — from network operations and service assurance to BSS/OSS architecture, transformation and AI-native telecom operations.

NowPrincipal Transformation ConsultantAnalysys MasonOslo

  1. Operations
  2. Service Assurance
  3. Architecture
  4. BSS/OSS
  5. Transformation
  6. AI / Modern Telecom
Nick Mudie, portrait
25+ years
Telecom experience
Five operators
Telia · Telenor · Vodafone · UPC · Marlink
BSS / OSS
Architecture & transformation
AI / Modern telecom
Current focus

Architecture that starts from how telecom actually runs.

Nick Mudie is a telecom architecture and transformation professional with more than twenty-five years inside operator technology. He started in OSS delivery and operations, built service assurance and observability capability for a national operator, and moved through architecture into BSS/OSS, greenfield transformation and hybrid cloud.

His work spans Telia, Telenor, Vodafone, UPC and Marlink — operator, vendor and managed-service perspectives. He is currently a Principal Transformation Consultant at Analysys Mason in Oslo, and his thinking centres on AI-native operations, modern telecom platforms and the BSS/OSS Academy, an independent body of work explaining how modern telecom architecture actually works.

  • Has operated, provisioned and assured the systems he now designs — architecture grounded in live-operator reality.
  • Delivered firsts: Europe's first triple-play provisioning platform, Telia's first E2E observability platform, Telia's first hybrid cloud.
  • Greenfield and post-merger BSS/OSS transformation across countries, not only single-system replacement.
  • Publishes the thinking: a vendor-neutral BSS/OSS Academy, architecture models and viewpoints that others use.

Order · Order-to-Activation. A product order is decomposed into service orders and then resource orders. Each decomposition step is an architectural boundary: a different system, a different owner and a different definition of done.

Explore →

The estate as I hold it in my head: layers down, lifecycle across. Open the interactive model.

From the network up.

Not many telecom jobs — one direction: deep operational experience, then architecture, then transformation, then the technology now changing both.

  1. Close to the network

    OSS delivery on live provisioning platforms — seeing, first-hand, what happens when the systems that describe the network disagree with the network itself.

  2. From alarms to services

    Monitoring, observability and ITSM across BSS, OSS, applications, infrastructure and network — building the model that lets an operations team talk about services rather than devices.

  3. Designing the whole

    Moving from operating and delivering systems to designing them: application, integration, infrastructure and domain architecture across the operational and commercial estate.

  4. Catalog, order, fulfilment, inventory

    Greenfield BSS/OSS stacks, catalog-driven design, order orchestration and service provisioning — the core that decides whether a product can be sold, delivered and assured end to end.

  5. Changing it while it runs

    Legacy modernisation, greenfield programmes and post-merger integration with real customers on the old stack — sequencing, coexistence and governance.

  6. Operations that reason

    AI-native operations, agentic assurance and the infrastructure behind them — applied with the scepticism of someone who has run monitoring for a national operator.

What I am working on now.

Telecom transformation consulting at Analysys Mason — and, around it, AI-native and agentic operations, AI infrastructure as part of the telecom estate, and catalog-driven, ODA-aligned BSS/OSS transformation that survives real orders and real incidents.

  • applying

    AI in Telecom

    Where AI genuinely changes operations and architecture, and where it is still a demo.

  • exploring

    Agentic Operations

    Agents that reason over service topology, events and inventory — and the guardrails they need.

  • exploring

    Autonomous Networks

    Closed-loop assurance and intent-based operation, judged against what a NOC can actually trust.

  • building

    AI Infrastructure

    GPU-dense data centres, networking and placement as part of the telecom infrastructure estate.

A body of work, not a blog.

The BSS/OSS Academy, architecture models and viewpoints — evidence of how I think, built for other people to use.

A vendor-neutral educational platform I built to explain and explore modern telecom architecture — the concepts I work with every day, written down so that business, IT and vendor teams can share the same model of the problem.

It covers BSS/OSS from first principles to transformation strategy, uses TM Forum SID, eTOM and ODA as a shared vocabulary, and extends into AI in telecom, AI infrastructure and modern telecom architecture. It is used for onboarding, programme alignment, glossary decisions and assessing architectural reasoning.

What it covers

  • BSS/OSS

    Catalog, order management, fulfilment, inventory, assurance — end to end

  • TM Forum · SID · eTOM · ODA

    Standards used as a shared language, not a compliance checklist

  • Product & Service Catalog

    Product, service and resource specifications in practice

  • Order Management & Service Fulfilment

    Decomposition, orchestration and activation

  • Service Assurance

    From alarms to services; observability and closed loops

Discuss an engagement, an architecture, or a second opinion.