article page
| 1
| 2
| 3
| 4
|
and ResourceFacingService, each of which contains three low-level ABEs. The lowest level ABEs are cohesive collections of specifically related entities, in which each entity describes a thing or concept, such as a Customer or a Customer Account, and defines its essential attributes. ABEs and entities are mapped to eTOM processes at each level of decomposition, so that the relationships between business processes and affected data elements can be clearly understood. The SID is primarily an information model - the base from which a service provider, systems integrator or ISV derives, extends, customizes and details a specific data model.
|
|
The SID begins with high-level information domains that are aligned with the high-level functional processes of the eTOM. |
|
fully developed as the eTOM and SID, and because the inter-framework mappings were incomplete, pre-TIP TM Forum interface development did not fully account for all
|
|
|
Figure 3 - TIP Organization
(used by permission of TM Forum)
|
|
The TAM defines procurable applications that perform the processes defined in the eTOM and manipulate the information defined in the SID. The TAM subdivides applications into lower level functional units, and describes specific interactions that can occur between applications. These interactions effectively define application boundaries.
The TNA defines architectural concepts and requirements that provide a foundation for systems integration, including distributed information-oriented architecture and the use of NGOSS Contracts to define and manage the interaction between application components.
We can use these NGOSS frameworks to fully define the management environment - provided that we include the detailed relationships, or "mappings," between eTOM, SID and TAM. Because the TAM was not as
|
|
three frameworks or their mappings. Past TM Forum interface specifications also differed significantly in focus, granularity, protocol support, features, documentation, and certification. TIP builds on the best characteristics of its predecessors.
Recent intensive development of NGOSS Contract concepts has not only fleshed out contract contents (pre-conditions, post-conditions, constraints, service level agreements, and more) and contract lifecycles. It has also defined a method for the identification, sizing, and specification of the low-level services and operations that are essential to both systems integration and application design. As shown in figure 2, this method uses inter-framework mappings to identify the low-level eTOM processes that fall on TAM application boundaries, map them to
article page
| 1
| 2
| 3
| 4
| |
|
