Yesterday’s blog provided a contrast between a NOC and NASA’s Mission Control. It indicated that Mission Control is focussed on a single payload whilst NOCs are managing thousands / millions of services simultaneously.
From a customer experience perspective, we need to build OSS / BSS suites that are able to track every journey from end-to-end rather than the more common batch / silo approach. But this can be a really difficult, perhaps even insurmountable challenge for organisations with many legacy systems that contribute to existing workflows. Journey mapping can be difficult to retrofit.
As a proxy if you don’t have linking keys, you can use the cascading bucket technique. The diagram below (stolen from SolveforInteresting.com) shows the concept (disregard the numbers though).
If you can measure volumes of flows at each step in the journey then you can get a feel for where fallouts are happening. Sankey diagrams can be a good way of visualising.
It’s only a proxy though as most customer journeys traverse complicated service provider processes that have time gaps and data mutations / augmentations.
Earlier this week, I was lucky enough to be introduced to a talented RAN automation expert. He’s one of Australia’s foremost, hands-on, experts on SON
I was listening to a group of telco experts on a podcast the other day. As they were talking, I kept picturing the image of
Earlier in the year, we wrote a series of articles about the chasm that exists between OSS/BSS buyers and sellers (pt1, pt2, pt3, pt4, pt5, pt6). “The chasm” is
Actually, maybe a few related questions. As you’ve seen from recent articles such as this, I’m increasingly interested in the cross-over worlds of comms and
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.
