Metadata Integration Vendor Panel Introduction & … · Metadata Integration Vendor Panel –Page 1 Tuesday, ... Cognos Rachel Bland Product Manager, ... ETL Vendors BI Vendors

The 10th Annual Wilshire Meta-Data Conference and the 18th Annual DAMA International Symposium,

Metadata Integration Vendor Panel – Page 1Tuesday, April 25, 2006 10:30 am - 11:30 am &11:45 am - 12:45 pm

Denver, Colorado2006, April 23d, to 27th

Vice President, RochadeScott McCurdyASG

Product Manager, PowerDesignerDave DichmannSybaseMetadata Integration TechnologiesLiz McIntoshSASDirector, Software Development, OWBJoseph ZhengOracleProduct Manager, Meta Data ServicesSteve LongNCR TeradataGroup Program Manager, SQL Server BIDonald FarmerMicrosoftPrincipal Software EngineerJohn VerhaegMetaMatrixProduct Manager, Metadata ServicesMarc BourgetInformaticaProduct Manager, Metadata ServicesNathan BobbinIBMVice President, Product ManagementGreg KellerEmbarcaderoProduct Manager, Metadata & ModelingRachel BlandCognosProduct Manager, ERwinDanny SandwellCADirector, Product ManagementAwez SyedBusiness Objects

Senior Consultant, Adaptive RepositoryGeoff SherwoodAdaptive

Metadata Integration Vendor PanelIntroduction & Welcome

presented by Christian Bremeau Meta Integration, President, CEO




Multi-Vendor Development Tools

Design & Modeling

Data Movement &Data Integration(EAI, ETL, EII)

Business Intelligence (BI)

DM - DataModeling

OM - ObjectModeling Dimensional

ModelingReport

Authoring

Metadata insideOperational Data Stores & Data Warehouses

RDBMS Schema / DDL

Forward Metadata Flow

OLAP metadata

Flat File Structures

XML Schema or DTD

Reverse Metadata FlowLegacy

Migration

Metadata Flow & Life Cycle:the heart beat…

The metadata movement between tools can:- preserve the model “as is” or include transformations

(e.g. forward or reverse engineering from/to BI tools)- create and a new model, or update an existing one




Metadata Lineage & Impact Analysis“Quadrant of Use Cases”

High InterestReport Analysis:

where is this data coming from? how was it calculated?

Sarbanes-Oxley Act (SOX) Compliance!!!

High InterestReport Analysis:

where is this data coming from? how was it calculated?

Sarbanes-Oxley Act (SOX) Compliance!!!

Forward Lineage Reverse Lineage

Technical Users

- Application Development:RDMS, ETL, EAI, EII,DW, BI, & Reporting

- Unit Testing- Integration Testing- Certification Testing- User Acceptance- Deployment- Auditing

Business Users

ODS > ETL > DW > DM > BI

Little to No

Interest

Little to No

Interest

Very High InterestLife Cycle

Impact AnalysisChange Management

Very High InterestLife Cycle

Impact AnalysisChange Management

High InterestSupport Business Users:

Metadata/Data OriginReport Justifications

High InterestSupport Business Users:

Metadata/Data OriginReport Justifications




ReportsDimensional

Stores(semantic/business layer)

Metadata Lineage & Impact Analysismore & more vendors involved…

DataWarehouse

DataMarts

OLAP Cubes

StagingDatabases

EII Stores

DataWarehouse

DataMarts

OperationalData Stores

StagingDatabases

Reports


ETL Vendors BI Vendors

BI VendorsRDBMS Vendors

Classic Enterprise Architecture

Modern Enterprise Architecture

ETL Vendors

EII Vendors

OLAP Vendors




DataWarehouse

DataMarts

OLAPCubes


StagingDatabases Reports

DimensionalStores

(semantic/business layer)

Metadata Lineage & Impact Analysismore & more complex…


DataWarehouse Reports

StagingDatabases

EIIStores

