🔄
Section 3.4
Resource Order Management (ROM)
How service orders decompose into resource orders for network activation.
What Is Resource Order Management?
Resource Order Management (ROM) is the lowest layer of the three-layer order model. It receives resource orders from SOM via TMF652, allocates physical and logical resources from Resource Inventory (TMF639), drives configuration to network elements via activation adapters, and confirms completion back to SOM. ROM operates at the RFS and Resource layers — the bridge between the OSS fulfilment stack and the network.
Resource Order Management (ROM)
The OSS capability responsible for receiving resource orders from SOM, allocating physical and logical resources from inventory, driving configuration to network elements via activation interfaces, and confirming resource provisioning completion. ROM is the system of record for Resource Order entities and works closely with Resource Inventory (TMF639) and the network activation layer.
Service Order Management (SOM)Service Layer — TMF641
Service Order
TMF641
TMF652 POST
Resource Order Management (ROM)OSS — Resource Layer
Resource Order
TMF652 Reception
Resource Assignment
Query Available
TMF639 GET
Select Best Fit
Assignment rules
query
Resource Inventory
TMF639
Reserve Resource
Lock in inventory
reserve
Resource Catalog
TMF634
Activation via Adapters
NETCONF/YANG
Routers, switches
REST API
SDN, VNF, cloud
TR-069
CPE / ONT
CLI / SSH
Legacy elements
TMF652 events ↑ to SOMread-back & verification ↑ from network
config push
Network InfrastructurePhysical & Virtual Network Elements
OLT / Switch
BNG / Router
DHCP / IPAM
SDN Controller
CPE / ONT
ROM is typically provided by specialised network orchestration tools such as Itential or Cisco NSO — not by traditional O2A platforms like Hansen or Cerillion
ROM Core Responsibilities
- Resource order reception — receive and validate resource orders from SOM (TMF652)
- Resource assignment — select specific resources (ports, VLANs, IPs) from Resource Inventory based on availability, proximity, and capacity
- Reservation — lock assigned resources to prevent concurrent allocation by other in-flight orders
- Network activation — push configuration to network elements via adapters (NETCONF, CLI, REST, TR-069)
- Verification — confirm configuration was applied correctly via read-back or service test
- Inventory update — update Resource Inventory (TMF639) with the activated resource state
- Rollback — release resources and reverse configuration if activation fails or the order is cancelled
ROM Is Specialised Network Orchestration
Most traditional O2A platforms (e.g. Hansen, Cerillion) do not provide ROM. Resource-level orchestration requires deep integration with network element managers, device configuration models (YANG, MIBs), and southbound protocols — capabilities that sit outside a typical BSS/OSS order management stack. In practice, ROM is delivered by specialised network orchestration tools such as Cisco NSO, Itential, or Nokia NSP. These tools manage the translation from abstract resource orders into device-specific configuration, handle rollback on failure, and provide the southbound adapter framework. When evaluating an O2A vendor, assume ROM must be sourced separately and integrated via TMF652.
The Activation Adapter Pattern
ROM does not interface with network elements directly. It uses activation adapters (southbound drivers) that translate abstract resource order items into device-specific commands — NETCONF, RADIUS, Diameter, HTTP/2 SBI, TR-069, ETSI SOL005, and cloud REST SDKs. When a new device type is introduced, only a new adapter is needed, not a change to ROM itself.
Section 3.4 Key Takeaways
- ROM is the lowest layer of order management, responsible for resource allocation and network activation
- Resource assignment selects specific resources (ports, VLANs, IPs) from inventory; reservation prevents concurrent allocation conflicts
- Network activation uses adapters to translate abstract orders into device-specific commands (NETCONF, CLI, REST, TR-069)
- TMF652 standardises the SOM → ROM interface; TMF639 is the resource-level system of record