Telecom Pack is a business accelerator for Telecom domain. It provides assets that showcase the integrated capabilities of Business and IT. The assets which are part of Business Process Manager (BPM) Telecom Pack are templates which can be used as-is or extended based on the business requirements.
Some of the assets are based on Telecom standards NGOSS based SID, MTOSI and eTOM and IBM best practices in the Telecom industry. These assets saves the pre-modeling and modeling phase and are ready for the integration or assemble phase and hence a business accelerator.
The artifacts in the assets have a familiar name based on standards thus providing the easier identification of the artifacts to be used for SOA solution development.
Every asset has its own contribution in the development phase. Following are the different assets based on Telecom standards and IBM best practices alongwith their role in the SOA solution development.
The Capability model is based on eTOM Process Framework and IBM best practices. This asset provides the decomposition of Telecom domain into Capabilities and Processes. Capability model is needed before the start of any SOA based Telecom application development. The capability model provides the Process framework to use the Business processes of interest. These business processes are further drilled down and the lowest level such as level 3 are then implemented with set of activities. These activities require Service Model (asset of BPM Telecom Pack) to define the technical specifications of itself. The identified business processes of interest are realized further into the Process Model (asset of Telecom pack)
The Process model constitutes of Process flows which are aligned with different levels of business processes in the Capability Model. A BPD defines the process workflow for users, creates logic inside a process, and integrates with other applications and data sources. The process acts as a container for all the components of a process definition, which includes participant groups, lanes, services, activities, gateways, sequence lines, rules, and variables.
The process flows are grouped as per the subject areas based on Telecom domain. The subject areas such as Fulfillment, Assurance and Billing have the different process flows related to the individual subject areas. Example: Order Handling belongs to Fulfillment subject area. Hence the process flows relevant to Order Handling are found in Fulfillment toolkits. The process flows requires Service Model to define the activities involve to accomplish the business goal of the process flow.
The Telecom Process Models are modeled as Business Process Definitions (BPDs) inside the IBM® Process Designer.
The Service model is the data model of the BPM Telecom Pack. The operations (Service interfaces) and the schemas based on the NGOSS based SID, MTOSI and OSSJ are available in the Service Model. The Service model is group as per the subject areas and functional areas based on the Telecom domain.
The schemas are grouped as per the Subject areas.
Example: All the schemas pertaining to Fulfillment subject areas are found in SIDFulfillment SCA library (IBM integration Designer is used to work with this asset)
The Service interfaces are grouped as per the Functional areas which are also the Aggregate Business Entities like Customer, Service, Resource, and Product and so on. So ProductFulfillment SCA library will have all the Service interfaces belonging to the Product related functional areas and Fulfillment subject areas.
This decomposition of Service model into Functional and Subject areas helps the identification process easier while developing the SOA solution.
The service models are packaged as SCA libraries which can be viewed in the IBM® Integration Designer.
Business Object Model
After creating Process templates and mapping the process activities to the service interfaces the next thing needed is persisting the data used in the process-flows. This data can be used as information in reports and other processes. The Business object model provides a conceptual data model which can be viewed using IBM Rational® Software Architect. The Business object model is based on the SID domain model and IBM best practices.
The SID model provides the Telecom industry with a common vocabulary, set of information, data definitions, and relationships used in the definition of NGOSS architectures.
The Business object model can be used to further extend based on business needs and generates a Logical data model which forms as a base for the Physical data model of a Telecom application.
A Business Vocabulary is a collection of business concepts, terms, and data definitions. These are collectively used to ease collaboration between the business and Information Technology (IT) users. Some of these Business Items are mapped to a Business Object (data type) from the Industry Schema (SCA library from Service models asset) and contains a set of aliases. Aliases are used to describe properties of the underlying data type in the best business user accessible format.
An Alias is a simple name that can be used to point to properties or attributes that are in the technical data type format. Aliases consist of a simple name, type, and an associated Xpath expression based on the referenced Business Object
The Business Vocabulary provided for a domain can be used as-is or can be extended based on business requirements. The predefined Business Items and aliases are used to define a set of common Xpath expressions, which can be used within a solutions library.
The Telecom Common Components includes a set of Telecom-specific common service definitions and implementations. The common services help achieve component reuse and serve as accelerators for BPM solutions, where you can use the provided implementations or customize their configurations to suit your application needs. The Common Components are based on the TM Forum's Solution Frameworks (NGOSS) Information Framework (SID), MTOSI, NGOSS OSS/J standards, and IBM best practices. The Rule Engine common services can be configured to work with different Rule engines such as a JSR94-complaint rules engine or IBM® WebSphere Transformation Extender.
These assets are packaged as SCA Modules that can be imported within IBM® Integration Designer and then deployed onto the IBM Process Server runtime.
Solution Scenarios for the Business Process Manager Telecom Pack demonstrate the capabilities of assets in developing an end-to-end Business Process Management (BPM) solution based on a set of real-life scenarios that are considered common within the telecom industry. Examples of the Telecom Solution Scenario include Order Handling and Incident Problem Management.
The Telecom provider can use the Order Handling Solution Scenario to demonstrate the process of checking whether a customer order can be provisioned for a product that is ordered. A Customer Service Representative can execute the Order Handling Solution Scenario by logging in, initiating a request, providing details using forms, and submitting the data for processing. A Business Manager can view and analyze information using the various graphs and diagrams displayed in the generated reports and scoreboards.
The Telecom provider can use the Incident and Problem Management Solution Scenario to demonstrate the key process steps such as Detect, Enrich, Diagnose, Fix, Verify, and Close. These steps are streamlined using automation and orchestration methods in the business process. A Customer Service Representative can execute the Incident and Problem Management Solution Scenario by logging in, creating a trouble ticket for a customer or network-related problem, providing details using forms, and submitting the data for processing. After the problem is resolved, the Customer Service Representative can verify and close the trouble ticket.