Have you ever been tasked with mapping out the processes for the telco you work for? Either as a way of documenting current state, or just to perform a first-time mapping for your company?
It can be a lengthy exercise, and based on the regular feedback we get, a daunting task too.
There are some wonderful resources, including TM Forum’s eTOM and AXELOS’s ITIL frameworks. These don’t always cover the full range of processes used within telco network operator environments.
As a result, we’ve been slowly chipping away at an OSS/BSS Process Mapping Guide for quite some time now. It has over 50 starter processes for you to refine to your organisation’s unique needs and structures. Click on the image below, or the URL beneath it to be taken to the download page.
In all honesty, it’s not perfect and it will still need lots of ongoing refinement as we continue to test it out in the wild. However, we hope it’s a useful starting point for those who have been tasked with a large telco process mapping exercise.
We’d be grateful if you’d consider reviewing and suggesting improvements / corrections / recommendations!
Have you ever had an OSS or BSS project that’s impacted by poor data quality? The problem of data integrity gets raised on almost every
“One of my favorite things about designing software is designing the defaults. The defaults define the experience for everyone out of the box. And, therefore,
In the last week alone, I’ve had two potent reminders that the world of OSS is simply (pun intended) too complex. This manifests in many
It seems fairly obvious (to me at least) that AI is an existential threat to many traditional information-based roles like consultants and architects. I’ve already
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.
