Tmf Etom Poster
Etom Poster Creator
Etom Poster Design

Business Metrics Framework (ETOM) Poster Frameworx 14 - Free download as PDF File (.pdf), Text File (.txt) or view presentation slides online. Business Metrics Framework (ETOM) Poster Frameworx 14.
Join us at our Upcoming Conferences. View past conference information, including shared resources and recordings, at Past Conferences.

(Redirected from Information Framework (Frameworx))

Frameworx is an enterprise architecture framework geared towards communications service providers.

It is developed by the TM Forum.

Structure[edit]

Frameworx consists of four frameworks:

Application Framework (sometimes referred to as the Telecom Application Map (TAM))
Information Framework (sometimes referred to as the Shared Information/Data (SID) model)
Integration Frameworks (which is developed in the TM Forum Integration Program (TIP))

Frameworx (eTOM SID TAM) Metrics As service providers transition into digital service providers, the use of common metrics across the industry has become vitally important. The TM Forum metrics team, led by IBM, has published this latest Frameworx-aligned poster which speeds CSP metrics planning and capture. Inglorious Basterds poster - Bonjourno Brad Pitt, Aldo Raine, Inglorious Bastards, Quentin Tarantino print, wall art, man cave signs gifts QualityLootCom. From shop QualityLootCom. 5 out of 5 stars (1,597) 1,597 reviews $ 11.20. Favorite Add to.

Information Framework[edit]

The Information Framework (formally Shared Information/Data Model or SID) is a unified reference data model providing a single set of terms for business objects in telecommunications. The objective is to enable people in different departments, companies or geographical locations to use the same terms to describe the same real world objects, practices and relationships.It is part of Frameworx.

The Information Framework, as the Frameworx information model, provides an information/data reference model and a common information/data vocabulary from a business as well as a systems perspective. The Information Framework uses Unified Modeling Language to formalize the expression of the needs of a particular stakeholder viewpoint.

The Information Framework provides the common language for communicating the concerns of the four major groups of constituents (stakeholders) represented by the Frameworx Viewpoints - Business, System, Implementation and Deployment, as defined in the Frameworx Lifecycle. Used in combination with the Business Process Framework (eTOM) business process and activity descriptions and the Telecom Application Map the Information Framework make it possible to bridge between the business and Information Technology groups within an organization by providing definitions that are understandable by the business, but are also rigorous enough to be used for software development.

The Information Framework model takes inspiration from a wide variety of industry sources, but its principal origins are the Alliance Common Information Architecture (ACIA) created by a team led by Bill Brook from AT&T and BT Group and the Directory Enabled Networks - next generation (DEN-ng) model created by John Strassner.

When initially released in 2000, the Information Framework model covered the business (BSS) arena well, and also the device management field well, but was insufficient in its ability to represent logical networks and capacity. These deficiencies are being addressed through revision of the model to include concepts such as topologies, but the history has resulted in poor utilisation of the model in certain telecom fields, such as inventory management.

Principles[edit]

Frameworx is based around these key principles.

Separation of Business Process from Component Implementation[edit]

When Operations Support Systems (OSSs) are linked together, the business processes they support become distributed across the IT estate. In effect the situation is reached where a process starts with application A, which processes some data and then knows that it must call application B, which also does some processing and then calls C, etc. The result of this is that it's extremely difficult to understand where any of these flows actually are (e.g. if the process flow is one intended to take a customer order, is it Application A or B or C that’s currently handling that order?) and it's even more difficult to change the process owing to its distributed nature.

Frameworx proposes that the process is managed as part of the centralised infrastructure, using a workflow engine that is responsible for controlling the flow of the business process between the applications. Therefore, the workflow engine would initiate a process on application A, which would then return control to workflow engine, which would then call application B, and so on. In this way it's always possible to find out where an individual process flow is, since it is controlled by the central workflow engine, and process modifications can be made using the engine’s process definition tools. Clearly some lower level process flows will be embedded in the individual applications, but this should be below the level of business-significant processing (i.e. below the level at which business policy and rules are implemented). The Frameworx certification methodologies help us deal with the scope of preferences that are not linearly distributed as an opening to improve the customer accepted undeniably appropriate method.

Loosely Coupled Distributed System[edit]

'Loosely coupled' means that each application is relatively independent of the other applications in the overall system. Therefore, in a loosely coupled environment, one application can be altered without the alteration necessarily affecting others. Taken to extreme, this can sometimes be viewed as producing the ability to 'plug and play' applications, where they are so independent that they can be changed without affecting the overall system behaviour. That extreme is considered an unlikely nirvana at the present time.

The 'distributed system' is emphasising that Frameworx is not based on a Communication Service Provider (CSP) using a single monolithic application to manage all its activities, but is instead using a set of integrated and co-operating applications.

Shared Information Model[edit]

Integrating OSSs means that data must be shared between the applications. For this to be effective, either each application must understand how every other application understands/interprets that part of the data that is shared, or there must be a common model of the shared data. To understand this, consider an order handling application which has gone through a process to enter a customer order and where it now needs to send out a bill using application B (a billing system). Application A will have a record of the customer address and it therefore needs to ensure that application B sends the bill to this address. Passing this data between the systems simply requires a common format for the address information – each system needs to expect the same number of address lines, with each line being the same length. That’s fairly straightforward. But imagine the difficulty that would occur if the ordering application worked on products that consists of bundles of sub-products (e.g. a broadband access product made from a copper line, a modem, a set of filters and a broadband conversion), whereas the billing application only expected single product/order lines. Trying to convert hierarchical products into non-hierarchical ones without losing information would not be possible. A single information model for data that is shared between applications in this way provides a solution to this problem. The TMF solution to this is called the Shared Information/Data-Model (SID).

Common communications infrastructure[edit]

Through the mid-1980s, computer-based OSSs were developed as stand-alone applications. However, during the early 1990s it became apparent that employing these as purely isolated applications was highly

Etom Poster