Why use SID
OSS / BSS is a comprehensive support system for telecom operators to address enterprises to manage automation, information, and improve product sales (business) and customer service quality. Its development can be roughly divided into network elements and network management, facing business management, and managing three development phases. At this stage, the OSS system is based on the NGOSS (New Generation Operation System and Software), which describes the OSS system from the business, system, implementation, and running four viewpoints, and these four viewpoints correspond to each stage of the OSS system. At this time, the OSS system not only covers the meaning of BSS, but the primary feature is customer-centered, so this system is often referred to as OSS / BSS.
NGOSS provides a complete set of methodology to guide the design and establishment of OSS / BSS. Its core design idea is to use "process driver". When designing system design, the core business process of our company will start, analyze the core business process; then through analysis process Refine the critical data, use the shared information model to abstract, divided into different management domains to establish a shared data model; finally set up the actual OSS / BSS system based on the shared data model. Data is the most important feature in OSS / BSS design, and the key to establish an OSS / BSS system is a good shared information model. Therefore, NGOSS provides a universal framework of shared information model - SID.
SID model analysis
SID is a general framework for establishing a shared information model proposed by NGOSS, and SID describes shared information models from both commercial and system two viewpoints. On the one hand, SID starts from commercial viewpoints, based on the business processing model defined by ETOM Level 0, according to the abstraction and analysis of various commercial information involved in the business process, various conjugated commercial entities ABE and each Commercial entity be, divided into different management domains, forming systems and infographics SIM, thus maximizing information and data sharing. On the other hand, the SID is defined from the viewpoint of forming an OSS system, and the properties of various commercial entities are defined, and they are organically combined with them to form a UML model to form a sharing for the actual use of OSS systems. The data model provides a reference model. In summary, the SID is an organized collection of commercial and system entity definitions and UML models. The SIM and UML models are described below.
SIM model analysis
The SIM model reflects the design concept of the "business process driver" of the OSS system. Based on the ETOM business model, from the perspective of information sharing, four horizontal levels in the ETOM business model respectively define the corresponding conjunction with commercial entities. ABE and business entities, and divide them into different management domains, as shown below.
Chart 1 SIM model
Information field and condensed and commercial entity ABE
SIM analyzes the information of ETOM's market / sales, products and customers, services, resources, and suppliers / partners, and divides them into different information management domains, and then define ABE for each domain. And Be. The information involved in the level of market / sales, products, and customers is divided into three information fields of market / sales, products and customers, and briefly analyze the fields and corresponding ABEs below.
(1) Market / Sales
Market / Sales domain mainly includes various data operations and contractual operations required to achieve sales and marketing activities to achieve customer or potential customers. Thus, six ABEs: strategic product plans, market segments, market competition activities, competitors, sales channels, contract / guidance / prospects and sales statistics are defined for market / sales domain.
(2) Product domain
The product domain mainly includes various product cycle information and contracts and information operations related to product cycle. The product domain defines 6 ABE: Strategic Products Program, Product Code, Product Features, Product, Products Statistics and Product Performance.
(3) Customer domain
The customer domain mainly includes information and contractual operations related to the customer when you acquire product, as well as the contractual operation of the contractual operation of the company (the service provider) and the contractual operation when they get products, as well as the customer's ordered data and contractual operations. The customer domain defines 9 ABE: customers, customer interactions, customer orders, customer statistics, customer issues, customer SLA, customer bills, tariffs for customer bills, customer bill collection, and customer billing query. (4) Service domain
The service domain mainly defines ABE related to service specifications and service instances. The service domain reflects the implementation of the product, combining various products, and forms various services provided by customers. The service domain includes 9 ABE: service plan, service specifications, service ordering, service, service failure, service abort, service test, service quality, and service.
(5) Resource domain
The resource domain defines a variety of ABEs for managing networks and network technology. The purpose of the resource domain is to ensure that various network technologies can achieve various services. Resource domains define 17 ABE: Resource Plan, Physical Resource Specification, Physical Resources, Logical Resource Specification, Resource Ordering, Network Topology, Logic Network, Resource Fault, Resource Alarms, Substation, Resource Stop Repair, Resource Test, Resource Performance , Resource performance trends, resource traffic control, resource traffic, resource traffic trends, and resource usage.
(6) Supplier / partner domain
The supplier / partner domain mainly involves various information of suppliers / partners (S / P) and various contractual operations for suppliers / partners, as well as data and contractual operations related to S / P accounts. This domain defines 12 ABE: S / P programs, suppliers / partners, S / P interactions, S / P products, S / P order, S / P SLA, S / P problem, S / P statistics, S / P performance, S / P bill, S / P payment and S / P query.
(7) Public commercial domain
The public business domain defines some shared ABE, which does not belong to a particular domain, can be shared by other domains. These ABEs are the universal abstraction of commercial commercial entities, such as commercial interactions, as an abstraction of customer ordering and S / P SLA. The public business domain defines 5 shared ABEs: conferences, commercial interactions, locations, protocols and strategies.
Commercial entity
In addition to defining the SIM model, the SID has also defined a detailed definition of commercial entities involved in the ABEs in the SIM model. For example, customers ABE and customers in the client domain define commercial entities; ABEs provide ABE for product specifications for product domains to define commercial entities; commercial interaction ABEs and conference ABEs for public commercial domains define business entities. As shown below:
Chart 2 Business entity
UML model analysis
In addition to defining the SIM model, SID also defines the properties of the business entity and uses UML to combine them together, forming a UML model, thereby providing a reference model for the shared data model for implementing the actual use of the OSS system.
Problems in the construction of OSS / BSS system in China
The construction of the domestic enterprise OSS / BSS system is in the new and old alternating stage, from the early network, facing the business, facing the business, facing the customer.
Early company Early OSS / BSS is a static, relatively independent operational support system, which is mostly established in accordance with the needs of various departments of the company itself. Its main problem is that enterprises have multiple "island" systems, and there is no sharing of data between systems.
With the continuous change of business needs and the intensification of market competition, the early established OSS / BSS system has not adapted to the current market development, and companies have encountered the following problems in the current OSS / BSS system:
1. How to transform existing, old OSS / BSS systems, adapt to the current business development and market competition. When the system is transformed, there is mainly necessary to solve the following problems: multiple separate systems; automation of low degree of straight-through processes; highly functional overlapping chimneys type solutions for special business; repeated and limited data, data quality difference Multiple system platforms lead to integrated difficulties; high operating costs, etc .;
2. When establishing a new OSS / BSS system, how to establish a flexible, efficient OSS / BSS system, avoid problems in the old system, so that the OSS / BSS system is truly generated by enterprise management, information, and improve product sales (business ) Comprehensive support system for customer service quality. Domestic enterprise OSS / BSS system construction strategy
Based on the current status of the domestic enterprise OSS / BSS system construction, combined with the development of OSS / BSS technology, this paper proposes the following OSS / BSS system construction strategies:
1. When enterprises create a new OSS / BSS system, when the system logical architecture is designed, it should be based on the process, namely, from the analysis company's business and operations. When designing system physical architecture, it emphasizes data-centric to implement data sharing. That is to use the "process-driven" design concept to achieve data design, make full use of the SID model to achieve data sharing, implement system modularity and integration.
2. When the company is transformed, the data sharing is the key to the success of the OSS system. Enterprises use the SID model to develop a architecture to achieve unified management, and integrate multiple "island" systems to all systems.
Conclude
The OSS / BSS system is the basis for telecom enterprises to provide end-to-end businesses to various new business flexible support. In order to avoid multiple versions and multiple databases and avoid data in each subsystem, they must be based on process analysis results. Using the SID model, data is abstract and classified, divided into different management domains, and data sharing should be maximized when the management domain is divided, and the data cross-domain processing should be avoided.