Classic Enterprise Architecture

Modern Enterprise Architecture




MetadataResourceTypes: Cobol Record Object C++ Java Data RDBMS XML XML Transformation Dimensional Cube Report

code definition Model code code Model Schema(DDL) DTD Schema in ETL, BI, etc. Model Model Model

OBJ ERA TRF REPDIMCPP JAVCOB RELREC DTD XSD

REL TRF REP

REL DIMTRF DIM REPTRF

OBJ TRF XSD XSD TRF REL

REL TRF REL

ERA TRF RELBO Universe BO Reporter

BO Crystal 9

InformaticaPowerCenter

Oracle WarehouseBuilder

CA AllFusionERwin

IBM RationalRose

REL

TeradataMDS

REL DIMTRF DIM REPTRF

CognosFramework

ManagerCognos

ReportNet

ERA TRF REL

EmbarcaderoER/Studio

REL TRF RELMicrosoft DTS

REL DIMTRF

IBM DB2Cube Views

CUBTRFREL TRF REL

IBM / AscentialDataStage

CUB

Metadata Lineage & Impact Analysis“Metadata Stitching”

REL TRF REL

NCR TeradataFastLoad / BulkLoad




REL

REL

Metadata Integration Strategies

XSD TRF REL

ERA

TRFBO UniverseInformatica PowerCenter

CA AllFusionERwin

REL DIMTRF

REL TRF RELAscential DataStage Cognos ReportNet

REL DIMTRF

XSD TRF

ERA

TRF BO UniverseInformatica PowerCenter

CA AllFusionERwin

DIMTRF

REL TRFAscential DataStage Cognos ReportNet

DIMTRF

Metadata Merging- The classic “one version of the truth”

that drove so many repositories…

- Metadata is merged as side effect ofthe metadata import into the repository.

- The target of the ETL is merged withsource of the BI for one version of the truth

Metadata Stitching- Each tool has its own version / interpretation

of the truth for each metadata store.

- Metadata is integrated as a “stitching” (post) processwhich is independent of the metadata acquisition process.

- A data flow “Configuration” integrates (stitches)together a set of “Versions” of data storesand data processes like ETL, EII, BI, etc.

- Leads to metadata Version & Configuration Managementfor metadata life cycle management / change management,and for metadata lineage & Impact Analysis




ETL Development Tool e.g. Informatica

Data Modeling Tool e.g. CA AllFusion ERwin

BI Development Tool e.g. Cognos ReportNet

Repository Categories“similar data & metadata architectures”

DevelopmentMetadata

Repositories

OperationalMetadata

Repositories

Life CycleMetadata

Repository

Version & configurationManagement

Metadata ComparisonMetadata IntegrationMetadata Mapping

Met

adat

a EA

I

Metadatabi-directional

ETLMetadataone-way

ETL

The development and operational metadata repositoriescan be the same product (development vs. production instance)

or the operational repository can be a specific productwith only run time metadata

The life cycle and analysis metadata repositoriescan be the same product.

Metadata DW / BI

Metadata Stitching

Metadata Lineage& Impact Analysis

Metadata Reporting

Met

adat

a im

port/

exp

ort

Development to production

MetadataCheck-in

Check-out

AnalysisMetadata

Repository

Development to production

ModelManager

PowerCenter

FrameworkManager

Run-time(execution log)

Metadata




Information Management Metamodel(IMM)

OMG Meta Data Standardsfrom CWM to IMM

{ Meta Integration, Inc.,949 Sherwood Ave. Suite 200,Los Altos, CA 94041 }

M0Data, Object, Instance,(also record, row)

A UML Object Model with a Class “Customer” and an operation “getAddress”A CWM Relational Model with a Table “CustomerAddress” and Columns: “Street”, “Zip”, etc.

M1

Model,Metadata,(also Schema)

The UML MetaModelwith Class, Operations, Attributes, Relationships, etc.The CWM Relational MetaModel with Table, columns, Primary Keys, etc.

