for Information Management Blogs
JAN 13, 2010 5:33am ET

Blogroll

Standardizing Data Migration

Print
Reprints
Email

In the motion picture industry, studios separate responsibilities for creating content from responsibilities for distributing content. The people who make the movies option the scripts, hire the talent, and film the scenes. The distributors of the films, on the other hand, figure out how to package and deploy the films. They need to know which theaters require 30 millimeter versus 70 millimeter formats, or even IMAX. They also deal with DVD packaging, including different international DVD formats. The industry understands the importance of having a supply chain that differentiates between the roles of content creation, content packaging, and distribution.

In IT we’re very quick to point to our operational systems as creators and owners of data. But maybe the solution is that IT establishes a functional team that’s responsible for data packaging and distribution, just like the movie industry.

Traditionally data formats and standards have fallen into the realm of the architecture team. Unfortunately this is typically a paper-only activity without teeth. A data distribution team wouldn’t focus on paperwork. They would be focused on data logistics, receiving content from the various source systems and packaging the data for consumption by other systems. This isn’t about implementing a specific platform to store or move data. It’s about active management of corporate data content.

One of the biggest development challenges is the hunting expedition that developers go on to find and acquire the data they need. Most aren’t aware of all their choices, let alone the optimal systems of record.

Currently every application, data mart, data warehouse, reporting system that needs data from another system follows a specific set of procedures to obtain that data. Each system requests different data formats, different delivery schedules, and different content. Everything is custom, there are few if any standards, and there are no economies of scale.

This will also unburden the various application teams from building and maintaining the never ending volume of custom extract requests. The only way to stop the madness is to compartmentalize content creation from data packaging and distribution. This means establishing a data supply chain that separates data creators from data distribution from consumers. Who knew IT infrastructure was just like the movies?

Evan Levy also blogs at evanjlevy.com.

Filed under:

Advertisement

Comments (3)
Evan, I like the analogy of movies. What you referred as data supply chain can also be a data services or integration competency center that achieves economies of scale in shared services environment. Your remark of "paper-only activity without teeth" is spot-on as there are many CoEs that document best practices but don't have any control over what gets implemented. Data services/distribution/competency center, whatever we call it would need to have that teeth. In experience, such data distribution/competency center shouldn't be centralized to the extent that it gains monopoly impacting innovation. Some pockets should purposely be allowed to continue in silos for the distribution/competency center team to innovate continuously and truely provide economies of scale.
Posted by Sachin K | Wednesday, January 13 2010 at 4:15PM ET
Thanks for the comment. Implementing data extract and data migration standards doesn't require centralization; it requires a level of discipline and rigor that developers follow. The key is to reward folks for aligning their activities with standards. The reason for standards isn't to stifle innovation -- it's to reduce the need for invention, simplify development, and speed up delivery.
Posted by Evan L | Thursday, January 14 2010 at 2:24AM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.

Blog Archive for Evan Levy

The Time Has Come for Enterprise Search
The Problem with Total Cost of Ownership
Complex Event Processing: Challenging Real-Time ETL
The Flaw of the Data Inventory
So You Think You’re Ready for a Data Warehouse Appliance, Part 2

More from Evan Levy »

Blog Index »

Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.