What is special about OSSera?
We can look at multiple key differentiators with OSSera:
But fundamentally it is the Service Management approach. OSSera has a unique approach which is different from what others are saying in the market.
What are others saying?
By referencing the TMF eTOM we've simplified the map for the sake of discussion. Other traditional solutiions are represented below and positioned in black arrows:
- horizontally in the Resource Domain and Service Domain.
- vertically in the Strategy, Infrastructure, Product (SIP) and Operations business process domains.
What we see in the industry is a wide array of solutions that CSPs have already installed or can purchase from various OSS vendors. There are traditional bottom-up resource management products including:
- Fault Management
- Performance Management
- Probes and Agents
All provide some key functionality at the resource level. Some have extended up in the last decade into the Service Management domain but still have not connected the dots very well. Each is still a silo'd solution and it is very difficult to manage services end-to-end. Probes and Agents typically provide metrics at the end-user level (i.e.: mobile wireless smartphone, PC, or home IPTV service) valuable for Customer Experience Management yet may not provide the core end-to-end view into a complex service offering. Probes and Agents do provide a top-down approach to service management through the customer experience.
What is OSSera's Approach?
OSSera is less bottom-up or top-down but more
- left to right...
- SIP Planning to Operations.
- This focus is less managing every single resource and more every single service.
- The focus is less fault versus performance management to more service management
- Less Inventory Management but leveraging inventory data to create nodes, node groups, and network paths which are critical to a Service Sequence.
- Not just Service Impact but also Service Sequence and Service Topology first
OSSera enables SIP:
- Strategy - What Services are most important and have the greatest ARPU?
- Infrastructure - What nodes, node groups and network paths impact those Services?
- Product - What Service Sequence Diagrams and Topology Diagrams are required to model these complex services?
then OSSera enables Operations... both SIP and Operations in a Unified Data Model (UDM)
The OSSera approach involves a primary focus on the Service Management Domain and Service Planning tools. These rich Service Specification and Catalog planning tools allow a planner to create service impacting nodes, node groups, and network paths which are glued together with a Service Sequence, Topology, and Impact diagram for critical Customer-Facing and Network-Facing Services.
Then everything is modeled and stored in the Unified Data Model (UDM) connecting the points across all services.
Also the UDM is the glue between organizations from the SIP Planning teams to the Operational stakeholders. All service diagrams, node groups, nodes, and network paths are now accessible to the Operation teams with real-time alert status indicators. Real-time events, threshold crossing alarms, as well as KPI/KQI metrics are available to the Operational teams to determine Service Problem, Service Quality, and Service Impact Analysis.
This is the fundamental difference with OSSera's solution:
- Connecting the Dots across Service and Resource Management silos
- Connecting the Dots across SIP to Operational organizations
Download our latest Case Study where we are managing over 2000+ wireless and broadband services for the largest mobile service provider in Thailand.