M2

Metamodel, Meta-metadata

The MOF MetaMetaModelM3Meta-metamodel

OMGExamples

Meta-Levels

Unified Modeling Language(UML)

Inst

ance

of

Lev

el…

Common Warehouse Metamodel(CWM)

WarehouseManagement

Resources

Analysis

Foundation

WarehouseProcess

WarehouseOperation

Transformation

XMLRecord-Oriented

MultiDimensionalRelational

BusinessInformation

SoftwareDeployment

Object Core

Object-Oriented

OLAP Data Mining

InformationVisualization

BusinessNomenclature

DataTypes Expressions Keys

IndexType

Mapping

CWMLevels

Meta Object Facility(MOF)

XML Metadata Interchange(XMI)

NewRFP

(CWM 2.0)




Shall your next modeling tool, EAI, ETL, EII design tool, or metadata repository provide:

More Metadata Integration between tools ?for better integrated single vendor total solutionfor better integrated multi-vendor best of breed solution

Better integrated Metadata Version& Configuration Management ?New Metadata Lineage & Impact Analysis ?More support for Metadata Standards ?More Metadata tools?

Metadata comparators, mappers, integrators ?

What level of Metadata support to expect from these vendors ?




Web-based Enterprise Repository

OracleOracle

Mid-Tier Server

Adaptive Web Application

XSLTXSLT

JSPsJSPsBrowserBrowser

XML

Application Server

Database Server

SVGViewer

CorporateEmail Server

External Source or Target Systems

Adaptive Adaptive IntegratorIntegrator

MIMB Adapter

Other Adapters

CorporateSecurity Server

(S)HTML

SVG

Web ServicesWeb Services

URL

LayoutEngine

HTML

Core Core FunctionalitFunctionality (servlets y (servlets and Java and Java libraries) libraries)

XMIJDBC

LDAP

SMTP

ClientIntegration

Library

AdaptiveGeoff Sherwood (Senior Consultant, Adaptive Repository)




Standard Metamodel Support– MOF– MOF Versioning– XMI– UML– DI– CWM– SPEM– EDOC CCA– RAS– ITPMF– BMM

Under Development:– MOF Facility– MOF QVT– BPDM– BSBR– ODM– KDM– OSM– IMM

Get Involved! Contributors required for definition of “IMM”the “Information Management Metamodel”





Adaptive EA - The Bigger Picture

Finance

HR

Organisation

Strategy

Governance

External

ProcessPerformance

Project

IT





The Vision for Metadata• Single Point of Truth

– Starts with specific problem space (e.g., data warehouse), …– …that expands with demand (becoming corp. infrastructure)

• “Out of the box” solutions for common needs– Data Warehouse Management– Application Mapping and Understanding– Enterprise Architecture– Service-oriented architectures– …

• Built on Industrial strength core technologies• Ubiquitous (metadata)

– Access anytime, anywhere– Across a spectrum of skill-levels– Supporting all languages / geographies

ASGScott McCurdy (Vice President, Rochade)




Bus. Processes

NetworkRouters, Network protocols, Middleware, etc.

PeopleBus. Goals

HW/OS Client Web Svr App Svr Mid-range Mainframe

Wind

ows

AS400

Linux

UNIX

z/OS

more…

Data

DB2UDBSybase

OracleSQL SvrTeradata

Data ModelingTools

Applications

COBOLJavaPL1

Case ToolsETL ToolsBI Tools

SAPPeoplesoftSiebel, …

AssemblerC/C++

ProcessModelingTools

Single Point of Truth for DW? (a scenario)





Single Point of Truth for DW?

ER, logical, physical perspective(Arch / Data Admin teams)

ScenarioSAPCOBOLData ModelingUDBOracleCOBOLETL ToolsTeradataBI Tools

Definition of data, transformations, and stewards

(business and tech users)

Graphical drill down of data lineage, transformations, and impact analysis

(arch, analysts, dw proj team, etc.)

