• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Zen of metadata 09212010
 

Zen of metadata 09212010

on

  • 404 views

 

Statistics

Views

Total Views
404
Views on SlideShare
404
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Zen of metadata 09212010 Zen of metadata 09212010 Presentation Transcript

    • The Zen of MetadataScott NorthrupData Architect September 21, 2010
    • biography I work for CCSF DPW (City and County of San Francisco Department of Public Works) I’m a DA (that’s Data Architect) with no particular credentials except 30+ years experience in database design PAGE 1
    • HomERwinPAGE 2
    • biography continued • Prior roles – Analyst – business & operational – Programmer – at least 6 languages – Network tech – Project manager – SDLC – Data modeler – logical & physical • Current roles – Data Architect for Data Governance and MDM – Metadata manager – data dictionary – Data standards admin PAGE 3
    • agenda – Intro and environment – DATA – DATA and METADATA – Business Requirements – Metadata types and philosophies – CIA’s compilation and usage of Metadata – Some examples and caveats PAGE 4 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ZEN… …emphasizes experiential wisdom, discernment, or understanding, particularly as realized in the form of meditation for the attainment of enlightenment… ??? Inmon or Kimball ??? who cares… ! BEST PRACTICES ! PAGE 5 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • application environment • Teradata • ERwin • E/R Studio • Ab Initio • Microstrategy • SQL Server PAGE 6 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • data environment • Data Warehouse – 70 databases from 62 source systems – DSL – Data Source Layer • 62 databases – DIL – Data Integration Layer (Data Mart) • 3 databases – DAL – Data Application Layer • 5 databases – Aggregates & Composites PAGE 7 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • classic rock A little bit of data is better than no data Even the bad data is better than no data And any kind of data is better than no data at allInspired by BJ Thomas, “No Love At All” PAGE 8 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • data is… DATA PAGE 9 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • KING… of OUR world ! DATA PAGE 10 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • data “analysis”What does a BYTE of data cost in your organization (and does anyone know or care)?WHAT is the ROI of your data usage? (Alton Brown)HOW can you leverage your data if you don’t really know what it is?WHO cares most about any given piece of data? PAGE 11 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • data management Data Governance Metadata Quality Analysis Design Load Data Acquisition PAGE 12 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • key components• MDM – Master Data Management (-OR- Master Data Mess)• Metadata management – robust metadata with acceptable content & presentation• Data quality and governance – EVERY data element needs a steward PAGE 13 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • so… what is? DATA about DATA PAGE 14 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • co-existence of data and metadata – – PAGE 15 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • co-existence of data and metadata Business Card Request Joe Camel 4321 Puff St. El Nicotine, CA 415–555–1212 Mascot Joe@Camel.com PAGE 16 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • co-existence of data and metadata Business Card Request Name Joe Camel Location 4321 Puff St. El Nicotine, CA Phone 415–555–1212 Title Mascot Email Joe@Camel.com PAGE 17 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • validating business requirements Defining and Purpose and Scope Planning a What the project is intended to accomplish; what’s “in” and Project “out” Objectives General statements of what we intend to accomplish Process Problems Constraint Risks Activities Goals Opportunities Issues that may Uncertainties Manual and s that might Timed and Factors that may enhance our arise that are Issues that may automated unfavorably measurable chances of success under our arise that are processes and impact our milestones control beyond our procedures effort influence Data Metrics Business Operational Data The performance measures we Data used and produced use to assess our progress Systems by manual and Technology automated activities Organization Business Requirements Physical Information to be included in data models PAGE 18 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • joint requirements discoveryINTRODUCTION JOINT REQUIREMENTS DISCOVERY (JRD)As CIA is responsible for maintaining a Data Warehouse, we do not create new sourcesof data, per se. We extract data from other source systems and load it into the warehouse. I. DEFINING THE PROJECT (and Scope)We may possibly manipulate some of the source data which could result in “new”warehouse data. A. Project Purpose B. Project ScopeTo that end, designing a database in the warehouse requires a somewhat differentapproach than designing a database from scratch that would be used to support an D. Risk Assessmentapplication. E. Roles and Responsibilities II. DESCRIBING THE CURRENT SITUATION - Source SystemTo aid in our design, we should understand things from these perspectives: A. Systems and Procedural Analysis  What the data functionality and make-up of the source system is B. Data Analysis o What is the functional data flow, content and meaning o What is the layout/design C. Technical and Environmental Analysis  Why we want to have this data included in the warehouse III. GAP and/or IMPACT ANALYSIS - Data Warehouse o What business need will this support (high-level) A. Current Systems and Procedures o What business question(s) will this answer (detail) B. Data Impacts  How the data will be added to our warehouse or how it may replace or change C. Technical and Environmental Impacts existing data in our warehouse o Will this be a new source IV. SPECIFYING BUSINESS REQUIREMENTS o Can it be integrated into an existing database o How does it differ from other similar data sources A. Business Process Analysis o Are there any downstream affects 1. Process Analysis a) How will we leverage existing documentation or  How we can best make this data available to the widest possible audience diagrams o How does it relate to the overall architecture 2. Process Analysis Deliverables o What standards will be applied o What is the level of granularity - are composites or aggregates needed B. Business Data Analysis 1. Data Analysis  How the data might be integrated with our datamart layer a) What user output is needed (Views, Reports, Forms) o Is it “Partyable” 2. Data Analysis Deliverables o Can it incorporate, or be incorporated into, any existing objects (reference tables, etc.) V. PLANNING the PROJECT A. Resource allocation PAGE 19 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • metadata management (80/20 principle) Business Metadata Business Policies Information Policies Business Rules Data Governance Information Usage Information Quality Access Controls Information Architecture Entity Models Relational Tables Master Objects Data Elements Critical Elements Data Formats Alias & Synonyms Reference Metadata Conceptual & Value Reference Tables Mapping & Lineage Domains Business Definitions Business Terms & Definitions Semantics Concepts PAGE 20 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • metadata types• Bretheron & Singley – Structural metadata is used to describe the structure of computer systems such as tables, columns and indexes – Guide metadata is used to help humans find specific items and is usually expressed as a set of keywords in a natural language• Kimball – Business metadata describes data content (data dictionary, maps, rules) – Technical metadata describes objects and processes (sources, systems) – Process metadata describes results of operations (audits, outputs)• NISO – Descriptive metadata is the information used to search and locate an object such as title, author, subjects, keywords, publisher – Structural metadata gives a description of how the components of the object are organised – Administrative metadata refers to the technical information including file type. Two sub-types of Administrative metadata are rights management metadata and preservation metadata PAGE 21 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • Kimball - DW architecture metadata worksheetTABLE metadataMetadata Item Short Description Possible ValuesDescription A short description of the table Free textIs Audit Subsystem Is this table part of the audit subsystem? Y or NDisplay Name The name displayed on the screen Free textTable Type The type of table Free textUsed In Schemas The schemas that the table is used in Free textView Name The name of the single table view Free textCOLUMN metadataMetadata Item Short Description Possible ValuesDescription Short description of the column Free textDisplay Name The name of the column as displayed on the screen Free TextExample Values Example values stored in the column Free TextIs Audit Subsystem Is this column part of the audit subsystem? Y or N PK (Primary Key), SK (Surrogate Key), or FKIs Key What type (if any) of key this column is (Foreign Key) PAGE 22 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • metadata benefits – Information can be viewed in an understandable context – Better usage of the organization’s data assets – Preservation of corporate knowledge and business rules – Improved impact and gap analysis (new or existing systems) – Facilitation of standards and reusability – Decrease in data redundancy and storage – Easier transitions or interactions with new platforms – Assists in answering security and regulatory questions – Employees/contractors can get up to speed more quickly – Potential reduction in costs for equipment and manpower – Data becomes USEFUL INFORMATION – Data becomes a TRUE ASSET PAGE 23 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • metadata matrixPLANVIEW NUMBER: ___________________________________ 0 us rd ing ing er s on el > od pp sh l lop el et s h IM g Co c es s B == Me ess fu w e ase a a ta S p > M sin ite ite mod nM s s ma n S re g ma ubli li ve ion ion o- t pub bs tad MD in == DS u b if y e fi e de ase d p n C a ta Wi ry Su cc l t ctio on nit nit tat ati e rna es pd a es / v er a Pro u ni er p ar g d w e dat ER to e fi d u cati p o ish d tab te an mm Us an W te M IA /u t sd sd on of De nfirm no n d in bu v iew CIA b lis h te bs bu llec t s o ea te Co e nd ro l e-t da da da ub liv e tific urc Co sin Re sin Up Up Up .P .S Se Pu Cr ER ma da 10 11 DELIVERABLE 1. 2. 3. 4. 5. 6. 7. 8. 9. Entity names Logical Entity definitions Model Attribute names Attribute definitions Relationships Table names Source-to-target file/table mapping Column names Column Transformations Source-to-target element/column Physical Model mapping Column data types Column null options Column valid values, decoded (validation rules) Column derivation rules (embedded in definitions) Primary Key and Primary Indexes Relationships Groupings of tables to define a Map subject area DB Cardinality between tables Join strategies Signature of person responsible for project: Date: Title: Data Modeler: Date: PAGE 24 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – data warehouse source PAGE 25 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – UDP’s PAGE 26 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • source to target using MS Excel PAGE 27 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – validation rules PAGE 28 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • domain of values PAGE 29 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – data model PAGE 30 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – import/export bridge PAGE 31 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – column definitions via RTBTable Name Column Name Column Datatype Attribute DefinitionT_XYZ_ACCT XYZ_ACCT_ID DECIMAL(18) The system generated identifier for an existing users AccountT_XYZ_ACCT XYZ_ACCT_NUM VARCHAR(17) The unique identifier used for an account within a given account type.T_XYZ_ACCT XYZ_CO_ID VARCHAR(5) This identifier denotes the original (legacy) bank that booked or owned the associated account. type.T_XYZ_ACCT XYZ_CRTE_DT_TM TIMESTAMP(0) The date and time a particular Account was added to the system.T_XYZ_ACCT XYZ_STAT_CD INTEGER Status of the accountT_XYZ_ACCT XYZ_STAT_DT_TM TIMESTAMP(0) The STATUS is as-of this time, per the Servers local time.T_XYZ_ACCT XYZ_IS_BUS_IND CHAR(1) This is a Business Account.T_XYZ_ACCT XYZ_LST_UPDT_DT_TM TIMESTAMP(0) Server local time.T_XYZ_ACCT XYZ_MASK_ACCT_NUM VARCHAR(64) This is a masked verison of or surrogate key for a real Account number,T_XYZ_ACCT XYZ_PROD_CD VARCHAR(6) The BOS product code.T_XYZ_ACCT XYZ_PROD_SUBCODE VARCHAR(6) a.k.a. Sub-Product Code.T_XYZ_ACCT XYZ_SOR_ACCT_NUM VARCHAR(17) The Account Number, per the SOR. Generally a padded version of ACCOUNT_NO.T_XYZ_ACCT XYZ_SOR_PROD_CD CHAR(3) The SOR doesnt use the BOS code as its Product Code, so this what it wants.T_XYZ_ACCT XYZ_SOR_TYP INTEGER System of Record TypeT_XYZ_EMAIL_EV XYZ_EMAIL_ID DECIMAL(18) This identifier is the key randomly assigned to an email item when one is created for a given user.T_XYZ_EMAIL_EV XYZ_CNTNT_TYP_CD VARCHAR(40) This is the MIME type of the email message (this could be "text/plain" or "text/html" ).T_XYZ_EMAIL_EV XYZ_CRTD_DT_TM TIMESTAMP(0) Date and time this email item was created.T_XYZ_EMAIL_EV XYZ_EDS_PROF_ID VARCHAR(30) The EDS profile used, in conjunction with a template Identifier, for sending the message.T_XYZ_EMAIL_EV XYZ_EMAIL_TYP DECIMAL(18) Used for sub-type identification by Hibernate.T_XYZ_EMAIL_EV XYZ_EVNT_ID DECIMAL(18) This identifier is the key randomly assigned to an inbox item when one is created for a given user.T_XYZ_EMAIL_EV XYZ_INBOX_ID DECIMAL(18)T_XYZ_EMAIL_EV XYZ_LST_UPDT_DT_TM TIMESTAMP(0) Date and time any attributes of this email item were last updated.T_XYZ_EMAIL_EV XYZ_NNM VARCHAR(120) The nickname from the ContactPoint (at the time the Email was created), used for the "friendly name" of the recipient.T_XYZ_EMAIL_EV XYZ_PRI_CD INTEGER Identifies the priority queue used to sequence handling. (loosely related to Urgent Indicator)T_XYZ_EMAIL_EV XYZ_PROC_STAT_CD INTEGER Status of the email processing.T_XYZ_EMAIL_EV XYZ_SNT_DT_TM TIMESTAMP(0) The date and time the email message was sent.T_XYZ_EMAIL_EV XYZ_SMTP_FAILURE_CD VARCHAR(60) This is the failure code returned with failed email messages, per RFC821.T_XYZ_EMAIL_EV XYZ_TMPLT_ID VARCHAR(100) The identifier of the template used to create this email item, if one was used.T_XYZ_EMAIL_EV XYZ_TO_ADDR_LN VARCHAR(200) The destination email address.T_XYZ_EMAIL_EV XYZ_URGENT_IND INTEGER This is the "importance" flag on a typical email item. It is carried along with the email message to indicate that the sender cT_XYZ_EMAIL_EV XYZ_USR_ID DECIMAL(18) This identifier is the key randomly assigned to a user when he/she completes registration within the system. PAGE 32 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • SYS_MDS database using MS Access Database Column Attribute Attribute Def AbC cleansed version of the CN: Customer Number assigned to theDB_DAD ABC_CN AbC_CN customer.DB_HIGH ABC_CN AbC customer number AbC customer number found in T_ABC_MBR_CN table.DB_EVX ABC_CN ABC customer number A unique number assigned by Hogan for identifying a bank customer. This attriDB_CGG ABC_CN ABC customer number AbC customer number found in T_ABC_MBR_CN table.DB_RS ABC_CN ABC_CN See corresponding column in DB_AbC.DB_OPS ABC_CN ABC_CN The Customer Number of the person associated with this account in AbC formaDB_ABC ABC_CN AbC_CN @@DB_BMT ABC_CN AbC customer number AbC datamartDB_EDS ABC_CN AbC CN see AbC definitionDB_VSS ABC_CN ABC customer number Refer AbCDB_RS ABC_CN AbC_CN See corresponding column in DB_AbC.DB_OPS ABC_CN AbC_CN The Customer Number of the person associated with this account in AbC formaDB_APK ABC_CN AbC customer number AbC customer number found in T_ABC_MBR_CN table.DB_XYZ ABC_CN customer number AbCDB_EDS ABC_CN AbC CN see AbC definitionDB_CM ABC_CN customer number undefined OR unable to load definitionDB_PE ABC_CN CN wells fargo CN of the visitorDB_BMT ABC_CN ABC_CN AbC datamartDB_EDS ABC_CN ABC_CN see AbC definitionDB_AA ABC_CN AbC customer number AbC customer number located in T_ABC_MBR_CN table.DB_STS ABC_CN customer number See AbC Business DefinitionsDB_APK ABC_CN AbC customer number AbC customer number found in T_ABC_MBR_CN table.DB_OPS ABC_CN AbC_CN The Customer Number of the person associated with this account in AbC forma PAGE 33 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • SYS_MDS database continued Database Column Attribute Attribute Def A unique number assigned for identifying a bank customer associatedDB_DAD ABC_CN AbC_CN with this account.DB_HIGH ABC_CN AbC customer number A unique number assigned for identifying a bank customer associated with thisDB_EVX ABC_CN ABC customer number A unique number assigned for identifying a bank customer associated with thisDB_CGG ABC_CN ABC customer number A unique number assigned for identifying a bank customer associated with thisDB_RS ABC_CN ABC_CN A unique number assigned for identifying a bank customer associated with thisDB_OPS ABC_CN ABC_CN A unique number assigned for identifying a bank customer associated with thisDB_ABC ABC_CN AbC_CN A unique number assigned for identifying a bank customer associated with thisDB_BMT ABC_CN AbC customer number A unique number assigned for identifying a bank customer associated with thisDB_EDS ABC_CN AbC CN A unique number assigned for identifying a bank customer associated with thisDB_VSS ABC_CN ABC customer number A unique number assigned for identifying a bank customer associated with thisDB_RS ABC_CN AbC_CN A unique number assigned for identifying a bank customer associated with thisDB_OPS ABC_CN AbC_CN A unique number assigned for identifying a bank customer associated with thisDB_APK ABC_CN AbC customer number A unique number assigned for identifying a bank customer associated with thisDB_XYZ ABC_CN customer number A unique number assigned for identifying a bank customer associated with thisDB_EDS ABC_CN AbC CN A unique number assigned for identifying a bank customer associated with thisDB_CM ABC_CN customer number A unique number assigned for identifying a bank customer associated with thisDB_PE ABC_CN CN A unique number assigned for identifying a bank customer associated with thisDB_BMT ABC_CN ABC_CN A unique number assigned for identifying a bank customer associated with thisDB_EDS ABC_CN ABC_CN A unique number assigned for identifying a bank customer associated with thisDB_AA ABC_CN AbC customer number A unique number assigned for identifying a bank customer associated with thisDB_STS ABC_CN customer number A unique number assigned for identifying a bank customer associated with thisDB_APK ABC_CN AbC customer number A unique number assigned for identifying a bank customer associated with thisDB_OPS ABC_CN AbC_CN A unique number assigned for identifying a bank customer associated with this PAGE 34 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • MetaSurf – Meta Data Services PAGE 35 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • MetaSurf search PAGE 36 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • Metadata LiteT_XYZ_ACCT This represents an account.T_XYZ_CNTCT A Contact is a channel for notifying a user. An Email address is the primary typeT_XYZ_EMAIL_MSG_TYP table level has NO definitionT_XYZ_IN_EV Table of In Items 555 AccountBasedSubscript 666 PasswordLockoutSubscript 777 CheckClearSubscript 888T_XYZ_SUBSCR CheckReorderReminderSubscript 999 DepositAccountUpdateSubscriptDATABASE TABLE COLUMN DESCRIPTION The system generated identitfier for each Contact Point enteredDB_XYZ T_XYZ_CNTCT_PT XYZ_CNTCT_PT_ID by a user. This is the type of method or device used as a contact point byDB_XYZ T_XYZ_CNTCT_PT XYZ_CNTCT_PT_TYP the user. The date and time a particular Contact Point was setup (created)DB_XYZ T_XYZ_CNTCT_PT XYZ_CRTD_DT_TM by the system.DB_XYZ T_XYZ_CNTCT_PT XYZ_EMAIL_ADDR If the contact point type is an email then this is the address. Date and time any attributes of this contact point item were lastDB_XYZ T_XYZ_CNTCT_PT XYZ_LST_UPDT_DT_TM updated. This code is set by the user to rank the priority or order in whichDB_XYZ T_XYZ_CNTCT_PT XYZ_PURP_CD a contact point is used. This identifier is the key randomly assigned to a user whenDB_XYZ T_XYZ_CNTCT_PT XYZ_USR_ID he/she completes registration. PAGE 37 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • enterprise metadata repository – EMR PAGE 38 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • EMR lineage diagram PAGE 39 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • source systems’ (metadata) websites PAGE 40 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • Data Modeling Set of Standards – DMSOS PAGE 41 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • model submission checklist MODEL Submission Checklist (v5) Physical model This Submission Checklist is used to ensure that all models meet CIA modeling standards. Table Check mark each entry to indicate that it has been successfully completed and reviewed. “T” plus acronym used in name prefix If an item is not checked, explain in the comments section. All UPPER case names Model Name (in MM): Standard abbreviations applied Date: Column Data Modeler: other All UPPER case names Data Base Administrator: other Acronym used in name prefix Check each requirement below if complete X Standard abbreviations applied Logical model Misc. Template logical domains set to Physical Only, as needed Entity Indexes have been identified All lower case names Complete Compare done with previous Production model Singular nouns used (no plural or past tense) English business name Abbreviations not used Both (L/P) - AND/OR - Standard acronyms used (when necessary) Model Special characters not used Model considers usage of third normal form in design Naming standards followed for References & Composites If colors used, there is a legend for color scheme Definition entered Subject Areas used for functional or project categorization Attribute Text Boxes and comments use a standard format layout All lower case names Successful “export” and “import” of model via XML Singular nouns used (no plural or past tense) Metadata Matrix form has been reviewed English business name (consisting of descriptors, followed by a classword) Subject Area Classwords taken from template of logical domains Template Subject Areas have NOT been modified or deleted Abbreviations not used in descriptors Subject Areas added and/or used appropriately for - AND/OR - functional or project categorization Standard acronyms used as needed Special characters not used Website (to be completed by modeler and website Admin) (See the document „Data Model Implementation.doc‟ for further detailed information) Naming standards followed for: Keys, Indicators, Codes, Identifiers, Dates or Timestamps PDF file of model diagram (w/o date) moved to staging Definition entered S2T (source to target) file for model moved to staging New or Existing Source: Existing Logical Datatype Supplemental Documents: No Assigned to every attribute Source Description (required): Source Summary: Datatypes assigned properly for: Indicators, Codes, Dates or Timestamps PDF file of model diagram uploaded to website Keys & Key Groups S2T (source to target) file uploaded to website Primary key has been assigned for every entity All attributes which participate in a key are either part PAGE 42 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ERwin DM – database maps PAGE 43 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • corporate GLOSSARY of acronyms PAGE 44 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • intranet web site using Sharepoint PAGE 45 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • ‘Data Sources’ page for a given Source System PAGE 46 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • integrating technical documents • Business Requirements Document • Data Modeling Checklist • Database Design Spec • ETL Design Spec • Service Delivery Runbook PAGE 47 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • global objects • Model Mart Reports • Data Dictionary Search • Data mining tools Looking for common element names and/or datatypes and/or data values Create reference or cross-reference tables PAGE 48 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • enticement ! PAGE 49 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • user support and support of users• Brown Bag presentations – business unit functionality• Training Sessions - new projects & ongoing courses – in person – video / audio – online• CIA Communications – What’s happening? – How am I impacted? – Questions – call…• User meetings & group discussions PAGE 50 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • examples• Expanding acronyms – CIA = – MOB =• Abbreviations – st_cd CHAR(2) – sta_cd CHAR(2)• Data element value/content – 10 digit ID = PAGE 51 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • examples• Expanding acronyms – CIA = Certified Internal Auditor – MOB = Mobile Browser• Abbreviations – st_cd status code CHAR(2) – sta_cd state code CHAR(2)• Data element value/content – 10 digit ID = SSN + check digit (potential security violation) PAGE 52 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • caveats• Metadata – Data Element Definition – be detailed in your descriptors and be consistent in their use – It’s better to be consistently wrong than inconsistently right – A good example is worth a thousand words… of definition• Models – Normalize the physical data structure and de-normalize the view of that data or create separate (aggregate/composite) physical structures – Create Reference and Cross Reference information that can be shared across models/databases PAGE 53 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • in conclusion • Data and Metadata • Standards and Roadmap • Tools and Usage • Communication PAGE 54 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • Vendor environment / products • Computer Associates – ERwin DM • Embarcadero Technologies – E/R Studio • Axis Software Designs – Data Model Set of Standards • Teradata – MetaSurf and Metadata Services • ASG – Rochade / Enterprise Metadata Repository • Microsoft – MS Excel, MS Word, MS Access, MOSS PAGE 55 © 2010 Wells Fargo Bank, N.A. All rights reserved.
    • Q&A PAGE 56
    • thank you PAGE 57