We can also teach an extended 5-day version of the course that includes additional case studies and discussion to help you apply the BPM tools and techniques to your own operating environment. If you are familiar with some aspects of this training course, we can omit or shorten their discussion. We can adjust the emphasis placed on the various topics or build the Frameworx: eTOM, SID and TAM Training around the mix of technologies of interest to you including technologies other than those included in this outline. If your background is nontechnical, we can exclude the more technical topics, include the topics that may be of special interest to you e.
|Published (Last):||5 June 2004|
|PDF File Size:||5.99 Mb|
|ePub File Size:||11.39 Mb|
|Price:||Free* [*Free Regsitration Required]|
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 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.
When initially released in , 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.
Frameworx is based around these key principles. 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. 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. 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. 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 ] Main article: Loose coupling "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.
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.
But imagine the difficulty that would occur if the ordering application worked on products that consists of bundles of sub-products e. 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. Common communications infrastructure[ edit ] Through the mids, computer-based OSSs were developed as stand-alone applications.
However, during the early s it became apparent that employing these as purely isolated applications was highly inefficient, since it led to a situation where, for example, orders would be taken on one system but the details would then need to be re-keyed into another in order to configure the relevant network equipment. Major efficiency gains were shown to be available from linking the standalone OSSs together, to allow such features as "Flow-through provisioning", where an order could be placed online and automatically result in equipment being provisioned, without any human intervention.
However, for large operators with many hundreds of separate OSSs, the proliferation of interfaces became a serious problem. Each OSS needed to "talk to" many others, leading to the number of interfaces increasing with the square of the number of OSSs. In this way, each application only requires one interface to the CCI rather than many to other applications.
The complexity is therefore reduced to one of order n, rather than n2. The CCI may also provide other services, including security, data translation, etc. The Frameworx contract specification provides a means to document these interfaces, and these are therefore contract defined interfaces.
Business Process Framework (eTOM)
It enables you to assess and optimize performance using a proven, service-oriented approach to operations and integration. The practical tools available in Frameworx help improve end-to-end management of services across complex, multi-partner environments. It is a comprehensive, industry-agreed, multi-layered view of the key business processes required to run an efficient, effective and agile digital enterprise. SID a. It provides standard definitions for all the information that flows through the enterprise and between service providers and their business partners. TAM a. It provides a common language and means of identification for buyers and suppliers across all software application areas.
GB921 Business Process Framework (eTOM) R17.0.1