• What’s required (what are we doing):• Single point of understanding across…

– DBMSs– Transformation technologies

• ETL tools, development languages, etc.– BI Tools

• Support for automated linking across technologies and vendor tools

• Data lineage / impact analysis available back to operational system

• Metadata information viewable in format acceptable to a variety of users…

• examples…

• Launched from user’s tool of choice– ETL Tool, BI Tool, modeling tool, Excel, etc.

• With openness and standards in mind– XMI, web services, CWM, etc.

• Enabling the business problem to be solved more quickly and efficiently

• …while implementing metadata as an infrastructure leveragable by the entire organization.





Business Objects, Inc.Awez Syed (Director, Product Management)

Where did that number come from?Will it meet compliance regulations?How fresh is the data?How was it transformed & filtered?




Business ObjectsAwez Syed (Director, Product Management)

Integrated metadata across BusinessObjects suite– Metadata is common and shared between all the products in the suite

including ETL, EII, Quality, Profiling, BI, Dashboards, Applications

Open metadata across BusinessObjects suite– Metadata in Business Objects products is open and accessible via SQL or

open API and available to everyone

Open metadata exchange with 3rd party products– CWM support, open SDK to transfer metadata to and from other tools and

products– Event-based publishing and acquisition of metadata elements




Business ObjectsAwez Syed (Director, Product Management)

Track metadata relationships– Automatic lineage detection, data transformations through multiple steps– Answer ‘Where used’ and ‘How used’ questions easily– Explore and understand metadata relationships from source to target to

tools and users

Search– Easily locate reports, tables and other metadata elements based on name,

descriptions, relationships, usage and currency

Versioned with ability to track changes– For tables, reports, mappings etc.

Extend metadata attributes and relationships– Define custom relationships, add new attributes




CADanny Sandwell (Product Manager, AllFusion Modeling)

Customers expect our metadata to be:– Complete – Open– Portable– Accessible– Reconcilable




CADanny Sandwell (Product Manager, AllFusion Modeling)

Our current metadata vision includes:– Support for industry standards– Improved “meta model” and “meta object” filtering

when exchanging model specific metadata– Metadata based strategic product integrations

• Other modeling products• Other repository based products• Metadata CCM products

– Interfaces to participate in the automation and management of meta data related processes




Cognos Metadatafor Performance Management

Rachel Bland (Product Manager, Metadata and Modeling)

• Modeling of business views independent of data source type and structure.

• Advanced query generation• Support for third party metadata to leverage

existing metadata • Information exchange

– For Cognos Data Integration - ETL, EII and OLAP– Common foundation modeling of BI, Metrics and

Adaptive Analytics




What drives Metadatain the Performance Management space?

• Rate of adoption of any concept or technology is driven by customer pain points and value:– Data storage

• Where does the data come from?– Data access

• Where does the data go?– Reporting and Analysis

• What does the data mean?– Performance Management

• How do we use the data to run our business better?

• Metadata is the glue that ties together the information acquired during all of these phases of building an IT infrastructure.

Cognos Metadata for Performance ManagementRachel Bland (Product Manager, Metadata and Modeling)




Integration, Versioning & Configuration

Metadata Integration between tools:– Diverse purposes:

• Administrative metadata: physical source schemas, transformations etc

• Semantic and Administrative metadata for power users.• Business metadata: semantic naming, calculation formulae, filters

– Different scope for different system architectures: • Leverage existing technology investments across diverse vendors.• Leverage single-vendor investments

• Metadata Version & Configuration Management– Lifecycle is the key

• Volatility of metadata differs throughout the tiers of a solution.– 2 pronged approach: Methodology and Technology – MetaIntegration plays a key role by enabling us to better

integrate with our partners.





Lineage and Impact AnalysisSeparate but Intertwined

Lineage - means different things to different groups• Finance – Legislative standards compliance

– Who changed what/knew what and when?• Power User – Which data from which source?

