“Refining is inevitable in science when you have made measurements of a phenomenon for a long period of time.”
Charles Francis Richter.
When setting up your alarm / fault management modules, the KISS principle again applies.
Focus first on getting raw alarms flowing and conduct audits to ensure all are reaching your OSS as planned.
Only once that step is completed should you look to augment your alarms with additional data that can be gathered or cross-referenced from other sources (eg taking acronyms / codes within the raw data and using reference tables to augment with human readable data, or referencing data from inventory to show impacted customers, etc).
Once that is bedded down, then build optimisation mechanisms (filtering, suppression, route-cause analysis, etc) in a step-by-step manner once your experts first evaluate and understand the flow of raw data.
I don’t recommend to start optimising in this manner before you know all alarms are reaching your OSS or before you have a thorough understanding of the raw data and how augmentations / mappings against this data work manually.
This KISS principle ensures that the tool is in and working as early as possible (a quick win for the project team to build credibility upon) and also gives operators a deeper understanding of your OctopOSS’s data. Many implementations will try to build alarm feeds, augmentation and optimisation mechanisms all at once for a big-bang cutover.
From my experience, this delays and complicates the solution as well as losing the opportunity to build momentum via phased developments.
Over the years, I’ve often referred to The Corkscrew Analogy or Momentum Spiral to describe a mindset of incremental improvement that’s needed to keep an
We’ve embarked on a journey of trying to plan for the future of OSS/BSS, not by predicting the future, but by seeking ways to be
As discussed in the previous article, “Future Scenario Planning: Have you given up on doing an OSS transformation? (part 1)” part of the fun of
Earlier in the week, a friend mentioned he was reading “Alchemy” by Rory Sutherland. It’s not an OSS book per se, but does provide some
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.
