TM Forum Applications Framework (TAM)

Standardizing the OSS/BSS Systems Landscape

The Applications Framework defines the functionality common in OSS and BSS applications, thus enabling a more modular approach to applications development to evolve. The functional decomposition enabled by the Applications Framework breaks applications down into individual components, without bogging Service Suppliers and other purchasers down with esoteric rules. Because the Applications Framework maps to the TM Forum Business Process Framework (commonly known as the eTOM), Service Providers, ISVs and other purchasers improve communication and expedite the implementation of applications. That helps to create an environment in which services can be deployed or evolved more rapidly.

executes and accomplishes. By breaking applications down into bite-size pieces, all members of the value chain share a common language and syntax to mitigate misinterpretations of outwardly similar functionality. In fostering better communication among all partners, and in allowing for the exchange of information among applications, the Application Framework reduces the risks inherent in purchasing and integrating new applications. It helps to streamline the entire procurement processfrom the initial request for information, through systems comparison, to actual implementation. That helps purchasers to procure from a standard applications model, and to ultimately drive standardization industry-wide. Systems Rationalization Mergers, acquisitions and streamlining of operations are common events. Each introduces the need to examine the operational and business support systems in order to discover: Duplicate functionality; Which outwardly similar applications are best-suited for supporting business needs; Functional gaps and how to reflect them in procurement documents. The Applications Framework is an effective tool for answering to those needs, as it maps existing OSS/BSS environments in such a way that functional overlaps and gaps are more readily discovered. The Benefits: System support costs are reduced; Support and other training costs are reduced; Re-use is more common and lowers custom-development and license costs. Procedures can be rationalized the framework is mapped to the eTOM process Framework System management costs can be reduced Space can be freed in servers and physically in computer rooms

By providing a structure around which OSS/BSS application functionality can be defined, the Applications Framework empowers Service Providers and their partners to: Procure documents for applications with clear, concise language about required functionality; Discover functional overlaps of existing applications to be identified, thereby facilitating rationalization; Discover functional gaps. Why use the Applications Framework? There are a number of benefits to the industry in using a common applications framework: Common Application Language Using the Applications Framework, application vendors and purchasers can reach a common understanding of what an application actually

Standard Application Requirements A key deliverable is an industry set of standard application requirements, which will facilitate the development of reusable components and a more modular approach to application development. This reuse will result in lower costs through economies of scale. The component approach also will encourage the adoption and development of standard interfaces among components, further reducing development costs. Automation Enablement The standard, deployable components that result from the adoption of the Applications Framework will create a higher degree of automation within the purchasers businesses. That, in turn, reduces human errors and improves operational efficiencies. With solutions based on this standard Applications Framework, it will be easier for organizations to add or change out components within their support systems.

Developing the Applications Framework The Applications Framework has been developed from a deployment- or implementation viewpoint. That means it identifies a common denominator in terms of what systems typically exist across all CSP environments, thus helping various communities to specify, procure, design and sell OSSs and BSSs. Wherever possible, the Applications Framework uses language already common in the industry and builds on the Business Process Framework (eTOM) and Shared Information/Data Model (the SID)both of which are critical to the TM Forum's New-Generation Operations Systems (NGOSS). The Applications Framework has been designed to be generic without losing touch with the industry realities to which people are accustomed. Therefore, the Applications Framework uses familiar layering concepts, including the Business Process Framework and Shared Information/Data Model, which complement one another to describe the principal functions of each layer and each system. Using the Applications Framework The Applications Frameworks common implementation-oriented nomenclature is useful for a variety of functions and allows the entire telecom value chain to have a common frame of reference in describing both current and future needs and intentions. Who Should Use The Applications Framework? An operator could use the Applications Framework to model its current OSS applications in a structured format, as well as for development of a future model that engenders clear gap analysis. Suppliers may use the framework to highlight the systems that they supply, and the systems they develop through partnership with other companies. The Applications Framework may be used to show both current and future portfolios. A Systems Integrator can highlight its areas of expertise and its past work. Investors or Financial Analysts may find the Applications Framework useful to describing the OSS market in terms of its growth and value. Analysts or the Media will find the Applications Framework useful for classifying suppliers in each segment of the market.

Inside the Applications Framework The Telecom Applications Map R2.1 (see Figure 1, left) is segmented by the primary Business Process Framework area of Fulfillment, Assurance, and Billing functions, along with the layering of processes, including: Market/Sales Process, Product Process, Customer Relationship Management processes, Service Management Process, Resource Management and Operations processes, Supplier Partner Process, Enterprise Management Process and the Integration Infrastructure Process. The Applications Framework also recognizes managed resources, including network-based resources, content servers, intelligent network platforms, and related network control technologies (i.e., element management systems, and OSS/BSS infrastructure such as bus technology and business process management engines). The Applications Framework is used to describe the primary functions and roles of each of the layers of the map, and each of the main segments. The main segments are then broken down into sub-segments, where additional clarity is realized. For each segment, the Applications Framework identifies the key workflows and associated data entities for support of applications.

(The diagram of Capacity and Forecasting Apps (above) shows the workflows and key data entities for Resource Performance Monitoring/Management applications). For further information on the Applications Framework, please visit www.tmforum.org or email us at info@tmforum.org.