OSS / BSS in the clouds
Have you noticed the recent up-tick in headlines around telco offerings by hyperscalers AWS, Google and Microsoft? Or the multi-cloud telco models, the middleware, supplied by VMware and Red Hat? Whilst previous generations of wireless connectivity have focussed on voice and data capabilities, 5G is architected to better enable consumer business models. Edge compute (both […]
Getting confused by key Assurance metrics?
Are you a bit slow like me and sometimes have to stop and think to differentiate your key assurance metrics like your MTTRs from your MTBFs? If so, I thought this useful diagram from researchgate.net might help The metrics are: MTBF (Mean Time Between Failures) – the average elapsed time between failures of a system, […]
Softwarisation of 5G
As you have undoubtedly noticed, 5G is generating quite a bit of buzz in telco and OSS circles. For many it’s just an n+1 generation of mobile standards, where n is currently 4 (well, the number of recent introductions into the market mean n is probably now getting closer to 5 🙂 ). But 5G […]
An Asset Management / Inventory trick
Last week we discussed the nuances between Inventory, Asset and Config Management within an OSS stack. Each one of these tools are designed to supports functionality for different users / persona-groups. However, they also tend to have significant functional overlap. Chances are your organisation doesn’t have separate dedicated tools for each. So today I’m going […]
Bleak sentiments
“People in a tough spot often focus on their own problems, when the answer usually lies in fixing someone else’s.”Steve Schwarzman. The telco industry is in a tough spot in many areas around the globe. Sadly, there were more stories of wholesale retrenchments here in Australia this week, including good friends. Revenues falling. Sentiment bleak. […]
OSS discovers a network
Following yesterday’s post about OSS Inventory, I received another great follow-up question from another avid reader of the PAOSS blog: “Interesting thoughts Ryan! In addition to ‘faults up’, perhaps there is a case also (obvious?) for ‘discovery up’ to capture ongoing non-planned changes? Wondering have you come across any sort of reconciliation / adaptive inventory […]
In need of an OSS transformation translator
As OSS Architects, we have an array of elegant frameworks to call upon when designing our transformational journeys – from current state to a target state architecture. For example, when providing data mapping, we have tools to prepare current and/or target-state data diagrams such as the following: Source here. These diagrams are really elegant and […]
Orders down, faults up (and the TMN Pyramid)
As mentioned in a post about Service and Resource Availability last week, I do tend to think of OSS workflows around an “orders down, faults up,” flow direction. And that means customers (services) at the top, network (resources) at the bottom of the (TMN) pyramid [see more about the TMN pyramid reference at the end […]
The Ineffective OSS Scoreboard Analogy
Imagine for a moment that you’re the coach of a sporting team. You train your team and provide them with a strategy for the game. You send them out onto the court and let them play. The scoreboard gives you all of the stats about each player. Their points, blocks, tackles, heart-rate, distance covered, errors, […]
One big requirement category most OSS can’t meet
We talked yesterday about a range of OSS products that are more outcome-driven than our typically transactional OSS tools. There’s not many of them around at this stage. I refer to them as “data bridge” products. Our typical OSS tools help manage transactions (alarms, activate customers services, etc). They’re generally not so great at […]
An OSS checksum
Yesterday’s post discussed two waves of decisions stemming from our increasing obsession with data collection. “…the first wave had [arisen] because we’d almost all prefer to make data-driven decisions (ie decisions based on “proof”) rather than “gut-feel” decisions. We’re increasingly seeing a second wave come through – to use data not just to identify trends […]
Crossing the OSS chasm
Geoff Moore’s seminal book, “Crossing the Chasm,” described the psychological chasm between early buyers and the mainstream market. Seth Godin cites Moore’s work, “Moore’s Crossing the Chasm helped marketers see that while innovation was the tool to reach the small group of early adopters and opinion leaders, it was insufficient to reach the masses. Because […]
Over 30 Autonomous Networking User Stories
The following is a set of user stories I’ve provided to TM Forum to help with their current Autonomous Networking initiative. They’re just an initial discussion point for others to riff off. We’d love to get your comments, additions and recommended refinements too. As a Head of Network Operations, I want to Automatically maintain the […]
We use time-stamping in OSS, but what about geo-stamping?
A slightly left-field thought dawned on me the other day and I’d like to hear your thoughts on it. We all know that almost all telemetry coming out of our networks is time-stamped. Events, syslogs, metrics, etc. That makes perfect sense because we look for time-based ripple-out effects when trying to diagnose issues. But therefore […]
As a network owner….
….I want to make my network so observable, reliable, predictable and repeatable that I don’t need anyone to operate it. That’s clearly a highly ambitious goal. Probably even unachievable if we say it doesn’t need anyone to run it. But I wonder whether this has to be the starting point we take on behalf of […]
For those starting out in OSS product, here’s a tip
“For those starting out in product, here’s a tip: Design, Defaults*, Documentation, Details and Delivery really matter in software.”Jeetu Patel here. * Note that you can interpret “Defaults” to be Out-Of-The-Box functionality offered by the product. Let’s break those 5 D-words down and describe why they really matter to the OSS industry shall we? Design […]
Net Simplicity Score (NSS) gets a little more complex
In last Tuesday’s post, I asked the community here on PAOSS and on TM Forum’s Engage platform for ideas about how you would benchmark complexity. I also provided a reference to an old post that described the concept of a NSS (Net Simplicity Score) for our OSS/BSS. Due to the complexity of factors that contribute to […]
Opinions wanted – How to Benchmark OSS/BSS complexity
I’d love to ask you an important question… how do we benchmark OSS/BSS complexity? To measure how complex our systems are and therefore provide a signpost for simplification. A colleague has opined that the number of apps in a stack could be used a proxy. I can see where he’s going with that, but I […]
The digital transformation paradox twins
There’s an old adage that “the confused mind always says no.” Consider this from your own perspective. If you’re in a state of confusion about something, are you likely to commit wholeheartedly or will you look to delay / procrastinate? The paradox for digital transformation is that our projects are almost always complex, but complexity […]
What will get your CEO fired? (part 4)
In Monday’s article, we suggested that the three technical factors that could get the big boss fired are probably only limited to: Repeated and/or catastrophic failure (of network, systems, etc) Inability to serve the market (eg offerings, capacity, etc) Inability to operate network assets profitably In that article, we looked closely at a human factor […]