What it is (plain English)
The telecom order-orchestration layer: it takes a product order, decomposes it into customer-facing service orders and resource-facing orders, and coordinates the work needed to deliver and activate the service.
Problems it solves
- Product orders stall because service, resource, and fulfillment work are managed in separate queues or systems.
- Teams cannot consistently decompose a sold telecom product into the network, field, and partner work required to deliver it.
- Order status and fallout are difficult to trace across fulfillment domains.
What must exist first
Platform Core Setup, a telecom product and service model, and defined fulfillment processes. Telecom Network Inventory is not a universal OMT prerequisite, but both applications must be licensed in the same instance when using the documented TNI integration for network-inventory actions.
What the customer needs to provide
- Product, service, and resource specifications plus decomposition rules.
- Order types, lifecycle states, orchestration tasks, and exception/fallout ownership.
- The systems and teams that fulfill each domain order, including partner and field work.
- Decision logic for when an order task must create or update a network resource.
Where it can go next
Works with Telecom Network Inventory for network-aware design and assign work. The documented integration supports the ADD action for creating network resources through inventory-related change requests; broader action coverage should not be implied. Telecom Service Operations Management (TSOM) handles assurance and operational issues once services are live.