Technical Description
The Application Framework provides a common language to the various communities who specify, procure, design, and sell operation and business support systems, so that they can understand each other's viewpoints.
The Application Framework is a practical, everyday working guide to position and navigate the complex landscape faced by organizations that buy, sell, or outsource management systems. It is not intended to be prescriptive or mandatory, however, it does provide a ‘lens’ to compare current implementations with an idealized approach.
In order to be included in the Framework, there must be at least two commercially available products that provide that functionality. This requirement keeps the Application Framework grounded in the day-to-day realities facing Service Providers.
Wherever possible, the Application Framework uses language already common in the industry and builds on TM Forum Frameworx particularly the Business Process Framework (eTOM) and the Information Framework (SID). The Application Framework uses identical layering concepts as the Business Process and Information Frameworks. It also recognizes managed resources, including network-based resources, content servers, Intelligent Network platforms, and related network control technologies (such as element management systems), as well as the management applications infrastructure fabric (e.g., bus technology or business process management engines).
Note that the purpose and nature of the Application Framework is to focus on how the business requirements captured in the Business Process Framework and the Information Framework are translated into a solution design that can be visualized as applications that are built or procured by the enterprise. It therefore provides a different perspective from the process view or information view in these other frameworks, and allows a company to advance their insight into the system design and implementation aspects of their management solutions.

Click here for a larger version
The high level view of the Application Framework is shown in the diagram above. It is divided into seven horizontal layers—consistent with the Information Framework (SID). It is also divided into four vertical columns—consistent with the Business Process Framework (eTOM). Each box on the map represents a level 1 real Application such as Customer Order Management or Bill Calculation.
The Applications Framework can be further decomposed into “lower levels” of functionality. In the example below, ‘Corporate Sales Management” is a level 1 application and the applications in the boxes are at level 2.

Each of these ‘level 2’ applications can, in turn, be decomposed further into even smaller ‘level 3’ applications. The complete listing of all available decompositions can be found in the Application Framework document (Document Number: GB929).
Rationalization Example
One of the prime benefits of using the framework is the ability to identify and document the key attributes associated with each application, which then enables Service Providers to understand fully the functionality they already have within their organization. Examples of information and attributes that the Service Provider could include are:
- Owned applications and modules—as defined in the Framework
- Additional functionality that could be bought by extending the application (as opposed to buying another one)
- License costs; maintenance contracts and costs
- Quality of documentation
- Any legal issues, such as data protection
- Owner, users
- Interfacing applications
- Business Services (NGOSS contracts) supported
- Business processes (eTOM) covered
- Information (SID) entities impacted
- Management issues
- Policy rules
This information enables the Service Provider to assess the viability/desirability of rationalizing their applications. With this evaluation of applications, the Service Provider has the information to make an informed choice. Additionally, when armed with this information the Service Provider can map applications to functionality—actual or available:
And subsequently, for each application, some basic questions can be posed to better assess the impact of change on the business. Example of questions include:
- Are the applications centrally based or dispersed?
- To what degree have the applications been customized, either in their use or the user interface?
- What software level is in use?
- Is it the same level across the Business Unit?
- How is the application supported—in house or under contract(s)?
- What Service Level Agreements are in place?
- Are the naming conventions the same?
Once functional gaps and overlays are identified, and an impact assessment completed, more work can be done to implement the changes, for example by prioritizing the results of the rationalization process into a work program. Then if systems will be purchased, Procurement can create their requirements and master plan based on the Application Framework map.
Of course using the Framework for cataloging functionality with a view to application rationalization is not the only benefit. Additional ways to take advantage of the Application Framework are below.
Using the Framework
The key uses of the Application Framework include:
- Procurement: Service Providers can use it across the entire procurement process—from initial request for information, through systems comparison, to guidance for implementation.
- Product Positioning: It helps Suppliers position which systems they supply themselves (see TM Forum's Product and Services Directory) and which they supply through partnerships with other companies.
- Streamlining IT/Operation Systems: It provides a map to rationalize and combine application stovepipes across multiple technologies and services (e.g., mobile or fixed)
- Mergers and Acquisitions: It provides a common vocabulary and structure against which merging organizations can map their systems.
- Outsourcing: The Framework can be used to define precisely the boundaries between interfacing applications, allowing more effective outsourcing of key functions.
- Cloud Implementation: By identifying typical application interactions, the Application Framework can help companies that are implementing an application in the Cloud environment assure they have considered the impacts to interfacing systems.
TM Forum members are encouraged to register their products and services in the Product and Services Directory, which uses the Application Framework as the reference for its categorization.
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) that give you an accurate assessment of your project’s success.
Go back to the Application Framework Overview page or read about how the Application Framework is integrated with TM Forum Frameworx.