– Timeliness - how latent is the data?– Quality – does this data match that data – why/why not?

• Business user analysis – What does this data mean? – What is the difference between unit_price and unit_sale_price?– Where is this list of products sourced from? Sales system? Inventory?– Who is the steward of this data (MDM)

Impact Analysis • Finance

– uses lineage to determine upstream impact• Power User

– When my data changes or refreshes or is merged how does this impact my consumers? Has the meaning changed? Is a report broken?

• Business user – is this report valid, is the data up to date





Emerging opportunities for metadata

• Standardize Physical and Logical Views of Business Entities (MDM)

• Enable Solution Lifecycle Management across technologies

• Map systems and solutions to workflows and processes





• ER/Studio Enterprise– Business data modeling/database design and maintenance– Central point of meta data analysis and design– “MetaWizard” Metadata Integration Utility

• DT/Studio– Model-driven ETL/data integration– “MetaWizard” Metadata Integration Utility

• Describe™– UML 2.0-based application, system and business modeling

Embarcadero’s Metadata Integration Approach

EmbarcaderoGreg Keller (Vice President, Product Management)




Embarcadero’s Metadata Integration Approach• Embarcadero’s model-driven solutions easing the Data Management process

– Analysis:• Import/Consume• Analyze• Create Standards

– Communication:• Integrate Stakeholder Roles • Publish/Enforce Standards• Where Used

– Re-purpose• Export/Provide





• Embarcadero’s model-driven solutions easing the Data Management process


– Communication:• Integrate Stakeholder Roles• Publish/Enforce Standards• Where Used

– Re-purpose• Export/Provide• Leverage for Data Integration• Leverage for App Development






• Embarcadero’s model-driven solutions easing the Data Management process


– Communication:• Integrate Stakeholder Roles• Publish/Enforce Standards• Where Used

– Re-purpose• Export/Provide• Leverage for Data Integration• Leverage for App Development






Information as a Service Depends on MetadataAll Activities Generate MetadataMetadata Must Be Managed as a Critical Asset

IBM Information Integration Solutions Metadata ServicesNathan Bobbin (Product Manager, Metadata Services & Technologies)




Roles-based Tools & Integrated Metadata Simplify Delivering Information as a Service

Simplify integration

Increase trust and confidence in information

Increase compliance to standards

Facilitate change management & reuse

IBM Information Integration Solutions Metadata ServicesNathan Bobbin (Product Manager, Metadata Services & Technologies)




General Trends

• Information System Architecture has become complex– ERP, CRM, Supply Chain, Financials

• Variety of user profiles– Business Users, Business Analysts, IT Developers,

Architects• Varying requirements across business functions

– Financial Reporting, Compliance, Operational, etc

InformaticaMarc Bourget (Product Manager, Metadata Services)




Addressing the Information Lifecycle

30% 30% 40% OngoingDiscovery Design Develop Deploy/Operate

Business/Technical AnalystDeveloper

Admin/Operator

Metadata SearchModel renderingData Profiling

Data PreviewView explosionData LineageLogical/Physical

Mapping specificationBusiness rules wizardBusiness Lineage

Mapping TemplatesMapping GenerationPC DesignerData Lineage

Admin ConsoleWorkflow MonitorRepository Manager

Robust Metadata Management foundation to entire life cycle





Innovation Directions (Metadata)• Broader Audience

– Metadata Catalog as ‘Finder’ to Data– UI Personalization – Using metadata to accelerate IT projects

• Information universe– BI (Business User)– Design Tools, EII (Information Architect)– Databases, ETL (Technical Developer)

• Metadata services– Data Element Profiles – Data Lineage





Metadata Journey

Create “Data Dictionary” and initiate data stewardship

Search and discover objects across multiple

sources

Look for reuse, and retire least-used data sources to optimize assets

Connect the information

“supply chain”across sources

Execute and monitor change management processes

Analyze lineage, where used, and track operational

dashboards

Central console for change management implementation

Update and synchronize data

