Data mapping is hard, expensive and requires constant maintenance, but if you get it right, it can pay off in all sorts of interesting ways, particularly in managing data during mergers and acquisitions, says Bruce Phillips, the Information Security Manager at Fidelity National Financial.
In a recent interview with CSO Online, Phillips shares the details of the company's data mapping project, including their missteps in trying to build their own system.
Data mapping can be done for regulatory, legal or security reasons. But it's also first step in a range of data integration-related projects, such as transformation or migration of data, according to Wikipedia, which defines data mapping as "the process of creating data element mappings between two distinct data models."
As you might expect from that definition, it's hard to get right and it's expensive-particularly when you have to redo part of the project, as Fidelity National Financial did. So by sharing the company's mistakes and what they learned, Phillips is offering something pretty valuable here. It's the type of useful insight you seldom see with something as low-profile as data mapping, and I think business and IT executives will find it helpful.
While I suggest you read the full article, particularly if you're thinking about a data mapping endeavor, here's a highlight of some of the lessons Phillips shared from Fidelity's project: