- Make sure this fits by entering your model number.; 45L capacity - Fits 9 slices of toast on 2 racks for a total of 18 slices and roasts up to a 20lb turkey. Four rack positions fit up to 2 x 14' pizzas with interior dimensions of 16-3/8 W x 15-7/8 D x 8-1/2 H (upper element to rack at bottom position).
- 032216eTOMPosterv155 - Free download as PDF File (.pdf), Text File (.txt) or view presentation slides online. ETOM poster by TM Forum.
Of all the OSS standards available you will probably come across TM Forum’s eTOM and TAM most often. The problem is no one can remember the difference between the two. And are they even worth the huge posters they’re printed on?
TM Forum Frameworx Standards
Under the Frameworx brand (formerly known as NGOSS), the TM Forum maintains a number of industry standards for describing system functionality, processes and data exchange. eTOM and TAM are just two examples of TM Forum standards. Others TM Forum standards exist, such as SID, MTOSI, OSS/J and SMI.
Classic STEVEN SPEILBERG movie poster ET riding bike across the MOON 24X36 - VY2 4.5 out of 5 stars (2) 2 product ratings - classic STEVEN SPEILBERG movie poster ET riding bike across the MOON 24X36 - VY2. ETOM Poster The eTOM business process framework poster shows the eTOM reference model complete with all component processes. This enables implementers to use the poster as a quick reference point to locate any eTOM process within the framework, ensuring any process can be quickly contextualised. If you like this, check out our eTOM reference Model. OMG’s Issue Reporting Procedure All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they.
Some standards are specifications that can be implemented. Others, like eTOM and TAM, are used to describe and position OSS/BSS systems and processes in relation to one another.
Let’s clear something up right now: Neither eTOM nor TAM are interfaces, data or integration standards. They are not APIs. You cannot ‘write’ some code to implement them.
TAM and eTOM allow vendors and customers to talk about OSS/BSS functionality and process with a common reference point and a common language. They allow vendors to articulate how a product fulfils a particular role in the telco’s OSS/BSS environment.
In fact, TAM and eTOM are both ‘maps’.
Common Terrain
Both TAM and eTOM share the same ‘terrain’ for their maps, a matrix of:
- ‘Vertical’ business processes such as Operations, Fulfilment, Billing, Assurance, and Strategy
- ‘Horizontal’ management functions, that must be considered by some or all of the vertical business functions, such as Customer Management and Resource Management.
For example, Resource Management must be considered in all business functions: Resources are allocated during Fulfilment; Resource usage is tracked for Billing; Resources are planned and procured as part of the CSPs business Strategy….
While the terrain is the same, the directions provided by the two maps is subtly different.
What is the Difference Between eTOM and TAM?
Telecom Application Map (TAM)
TAM lists applications that support particular business processes and management tasks. Essentially it tells you that in order to do X you need a Y.
For example, to do Resource Management in a Fulfilment process, one of the applications you will need is a Resource Design/Assign application.
Etom Poster Maker
Enhanced Telecom Operations Map (eTOM)
eTOM is a map of processes. In many ways it is similar to TAM but is somewhat more detailed, identifying tasks rather than just applications.
For example, the Resource Management task that must be completed in a Fulfilment process is Resource Provisioning. This task itself comprises many sub-tasks such as Allocate & Install Resource, Configure & Activate Resource, Test resource, and many more.
TAM does eTOM
Guess what. The Resource Design/Assign application from TAM is an OSS system that runs Resource Allocation and Configuration tasks described by eTOM.
When to use eTOM and TAM
Want to learn more? Get the free 79 page Guide
They’re big and they’re clever. But what practical use are eTOM and TAM?
As I discuss in an upcoming chapter in the Guide to Modern OSS, they are both too detailed to serve as a simple, high-level way to describe an OSS/BSS environment.
Where they excel is in any project that requires a complete or precise description of the OSS/BSS environment.
Two examples:
When buying OSS/BSS applications. You will often find references to eTOM or TAM in CSPs’ RFI or RFQ (Request for Information/Quotation) procurement documents. Having an common reference means that both the CSP and supplier are talking the same language. If the CSPs asks ‘do you have a Resource Design/Assign application that can Allocate and Configure LSP tunnels on an IP network?’ there is little doubt what they mean.
Etom Poster 18.5
When designing and integrating systems. As I mentioned, neither eTOM nor TAM describe APIs or data formats for integration. But they do help by mapping out the processes and applications that need to interact to enable particular business processes. For example, TAM shows us that to carry out a Fulfilment process, we need to consider how an order flows from the Customer-facing systems, through Service Order Management and on to Resource Order Management. As a System Architect or Business Analyst, both eTOM and TAM are a useful reference to ensure you’ve considered all the points of interaction and the end-to-end flow of a process.
Summary
eTOM and TAM are just different ways of looking at the same thing: What tasks does a CSP need to do? What applications does the CSP use to do those tasks?
Simple.
Five minutes after reading this you will have forgotten which is which…