We recently were asked to contribute to the latest Pipeline Magazine Article: Why Comply? through Jesse Cryderman, Senior Editor. Thank you Jesse and Pipeline for this opportunity.
We responded to three questions which will be featured in three blogs:
The first question: How important is standards compliance for vendors and carriers operating in the BSS/OSS space?
"The TMF provides members the best practices and the Frameworx suite of standards proven to deliver success every step of the way. Therefore standards compliance is very important for both vendors and carriers. In order to succeed, we follow the TMF Frameworx best practices knowing already that most carriers follow these standards to some degree internally and they expect their suppliers to do the same. By following these standards, OSSera is able to understand the customer requirements and to design and implement products and solutions to better serve the carriers’ business needs, as defined by the Frameworx Business Process model.", Mingxia Zhang, CEO of OSSera, Inc. and OSSera China.
“Standards form the bridge for vendors and carriers to collaborate on best practices to improve efficiencies from planning, activating, operating, maintaining, and billing today’s complex services. Value-Added-Services can no longer just be managed in a silo and require not only a bottom-up and top-down perspective of their service but also a planning to operations unified view.”
“Standards provide a common language for software providers to communicate with carriers and other partner solution providers. Without this common language solutions become decoupled, overlap, and form redundant silos, which do not unify the end-to-end processes flow for true business transformation and automation.”, Andrew Lee, VP of Marketing, OSSera, Inc.
The problem is many have legacy software solutions, which worked in the 90’s when standards were simpler and the goal was to manage network resources efficiently. For example over a decade ago the focus was on Fault Management and Performance Management but now the focus is Service Impact, Service Quality, Service Specification, and Customer Experience. Very few can actually reach the customer and service level management requirements as they are overwhelmed with just focusing on a bottom-up strategy in gathering all the network related faults and metrics.
Once a service provider begins to go down the road of managing all messages and metrics from all resources it becomes overwhelming to any operations center to distinguish what is wrong.
“For example, Fault Management may tell you that a port on a card on a switch has failed but what services are impacted. Similarly a top-down Active Service Test solution may tell you that a service has failed but what do I fix and where is the root cause? How do I as an operator connect the dots?”
“Standards set the stage for business transformation to connect the dots. Standards define the necessary systems, organizations, and interactions necessary to make this happen. But then it is up to the vendors and carriers to execute on these standards to make it a reality in their business.”, Andrew Lee.
The OSSera approach enables the TeleManagement Forum’s (TMF) suite of business transformation standards. For example, OSSera’s solution combines Service Problem, Impact, and Quality Management into a unified framework to seamlessly monitor the service blueprints developed by service planners in a Unified Data Model. These service blueprints with both correlations and KPI/KQI’s are passed to Service Operation Center (SOC) stakeholders. The solution enables the SOC to:
- Identify customers and services potentially impacted due to changes in the network based upon KPI/KQI threshold crossings along with correlated service impacting events.
- Analyze problems impacting end-to-end services where users can drill-down to the originating KPI/KQI Threshold Crossing Alarms against a Node or Node Group.
- Monitor, analyze, and report the end-to-end service quality