Technical Description
A key part of TM Forum Frameworx, the Information Framework (also known as SID), provides an information reference model and a common vocabulary from a business perspective. The Information Framework scope covers all of the information required to implement business processes in a Service Provider’s operations based on the Business Process Framework (eTOM) processes.
The Information Framework focuses on what are called “business entity” definitions and associated attribute definitions. A business entity is a thing of interest to the business, such as customer, product, service, or network. Its attributes are facts that describe the entity. Together, the definitions provide a business-oriented perspective of the information and data that you need to run your organization. In short, the Information Framework provides the model that represents business concepts and their characteristics and relationships, described in an implementation independent manner.
Click here to view a larger version
To classify the data in a usable fashion, the framework is designed as a layered model, which partitions the shared information and data into eight domains. At the top layer (Level 1), each of the eight information domains is aligned with the Business Process Framework (eTOM). Within each domain there is a high degree of cohesion between the business entities; and between the domains, there is a loose coupling. This arrangement enables segmentation of the total business problem into manageable pieces and allows resources to be focused on a particular area of interest. In other words, for a particular business process that you are automating, you can identify the information within the Framework that is needed to support that process.
Within each domain, multiple business entities known as “Aggregate Business Entities” (ABEs) are defined. ABEs may contain smaller ABEs related to their respective areas. Each ABE contains finer-grained business entities and their associated attributes. As an example, the picture below shows level 2 ABEs identified within the Product domain (note that some domains are detailed down to Level 3).
The ABE content and structure within each domain are consistent and include the following categories:
- Strategy and Plan
- Managed Entity
- Managed Entity Specification
- Interaction
- Configuration
- Performance
- Test
- Trouble
- Price
- Usage
ITUT Recognition
In order to provide a single common framework to harmonize all information models across the industry, the Information Framework Product and Service domains have been adopted by the ITU and are included in the ITUT recommendation M.3190.
UML Diagram Example
The Information Framework definitions are available in a document and also modeled in a consolidated Unified Modeling Language (UML)-based model format for flexible use. The UML version of the Information Framework is supported by commercial tools for easy implementation. The detailed UML diagram shown below illustrates the level of detail available within the Information Framework and demonstrates that, while ABEs are groups of closely related entities, the entities contained within a domain and an ABE within a domain are naturally related to entities in other domains as well as their respective ABEs. The diagram shows how companies can model their data, their characteristics and relationships, and implement them in an independent manner.
More examples can be found in each domain-specific addendum of the Information Framework.
The Information Framework (SID) model is often used as the basis for database design, with implementation-related modifications made to it. Other uses of the Information Framework are described below.
Using the Framework
- Where an information model is to be developed as part of a project, the applicable Information Framework domains/ABEs are used as a starting point
- Where a project requires standards-based APIs, the Information Framework-based TM Forum Interfaces are used or if there are no existing interfaces the Information Framework is used as the basis to define interfaces
- Where a project involves integrating applications, the Information Framework-based interfaces are used along with the Information Framework’s use within the Frameworx Integration Framework rather than using a proprietary model
- Where a project requires an information architecture that is dynamic and extensible, such as for Product, Service, Resource Catalog applications, the Information Framework’s adaptability to changing requirements makes it the model of choice to use
- Where an organization wants a standards-based reference model, existing models are mapped to the Information Framework
- For developing service oriented applications, the Information Framework is used as the basis for the structuring of services (note: this is evidenced in the business service classification developed as part of the TM Forum Frameworx Integration Framework)
The Information Framework can be used as a standalone framework, or when used in combination with the Business Process Framework (eTOM) it creates a bridge between the business and the Information Technology (IT) groups by providing definitions that are understandable by the business, but are also rigorous enough to be used for software development.
Don’t forget to take advantage of our TM Forum Benchmarking program to provide you with before and after measurements (Key Performance Indicators or KPIs) to give you an accurate assessment of your project’s success.
Go back to the Information Framework Overview page or read about how the Business Process Framework is integrated with the TM Forum Frameworx.