Service models, slicing and edge, at the level an IT engineer needs.
3 questions in Telecom.
They turn a service into a parameterised, capacity-constrained thing with a location. The catalogue must model performance characteristics and a site, the order flow gains a serviceability and reservation step that can legitimately say no, and SLA measurement has to feed billing.
Blast radius is a property of the change process, not of the redundancy diagram - identical config applied to both halves of a resilient pair fails both. You need staged exposure with soak time, subscriber-visible health checks, a management path that survives the outage, and a rollback that has been executed.
Mostly the work of identifying who loses service and moving them, which network data alone cannot tell you. Device capability comes from the IMEI, packet voice needs subscription and IMS provisioning in bulk, and the machine-to-machine base is the population that cannot be reached by a campaign.