📦Module 10

Network Activation & Provisioning

From Service Order to an Active Service Across Network Domains

How a service order becomes an active service across network domains: how the network is recorded in inventory, the EMS/NMS and controllers that manage each domain, how ROM reaches them, how resources are configured and activated, and how orchestration coordinates several domains for one order.

Sections

10.0

Network Activation & Provisioning: How It Fits Together

The whole module on one page: from a service order to an active service, through orchestration, ROM, inventory, the EMS/NMS and controllers of each domain, down to the network. Select any part to see what it does and where it is covered.

6 min

10.1

Network Inventory Overview

What network inventory means in telco — the runtime record of physical and logical resources on the network, managed by solutions like Ericsson Adaptive Inventory.

10 min

10.2

Resource Inventory

Resource Inventory for managing physical and logical network resources — devices, ports, cables, VLANs, IPs, and network topology.

12 min

10.3

EMS/NMS Architecture

Where ROM stops and EMS/NMS begins — vendor-specific element management, integration patterns, protocol landscape, and the O-RAN boundary shift.

12 min

10.4

ROM's Southbound Edge: Network Automation & Interfaces

What sits below ROM — network orchestrators and SDN controllers, the NETCONF/YANG, gNMI and SNMP interfaces they use, and the multi-domain network elements they configure. A map, not a tutorial.

10 min

10.5

Activation & Provisioning

How services are activated on the network: provisioning patterns and integration.

15 min

10.6

OSS Functional Layering & Cross-Domain Orchestration

A strict functional layering of the OSS runtime path — CRM/CPQ, COM/SOM, cross-domain service orchestration, ROM / domain execution — and why each layer is a distinct product category. Clarifies where Itential, Ericsson Order Care, Hansen Order Management, Cisco NSO, Nokia E2E SO, Ericsson SOA, Blue Planet MDSO, and Oracle Unified Orchestrator actually sit.

20 min