Legacy Architecture Gap Assessment

Do you have a centralised product catalog that all systems reference?

A single system defining all product offerings, specifications, pricing rules, and eligibility — consumed by CRM, CPQ, billing, and order management via API.

Do you have a dedicated commercial order management system?

A system that captures, validates, and manages commercial orders separately from service fulfilment — handling order lifecycle, amendments, and cancellations at the business level.

Do you have a service order management system that decomposes commercial orders into service orders?

A system that takes commercial order items, decomposes them into CFS-level service orders, and orchestrates fulfilment across service domains.

Do you have resource order management that handles network-level activation?

A system that decomposes service orders into resource-level instructions and coordinates activation across network elements, EMS/NMS, and provisioning platforms.

Do you have a product inventory that tracks what each customer currently has?

A runtime inventory of instantiated product instances per customer — not what they ordered, but what they currently have active, including all characteristics and lifecycle state.

Do you have a service inventory tracking active CFS/RFS instances?

An inventory of instantiated service instances (CFS and RFS) with their current state, relationships, and configuration — the OSS runtime view of what is deployed.

Do you have a resource inventory managing physical and logical network resources?

An inventory of network resources — ports, VLANs, IP addresses, devices, logical links — with assignment state, capacity, and relationships to services.

Do you have a service catalog that defines CFS and RFS specifications separately from the product catalog?

A catalog defining customer-facing service (CFS) and resource-facing service (RFS) specifications, with decomposition rules that map commercial products to technical service components.

Are your BSS/OSS systems integrated using TMF Open APIs (or equivalent standardised APIs)?

Systems communicate via standardised REST APIs following TMF Open API specifications — not custom point-to-point integrations, file transfers, or direct database access.

Do your systems use event-driven patterns for state changes and notifications?

State changes (order status, inventory updates, alarm events) are published as events to a broker (Kafka, AMQP) rather than relying solely on synchronous polling or batch file transfers.