Skip navigation links
NewsEvents
Lists

Workshop: Master Data Management

Managing Master Data, Part II

Having recognised the need for master-data management what is the appropriate architecture for a company?


By Mike Fleckenstein

[This article contains references to illustrations that cannot be reproduced with our current web technology. Please accept our apologies for this shortcoming and e-mail the editor,
gburton@ark-group.com, for a full PDF version if you would like to read it in its original print form]

Most companies today have anywhere from a handful to thousands of transaction data stores (TDS) in which daily business processes are recorded. Examples include financial systems, marketing systems and operational systems, such as order entry. These systems are often developed separately and, as a result, contain the same data with inconsistent definitions. This is particularly true for companies that have undergone mergers or acquisitions. Additionally, companies undergo constant change. This adds to data structure inconsistencies over time and between systems. Integrating these systems to glean operational, historical, future and summary data is a challenge for any company. (continued at the source -
www.ikmagazine.com)

Read the indepth series (4 parts):
Part 1
Part 2
Part 3 (PDF)
Part 4

 

CONTACT INFORMATION
Debi McGhee

Project Performance Corporation
703-748-7000
dmcghee@ppc.com