 |
|
|||||||
 |
   
|
|
||||||
|
|
|||||||
|
|
|
||||||
 |
 |
 |
 |
|
 |
|
 |
 |
MIMB and its metadata bridges can be used to reverse engineer the metadata
found in many popular database design tools, ETL tools, and BI metadata. The MITI Total Solution
can then be sed to stitch these metadata elements together to form a complete description
of the data lifecycle within an enterprise.
A common business user oriented use case is one where it is important to determine the ultimate sources of data that is presented as part of a report in the BI system. The harvesting and stitching shown above truly pays off at this point, as it provides the lineage traceability from the BI reports, back through the BI design, to data marts, warehouses, ETL and back to the ODS's where the data is originally entered. A quick answer to this question may be obtained using the MIRWeb metadata analysis capabilities.
First, search for the element within the BI report:
Now, select the textual lineage report to see the ultimate data source(s) involved:
A common technically oriented use case is one in which it is important to determine what systems, transforms, databases and reports are impacted by a proposed change, perhpas in an ODS. Again, the harvesting and stitching brings great returns, as it provides the answers in the form of impact analysis the downstream ODSs, ETL, Warhouses, ERPs, Marts and BI design and reports. A quick answer to this question may be obtained using the Meta Integration Lineage Analyzer (MILA) capabilities.
First import the proposed changes and compare with the existing metadata:
Based upon this report, search for the changed elements:
Now, select the graphical MILA report to see the the impacts involved:
As new versions of the metadata schemas, transformations, mappings, reports, etc., are continually harvested, it quickly becomes imperative that these tools must be built from the ground up to supporttrue metadata version and configuration management. Imagine a fairly normal information technology department, with several different releases of different configurations systems planned to be deployed over the next year or two. Now, a new initiative is proposed, and impacts are to be assessed. What a terrible mistake it would be to limit impact analysis only to the current production environment! Impact must be determined and reported on for ALL of the proposed/planned/prodiction configurations. To do less would be to miss the very impacts that one needs these tools for.
Again, quick answers to these question may be obtained using the Meta Integration Lineage Analyzer (MILA) and lineage analysis
capabilities. And through the automation and automapping capabilities of the Meta Integration Works (MIW), one can genuinely keep
up with these changes, plans and proposals, as well as the configurations that they imply. In this way, the MITI tools
truly justify the investment up front of harvesting and stitching.
|
|
|
|
|
|
|
|
|
Copyright © Meta Integration Technology, Inc. 1997-2008 All Rights Reserved.
|
