STP aims to enter transactional data only once into the system. This data can
flow within or outside the organization. To achieve STP, there should be mechanism
for seamless data flow, also in a flexible manner.
Data redundancy can be managed if and only if there is a mechanism to consolidate
data in the form of Common Information Model (CIM). For example, the NGOSS's
Shared Information/Data (SID) model from Telecom Management Forum is the
industry's only true standard for development and deployment of easy to integrate,
flexible, easy to manage OSS/BSS components. The SID provides an information
or data reference model and a common information or data vocabulary from a
business and systems perspective. Not every domain or organization has access to a
readymade information model similar to this.
In such a scenario, ESB can play a vital role by providing the edge of the system view
by wrapping and exposing available network resources. Thus, ESB provides hooks
for a "leave-and-layer" architecture which means that instead of altering existing
systems to provide a standards-based services interface they are wrapped with a
layer that provides the services interface.
Pages:
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55