Adding to this, each LOB will have their own budgeting and cost constraints which
determine how often systems are upgraded or introduced.
No Canonical Data Format
Multiple LOBs will have their own systems, and hence their own data schemas, and
a way of accessing the data. This leads to duplication of data, which in turn leads to
multiple services providing views for the same entity in different ways.
Let's consider the example shown in the following figure. There is one LOB system,
Product Information System, which will keep track of customers who have registered
their interest for a particular product or service. Another LOB system, Event
Registration System, will provide membership management tools to customers, for
a sales discount program. Sales Information System will have to track all customers
who have registered their interest for any upcoming products or services. Thus, we
can see there is no unified view of the Customer entity at the enterprise-level. Each
Chapter 1
[ 9 ]
LOB will have its own systems and their own view of Customer. Some will
have more attributes for the Customer, while others a few.
Pages:
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33