Business Intelligence Network business intelligence resources

Blog: William McKnight

« Best, worst... and craziest uses of RFID | Main | When Not to Use Enterprise Information Integration »

When to use Enterprise Information Integration (EII)

This blog entry is co-authored by William McKnight and Mike Ferguson (link) and is being cross-posted on our blogs. This is the first in a series of entries on Enterprise Information Integration (EII). EII is gaining traction for enabling data integration without the need for the physical instantiation of the integration. In other words, EII adds integrated reporting capabilities while minimizing impact on existing systems. We have been selectively adding EII to our data warehouse architectures. Today, we’ll look at those situations when EII makes sense for data integration requirements.

1. Connecting structured (as in data in a data warehouse) data in particular with unstructured data takes advantage of EII’s strength of leaving data in place that could dramatically increase overall storage requirements if duplicated

2. When immediate data change in response to the data view is desired (changing a copy of the data would not suffice)

3. When data transformation is relatively light or nonexistent and just getting the data together for integrated query is the biggest challenge

4. When the relatively worse query performance of EII query is acceptable (versus the obvious advantages of physically cohabitating all data for the query)

5. Some operational and regulatory reporting where the data needed is not completely integrated in one place

6. Integration of Performance Management software with multiple underlying line of business BI systems to allow a company to see performance management at the enterprise level (across line of business BI systems) using LOB metrics to calculate enterprise KPIs

EII is changing and some of the disadvantages and restrictions will lessen over time but it’s a chicken-and-egg situation. More end clients will need to incorporate small adaptations of EII in their decisioning environment to spur the growth. There may be opportunities and TCO propositions to federate your data acquisition requirements now using EII. Small sized, relatively smaller transformations, unstructured and interactive situations provide those opportunities.

Technorati tags: eiiTechnorati tags: Enterprise Information Integration

  Posted by William McKnight on January 5, 2007 7:33 AM |

Comments

Great summary, guys. I think your analysis is right on the money. The one situation I might add is when you are trying to make your data available to a new SOA project. Perhaps this is where you might see some departmental implementations.

Thanks for posting this summary online, great help. Demand of EII is growing vertically. Please keep posting such articles, it will be very helpful for us.

Regards.

Post a comment