across multiple repositories

1. Discover

2. Design and Build

3. Deploy

4. Control





MetaMatrixEnterprise

MetaMatrixDimension

MetaMatrixQuery

MetaMatrix Enterprise • Web services & SQL• Modeling enterprise data• Scalable deployment server• Metadata management• Application/legacy connectors

MetaMatrix Dimension • Web service-enablement of data sources• Expose business views as XML• Lightweight modeling – rapid integration• Standard WAR-based deployment

MetaMatrix Query • Embeddable Java component • Federated query engine• Query optimization• Standard JDBC to all sources• Standard SQL to all sources

Ent

erpr

ise

Ent

erpr

ise

Pro

ject

Pro

ject

ISV

/ P

roje

ctIS

V /

Pro

ject

MetaMatrixJohn Verhaeg (Principal Software Engineer)




Rapid Web Service-Enablement

MODELWebservice

1

PACKAGEWebservice

2

DEPLOYWebservice

3

• Dimension Designer• Model-based integration• Expose multiple sources, integrated• Expose business views of data• Output an integration package

• Standard WAR file• Integration package is bundled• Query engine is bundled• Web service fully defined

• Deploy WAR file to Web Server• Web service fully executable• Access via standard SOAP• Data exposed as business views

Web Svc App (WAR)Web Svc App (WAR)

MetaMatrixQuery Engine

Web Server




MetaMatrix Dimension Modeling

• Rapid design & deployment of Web Services• Expose integrated data as XML-based business views• Deployment of Web Services as standard Web apps• Runtime execution optimized through use of MetaMatrix Query Engine

Dimension Dimension ModelsModels

Web Server

Data Sources

Business Views

<XML><XML><XML>

Web Service Operations

WSDLXSD

Source Models

DeployImport Map ModelWARastoto




Microsoft (SQL Server)Donald Farmer (Group Program Manager,

SQL Server BI, Integration Services)

Let's distinguish two use cases …• Metadata Management

– Creation, storage, versioning, administration– Supported through Visual Studio integration in

SQL 2005• Metadata Intelligence

– Impact analysis, lineage and business metadata– Emphasizes relationships and high-level narrative– Supported through the Metadata Samples Pack

in SQL 2005





SQL Server BI, Integration Services)

• Metadata Samples Reporting Pack– Launched on MSDN in November 2005– > 3100 downloads

• Lineage, Impact analysis– Customizable reports– Embeddable lineage / impact viewer

• It's shared source!– Customizable, extensible – and free!





SQL Server BI, Integration Services)• No "boil the ocean" repository

– Model-based systems could not keep pace with rapid technology change

– Either innovation suffered or repositories became outdated quickly

• Future directions– Technology specific "repositories"– Bridging will always be necessary between them– Metadata intelligence will help make sense of the

relationships• It's social networking for data!




Teradata Meta Data Services (MDS) • Provides a framework for storing, retrieving, viewing,

and customizing Teradata Warehouse metadata.

• Persists metadata in the MDS Repository, which is a set of Teradata tables using an Object

Model Design.

• Provides a set of Utilities and APIs for metadata management, customization, and extensions.

NCR (Teradata)Steve Long (Product Manager, Meta Data Services)




Microsoft COM interface

C++ programming

XML

Web Services

Build bridges using APIs: Or acquire from:

www.metaintegration.com

Teradata Partner

Metadata Interchange using Bridged Architecture

ModelingTools Query ToolsExcel

OLAP ToolsETL tools MetadataRepository

ApplicationsOther DBMS’s

BI Tools

metadata

metadata

metadatametadata

metadata

metadatametadata

metadataData Warehouse





ParallelETL

Utilities

Metadata Repository

Schema,Lineage,Data Loc,

etc.

Lineage,Filtering,

Transforms,etc.

OLAP

BI Tools

CRM

Schema,Cube Def,Quants,

etc.

DataSource1

DataSource2

DataSource3

Data

Warehouse

