“We are not cisterns made for hoarding, we are channels made for sharing.”
Billy Graham.
Have you ever stopped to wonder why most CSP’s OSS are so complex? Put simply, they are almost all hoarders.
They collect services, device types, management systems, data, interfaces, etc. But how often do they ever discard one? Even when their house is full of stuff, they just build a shed in the backyard (ie they archive their data in cheaper storage).
If they could only implement a one-in-one-out (O-I-O-O) policy, their B/OSS might be a bit easier to manage. It might curtail the products department if you ask them to offload one of their existing products before creating a new one. Or if you’re storing records from when Elvis was just starting out. No, not those records.
This O-I-O-O policy is just a little idealistic because it could hold innovative solutions back but it would make CSPs think more about mandated simplification as a common goal across all business units and all aspects of operations.
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
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
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.
