“Integrity is not a conditional word. It doesn’t blow in the wind or change with the weather.”
John D. MacDonald.
So you have found the holy grail of the OSS world and delivered the perfect OSS product. Hats off to you!
But you can’t stop there can you? Is the data in your OSS perfect? If it is, that’s holy grail number two.
But you’re still not finished are you? Holy grail number three is defining the process (or processes) that keep the data perfect.
Holy grails one and two are probably impossible:
To be honest, HG#3 is also impossible but with clever process designs that have data integrity feedback loops built in, you can at least ensure that daily activities are pushing data ever closer to the asymptote of perfection.
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.
