Blogs

Filter by Date Period

Select Date
Filter by Date Range
Filter by Date Range

Filter by Category

Filter by Category

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 the supplier. They obviously have the greater know-how from building and…

Read More »

OSS user heat-mapping

Over the many OSS implementation projects I've worked on, UI/UX (user interface / user experience) has been an afterthought (if even thought about at all). I know there are OSS UI/UX experts out there (I've met a handful), but none have ever been assigned to the projects I've worked on unfortunately. UI has always just been the domain of the developer. If the functionality worked (even…

Read More »

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 to lead the technical implementation and guide the client through any…

Read More »

A modern twist on OSS architecture

I was speaking with a friend today about an old OSS assurance product that is undergoing a refresh and investment after years of stagnation. He indicated that it was to come with about 20 out of the box adaptors for data collection. I found that interesting because it was replacing a product that probably had in excess of 100 adaptors. Seemed like a major backward step...…

Read More »

I’m really excited by a just-finished OSS analysis (part 3)

This is the third part of a series describing a really exciting analysis I've just finished. Part 1 described how we can turn simple log files into a Sankey diagram that shows real-life process flows (not just a theoretical diagram drawn by BAs and SMEs), like below: Part 2 described how the logs are broken down into a design tree and how we can assign weightings…

Read More »

I’m really excited by a just-finished OSS analysis (part 2)

As the title suggests, this is the second part in a series describing a process flow visualisation, optimisation and decision support methodology that uses simple log data as input. Yesterday's post, part 1 in the series, showed the visualisation aspect in the form of a Sankey flow diagram. This visualisation is exciting because it shows how your processes are actually flowing (or not), as opposed to…

Read More »

I’m really excited by a just-finished OSS analysis

In your travels, I don't suppose you've ever come across anyone having challenges to capture and/or optimise their as-is OSS/BSS process flows? Once or twice?? :) Well I've just completed an analysis that I'm really excited about. It's something I've been thinking about for some time, but have just finished proving on the weekend. I thought it might have relevance to you too. It quickly helps…

Read More »

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 I've had to ponder is whether they're necessarily complex. As the…

Read More »

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 few years, OSS choice has proliferated, making project assessment more challenging?…

Read More »

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 these clients, and it comes from both sides. What is that…

Read More »

Can you solve the omni-channel identity conundrum for OSS/BSS?

For most end-customers, the OSS/BSS we create are merely back-office systems that they never see. The closest they get are the customer portals that they interact with to drive workflows through our OSS/BSS. And yet, our OSS/BSS still have a big part to play in customer experience. In times where customers can readily substitute one carrier for another, customer service has become a key differentiator for…

Read More »

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 using our OSS actually need constant availability (ie to be constantly…

Read More »

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 looking for the thread of an idea that had no relation…

Read More »

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. We contrasted this with the mechanisms used in most OSS that…

Read More »

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 thinking that perhaps flow doesn't just relate to OSS project delivery.…

Read More »

Stealing fire for OSS

I've recently started reading a book called Stealing Fire: How Silicon Valley, the Navy SEALs, and Maverick Scientists Are Revolutionizing the Way We Live and Work. To completely over-generalise the subject matter, it's about finding optimal performance states, aka finding flow. Not the normal topic of conversation for here on the PAOSS blog!! However, the book's content has helped to make the link between flow and…

Read More »

ONAP’s fourth release, Dublin, now available

ONAP Doubles-Down on Deployments, Drives Commercial Activity Across Open Source Networking Stack with ‘Dublin’ Release. ONAP’s fourth release, Dublin, brings an uptick in commercial activity –  including new deployment plans from major operators (including Deutsche Telekom, KDDI, Swisscom, Telecom Italia, and Telstra) and ONAP-based products and solutions from more than a dozen leading vendors – and has become the focal point for industry alignment around management…

Read More »

Lightning strikes in OSS

Operators have developed many unique understandings of what impacts the health of their networks. For example, mobile operators know that they have faster maintenance cycles in coastal areas than they do in warm, dry areas (yes, due to rust). Other operators have a high percentage of faults that are power-related. Others are impacted by failures caused by lightning strikes. Near-real-time weather pattern and lightning strike data…

Read More »

282 million reasons for increased OSS/BSS scrutiny

"The hotel group Marriott International has been told by the UK Information Commissioner's Office that it will be fined a little over £99 million (A$178 million) over a data breach that occurred in December last year... This is the second fine for data breaches announced by the ICO on successive days. On Monday, it said British Airways would be fined £183.39 million (A$329.1 million) for a…

Read More »

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 in the digital world, and our insatiable appetite for data demands…

Read More »

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 recommendation M.3703 then provided a set of guiding use cases for…

Read More »