The Runtime Gap Between OSS and Network Execution

For decades, telecom operations have relied on OSS systems to orchestrate networks. Provisioning flows begin in the OSS layer. Orders move through orchestration systems. Policies are configured, services are activated, and eventually the network reflects the intended state. On paper, the process looks coherent. But there is a growing gap between orchestration logic and what actually happens inside the network at runtime. This gap has existed quietly for years. As networks become more programmable and API-driven, it is becoming impossible to ignore. OSS Was Designed for Planned State, Not Runtime Behavior Traditional OSS systems were built around the concept of planned state. An operator defines a service configuration. The OSS translates that configuration into provisioning actions. Those actions propagate through orchestration systems until the network reaches the desired state. The process works well when network behavior is predictable and relatively static. However, modern networks