Some time back, we discussed A modern twist on OSS architecture that is underpinned by a common data model. Time to discuss this a little more visually. As the blue boxes on the left side of the diagram below show, you may have many different data sources (some master, some slaved). You may have a single OSS tool (monolithic solution) or you may have…
Read More »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 introduces some fairly big changes from an OSS perspective. As usual…
Read More »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 to share a trick I've used in the past when I've…
Read More »We recently discussed the differences between PNI (Physical Network Inventory) and LNI (Logical Network Inventory) solutions that appear as part of many OSS (Operational Support System) stacks. As promised, today we'll talk about the subtle differences between: Network Inventory Management Systems Asset Management Systems and Configuration Management Databases (CMDB) We even discuss: Virtual Infrastructure (VIM) and Resource Managers Config Managers (different from CMDB) TM Forum's four…
Read More »"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. Yet it's not like most declining industries. Telecom services and remote…
Read More »Hello, Trouble. It's been a while since we last met. But I know you're still out there. And I have a feeling you're looking for me. You wish I'd forget ya.. Don't ya trouble? Perhaps it is you, that has forgotten me. Perhaps I need to come find you. Remind you, who I am. Sounds like an apt mindset for working in the OSS industry doesn't…
Read More »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 patterns like this? Workflow based? Autonomous? (Going to far into chaos…
Read More »After reading other recent posts such as "Orders Down, Faults Up" and "How is OSS/BSS service and resource availability supposed to work?" an avid reader of the PAOSS blog posed the following brilliant question: "Do you have any thoughts on geospatial vs non geospatial network inventory systems? How often do you see physical plant mapping in a separate system from network inventory, with linkages or integrations…
Read More »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 powerful for communicating with other data experts and delivery teams. It's…
Read More »We're excited to announce the release of some new functionality on The Blue Book OSS/BSS Vendor Directory (which now hosts nearly 450 different OSS/BSS supplier listings). We've introduced: An Industry News feed If you wish to publish news / press-releases on products, contract wins, changes in ownership structure, job advertisements, tradeshow attendance or any other related news, you can click here to create a news item (note that…
Read More »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 of this article]. OSS/BSS Data Flows I also think of inventory…
Read More »Back in the old days, there was really only one OSS build model - via big milestone/functionality delivery. You followed a waterfall style delivery where you designed the end-solution up-front, then tried to build, test and handover to that design. The business value was delivered at the end of the project (or perhaps major phases along the way). For the large operators, there may have been…
Read More »Further to yesterday’s post about Service and Resource Availability, I received some questions about how to discern between CFS (Customer Facing Services) and RFS (Resource Facing Services) in relation to Fulfillment workflows. Then more specifically, how they relate to Service Order (SO), Service Order Manager (SOM), Product Catalog and Service Catalog solutions. Then finally how they relate to the orchestration or decomposition process. I thought the following diagram,…
Read More »The brilliant question above was asked by a contact who is about to embark on a large OSS/BSS transformation. That's certainly a challenging question to start the new year with!! The following was provided for a little more context: We have a manually maintained table for each address where we can store which services are available—ie. DSL up to 5 Mbps or Fiber Data 300 Mbps…
Read More »Last year a tier-1 telco asked me to develop a training / mentoring plan for graduates entering their OSS stream. Not just a short-term training plan, but a 4-5 year career development model for their team. They're setting aside approximately a day a week for personal development for each trainee entering the program. That blew me away. I was so impressed that they were willing to…
Read More »Huh? But they're just cost centres aren't they? Nope, they sell financial outcomes - they reduce downtime, they turn on revenue, they improve productivity by coordinating the workforce, etc... But they only "sell money" if they can help stakeholders clearly see the money! I mean "actually" see it, not "read between the lines" see it! (so many benefits of OSS are intangible, so we…
Read More »May I ask you a question? Do the senior executives at your organisation ever USE your OSS/BSS? I'd love to hear your answer. My guess is that few, if any, do. Not directly anyway. They may depend on reports whose data comes from our OSS, but is that all? Execs are ultimately responsible for signing off large budget allocations (in CAPEX and OPEX) for our OSS.…
Read More »ETSI Open Source MANO unveils Release SEVEN, enables more than 20,000 cloud-native applications for NFV environments! The ETSI Open Source MANO group is pleased to unveil its latest release, OSM Release SEVEN. This release brings cloud-native applications to NFV deployments, enabling OSM to on-board over 20,000 pre-existing production-ready Kubernetes applications, with no need of any translation or repackaging. OSM release SEVEN allows you to combine within…
Read More »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, etc. But it doesn't show the total score for each team…
Read More »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 (directly) managing objectives such as: Sign up an extra 50,000 customers…
Read More »OSS tend to be very technical and transactional in nature. For example, a critical alarm happens, so we have to coordinate remedial actions as soon as possible. Or, a new customer has requested service so we have to coordinate the workforce to implement certain tasks in the physical and logical/virtual world. When you spend so much of your time solving transactional / tactical problems, you tend…
Read More »