Last week we discussed whether big OSS was losing relevance and our tools are just operational support systems (little oss).
I firmly believe that the future for OSS, a future that already exists in some organisations, is for OSS to produce relevant insights and efficiency far beyond just operational teams. They need to be relevant to an organisations’ business units that look after sales, marketing, products, design, contact centres, etc, etc.
So if an OSS is the glue that allows a modern digital business to communicate, derive cross-department insights and deliver operational efficiencies, does having the “Operational” in OSS actually constrain our thinking into what our tools can actually be… MUST actually be?
I’ll dive more into what the ramifications of this statement is on future OSS design next week.
In our “chasm” series of articles, we’ve talked about the gap that exists between OSS buyers (eg carriers or network operators) and OSS sellers (eg
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,
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
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.
