Frequently Asked Questions
- a slow, error-prone sales process with a 95% drop rate for offered quotes
- a lack of agility that limits sales due to the manual nature of the process
- low conversion to sales and high customer acquisition costs
- a lack of simplification and automation opportunities for product offerings
MEF has defined a Lifecycle Service Orchestration (LSO) reference architecture and framework, published as the MEF 55 standard. LSO defines an agile approach to streamlining and automating the lifecycle of end-to-end connectivity services, such as Carrier Ethernet services. The architecture defines functional management entities and their interface reference points. The reference points are further defined by sets of Application Programming Interfaces (APIs) to characterize interactions between the functional management entities.
These interfaces are divided into two types: north-south interfaces and east-west interfaces. North-south interfaces are generally contained within a single Operator management domain and represent the flow of information and operations between higher layer Business Support Systems (BSSs) and lower layer network elements and network functions. Think of information that flows up and down a management stack. On the other hand, east-west interfaces are generally distributed across Operator domains. For example, Business Support Systems across multiple Operator domains can communicate across an east-west interface. Think of information that flows left or right towards the equivalent management functional entity in a different Operator's management domain.
The MEF LSO reference architecture and framework defines both north-south and east-west interfaces. The east-west interface at the Business Support layer is named the Sonata interface and supports management and operations interactions between network providers for business functions such as quoting, ordering, billing, and trouble management. Cataworx implements the Sonata east-west interface for business functions including quoting. For example, multiple instances of the Cataworx Catalog, deployed into two different Operator domains, exchange management and operations information via a set of east-west APIs. In effect, one Cataworx Catalog can query another Cataworx Catalog.
- Are there Product Offerings your partners search often that you don't offer?
- Are there Product Offerings you have that no partner ever searches?
- What Product configurations are the most/least popular?
We’re happy to answer any other questions you may have personally, just contact us here.