Data silos are inevitable, according to Lyn Robison of the Burton Group. Silos are a natural part of decentralized IT systems, he argues, existing not just because of decentralized information systems, but because of the departments, groups and teams that are part of everyday, enterprise life.
He makes a good point:
"It's important to realize that traditional approaches to this problem have not fixed the data silo problem. Service-oriented architecture or enterprise-wide software applications won't eradicate silos. Really, Silo busting is a fool's errand."https://o1.qnsr.com/log/p.gif?;n=203;c=204663295;s=11915;x=7936;f=201904081034270;u=j;z=TIMESTAMP;a=20410779;e=i
Therefore, instead of fighting a losing battle by trying to eliminate silos, IT divisions should instead focus silo-bridging, argues Robison.
In two recent blog posts, Robison outlines his case for bridging, rather than eliminating, silos. It's called MODS-Methodology for Overcoming Data Silos-and he says it's a ground-breaking approach for bridging silos and delivering integration information from decentralized systems, without the usual integration rigamarole.
Robison compares MODS to a library's card catalog system. In case you've forgotten, a card catalog was a series of cards about a book. The card catalog was arranged alphabetically, and included a subject, title and author card on each book. Each of these cards would give you the book's reference number so you could find it in the library stacks.
The key thing to remember here, as Robison points out, is that the library did not move all the books into the card catalog-which is basically how integration typically works-it just told you where to find the books.
Likewise, MODS requires a registry of all key enterprise data, but the registry simply tells you where you can find instances of that data. Meanwhile, the data stays decentralized, in its silo.
You can also think about MODS as a "project-based approach to MDM and data integration," with each MODS project consisting of scoping a topic and five steps:
- Model to understand the type, which includes understanding the data you have and the data you need on a particular topic.
- Identify to track individual instances, which involves creating a registry that contains a master list of of instances on the topic.
- Classify the data, which defines who can see what.
- Convey, or automate the delivery of information on the topic based on services. He specifically mentions that this will probably entail using REST, instead of SOAP, so users can access it via a browser.
- Control, which means applying the appropriate security to your automatic delivery systems.
How would this theory play out in practice? In "Data Integration that can actually Work," Robison points out that UPS basically uses this approach to manage information about shipping. Rather than trying to create one huge system to house all information about a parcel, UPS identifies each parcel and then uses that identifier to track the parcel across all its system silos.
To learn more about MODS, you can check out "A Data Management Freebie," in which Robison introduces MODS. It includes several key background links, but the bulk of the information is in an embedded webinar explaining MODS and how to get started with this approach.
The Burton Group is also giving away-for now-"Delivering Integrated Information from Data Silos Using MODS." This white paper, written by Robison, was published June 25 of this year, so it's up-to-date information about the Burton Group's MODS approach for managing data.
You'll need to register to download it, but that's a simple process.
MODS isn't meant to be a magic solution, Robison writes. But, he explains in the webinar, they "are ideal for today's it environment in that they are inexpensive, they are low-risk and they deliver compelling results for the business."
And at the compelling price of free, it's an approach worth checking out for your business.