Schema,Stored Procs,

Views,etc.

The Big Picture





Oracle Warehouse BuilderJoseph Zheng (Director, Software Development, OWB)

Metadata Management – Repository Platform

• A multi-user repository platform• A secure repository platform• An open repository platform

– Graphical Java UI and browser UI– Relational views– Complete scripting language (+ Java API)

• An extensible repository platform– User defined objects– User defined associations– User defined properties

Metadata Services

Relational M

odeling

Data Flow

Process Flow

Data Q

uality

Dim

ensional Modeling

Analytics S

upport

Repository

Oracle Warehouse Builder





Metadata Management - Metadata Services

• Dependency Management– Data lineage– Impact analysis

• Metadata Snapshots• Change Management

– Diff– Merge– Synchronization

• Security (roles)• Multi-language Support• Reporting (browser)• APIs (Scripting, SQL, PL/SQL)• Exchange (import/export)

Metadata Services

Relational M

odeling

Data Flow

Process Flow

Data Q

uality

Dim

ensional Modeling

Analytics S

upport

Repository

Oracle Warehouse Builder





Metadata Management - End-to-End Integration

iCal

XPDL

z

Designer

Legacy

File

ERP

Database

CustomApp

CWMImport

Relational &OLAP Catalogs

10g Scheduler, Workflow

WarehouseBuilder

DiscovererBI Beans

CWMExport




SASLiz McIntosh (Metadata Integration Technologies)

• Metadata Vision– Support the enterprise’s need to know– Share intelligence assets across the

enterprise– Deliver the single version of the truth

throughout the enterprise





• Need to know





• Need to share





• Need for single version of the truth




60% of Projects Lead to Failure• Industry analysts report that over 60% of

projects in IT still lead to failure• Metadata Management = Understanding

– Greater understanding creates:• Greater standards and regulatory compliance• Greater agility in IT – manage change with

speed AND accuracy

– IT effectiveness improves with automated alignment to business

– Today’s IT Managers are tasked to be more responsible for business alignment – we cannot just manage technology anymore

SybaseDave Dichmann (Product Manager, PowerDesigner)




Link And Synchronize Meta Data





Complete Meta Data Management• Impact Analysis

– Report On Dependencies And Downstream Dependencies– Spans Multiple Models/Sets of Metadata (Cross-Functional

Impact vs. Localized View)

• Requirements Management– Spans Multiple Models/Sets of Metadata (Cross-Functional

Requirements Management vs. Localized View)• Reporting

– Multi-model Reporting For Single Source Documentation – Spans entire Project or Enterprise

• … Requires Complete Customization• Enforce Standards and Practices

– Guaranteed Results from Standards and Practices Definitions• Enhanced Meta Data Definitions

– Total Define & Describe Experience – Tailored to Your Practices





Vice President, RochadeScott McCurdyASG

Product Manager, PowerDesignerDave DichmannSybaseMetadata Integration TechnologiesLiz McIntoshSASDirector, Software Development, OWBJoseph ZhengOracleProduct Manager, Meta Data ServicesSteve LongNCR TeradataGroup Program Manager, SQL Server BIDonald FarmerMicrosoftPrincipal Software EngineerJohn VerhaegMetaMatrixProduct Manager, Metadata ServicesMarc BourgetInformaticaProduct Manager, Metadata ServicesNathan BobbinIBMVice President, Product ManagementGreg KellerEmbarcaderoProduct Manager, Metadata & ModelingRachel BlandCognosProduct Manager, ERwinDanny SandwellCA

Senior Consultant, Adaptive RepositoryGeoff SherwoodAdaptive

Metadata Integration Vendor PanelOpen Discussions, Question & Answerspresented by Christian Bremeau Meta Integration, President, CEO

Documents

Metadata Integration Vendor Panel Introduction & … · Metadata Integration Vendor Panel –Page 1 Tuesday, ... Cognos Rachel Bland Product Manager, ... ETL Vendors BI Vendors