Ever been in a business that did not have some critical analysis that they thought could only come from some long-time employee secretively using Excel, some stored procs, some custom scripts and/or a ton of manual editing (ctl-C,ctl-V)?
I have not either. Chances are only one person (or a few folks) know how this is done each week and the CxO holds his breath when they’re on vacation and the process is not understood or documented it may even be done on an old desktop that has some magic configuration.
This is traditional strategic data integration – This is the worst of Edge Data Integration … often the sources are not an enterprise systems such as the ERP, the ODS or the big _______ (insert billing, manufacturing execution, transaction processing …) system.
In companies where robust integration environments and deep skill sets exist, the IT shop might see sees the “perfect” application for (or justification or) a new EAI framework, monolithic ETL tool or ESB and repeatedly proposes a six figure and multi-month project.
Without enrolling half the IT folks or worse, an army of junior consultants, there are strategies, design patterns, methodologies and even tools that are very appropriate for this type of Edge Data Integration. They can be built with the visibility/maintainability of logic and exception handling that the enterprise tools promise.
It’ll be interesting to watch Wikipedia … someone suggested that the topic “Edge Data Integration” be merged with Core Data Integration – The only pressure I can think of to merge these would be from tool vendors with a commercial interest as they are VERY different things.
Stay tuned and check out www.bus-informatics.com…
