Do I support the death penalty (of OSS RFPs)? Hmmm….
As per yesterday’s post, I’ll continue to reference a TM Forum report called, “Time to kill the RFP? Reinventing IT procurement for the 2020s” today. Mark Newman and the team have captured and discussed so many layers to the OSS/BSS procurement process. There’s no doubt the current stereotypical RFP approach to procurement is broken. It […]
Lobbying hard for the death penalty for OSS RFPs
Earlier this year, the TM Forum published a really insightful report called, “Time to kill the RFP? Reinventing IT procurement for the 2020s.” There are so many layers to the OSS/BSS procurement discussion and Mark Newman and team have done a fantastic job of capturing them. We’ll expand on a few of those layers in […]
OSS/BSS procurement is flawed from the outset
The industry we work in is worth tens of billions of dollars annually. We rely on that investment to fund the OSS/BSS projects (and ops/maintenance tasks) that keeps many thousands of us busy. Those funds originate from project sponsors in the buyers’ organisations taking a leap of faith in kicking off an OSS project. For […]
Moving from traditional assurance to AIOps, what are the differences?
We’re going to look into assurance models of the past versus the changing assurance demands that are appearing these days. The diagrams below are highly stylised for discussion purposes so they’re unlikely to reflect actual implementations, but we’ll get to that. Under the old model, the heart of the OSS/BSS was the database (almost exclusively […]
Going to the OSS zoo
“There’s the famous quote that if you want to understand how animals live, you don’t go to the zoo, you go to the jungle. The Future Lab has really pioneered that within Lego, and it hasn’t been a theoretical exercise. It’s been a real design-thinking approach to innovation, which we’ve learned an awful lot from.” […]
Three OSS project responsibility sliders
Last week we shared an article that talked about the different expectations from suppliers and clients when undertaking an OSS implementation project. The diagram below attempts to demonstrate the concept visually, in the form of three important sliders. When it comes to the technical delivery, it makes sense that most of the responsibility falls upon […]
This OSS is different to what I’m used to
OSS implementations / transformations are always challenging. Stakeholders seem to easily get their heads around the fact that there will be technical challenges (even if they / we can’t always get their head around the actual changes initially). When a supplier is charged with doing an OSS implementation, the client (perhaps rightly) expects the supplier […]
Are modern OSS architectures well conceived?
“Whatever is well conceived is clearly said, And the words to say it flow with ease.” Nicolas Boileau-Despréaux. I’d like to hijack this quote and re-direct it towards architectures. Could we equally state that a well conceived architecture can be clearly understood? Some modern OSS/IT frameworks that I’ve seen recently are hugely complex. The question […]
Making a basic assessment of OSS value
“…as technology gets more complicated, it becomes more difficult for buyers to acquire the skills needed to make even a basic assessment of value. Without such an assessment, it’s hard to get a project going, and in particular hard to get one going the right way.” Tom Nolle. Have you noticed that over the last […]
The OSS “out of control” conundrum
Over the years in OSS, I’ve spent a lot of my time helping companies create their OSS / BSS strategies and roadmaps. Sometimes clients come from the buy side (eg carriers, utilities, enterprise), other times clients come from the sell side (eg vendors, integrators). There’s one factor that seems to be most commonly raised by […]
The 3 states of OSS consciousness
The last four posts have discussed how our OSS/BSS need to cope with different modes of working to perform effectively. We started off with the thread of “group flow,” where multiple different users of our tools can work cohesively. Then we talked about how flow requires a lack of interruptions, yet many of the roles […]
OSS work practices that are repulsive
“I believe in the principle that deep work and constant availability are repulsive concepts (in the magnetic sense).” Tyler Mumford in comment 2 to this post. This blogging thing really amazes me at times. I’m regularly left shocked at the serendipitous connections that form when writing posts. Take today’s post. I did a web search […]
Completing an OSS design, going inside, going outside, going Navy SEAL
Our most recent post last week discussed the research organisations like DARPA (Defense Advanced Research Projects Agency) and Google are investing into group flow for the purpose of group effectiveness. It cites the cost of training ($4.25m) each elite Navy SEAL and their ability to operate as if choreographed in high pressure / noise environments. […]
Stealing Fire for OSS (part 2)
Yesterday’s post talked about the difference between “flow state” and “office state” in relation to OSS delivery. It referenced a book I’m currently reading called Stealing Fire. The post mainly focused on how the interruptions of “office state” actually inhibit our productivity, learning and ability to think laterally on our OSS. But that got me […]
The great OSS squeeeeeeze
TM Forum’s Open Digital Architecture (ODA) White Paper begins with the following statement: Telecoms is at a crucial turning point. The last decade has dealt a series of punishing blows to an industry that had previously enjoyed enviable growth for more than 20 years. Services that once returned high margins are being reduced to commodities […]
Step-by-step guide to build a systematic root-cause analysis (RCA) pipeline
Fault / Alarm management tools have lots of strings to their functionality bows to help operators focus in on the target/s that matter most. ITU-T’s recommendation X.733 provided an early framework and common model for classification of alarms. This allowed OSS vendors to build a standardised set of filters (eg severity, probable cause, etc). ITU-T’s […]
OSS change…. but not too much… oh no…..
Let me start today with a question: Does your future OSS/BSS need to be drastically different to what it is today? Please leave me a comment below, answering yes or no. I’m going to take a guess that most OSS/BSS experts will answer yes to this question, that our future OSS/BSS will change significantly. It’s […]
In an OSS, what are O2A, T2R, U2C, P2O and DBA?
Let’s start with the last one first – DBA. In the context of OSS/BSS, DBA has multiple meanings but I think the most relevant is Death By Acronym (don’t worry all you Database Administrators out there, I haven’t forgotten about you). Our industry is awash with TLAs (Three-Letter Acronyms) that lead to DBA. Having said […]
Two concepts to help ease long-standing OSS problems
There’s a famous Zig Ziglar quote that goes something like, “You can have everything in life you want, if you will just help enough other people get what they want.” You could safely assume that this was written for the individual reader, but there is some truth in it within the OSS context too. For […]
Auto-releasing chaos monkeys to harden your network (CT/IR)
In earlier posts, we’ve talked about using Netflix’s chaos monkey approach as a way of getting to Zero Touch Assurance (ZTA). The chaos monkeys intentionally trigger faults in the network as a means of ensuring resilience. Not just for known degradation / outage events, but to unknown events too. I’d like to introduce the concept […]